Where I live (Belgium) waste collectors pick up "rest" waste in relatively expensive trash bags weekly, PMD (plastic/metal/drink cartons) weekly, compostable waste every two weeks, cardboard monthly, and glass also monthly. Certain things we have to bring ourselves to a collection point (batteries) or recycling park where everything gets sorted even more specifically. I tend to go to the recycling park once every two or three months, the rest gets collected at home.
So the stuff they collect doesn't need 12 different kinds of bags/bins, and the (financial) incentives are correctly aligned. I think it's a good system and pretty convenient, but I'd wish they recycle & process the waste even better afterwards. But the hardest part – getting the population on board – seems to be well-established.
Recycling is difficult, some materials are relatively easy (aluminium cans, steel), some not so much (plastics f.e. tend to degrade, some materials are energy intensive to recover). Contaminants are a major issue that still need more public awareness. But we're going in the right direction.
This is really cool, I've been looking for an AOT compiler for ruby for a long time.
The lack of eval/meta-programming fallbacks is a shame though, but I guess they kept the focus on a small, performant subset.
It would be nice to have gems compiled with this AOT compiler that can interact well with MRI.
When it comes to packaging/bundling more standard ruby (including gems) we'll still need tebako, kompo, ocran – and then there's a bunch of older projects that did similar things too like ruby-packer, traveling ruby, jruby warbler etc.
It's nice to have another option, but still, I'm hoping for a more definitive solution with better developer UX.
To a degree, yes, but I was thinking something in the line of a commonly agreed on file format that defines a default style. To be used by libraries like charm, ratatui, tty, heck maybe even older ones like libnewt etc.
A bit like base16 but with more definitions and better semantics.
Looks great, I'm definitely going to have a look at it.
Off-topic: it'd be nice to have a configuration spec to define the look (and maybe even the behaviour) of the different CLI & TUI libraries out there. For things like colours/borders/corners/shadows/scroll- & progressbars etc.
Right now every library does its own thing, which can be quite jarring when using different apps.
I want to like framework, but whenever I've seen one of them in person I was pretty disappointed about the case/chassis. And the touchpad.
For me personally, weight doesn't matter that much, and neither does configurability (I guess by now they have data on the most popular port choices for example).
But size (as small/minimal as possible for a given screen and keyboard size – minimal bezels for both) and strength (no flex, solid hinge) do matter to me.
I understand these two things conflict with themselves, and with the framework's repairability and configurability.
Still, I'd like to see some true innovation there. I'm just afraid they painted themselves into a corner with their current mainboard design, and won't be able to diverge from that to bring us something truly solid yet compact and repairable.
I was hoping to use bcachefs to have one pool with subvolumes for root (encrypted by tpm), and for the home folders (also encrypted but with different keys, for example for systemd-homed use).
Any chance for different encryption keys per subvolume?
> I'd also really like to see affirmations that Matter is usable sans any big network, sans Google Apple and whomever else. That it really is something we can run ourselves.
I'm using Matter (over Thread, mostly) with Home Assistant – in addition to using it with Apple HomeKit, but I could have done it exclusively HA. My devices get an IPv6 ULA from the border router, HA can directly talk to them without any internet or cloud involved. Does this qualify?
It's true that certain non-standardized features are only available through "extensions" ie. the device vendor app. But both Thread and Matter get new revisions, and the devices get firmware updates in a standard way (again, installable via Home Assistant) to take advantage of new features and stability updates. All of this has gotten better with time.
But the best thing about Matter is that I'm not locked into a specific ecosystem or dependent on an app from the device vendor. So, in my view it has been a slow start but with steady improvement. And the right direction IMHO.
This is why Debian users should use apt-listchanges to display the latest NEWS.Debian items on upgrade.
I wouldn't expect to see all the important news of the tens of thousands of packages I don't have installed in the release notes.
I was hit by this using unstable (before they made a NEWS item), but when upgrading my stable machines to trixie I got a proper warning/reminder of this specific thing.
So the stuff they collect doesn't need 12 different kinds of bags/bins, and the (financial) incentives are correctly aligned. I think it's a good system and pretty convenient, but I'd wish they recycle & process the waste even better afterwards. But the hardest part – getting the population on board – seems to be well-established.
Recycling is difficult, some materials are relatively easy (aluminium cans, steel), some not so much (plastics f.e. tend to degrade, some materials are energy intensive to recover). Contaminants are a major issue that still need more public awareness. But we're going in the right direction.