News for hackers. Stuff that matters.

A comment on Rendering large terrains. Parent comment

Re:Rendering large terrains by theandrewbailey on Monday March 10, 2014 @08:52AM (#7372604)
It's 2014 and Javascript is awesome.

If I ever do anything 3D, it will probably be WebGL. Some industry veterans have reservations against it, but so long as it doesn't look like poop smeared origami, it's OK.

[ Parent | on HN ]
Re:Rendering large terrains by valarauca1 on Monday March 10, 2014 @09:10AM (#7372666)
>2014 and javascript is awesome

sort(1,10,5,3)

1, 10, 3, 5

Then there is this.

null == false //false

!null //true

[ Parent | on HN ]
Re:Rendering large terrains by Cthulhu_ on Monday March 10, 2014 @09:16AM (#7372698)
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

> The default sort order is lexicographic (not numeric).

Works as documented.

[ Parent | on HN ]
Re:Rendering large terrains by CmonDev on Monday March 10, 2014 @09:22AM (#7372725)
Ok, pick any other embarrassing design flaw: http://wtfjs.com/
[ Parent | on HN ]
Re:Rendering large terrains by al2o3cr on Monday March 10, 2014 @11:50AM (#7373602)
Documented boneheaded decisions are STILL boneheaded.
[ Parent | on HN ]
Re:Rendering large terrains by theandrewbailey on Monday March 10, 2014 @10:30AM (#7373072)
Sorry, by 'javascript is awesome', I meant 'javascript performance is awesome'.
[ Parent | on HN ]