plugnburn

I also don't get why are you still using those miles and pounds when the rest of the world agreed on kilometres and kilograms.

I don't get neither how thousands separator is useful, nor what a "genius" came up with an idea to make comma a decimal separator in computers. I have nothing against either of these things in handwriting (though I personally never separate thousands), but in computing?..

I agree though that this can (and should) be solved at font-rendering level, not at an application level.

I think you miss the point. When CP1251, KOI8-R and other crazy imcompatible things came around, they came around because there was a need: ASCII didn't provide a necessary character set. Now when we have Unicode that embodies virtually all character sets existing on Earth, we don't _really_ need either non-Unicode encodings, or even fixed-byte UTF versions. So a move to any hypothetical FutureText-64 will actually give no practical gain, unlike a move from single-byters to, for example, UCS-2 and then from UCS-2 to UTF-8.

But my main point is another: eliminate all single-byter and fixed-byter zoo and leave one universal encoding. When (if ever) it's time to replace it, we'll do it all and at once, not having those crazy iconvs everywhere.

I second this. JQuery must die.

Some masochist M$-fan could invent even this just in order to justify the difference from civilized world.

> And in 20-30 years we'll likely be saying the same about UTF-8.

Well... If we will, why not? But the thing is that in 20-30 years we won't be able to invent any new writing systems that UTF-8 won't cover. Single-byte encodings were doomed because of their single-byteness. The same awaits two-byte encodings like UCS-2 (aka UTF-16BE) - we already have extended code points for something that glamour hipsters call "emoji". Variable-byte encoding will never become obsolete.

Because, you see, not everyone in the world uses Latin characters. UTF-8 must become a new standard instead of that whole obsolete encoding zoo.

Without. BOM (when used for UTF-8) is an obsolete crap invented by necrosoft in order to make their software incompatible with normal.

And still U+5350 works. Better than a thousand words sometimes.

Seems like your mouse never broke (or, if you have a wireless one, the battery in it has never died, and if it did, you could immediately replace it).

Or are you the type that does everything on a touchscreen? Because, judging from your logic, traditional computer controls must die too...

Here in ex-USSR we have those problems too. Why not standardize decimal separators altogether worldwide? We're not dealing with feeking paper handwriting! If a number is printed on a computer display, it must look like 123456.78, not like "123 456,78"! Same goes for datetime representation.

This localization BS has spawned an entire race of nonsense, where, for example, CSV files are not actually CSV in some regions, because their values are not COMMA-separated (as the name implies), but semicolon-separated. And we, programmers, have to deal with it somehow, not to mention some obsolete Faildows encodings like CP1251 still widely used here in lots of tech-slowpoke organizations.

So: one encoding, one datetime format, one numeric format for the world and for the win. Heil UTF-8!

UTF-8 must be the default and only encoding. Why does anything else still exist?

Great there still are some multiplayer network games for terminal-only systems. Nice work!

Joined.

Mozilla was the only browser vendor that introduced ES6 features not only before actually fixing row-wrap flexboxes, but even before implementing <input type=number>... and now again. Who needs those ES6 classes as long as they are natively supported in FF only?

Push API is a good thing though.

Waiting for an official Arch Linux package.

Someone already called him Trollvalds, and for a reason.

My vision of the open Web: WebRTC-to-SIP, Web(socket)-to-XMPP gateways, end-to-end encryption everywhere and the invention of some easy publishing in-browser protocol in order for everyone (including those on mobiles) being a server just as easy as being a client.

WebGL?

Hello from Firefox 44 (sic!) running on an old laptop which only has 1 GB of RAM. Probably eats more than 100 MB but still doesn't slow down anything.

The relevant question is: Why do user agents without JavaScript support still exist?

I don't care what kind of agents they are - bots from some sucky search engine like yandex, outdated screen readers or lynx installed on some freaky geeky nerd's Pentium 3.

Everything must be ES5-compliant these days. Period.

If my website cannot be archived by the Internet Archive (like anyone gave them a permission to do so, anyway), it's entirely their fault, not mine. And if I want to present my info to some link scrapers or aggregators, I'd rather generate an RSS feed. Or it would be much better if some JSON-based feed standard already existed for this purpose.

JavaScript doesn't just serve behaviour enhancement any more. It is a full-blown platform for the modern Web citizens.