The biggest downside of this product is Windows

The second biggest is Microsoft's track record with hardware

It would be nice to have a signal as a warning to process to reduce it's memory footprint or else OOM will kill it.

You still need some way to make the kernel to send those signals to the processes of your choosing. If the kernel decides to send SIGLOWMEM to xlock instead of firefox, the xlock will get killed because it really doesn't have any memory it can give up.

It’s possible via cgroups, kinda.

cgroups v1 has a pretty nice API but it requires root. V2 does not require root but it’s a lot coarser and not as simple or reliable: https://unix.stackexchange.com/questions/753929/receive-a-me...

Looking at how GPU development has been sidetracked for NPU, I worry that this is 2035 target at best. Manufacturers will push for maximising matrix operation silicon area. In the era of trillion dollar investments into datacenters, traffic cost is afterthought. The only benefitors might be YouTube, Netflix and such, but on their scale investment into ISP level caches might be cheaper.

I used to love react of old with redux/flux and little to no hooks and weird side effects. It had super sound software design at the cost of being bulky.

I think we should return back to that with the era of LLMs. We don't write the code anyway. Let's use reducers and fully event sourced states.

I don't believe there was an era in history more DEI accepting than nowadays.

What is the point of this comment? Do you mean to say we should cease the pursuit of DEI because we've "come so far"? Of course that's engaging with you with the assumption that you're not intentionally ignoring the weaponization of the movement in the US to further the goals of the current administration.

That would be a strawman. I am not living in US and don't care about US politics other than they are rising my diesel prices.

I'm just pointing out that historically this is the most DEI friendly we have ever been. If americans would be able to see outside a 4 year election cycle and realise there is a whole world outside the TDS zone, we could have a more civilised conversation than throwing strawmans around.

I'm not refuting what you said, I'm asking you to elaborate why you said it.

Because I feel like it's unappreciative to act like we didn't make any progress. It's really degrading to people that really did put in an effort (like myself). It's like comming to a celebration of a sport victory with "you could have done better" attitude.

So let's now focus on why you assumed a hidden meaning somehow connected to "current administration"? Why this knee jerk reaction?

We used it for payment processing. We got huge CSVs from various APIs and used string decimals for computing to avoid overflows/underflows and rounding errors.

This the most hackernews post I've ever seen. Doing something in 50 hours that could have taken 20 minutes because vibe.

I love it.

The peak irony is that most of us work in a field that exists so that people don't need to do that stuff for 50 hours.

Car engine turbo? Can I get a photo of that packing?

Turbos for typical car engines aren't huge - roughly the size of a medium melon, give or take.

I just find the picture of turbo tucked between shirts and pants in a holiday suitcase hilarious

I admire your work, but at the same time I have to ask: Why?

Why not?

You may be in the wrong place

Memory management is pain. If you want to optimize, you're forced to 4k pages. Runtimes are fragmented. Wasi is a mess. Async and threading is awkward. Whenever you need to integrate with hardware you need platform specific adapters.

In practice, whenever you need more than a singlethreaded app with http/serial port, the "run everywhere" breaks.

Don't get me wrong I love WASM but we're not there yet