Within BEAM itself there’s no priority mechanism, however, on a RPi3 or BeagleBone you could get about an 200 uS average response time to GPIO on Linux, even under moderate load. The jitter was pretty low too, like 10-20 uS on average, but the 99.9% tail latencies could get up to hundreds of millis.
That’s fine for many use cases. Still I now prefer programming on esp32’s with Nim for anything realtime. Imperative programming just makes handling arrays easier. Just wish FreeRTOS tasks had error handling akin to OTP supervisors.
Now Beam/Elixir would be amazing for something like HomeAssistant or large networked control systems.
As of OTP 28 there's also priority messaging that a process can opt in to. Not really related, but it's new and interesting to note.
They have a different definition of "no culinary use" than I do!
I am curious what items in the list differ for you. When's the last time you grabbed your isolated fructose and maltodextrin to season your steak?
The way I think of it is if I were to cook a chicken breast or bake a loaf of bread and then write down the ingredients, they'd be chicken, oil, salt, pepper; or flour, water, yeast, salt. Now go look at the ingredients of a chicken breast (raw, marinated, or cooked) and a loaf of bread in the grocery store and note the differences between the ingredient list. If the ingredient list for an item from the store includes things a household wouldn't have at home, like fructose or maltodextrin, that item would be considered ultra processed.
I'll note that I don't eat as healthy as I should, people should do what they want, and it's possible to still be unhealthy while avoiding ultra processed foods.
Where's the line drawn, is ground beef ultra processed or not? how about a chicken schnitzel? canned sardines? dark chocolate?
Which part of the ultra-processing is making the foot unhealthy, is it chemicals they add? the fact that they heat it up (but at home when you cook you also heat up stuff)? something else they do with it?
If you bake fries yourself from potatoes with olive oil, is it ultra processed?
Bugs in understanding. Bugs in good taste.
A roach in your soup is a bug, even if the recipe says it should be there.
Similarly, as long as the mental model of a Python programmer is in line with the results of executing some computation with Python, all is well.
It's these quirky little things where the code doesn't exactly represent the way execution happens in most straightforward mental models of how execution works. Again, it's not bad and it's not unique to Python. It's just the nitty gritty of how some things work.
I will say that calling it "What The Fuck Python" is certainly more attention-grabbing than "Some Interesting Bits About Python Internals You Probably Don't Need To Know". What're you gonna do. :)
I don't feel strongly about Python, but I do think CPython is a great way for people to learn a bit about how interpreted languages work. The code is quite easy to understand, and you can easily play with these interesting aspects of how languages and runtimes work. Does every Python programmer need to know the difference between `a = 256` and `a = 257`? No. Is it interesting? Yes. Should someone on your team know? Probably.
There's a lot of interesting stuff here. Understanding the difference between the conceptual idea of each line of code and what actually happens is fun, and, in some cases, important.
Also tried SvelteKit (with Svelte 4) which was quiet nice but it completely misbehave in production with a lot of corner-case bugs that were not reproducable in development and I abandoned it for good. Didn't the creator of Svelte even joined Vercel? They seem to want to "unite" all the JS frameworks "under one roof" which I find a bit... disturbing?
If we want open source to be viable we have to support actually having businesses around it. Vercel making it easy to deploy to their servers seems like a fairly decent business model compared to some of the other options.
I don't claim to know their plans. I've never been in charge of a multibillion dollar company. I just think I have a vague idea of what their general strategy is, and I don't love it.
I'll also say that I definitely want open source projects to succeed. I don't know how they can in a great way in a capitalist system. So maybe this is, from my standpoint, the best of a bad situation. I still think it's worth pointing out and paying attention to from a free software and business position.
Also just want to say thanks for what seems to be a genuine discussion in good faith.
A much milder, and more sensible, expression of your underlying sentiment is:
If an activity becomes this essential, the government should provide a competitive entrant in the same field.
Now the incumbent provider has competition, and there is a market participant tied to other incentives, etc.
No theft necessary.
It just seems like the government entity would need to actively engage with seeking profits or just existing to artificially lower costs. I don't think the majority of people would want the government to have a for-profit arm that exists to compete with businesses, and I don't think corporations would just play nice.
I'd say that USPS is the closest example of this, and it's a pretty good example of how things can go wrong as well. The active attack against the postal service to try to privatize it is terrible. It will do nothing but continue to isolate power to the ultra wealthy and make people's lives worse. For-profit corporations and the government just have (or ought to have) fundamentally different incentives to exist.
I'd be curious to know of any examples of this working well. I don't mean to be so antagonistic, I just am really struggling to understand how this could work in any way.