Viewing profile — nex3

We're also working on improving the compilation speed of the canonical implementation. 3.2 will have some improvements that should help considerably.

I'm the primary author of Sass. Hampton came up with the original idea, but he hasn't worked directly on the language in years.

No, since they can be opened inline.

It looks like they're leaving out everything in the spec I linked above. Currently this is the only way to persist File objects locally, although it looks like they're planning to …

The specific requirement for being whitelisted is that it shouldn't have a MIME type that Chrome wants to open inline. Give me a list of extensions that you'd like to see supported…

I can't comment on unannounced engineering efforts, and I certainly didn't mean to imply anything about them. All I can really say is that if they wanted the primary Gmail client t…

(Offline Gmail team member here) Attachments should work, with a few caveats. Due to some annoying quirks of the HTML5 FileSystem API, there's a whitelist of supported file extensi…

(Offline Gmail team member here) One thing we learned early on was that making any existing system (especially one as big as Gmail) work offline had some very difficult, fundamenta…

(Offline Gmail team member here) The primary reason this is Chrome-only is because other browsers don't yet have complete implementations of relevant specs (for example the FileSys…

I'm working on one. I'll upload it once I have the chance to finish it up.

Haml keys can be plain strings. #main_page{"data-role" => 'page'} `data-` attributes are also special-cased: #main_page{data: {role: 'page'}}

> Javascript doesn't really have native concurrency operations Except for Web Workers, also part of HTML5. The way Google Gears handled this was to allow synchronous database opera…

It's not actually true that Sass and Less have the same features. Each has some features the other doesn't, with Sass having substantially more than Less. Notable examples include …

That's the difference between reference documentation and introductory documentation. You go to reference documentation when you want to look up the details of something you alread…

Software patents have a strong tendency to be both vague and obvious. Although these are supposed to make something unpatentable, this doesn't happen in practice with software pate…

There's a built-in listing of which applications use what proportion of the battery.

GitHub no longer builds or serves gems.

Yes. While combining minification and gzip doesn't produce as dramatic an improvement as either does above plain text, combining them does usually yield some additional improvement…

No it's not. Look at it: it's one-selector-per-line, which is a very common style for handwritten CSS. If it were compressed, it would have no line breaks.

I was assuming compiling to JSON wasn't an option since the point of the post was the usefulness of avoiding a manual compilation step. With such a step, yes, you could avoid all t…

Don't forget the accessibility considerations: screenreaders typically don't run Javascript either.

I agree. I'm objecting to the implicit suggestion in the article and more explicitly in comments here that this is in fact fast enough for production. Running it server-side is an …

It's impressive that your benchmark compiles that quickly. However, as I mentioned elsewhere, the real issue is how fast real-world code compiles. My benchmark uses real-world code…

This is real CSS handwritten by real people. It's not compressed, it's just not in a fully-expanded style. If your parser is slow for reasonably formatted CSS, then your parser is …