Except they're not, for the vast majority of them.
Yes, it might be true in the ski resorts, but most people leave in the plains.
Zürich has barely had any snowfall this year.
Even in snowier years, it's a few days per year at most.
Backslash escaping the number (or possibly the period) should work in most (and therein lies Markdown's biggest problem, the lack of a proper spec (fingers crossed for CommonMark)) parsers.
> One can imagine modifying the compiler to output llvm bitcode. You now can throw plenty of optimisation at it for free (but you are now slower to compile).
If you look at the FAQ, you'll see they can do exactly that but using gcc/Clang, not LLVM.
I doubt it, but it's hard to tell. More will become clear once they've actually released the langauge - as it is, this whole website seems super premature, since neither the language itself nor the source code to any real software written in it are available for public consumption.
The documentation that exists is minimalist enough that I would be very careful about assuming it represents a complete representation of the language's features.
They're giving you their content for free. It's a transaction--you want something, you pay for it. In the case of free content from an excellent magazine, in the form of ads.
If you want to steal it, install an ad blocker.
You can also buy the magazine in paper form, but you'd probably get upset because there's ads in there too.
I don't see it on my personal laptop on Firefox (Linux Mint), or on my workstation at work also using Firefox (Ubuntu 14 - no plugins).
Edit:
WOW I can't believe this, I opened it up in Chrome and it works / shows the comment folding option. It astounds me how much Chrome is becoming the new IE in regards to functioning websites where I wont be surprised to see (or not see) more cross-browser issues when using Firefox instead of Chrome.
Can I have the web where everyone wanted to be backward compatible with all browsers back?
Edit 2:
Also wondering how this got published by Reddit and nobody noticed some basic site functionality missing?
>You'll never see JPEG-XS images stored on disk or sent over the web.
I don't see why not. The image quality is near perfect, according to the article, for not even double the average file size, and it uses much less energy to encode and decode, so it's better for your battery life on mobile devices.
Because this would be at least 5 times slower to transfer compared to regular image formats, and on mobile a lot of energy goes to power the screen (while user is staring at a blank one, waiting for data) and radios (which now have 5x more work to do).
JPEG XS has severe restrictions of realtime encoding and a 30-line buffer, which are necessary for its goals, but make it a bad choice for anything that doesn't have such limitations.
I think the whole appeal is faster encoding/decoding, but compared to a normal jpeg, it's the same image quality with a larger file size. I could be mistaken, the article is kinda light on actual technical details.