stochastictrebuchet

It all started with that damn gorilla

I’m OOTL. Are these actual issues people have with the project?

C++ might not be as memory-safe as Rust, but let’s not pretend a Rust code base wouldn’t be riddled with raw pointers.

BSD tells me the team probably wants Ladybird to become not just a standalone browser but also a new competing base for others to build a browser on top of – a Chromium competitor. Even though BSD wouldn’t force downstream projects to contribute back upstream, they probably would, since that’s far less resource-intensive than maintaining a fork. (Source: me, who works on proprietary software, can’t use GPL stuff, but contributes back to my open-source dependencies.)

Word to the wise: stay away from productivity bro YouTube. You’ll learn a hundred systems for optimizing your obsidian-logseq-roam-notion hybrid gsd-kanban workflow with bidirectional zettl references and interstitial notes organized into a beautiful para system with more systems on systems and queryable data views and more fancy shit than you could ever dream of, and when everything is done and set up the way you think will work for you (which it won’t)…

… you’ll realize you haven’t actually accomplished what you were meant to.

(Source: myself, who’s fallen into the rabbit hole once or twice before)

Well-deserved win! Watched this in the cinema a few weeks back. What immediately struck me about the beautiful art style is that it felt more like what you’d expect from a labor-of-love indie game than from a dreamworks/pixar studio – and it was incredibly refreshing! Also, for a movie where water plays a big role, the fluid rendering was absolutely breathtaking. I could almost smell the warm plastic air of a GPU giving its all.