I'm really excited about array comprehensions, anyone know if that's actually going to be part of ES2015? Google kinda gives me mixed messages on this one.
V8 Release 5.1
21–30 of 62 posts
Re: V8 Release 5.1
#22I'm really excited about array comprehensions, anyone know if that's actually going to be part of ES2015? Google kinda gives me mixed messages on this one.
ES2015 was finalized in June 2015. Comprehensions aren't part of it.
If you ask MDN: Was initially in the ECMAScript 6 draft, but got removed in revision 27 (August 2014). Please see older revisions of ES 6 for specification semantics.
Non-standard. Do not use! The array comprehensions is non-standard, and it's unlikely to be added to ECMAScript. For future-facing usages, consider using Array.prototype.map, Array.prototype.filter, and arrow functions.
Array comprehensions were removed in Babel 6.0
Re: V8 Release 5.1
#23Earlier quoted context omitted.
Even if that's the case, I hope to still be a developer in 10 or 15 years from now, and I'm betting people will still be using the internet then too.
Yep just wish things could move along faster :)
Yes we do. But that only happens with technology dictatorships. And we've seen where that leads.
Re: V8 Release 5.1
#24Earlier 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…
Yeah, the free version is HTTPS only between client and CF. I made my blog hosted on Github HTTPS with this, mainly so that I can experiment some features like Service Workers.
Source? Last time I used it you could encrypt both hops (although you obviously need to tell CF to ignore the cert mismatch for backend server).
Re: V8 Release 5.1
#25Earlier quoted context omitted.
Y but how long will it take to get to the point where enough users have browsers that support WASM ? 10 years?
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.
Re: V8 Release 5.1
#26Earlier quoted context omitted.
Yeah, the free version is HTTPS only between client and CF. I made my blog hosted on Github HTTPS with this, mainly so that I can experiment some features like Service Workers.
Source? Last time I used it you could encrypt both hops (although you obviously need to tell CF to ignore the cert mismatch for backend server).
Yes, I use free CF with both hops encrypted. There's no way for my visitors to know this though. IMO CF should require both hops be encrypted.
Re: V8 Release 5.1
#27Earlier quoted context omitted.
Or put the domain on cloudflare. My site is hosted on github too, with a CF cert. Works fine with https :)
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…
> 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).
The free plan also supports securing the connection between CloudFlare and your server.
Re: V8 Release 5.1
#28In 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?
Re: V8 Release 5.1
#29In 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?
For some reason the mismatched usage of 'corner' really bothers me! I'm sorry for this pointless comment.
Re: V8 Release 5.1
#30Does this have any implications for npm addon authors?