It's doubly dismaying that my own country (US) is still doubling down on fossil fuels despite everything.

The concern about a new dependency on China is real, but renewables do have the advantage that once you have the infrastructure in place it keeps working without continuously importing fuel. Nonetheless, China has done a good job building up their PV/battery manufacturing capacity (including via subsidies for a while if I'm not mistaken) and to the extent the rest of the world wants to avoid a dependency on them we should do that too.

The RAM shortage is only starting to hit but I think this could potentially start to be more appealing if it lasts too long and gets too bad.

(Honestly I can't see Apple doing that either though since it'd cannibalize their other product lines. But c'mon, Apple!)

I think my brain naturally wants to think about things in terms of sending messages between smaller components of a program, so Goblins fits the way I think very well. It's also what introduced me to object-capability security, which is a lot more brain-bendy when you're first trying to understand it, but after a lot of reading and playing with Goblins I find myself wishing many more things used ocaps. :)

He posted on the list recently too if folks were worried: https://groups.google.com/g/cap-talk/c/XCBwf-zpJWA/m/6CWsNA-...

The integration isn't perfect (some important things like forwarding notifications to the host system are still missing) but it's already further along than you might have imagined.

There seems to be a Windows-only update tool available that might fix it, but that's rather inconvenient when it's used as a server running Linux! No update available as a standalone boot disk or via LVFS. So I haven't gotten it fixed yet because doing so involves getting a second SSD, taking my server offline to install Windows on it, just to run a firmware update.

If the design speed of your roads is a safe speed for those around you then yeah that works perfectly.

Comments URL: https://news.ycombinator.com/item?id=45387509

Points: 8

# Comments: 2

The value of a bike lane isn't in the lane in isolation, in the same way that the value of a street isn't in that street alone. It's in the ability of that lane/street to get you where you need or want to go.

Lavamoat would, if you get to the point of running your program with lavamoat-node or built with the lavamoat webpack plugin: https://lavamoat.github.io/guides/getting-started/

I think I need to read up more on how to deal with (avoiding) changes to your public APIs when doing dependency injection, because that seems like basically what you're doing in a capability-based module system. I feel like there has to be some way to make such a system more ergonomic and make the common case of e.g. "I just want to give this thing the ability to make any HTTP request" easy, while still allowing for flexibility if you want to lock that down more.

This also means that it's trivial to install a patched version of a package through the same package manager as everything else. No dedicated build infra required (though of course if you're deploying to a large fleet you may want to set up some build servers to avoid the need for rebuilds on most machines).

OEMs and SoC manufacturers have been getting better about upstreaming stuff recently from what I've heard (thank you Qualcomm!), but as far as stock OS images go I wouldn't expect manufacturers to support them for one moment longer than they have to.

This is part of why efforts like PostmarketOS are so helpful. Ironically, if this was an even older Pixel 3a, you could run it with modern software: https://wiki.postmarketos.org/wiki/Google_Pixel_3a_(google-s...