That’s exciting! Is there a summary of what’s new in 1.0 somewhere? Usually the version announcements contain an overview of the most important changes, but this one is more of a retrospective and general overview apparently.
You could still move e.g. /nix to the BTRFS disks and only keep /boot on the thumb drive, no? That’s more or less how I have NixOS set up with ZFS. But your solution is of course much fancier :D
Could you share more about your NixOS setup, or good resources? Genuinely curious as I’m looking into building a small, low-budget Plex server running NixOS :)
I’d love for Purism to succeed and they appear to be doing a lot of valuable work in the software space, but I can’t help feeling like that 75M self-assessed valuation is a bit on the optimistic side…
I’m not sure about these stable packages, but for the nightly packages they introduced recently they explicitly mention on [1] that you can keep browsing:
> Following community discussions, we have updated the post to highlight that Firefox can continue browsing after an APT upgrade, allowing people to restart at their convenience.
Oh, that's great! Between that very clear statement and the fact that in this post they call out that "you will still need to restart Firefox for the latest version", it sounds like they've finally fixed it!
From what I can tell, the “Ubuntu Mozilla Team” does not consist of people from Mozilla but rather just people packaging Mozilla software for Ubuntu. The latest packages in that PPA have been uploaded by Rico Tzschichholz, who does not appear to be affiliated with Mozilla.
I’m continuously impressed by the care and effort that goes into the developer experience of Elixir. Those improvements of the (already pretty great) documentation and the error messages look like they will make a real difference.
The way I see it, the problem is the C in CSS. If you rely on `.author-bio > h2`, then every time you make a change to `.author-bio`, you have to consider all the contexts in which this class may be used globally in your site, and if you change the styles for `h2` even more so. Sure you can say you encapsulate every context with a globally unique id, but since you’re probably already using some kind of templating system for you HTML, it’s easier to specify the styles there. It’s basically the difference between having variables scoped global vs. local by default.
The « > » part should not be necessary 90% of the time.
And while using Tailwind, I still have to know where I include my components. I still need to test different instances in different places.
With that in mind, I don't see the added benefit of Tailwind here (again, other than limiting the damage done by careless devs). Maybe I'm missing something?