I'm using it in production and are very happy with it.

Cool, not saying it is bad, just that it didn't catch on.

I miss the days of pixel art and 90s anime. I just can't appreciate contemporary game art.

I'm guessing that's because games and animations are created using 3D tools today almost exclusively because everything else is prohibitively expensive.

While every fool (even me) can create/CAD-out a 3D model and then render it (and there are spectacularly bad specimens out there even I would be ashamed of publishing), 2D is an artistic interpretation of reality and takes real craftmanship. Far as I know, most animation is produced in Asia in huge studios and the workflow is such that you record the audio (voices), and draw some key frames after the voice timings by chief artists. The intermediate product is then called a "Leica". Then the artists of the big producers "ink out" the rest.

Personally I can't stand the animation of the 3D variety; it might have been fun/innovative back when Shrek came out, now its just stereotypical and cheap.

Me too, but I always see retro game developers on LiveEdu like this one: https://www.liveedu.tv/thr4nduil/videos/nOgXw-watchdog-gameb...

I'm missing autocompletion for vim.

Your decryption/encryption secret (key) is stored on the server side only and if a client requests a thumbnail, you can validate the URL value by successfully decrypting it with this secret and probably do a simple HTTP URL validation check of the decrypted value. And you have to encrypt all thumbnail URLs with this secret before passing them to the client.

Another very happy customer. After doing React and Angular 2 for a while I'm very happy with Vue. And it would be really nice to see Weex reach production maturity someday (regarding docs as well). Thanks, Evan!

agreed! it would seem ready for production given the alibaba association but docs and official support for vue (weex is based on but not actually vue) seem like the blockers for other orgs to adopt it. evan has stated in some HN thread (can't seem to find it now) that an "official vue" version of weex is coming very soon, though.

In the article it states that that stage is complete already.

And how long until the next "modern React" will land? That's what drove me away from React.

Before, React projects evolved because they have to. They became too complex, to clumsy, etc. But now ? React is stable, the way to develop apps is well known, etc.

A small nitpick: The generated Go code omits error handling and doesn't escape quotation marks when adding a header value containing a space.

Throwing "Uncaught TypeError: Cannot read property '_currentElement' of null" on the page edit view. UA: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36. Just saying ...

Would be a good idea to write those in Go and just ship the runtime together with the binary IMO.

Well, I get quite the opposite impression of condescending with them hanging around HN and golang nuts discussing language issues. And I'm actually fine with them making the decisions in the end. Go wouldnt be as clear and productive as it is today if every request for a feature would find it's way into the language in some half-hearted manner.

Isn't comment-driven code generation kind of the definition of a "feature request implemented in a half-hearted manner"? People asked for generics and got this. It seems like the kind of suggestion most language designers would throw out as unelegant.

If the language is so conservative as people claim, it should have neither macros/generics nor any of these pseudo-macro-generic-y half-measures.