@Captain said in Idiots make their build process reliant on someone else's server, bitch when it goes down:
@WPT What is this left-pad thing?
TLDR version: NPM created a broken system that doesn't track dependencies properly. Some developer removed something from NPM that lots of people were using. A bunch of idiots across the Web then proceeded to blame him for the mess, rather than the people who built NPM.
It's not like this is a difficult thing to get right, either. Store your package dependencies in a relational database, set one single (very obvious) foreign key, and referential integrity automagically takes care of the entire thing for you. It would have been impossible to remove a package out from under the zillions of people who were using it. This has been a well-known, solid principle for decades. But apparently the people who built NPM were too trendy to use well-proven technology like that...
@ASheridan said in Idiots make their build process reliant on someone else's server, bitch when it goes down:
Aren't you getting C# and the .Net framework confused there? It's the .Net framework which has recently been open sourced, I was under the impression that C# as a language was always open.
A language is generally defined by two things: the compiler and the standard library. The .NET Framework is a bit of a unique beast here, as it's the standard library for multiple different languages. It's currently in the process of transitioning to open-source, although it's been "source-available" for many years now in the form of Reference Source.
As for the C# compiler, it was proprietary for a long time before being released as the open-source Roslyn version. IIRC this actually happened before the .NET Framework's transition to open-source even began.
@blakeyrat said in Idiots make their build process reliant on someone else's server, bitch when it goes down:
Right; but since there's no central control of it, it's extremely low-quality. It's huge in that "there's 57 implementations of an XML serializer", but that's no fucking good when 53 of those don't work and of the 4 that do, 2 of them don't understand XSD and can't validate and the third one only works on objects created on Tuesdays.
Sorry, hard to have any sympathy here. If you are trying to use XML for anything non-trivial, that's your own fault and you absolutely deserve all of the pain that it brings upon you.
Some people, when presented with a problem, think “I know, I’ll use XML.”
<Problem:Worsening> <Problem:TimeDescription>Now</Problem:TimeDescription> <Problem:Posessive>they have</Problem:Posessive> <Problem:Quantity>many, many</Problem:Quantity> <Problem:WorseningDescription>more problems</Problem:WorseningDescription> </ProblemWorsening>
@ASheridan said in Idiots make their build process reliant on someone else's server, bitch when it goes down:
So what you're saying there is, C# the actual language, was always open source. Glad you agree with me.
No, he's saying that the specification was open. But the actual source code (you know, the thing that puts the "source" in "open source") was never open until just recently.
Ugh, why do you have to be so obnoxiously wrongheaded that you put me in a position of agreeing with Blakeyrat?!?