eevee
Joined 14 years ago
Joined 14 years ago
I don't understand what "getting their act together" means here, when you're posting it on an announcement that the problem has already been fixed. Should Firefox proactively remove all security features that risk ever posing some modicum of inconvenience to users? Because that would be... all of them.
fwiw, lack of PyPy support is one of the most common reasons I hear for people being leery of Python 3. Of course the people using PyPy aren't the people excited to move to Python 3, if they're effectively mutually exclusive.
You mention C++ as though it worked out great, but C++ is still full of sharp edges and features that interact weirdly with its C legacy, and it has never completely replaced C (especially for libraries). And that's despite having a few advantages that made it possible in the first place, like having a completely different stdlib built on top of the C stdlib, and producing machine code rather than compiling for a VM on the fly.
Which one are you thinking of as the "default"?
Also, this is a thing many people already do, so I'm really advocating that it's fine for them to continue doing it.
Even if you did do that: why would anyone buy it in lieu of the original?
The facts of note seem to be: (1) you are, for whatever reason, in charge of freenode; (2) the very first moment you attempted to make use of that position, you destroyed freenode.
That is a *catastrophic* management failure on your part, and the fact that I haven't seen so much as a "my bad" from you is appalling beyond words. Despite how much you claim to care about freenode, you are clearly more concerned with your own image.