Therefor if you are not putting human effort on the document it is low-value.

We have seen this before when big data started to be a thing, tons and tons of reports being auto-produced weekly (or even daily), but even if they contain relevant information they are low-value because no one can take action on so much information.

Agents can't look at a large system holistically, guidelines on .md files only go so far.

WASI is a standard on where to poke holes on the sandbox for your specific use-case

WASM+WASI as a compilation target allows any program written for modern operating systems to work on any WASM runtime

https://www.raspberrypi.com/products/compute-module-5/?varia...

I personally worked on a system with raspberry compute modules 3 and 4, the total system cost was in the ~million dollar range. This was definitely a commercial product with dozens of engineers doing R&D, not a hobby project.

We were looking into smaller systems with lower profit margins (~20k USD) and for those we were considering moving away from raspberry CMs because of cost.

The main advantage of the raspberry CM ecosystem is just how widely popular it is and how cheap and available "dev boards" are (just grab a non-CM raspberry and it is almost the same thing). Most of these types of systems don't really have the I/O that makes testing and developing a lot easier.

Being popular is quite important because firmware issues are notoriously expensive to troubleshoot and fix often requiring the manufacturer help. Said manufacturer does not give a damn if you are a low-volume customer. More popular systems have more information available online and are less likely to have bugs (or at least the bugs are known).

I remember one of our other systems bluetooth module had a weird edgecase bug that caused the module to shutdown after several days of it being powered on. It took multiple engineers >1month of work to basically go "yep nothing we can do about this and manufacturer is not helping"

I know they are being used in Ukranian drones and some police-car systems in some cities (although this was hearsay from a coworker and I don't remember the city). But those are just the examples I heard of.

For example a SaaS services that accepts WASM plugins could provide a WASI that lets the plugin write to a object-store filesystem (like AWS S3) provided by the SaaS owner.

1) Replace webhooks in web apps with wasm binaries provided by the customer, but that run in the web app servers.

2) Safer plugin system for professional software (plugins for photoshop, plugins for IDEs, etc)

3) Safer mod system for games and server-side mods that run on the game-maker server.

const nestedDependency = { a: { b: { c: 'c' } } }

useMemo(() => nestedDependency.a.b.c, [nestedDependency])

vs

useMemo(() => nestedDependency.a.b.c, [nestedDependency.a.b.c])

neither triggers react hook lint warnings, although I guess this is more relevant to useEffect than memoization.

Sometimes it takes hours of discussion and tracking down decision-makers just to figure out what the intended behavior is.

I would be interest to hear how it worked out for you.

At some point the market will be saturated with supply and prices will come down for older gen hardware. It can take years though, but it happened to fiber cable and fiber doesn't even depreciate like chips.

The only thing I demand to be fast on my terminal is grep reverse search (ctrl+r) and of course typing a character. But if your terminal can't keep up with your typing speed there is something deeply wrong with it.

Also see this other comment on this thread about this issue:

https://news.ycombinator.com/item?id=48411778

https://en.wikipedia.org/wiki/Snus

It is basically the same thing but not synthetic. Supposedly nicotin pouches are not as harmful because they do not have tobacco leaves.

I am a bit ambivalent about it, on one hand people don't smoke as much because snus which means I don't get as much second hand smoke.

On the other hand it is WAY easier for kids to get started on it as they don't need to hide it after they put it in their mouths. I know a few people who are heavily addicted to it (one even keeps one in when he is sleeping) and they all started in their early teens.

The need for peaker plants to offset the need for batteries is greatly exaggerated. The batteries are mostly required for grid frequency stabilization due to renewal intermittence (clouds passing through, wind slowing down), not so much for overnight storage in most locations.

Of course this varies drastically from place to place, Hawaii for example can't really import energy production from other places.

Vertical indoor farming is far more sustainable than outdoors farming.

It would also push electrifying other types of transportation that is harder to electrify like airplanes and ships. For example, if energy is free flights in smaller electric planes with more connections would be far cheaper than getting direct flights in jets.

Free energy also means cheaper recycling, currently aluminium scrap gets shipped around the world to places that have cheap energy (like iceland with geothermal power) for recycling. With free energy you would be able to do it locally.

In my old place I would often sleep in the living room sofa because of the heat.

It also has a lot of problems with locking files that are open by a process, if you have a rogue process reading your node_modules npm install or rm node_modules can hang until that process finishes.

yarn2 keeps dependencies as tarballs instead of extracting them to disk, imported files get loaded from the tarball at runtime. Makes a massive difference in windows.