No. I've been reading your activity on Lobsters and in the Spanish Emacs Telegram group. You were banned in Lobsters primarily because you're a spammer. You don't interact with the community unless it is about something you did or a post you wrote. That behavior is not allowed on Lobsters and I agree with the rule. You said you "found a bug to allow posting" after the first ban. That also goes against the rules.
It's very strange of you because on your blog you're constantly talking about creating communities and then, you disrespect and fail to engage in communities not created by you.
The Adamuz train crash was a maintenance issue, or lack of checks after the maintenance jobs, as some sources say that part of the line was very recently renewed. Today's crash seems to be a human failure from ADIF train control.
This one is the kind of thing that's not supposed to be able to even happen (one train running into the back of another) if positive train control is implemented properly.
People rag on the USA refusing to allow higher speeds without PTC but their system is very simple and it works (it throws the train into emergency if it passes a red signal by physically knocking out the air).
Exactly, this can't happen. You need to put measures on this.
Both the maintenance issue and bad systems that lead to human error creating this crash need to be taken responsability by the public system and fix them.
Apparently they have the automated systems, but they were not working, so they were under human operating rules.
Which, in the USA at least, severely limits speed you're allowed to use (because once the only thing between you and gory death is a human, eventually that human makes a mistake).
They told the train to drive "as normal". This was a controller mistake as the procedure says they could only drive in visual/slow mode.
Same mistake was made with other train and the driver replied that that was not allowed, and the operator corrected accordingly. But the driver of the train that crashed didn't raise the issue.
As it looks now the controller made a mistake when taking over manual control of the segment after systems failure ("continue as normal" vs "continue slow"). The train driver probably should have also known they should not drive at normal speed without safeties in the segment, but I guess they trusted control had cleared previous trains.
Between 10-20 minutes control room did not realize a train was approaching an occupied section where the other train was holding on a red track signal.
Human error but signals serious deficiencies at protocol, oversight etc. In control room.
I've always thought that a train lacking PTC on the rails should be able to "deploy" a small car-sized thing that runs ahead of it at the same speed but 2x current stopping distance away from the locomotive - if it stops communicating or detects any anomalies the train goes into emergency.
People rag on the USA refusing to allow higher speeds without PTC
Who does this? The US barely has PTC because freight companies continue to fight it tooth and nail. You only need to look at the Amtrak Cascades crash to see how subpar even modern rail infrastructure is in the US. Neither is PTC a panacea as anyone who is old enough to remember when Thales' craptastic train control system sent a Muni train the wrong way down the wrong tracks in San Francisco.
There are definitely groups of people who hate the limited speeds of Amtrak, especially in the southwest corridor (the trains Amtrak runs there are capable of "technically high-speed (120 mph)" but can't do it because the freights haven't paid for the rails to be upgraded.
Everyone wants PTC installed, nobody wants to pay for it. Amtrak wants the railroads to pay for it. The railroads don't care about it because they run 50 MPH or less freights, so they want the government to pay for it. The government has no funding and wants Amtrak to pay for it. Amtrak reminds the government that Amtrak is just the government with a bad wig on, and the cycle continues.
And California keeps trying to build a high-speed rail for infinity billion dollars when the cost to PTC the entire LOSSAN corridor is only $250-500 million (and many agencies have done parts of it themselves already).
The state of US rail is entirely due to nobody actually giving a shit and there not being a central authority powerful enough to force it thought (because nobody gives a shit). Kind of the story of the USA in general.
The human failure appears to be mistake number 3 or 4.
1. Automated system fails
2. Decision is made to run the system manually
3. Iyro train fails to move on when instructed (Comms failure?, train failure?)
4. Controller uses imprecise language when instructing following train.
To say this is totally down to 4 is to scapegoat the last link in the chain.
PS2 can also be jailbroken with Yabasic, another BASIC interpreter, which was given for free in some consoles in Europe. But typing the exploit isn't very practical compared to other methods (and this exploit was found out later)
glfw is smaller and more focused (SDL adds a TON of stuff, including even its own GPU abstraction API) so the choice was most likely made because of that focus.
Yes! I've never been against languages with batteries included. In fact nowadays I prefer them. It's one of my biggest issues with Rust, but the problem also exists in Haskell. Funnily enough, in Node.js, which gave birth to npm, you can now do many stuff without external dependencies (last one I've seen are the sqlite functions).
But yes, in languages with batteries included sometimes they feel like an afterthought. It's not just Python. Java also used to have a big standard library, with many useful things including GUI programming which has been neglected a little bit.
The trick is, when shipping a new language having a batteries-included std lib is hard to do: what should you select, what is considered good (enough), how much time do you spent on it. This detracts from what most languages try to be. An exploration in novel language/compiler paradigms.
With node, what happened is that it was left to the ecosystem to grow good packages/batteries. Same with golang (see the uuid lib example from 1.27 the other day).
To bridge the gap you could have the language/platform declare some “blessed packages” or even “blessed packages and their versions for each release of the language”.
We had both depending on the school and sometimes even the teacher. fx-9750G and GII didn't support assembly programming... unless you used an undocumented procedure to flash them with unsupported firmware from a different calculator model...
We were specifically told to buy TI-84 Plus. Also, there was a list of specific brands and specific models that were approved for use on math exams.
If someone wanted to use a Casio instead, they could. But the teachers also said that if you buy a different brand and model other than TI-84 Plus, you are on your own to figure out how to use it for all the different things we needed graphing calculators for.
Everyone in my class did the sensible thing given that they told us this, and bought the TI-84 Plus. There was no reason to buy a different one when our classes assumed the TI-84 Plus. Only making extra problems for oneself.
It's very strange of you because on your blog you're constantly talking about creating communities and then, you disrespect and fail to engage in communities not created by you.