A rant on UPS on an (not-)delivery. Or why you should avoid it at all costs!

As I reflect on my experience with Gentoo Linux, I have to admit that I've grown increasingly frustrated with the all-encompassing nature of systemd. What was once a convenient and manageable system management tool has morphed into an overbearing behemoth that insists on doing its own thing. I've struggled with the countless issues it's introduced, from resource limits being imposed without warning to logging inconsistencies that leave me questioning what's happening behind the scenes. And let's not forget the constant tweaking required just to keep up with its ever-changing configuration. The final straw came when I found myself wading through a sea of logs and configs to troubleshoot a seemingly trivial issue - only to discover that systemd was hiding the problem from me in the first place. It was a moment of clarity: I'd had enough. I've made the switch, abandoning systemd for a more straightforward alternative. And while it's been a learning curve, I'm eager to enjoy the peace and quiet that comes with system management without this behemoth breathing down my neck.

The author is ranting about the state of modern front-end development, specifically with regards to the over-reliance on bloated libraries and frameworks. They're fed up with having to include unnecessary dependencies just for 3 lines of code, and how this leads to unmaintained libraries, complexity, and a never-ending cycle of upgrades and compatibility issues. They express frustration that developers are not taught efficient programming skills anymore, and that the focus is on using popular "hip" frameworks like React, Vue, or Angular, rather than learning vanilla JavaScript and building UI components from scratch. The author mentions that they've tried to lead teams in their companies to adopt more lightweight approaches, but were met with resistance. They describe how new versions of previously well-established libraries would break existing code, requiring major rewrites or migrations. They also lament the fact that developers are not optimizing for size and speed anymore, citing the example of 11MB (about 13 floppy disks' worth) for a web UI as "normal". In contrast, they mention that their own chat UI uses only 360kB, including other functionality. The author concludes by deciding to take matters into their own hands and investigate the Matrix Protocol SDK to build a lightweight, minimal chat UI from scratch. They express skepticism about the ability of modern front-end developers to create efficient code without relying on bloated libraries. Overall, the author's rant is a passionate plea for a return to more fundamental programming skills and a focus on simplicity, efficiency, and maintainability in software development.

Are websites really looking out for our best interests? Think twice before visiting those websites you love. The truth is, they're more concerned with their bottom line than your security, performance, comfort, and even well-being. From draining your battery to violating GDPR, the list of concerns goes on. It's time to demand better from our online friends. Read the full post to discover how Content Nation can help you take back control and enjoy a better browsing experience without sacrificing your data or wallet.