This reminds me the blog one would write around 2006. Not the text content, but the pixelated font and pictures of winamp wibe like that.
Myself, I am rather happily using mplayer - without any gui. Initially it was practicality of not leaking memory - like many gtk+ apps would do. Now, it is pure utility.
Like journalists who retain the copyright on their articles.
This is also a reason lots of decent open source code comes out of the media industry. As much as we despise the media for its effect on society, journalists are much better than software developers in enforcing their worldview on others.
I have built my web scraping system ( https://awesomegoat.com ) on Ruby on Rails. And while I spent this Christmas-break exploring Elixir/Phoenix, I am so far staying with Ruby on Rails.
While it seems I could have built a slightly more (CPU & memory) efficient system in elixir, I am afraid the development of new features would be a bit slower and my time is more precious than the machine's.
Also, CPU & memory are likely not the constraints in the scraping exercise. What you will likely find later on that you will get blocked by Cloudflare on week 2 and superb backend won't make a difference.
Today, I woke up feeling that elixir/phoenix is the best platform for rewrites.
I mean, when you know the problem domain well, you can build a master piece in elixir/phoenix. I still feel that putting together the first prototype has to be faster in ruby on rails.
It's quite ironic, or rather unfortunate, that recently we're seeing the opposite problem in the Elixir community.
A lot of the big famous companies used in case studies about how Elixir and Phoenix are amazing, save money, save resources, save development time etc. are starting to abandon the stack for technically worse solutions. And for no good reason other than coming from management it seems.
I agree that it's a great platform for rewrites in that once you have a working solution, and you know the bottlenecks, then you understand how to break it up to make it concurrent, parallel and distributed with minimal effort.
I also think that it's a great prototype language too, though. You can get up and running just as fast as Ruby on Rails for like 99% of projects. Or at least used to be able to. I have a rant about the last five years of Phoenix churn being responsible for the low adoption of Elixir but that's for another day.
I was always afraid to use on of these. I thought that the css selectors would be too brittle and ultimately break.
I have build my own solution that is automagical at https://awesomegoat.com/ but I am running into next set of issues which are various scraping protections. It seems that reasonable RSS gateway today needs to include botnet of residential proxies just to read content on the internet.
This is a different kind of sandbox. BPF functions by drastically limiting the shape of the control flow graph that will be accepted for a program; most working C functions will not be accepted in a BPF program. The simplest example (complexified by more recent BPF verifier work that relaxes this... somewhat) is that BPF programs can't have loops, at least in the sense that a normal program can.
You can crash a kernel with a BPF program. But it's overwhelmingly likely that the crash will arise from buggy pre-existing kernel code that just hadn't been seriously exercised before eBPF gave people new tools to push that code with. What's much, much less likely to happen is a segfault or NPE in your own BPF code.
I'm only aware of drivers, which were not sandboxed due to the nature of drivers (at least in late 90ties there was pobably not much of abstraction on that level, kernel features, hardware features available?)
More spiritual society is the less stuff it needs to amass.
One of the theories goes that ancient civilizations made progress in non material domains. How else would you explain these thousands years long periods in the history when a table or a spoon looked the same. And nothing visible happened?
Are you just neglecting all the human suffering, pain, and death that was occurring in that nothing visible happening moment? History looks a lot different when you just ignore the parts you don't like.
IIRC, Patternfly started many years ago, because many open source project (of Red Hat interest), had inconsistent ui. The idea was to develop a common guideline that other open source projects could use and be somewhat consistent with each other. To have a framework, artwork and guidelines that would be available on permissive terms forever.
Myself, I am rather happily using mplayer - without any gui. Initially it was practicality of not leaking memory - like many gtk+ apps would do. Now, it is pure utility.