HN user

ncake

70 karma
Posts1
Comments16
View on HN

I've been using Raspberry Pi 400 as the main desktop for a few months. The idea was that I'd be more productive without youtube and games. That's not as extreme as the OP setup, but the slowdown and freezes unfortunately outweigh the focus benefits.

Hutter Prize 4 years ago

"The organizers believe that text compression and AI are equivalent problems."

Are they? Not only interfacing with human-readable media is half of the story, optimizing for size isn't the same as optimizing for context.

If this is a US-only service, it should say so on the website somewhere.

I've also had this experience with e.g. Betterment and Wealthfront. The only way to find out they're US-only is halfway through sign up process, not even anywhere in FAQ's.

C Package Manager 4 years ago

I use CMake's FetchContent. It's probably the most universal solution for this out there.

I'll try to explain what I mean. Suppose you want an in game character to change the displayed weapon in their inventory.

Stateful way: your Inventory Manager component iterates through its private array of item entities to mark their model components as shown or hidden, then calls the dependency injected character's avatar component to update its animation state.

Stateless way: you flip an integer in character's struct, and the rendering function does something different.

It is a very good library, especially for 2d games. ..Just not 100% production-ready out of the box. Some features are lacking (e.g. no stereo audio) or oddly implemented. (e.g. rlgl primitive-dependent texturing)

In my brief experience in front-end, I've encountered weird Safari bugs on every single project.

In one case the code failed because the form object there doesn't implement the method to validate and submit. In another, it wasn't sending a form field if it was styled with "display: none;" (had to change to "left: -9999px;"). In another, playing a non-muted video would error out some of the time, if clicking an element wasn't recognized as a user event. In yet another, the mobile version refused to center text inside <button> no matter what. And so on.