Listen to Donald Trump robocall urging California's 'no party preference' voters to register as Republicans. see more here http://sh.st/IS9mr
V8 Release 5.1
11–20 of 62 posts
Re: V8 Release 5.1
#12In 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).
FYI - Your https link generates a cert error because node.green is being served with the www.github.com ssl cert.
Re: V8 Release 5.1
#13In 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).
FYI - Your https link generates a cert error because node.green is being served with the www.github.com ssl cert.
Thanks! I've updated it to an http link, I'm just so used to https working everywhere nowadays. Maybe it's time to petition GH pages to support letsencrypt!
Re: V8 Release 5.1
#14In 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).
FYI - Your https link generates a cert error because node.green is being served with the www.github.com ssl cert.
[deleted]
Re: V8 Release 5.1
#15Earlier quoted context omitted.
FYI - Your https link generates a cert error because node.green is being served with the www.github.com ssl cert.
Thanks! I've updated it to an http link, I'm just so used to https working everywhere nowadays. Maybe it's time to petition GH pages to support letsencrypt!
Or put the domain on cloudflare. My site is hosted on github too, with a CF cert. Works fine with https :)
Re: V8 Release 5.1
#16Earlier quoted context omitted.
Thanks! I've updated it to an http link, I'm just so used to https working everywhere nowadays. Maybe it's time to petition GH pages to support letsencrypt!
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 other it gives users a false sense of security.
Then again none of this is of actual concern for node.green
Re: V8 Release 5.1
#17"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?
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 :)
Re: V8 Release 5.1
#18"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?
These days software is mostly auto-updating so at least in the US and other first world countries, relatively soon. The rest of the world is where we'll be lacking. :/
Re: V8 Release 5.1
#19Earlier 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…
It's a static site. Security between cloudflare and client seems like plenty
Re: V8 Release 5.1
#20Earlier 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…
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.