31–40 of 62 posts
Earlier quoted context omitted.
>In case anyone is wondering, NodeJS v6 is right around the corner with V8 5.x. Any info on when it is going to come out of that corner?
For some reason the mismatched usage of 'corner' really bothers me! I'm sorry for this pointless comment.
In case anyone is wondering, NodeJS v6 is right around the corner with V8 5.x. Node is going to get a serious boost of ES2015 features. Including but not limited to: Proper tail recursion (^_^) and destructuring. Tracked at http://node.green We don't have an ES2015 features page up to date yet, but it's going to be ready any day now (and we're going to link to node.green anyway most likely).
"WASM 5.1 has a preliminary support for WASM. You can enable it via the flag --expose_wasm in d8. Alternatively you can try out the WASM demos with Chrome 51 (Beta Channel)." The future is coming fast.
Y but how long will it take to get to the point where enough users have browsers that support WASM ? 10 years?
In case anyone is wondering, NodeJS v6 is right around the corner with V8 5.x. Node is going to get a serious boost of ES2015 features. Including but not limited to: Proper tail recursion (^_^) and destructuring. Tracked at http://node.green We don't have an ES2015 features page up to date yet, but it's going to be ready any day now (and we're going to link to node.green anyway most likely).
Also, the fate for tail-call-elimination is pretty uncertain at the moment; see: https://github.com/tc39/proposal-ptc-syntax
Earlier quoted context omitted.
It took WebGL about 4 years to spread, the reason it took so long was in hardware (GPU, drivers ...). Wasm is just CPU-related, I believe it can reach most of the people within a year. Pouplar browsers get updated quite often. And those, which got updated rarely, became unpopular. Everything will be fine, I think :)
One of the major drags on WebGL was a lack of iOS support. Once that was in place there was an explosion in usage. I suspect we'll see the same here.
90% of the time someone puts a link to some WebGL demo on HN or Reddit I either don't get it running at all, or get single digit FPS after the mobile turned into oven mode.
In case anyone is wondering, NodeJS v6 is right around the corner with V8 5.x. Node is going to get a serious boost of ES2015 features. Including but not limited to: Proper tail recursion (^_^) and destructuring. Tracked at http://node.green We don't have an ES2015 features page up to date yet, but it's going to be ready any day now (and we're going to link to node.green anyway most likely).
>In case anyone is wondering, NodeJS v6 is right around the corner with V8 5.x. Any info on when it is going to come out of that corner?
"WASM 5.1 has a preliminary support for WASM. You can enable it via the flag --expose_wasm in d8. Alternatively you can try out the WASM demos with Chrome 51 (Beta Channel)." The future is coming fast.
Y but how long will it take to get to the point where enough users have browsers that support WASM ? 10 years?
What this means is that web standards can move significantly faster than in the past. Interesting new technologies like WASM can be implemented and tested without waiting 5-6 years anymore. Very exciting to see as a web developer.
What's the latest word on native ES2015 module support (i.e. the import keyword) in V8 or Node.js? Every ES2015 comparison table I know omits it, but it's the big one that could significantly reduce the modern JS toolchain complexity.
There's been some activity lately, but so far just looks like they're laying groundwork. Dunno where it is in the priority list. The last blocker was supposedly the finalization of the HTML5 module-loader spec, and that came out a couple weeks ago.
Earlier quoted context omitted.
Wouldn't that either cost money or only secure the connection from the client to cloudflare? From what I understand (and I admit, my knowledge is pretty lacking around what cloudflare offers) the free part is only the security between the client and cloudflare (and not the security between cloudflare and your server). On one hand it's better than nothing as I assume most MITMs are on local wifis and such but on the o…
It's a static site. Security between cloudflare and client seems like plenty