> If it solves concurrency the "right way" due to supervision trees, why not use Python libraries that also implement the actor model, making Python code concurrent the "right way"?
I can't speak too much about Python – but immutable vars is a core prerequisite for many of the features OTP (the platform underpinning Elixir (and Erlang)).
Erlang/Elixir supervision trees also rely on process linking, which is implemented in BEAM and doesn't have a real equivalent in most other language runtimes (modulo some attempts at copying it like Akka, Proto.Actor, etc, but it's fairly uncommon).
Sorry, I should have been more specific. In Europe (or Germany at least) it’s required by law that you provide an imprint with contact information for every site you host, as well as a privacy policy that includes contact information of your GDPR officer if you collect any kind of personalized data. Since I’m a one-person company, that includes my personal phone number since I don’t have a business phone. Also chrome webstore for example requires a phone number if you host an extension on there.
Edit: Also this wasn’t about collecting phone numbers, but about providing one for your business if you host a publically accessible site
There are no occurrences of "cell" or "phone" in GDPR, and the only relevant occurrences of "number" are about "national identification numbers", which phone numbers are not.
The question was 28x though. Not just are you getting more value, but is the value 28 times more. This is not clear, and probably answerable. Health care is very different between now and 1800 (in 1800 your lifespan was measurably better if you didn't go to a doctor ever - this was before handwashing and antibiotics). Even if you compare today, France and the US have many differences in the current system and so you can argue things either way and we learn more about your bias than any truth (there are pros and cons of both systems so all conclusions). Both todays are very different from either in 1800, and we have no way of knowing how either would be different.
I think probably the slaves in 1800, whose experience of the government was its violent enforcement of their sub-human status would probably find the protection of their civil rights in 2024 France to be quite a bit more than 28x as valuable, yes.
I think the women who couldn't independently own property, had no protections against marital rape, being beat by their husbands, or most any other form of abuse would agree that even the comparitively tepid protections offered by modern France are priceless in comparison.
I think children forced to labor without pay, homosexuals forced into hiding, Native Americans kidnapped from their parents and forced into boarding schools, and any number of other now-protected classes would also agree.
Sure, if the government only serves a small fraction of the population at the expense of all others, that small fraction can debateably get comparitively good value. But it sure sucks for literally everyone else.
The end of slavery was really due to slavery being uneconomic. That's why the Northern states didn't have slavery. It would have ended in the South as well, even without the Civil War (which was a kind of big state thing, of course).
Children forced to labour without pay -- also an economic issue.
Even though US is more wealthy than Europe, the average European seems struggling much less than their US counterpart. Just have a look at poverty, homelessness, health figures, even of educated people.
The latest votes, and your comment, only seem to indicate that US people on average find that to be fine enough, the price for a (for me weird) kind of freedom.
Perception is not reality. People complain all the time. People will always spend the most they can get by with. There are people earning $million/year who have less spending money after paying their monthly bills (to spend on things like food) than others living below the poverty line. This is all about how they spend money, the person making $million/year is clearly rich, but if they are still having trouble making ends meet.
Asking the question with the provided data is too simplistic to even argue about.
"Here's the non contextualized percentages, what do you think of the difference between this two percentages which are more than two centuries apart, and from different countries?"
Percentages don't really work like that. 56% of one number isn't 28 times 2% of a different number. And it's not even the right number. GDP measures rate of number flow, not rate of benefit flow, or amount of benefit.
It's also noteworthy how people ask this question about the government but never ask it about private corporations.
We have used that video as an exercise in how not to achieve change. Assuming everyone is acting in good faith, the presenter missed the opportunity to build consensus before the talk, Tsu unwilling to budge a bit, but most of all the moderator unable to prevent the situation from exploding. This could have been handled much better by each of them.
In contrast to the parent: yes, the presenter says „you don’t have to use rust, we are not forcing you“ but he fails to address the concern that a change they introduce would error downstream and someone else had to clean up afterwards.
>In contrast to the parent: yes, the presenter says „you don’t have to use rust, we are not forcing you“ but he fails to address the concern that a change they introduce would error downstream and someone else had to clean up afterwards.
He did not fail to address that concern. And then Ted shouted him down for 2 minutes such that he couldn't get 2 syllables in to respond.
Why would we assume that Ted repeatedly using strawman fallacies, bleating appeals to emotion and acting like a victim...all the while shouting people down...evidence of "acting in good faith"?
When you shout over someone like that you're nothing but a bully.
> he fails to address the concern that a change they introduce would error downstream and someone else had to clean up afterwards.
Because that "concern" was a strawman. It demonstrated that Ted either did not understand what the presenters were asking for, or simply didn't like others asking him to do something, because he's very important and nobody tells him what to do.
As has been exhaustively explained by others in previous HN threads and elsewhere: the Rust developers were asking to be informed of changes so that Rust developers could update their code to accommodate the change.
Ted loses his shit and starts shouting nonsense about others forcing people to learn Rust, and so on.
> but most of all the moderator unable to prevent the situation from exploding
When someone is being abusive to others, the issue is never "the people on the receiving end are not handling it as best they can."
Further: did it occur to you that Ted's infamous short temper, and his "status" as a senior kernel developer, might be why the moderator was hesitating to respond?
Imagine how Ted would have reacted if he was told to speak respectfully, lower his voice, and stop talking over others. Imagine how the army of nerds who think Ted's behavior was acceptable or understandable.
I don't understand how abusive bullies like Ted are allowed the privilege of being a senior kernel developer. This feels, in the end, like the fault of Linus, for allowing abusive maintainers to maintain their grip.
Linus was the original abusive bully maintainer, that's how. He's improved his personal use of language, but the culture that he initiated continues unabated. Linux's existing success as a project is used as evidence that it doesn't need any changes to the kernel maintainers' culture.
> As has been exhaustively explained by others in previous HN threads and elsewhere: the Rust developers were asking to be informed of changes so that Rust developers could update their code to accommodate the change.
I don't understand why you don't see this as "a really big deal". The C developers make a breaking change. They fix all the C code, then they write an email to the Rust devs explaining the changes.
Then the process of making the change stops, and the C devs have to wait for a Rust dev to read the email, review the C changes, fix and test the resulting rust, and check in the update. (including any review process there is on the rust side.)
Is it hours, days, or weeks? Are there 2 people that know and can fix the code, or are there 100's. Do the C devs have visibility into the Rust org to know its being well run and risks are mitigated?
This is adding a hard dependency on a third party organization.
I would never dream of introducing this kind of dependency in my company or code.
This is kernel development we're talking about. It progresses carefully, not a the breakneck pace of a continuous integration SaaS platform that is single-minded about pushing features out as quickly as possible.
A better analogy would be like an API inside of a monolithic app that has multiple consumers on different teams. One team consumes the API and wants to be notified of breaking changes. The other team says "Nah, too much work" and wants to be able to break the API without worrying about consequences.
If having multiple consumers of an API or interface is a goal, you make communication a priority.
If not Europeans, who elects the officials in EU that determine energy policy? Also, your graph shows a substantial decrease in domestic energy production.
If Germans want cheaper energy their only option is to elect other politicians. It's the same problem in Norway. People vote for politicians who do everything they can to increase the price, and then they whine that inflation is sky high. You get what you vote for in a Democracy.
More of a tool that exists for 15 years or more, and is an important tool for some of us. When my mac broke down in, hmm, maybe 2010-ish, my superduper-created bootable clone allowed me to instantly continue my work on a freshly bought mac (just boot from the clone). No Apple utilities give you that.
unless i miss something this should not be an issue. the lexer could parse if as an IF token, and the parser could treat tags as STRING || IF ( || other keywords… )
That seems like it'd get really awkward pretty quickly. "if" isn't unique in this regard; there are about a hundred shell builtins, and all of them can be used as an argument to a command. (For example, "echo then complete command while true history" is a valid shell command consisting entirely of names of builtins, and the only keyword in it is the leading "echo".)
The problem lies with shells extensive usage of barewords. If you could eliminate the requirement for any bareword to be treated as a string then parsing shell code would then become much simpler...but also few people would want to use it because nobody wants to write the following in their interactive shell:
- a oneliner over the video that explains what you are doing would be helpful,
- and then "If you don't know what mutation testing is, you must be living under a rock! " brings people away from your repo faster than you can look the other side.
I can't speak too much about Python – but immutable vars is a core prerequisite for many of the features OTP (the platform underpinning Elixir (and Erlang)).