Hacker News new | past | comments | ask | show | jobs | submit login

"IPv6 addresses have 64 bits too many in them" is not a very strong argument, especially not in 2017.



Its amazing people still wanna bike-shed what is essentially a 20+ year old protocol at this point. Its time to give up on the nitpicking guys, ipv6 is the future regardless of if you like it or not.


You're​ right that ipv6 is the future. However that does not mean it is impossible to find flaws in it. For some people, having 128 bits instead of 64 is a flaw.


Its about as relevant at this point as arguing that traffic lights shouldn't be red and green, sure maybe, but its not a very useful discussion because its both a trivial aesthetic concern and never ever going to change.


Colour blind folks might disagree with you. Just because we've always done it that way doesn't mean we shouldn't have a discussion about it.


Having a discussion about it is still allowed and in good style.


Ha ha. Like javascript! The thought alone depresses me (javascript, not IPv6).


JS is certainly not going to disappear.

But with WebAssembly, you'll not be locked into it, or into transpilers that produce it. Chances are, we'll see other reasonable languages being compiled to WebAssembly and getting mass adoption.

(WebAssembly is a stack machine with a bytecode interpreter, running in the browser, with code downloaded from the net. Java tried to be basically the same thing, only 25 years too early.)


Java also did it with 25x worse VM start times, 25x more security vulns, and a 25x more greedy and terrible company behind it (eventually). The legendary GC pause never helped. "Write once, run anywhere" then ironically becomes the specialty of Java...script.


It was when 4 MB RAM was what a typical desktop had.

Sun was inept in many regards, but not terribly greedy.

I don't see how JS doesn't magically have GC pauses. WebAssembly doesn't have a GC built-in, so it may host a pauseless process.



When direct DOM access from WASM happens. For now, it's designed for performance-sensitive stuff like game engines, codecs, crypto libraries, etc.


I wonder how hard it is to write a proxy from the JS side, and how large the performance penalty would be.

Also, with a relative clean slate, they have a chance to make DOM manipulation transactional finally.


People already trying to do this. It does not accomplish the "replacing JS" goal :)


Yeah I am really excited with Webassembly as the new JVM/CLR. But I was told this wasn't going to happen. As the downvote illustrates, there are many javascript militants who probably think we do not need any other language.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: