298 karma · joined August 22, 2013
However what I really want: AST driven auto-complete VS-style for coffee/coco/livescript. This will probably not happen in an editor written in JS... at least it will not be that pleasant.
How about harmonization instead of confrontation (Remember when that ever had a positive outcome?). How about global trade mechanics with a global currency not controlled by privately held banks and ever-corrupt governments of single nations.
The Demonstration against TTIP with roughly 50.000 attendees in Berlin a few weeks ago received no news, no articles and did not spark discussions other than satirical/comedy shows making fun about it. I start to believe they aim to kill the seriousness of the outrage.
The standards applied here are whack in the scope of what js and mongo are used for.
Also: You only get better by reiterating.
I work on a mongo project and doing aggregate queries is really ugly and painful. Everyone praising mongo probably never made "advanced" queries like that or dismissed SQL as shitty and unsecure without ever using it.
So he does not like Javascript and Nosql. Is it hard to find a JavaEE job? I think not.
I hardly use any add-ons other than ad-block and a handful of selected ones and do not have the problems described. Quite the opposite actually! I do have the occasional freezes and crashes with ff using webgl, html5 video and even firebug (with less than 10 tabs open).
With es6 around the corner and the possibilities those features will provide, i would still bet on pure js. Those precompilers will benefit a great deal too. Symbols and Proxies alone will remove a lot of the hoops they have to go through now.
Simple truth. Very fast and very convenient for the NATO isn't it?
The elbphilharmonie is at 800 million now. It will mostly make money for private hands (public private partnership) and will leave hamburg in dept for decades. Welcome to a CDU town.
I would much rather like a null type, or even better: have null be declared as void too.
I will rather wait until TypeScript pleases me with union types and proper es6 alignment.
Then wait for v8 performance: http://jsperf.com/performance-frozen-object ES5 is doing good...
And at last: Wait for < IE-11 to die.
It remains to be seen if io.js will boosts ES Next for the server. Since bound to v8 i don't expect much.
Other implementations like the ahead of time compiler echojs become interesting. I am also curious how Typescript will look at v2.0.
I am ready, however I still don't use arrow functions... Which were first heard of in 2010? 2011?
It still feels like so far away.
I am not sure if that justifies 70mb of additional dependencies and the "we can solve that with a grunt plugin" mentality devs get. Our Gruntfile is 440 lines long :/
context.func() //this == context
func() // this == global
http://www.gekaufte-journalisten.de/ (german)
https://ersjdamoo.wordpress.com/2014/10/06/bought-journalism... (english blog article about it)
http://theagendadaily.com/gekaufte-journalisten-german-book-... (english news article)
A good read on the subject of performance and native method replacements: