tinganho

I'm using TypeScript everyday, so I might can give a good answer to your question. They have just finished support for ES6 modules, template string, let/const etc. ES6 classes have been supported for a long time and most of the syntax sugar of ES6 I can think of is supported. On top of that, they are about to release v1.5 the big thing there is support for decorators.

What is not so good with TypeScript is that they have a rule of not polyfilling things. So if you want any new ES6 methods for array/string etc. You would need to polyfill them yourself.

The button was maybe created that way so people won't react.

I'm not sure if this is ARC? I think this is just Objective-C:s retain and release fundamentals. ARC as I understood it — is an offline compile solution. That outputs retain and release calls. What you seem to describe is the runtime and not the compiler?

They are two totally different services. Mailchimp lets you compose campaign emails. Whereas Sendgrid send transactional emails. Mandrill is Mailchimp's service for transactional emails.

I have been wondering the same thing. JS might be a good language. But we should still have a choice to choose other languages.

I'm seeing efforts with asm.js turning JS into a byte code language aka. LLVM IR. I'm not sure if turning JS into a byte code language is the best way either. It is still too high-level language. And it seems like a ugly hack.

I definitely don't like this proposal. SPA:s is under a heavily innovative period. Standardizing it will only slow downs its' development.

Just turn off twitter and Facebook and you can reach that kind of level.

Hi Jordan, I'm interested on which CSS rules causes reflows?

I wonder why it is such a big of a deal of not having DOM API:s on the WebWorker thread? I think the discussion from Browser vendors is that there is no use case or benefit of having them there.

And not having the "native feel" or performance. I think browser vendors are on the verge on closing this gap totally. If not browser vendors, hardware will do it.

I've already asked them this question. Slack is native.

I recommend that you need to teach the translator about the markup. It's really easy to understand.

The way L10ns try to mitigate the complexity of the markup language is to provide buttons for pasting the correct markup for translators. Also a developer translates on his own language first. And this example will always be visible to the translator of an another language for easy reference. So the programmer offloads the logic thinking from the translator.

IMO ICU's messageformat markup is also slowly becoming the standard for localizing strings. It is already used widely by big organizations such as Apple, Google and Yahoo.

L10ns pre-compiles all message string. So it offloads the parsing performance.

This have been done. It's called "ICU's messageformat". Though instead of having a general purpose language, the markup language is specially tailored for localization. One project that support ICU's messageformat is http://l10ns.org

ngettext can't handle two plural words well.

You might want to checkout http://l10ns.org

Here is more info about the plural format of ICU's messageformat. http://l10ns.org/docs.html#pluralformat.

ICU's messageformat solves this easily. One project that supports ICU's messageformat is L10ns http://l10ns.org

Please checkout http://l10ns.org It handles the pluralization case pretty well. It uses ICU's messageformat which is a markup for defining plural formatting http://l10ns.org/docs.html#pluralformat

It is quite naive to think that you can beat Google in design.

Durtis didn't the "left navigation" made that they browsed the feed more than other parts. I have never thought that the left navigation was any good. Since navigation navigation is a big part of UX and hiding it in the left is not good.

I just see one problem with this solution. You can't create Retina images out of base64 strings on any web browsers today.

Those who have tried to create an HTML5 based app and native. And who don't get the right "native" feeling on the HTML5.

There is a lot of tips and trick to get the native feeling. I just think that you should give HTML5 a chance and not out rule it.

it depends on which filter you are applying. But probably blue. Because of the big oceans we have.

The most interesting thing Google Dart will be used for the main languague for Android