WebGL directly exposes the complete OpenGL 2.0 ES API (soon 3.0) to Javascript
where did you get this? this is crap.
WebGL truly is an exposure of GPU hardware and driver software directly to web applications.
this is just complete FUD. WebGL is just an API.
an implementation might blindly forward everything to an apparently compatible hardware device. it would be fucking stupid if it did. especially since it's trivial to statically determine such things beforehand.
it would equivalent to having a "asm(...);" function in your browser's javascript JIT that allowed you to inject arbitrary x86 code into the function, or allowing you to write outside the bounds of arrays. this is perfectly valid javascript, but if your implementation allowed this you would be at fault - not the language.
you can't use WebGL in web safari on the iPhone because that would allow you to write compelling content on the web that would cut into Apple's 30% of everything.
The main requirement for WebGL is the driver supports OpenGL ES 2.0
that's bollocks. there's no requirement that the driver support any variant of OpenGL. the requirement is that the browser can perform the operations requested of it by the WebGL program and fragments. the browser is free to ignore them, send them to an OpenGL ES 2.0 driver, transform them into DirectX calls, or send them by carrier pigeon to your grandma.
somewhere along the long the line you might want to check your inputs, but this certainly doesn't need to be a function of any driver.
it's the same with JITing javascript - if you don't check your bounds and send crap code to the CPU then you're probably going to be vulnerable to remote code injection. but that's not the fault of javascript, just of your shitty implementation.
there's nothing about WebGL that's unsafe - just bad implementations. and marketing FUD.
The irony is that the ms java vm passed all sun's compatibility tests except for the JNI ones (which are platform-dependent anyway) and it did so significantly better than sun's sorry attempt. Sun's original awt implementation on win32 was a joke.
Indeed. But this really has little to do with games. It's just yet another instance of society failing to reject the self-reinforcing medieval bullshit mindset that treats men like sex crazed animals and women like objects. How is this shit any different than forcing women to walk around in bags? Isn't it time we evolved?
I Meant what I wrote. I'm not making a connection. I'm just pointing out your fallacy: just because some action is an effective method of achieving some goal ('sex sells') doesn't make it morally right. Unless you're a sociopath.
yeah, my whole point was that WE as an IT community should stop using unencrypted SMTP for exactly this reason. how do you think the NSA reads all of hotmail/gmail if they don't have a box inside? we've known they have bridge ports on the whole internet since Mark Klein showed us the wiring diagram. we knew back then they could read all our emails and we still haven't done anything about it.
How accurate does a clock in a web page need to be?
Btw: JavaScript isn't blocked by other pages. Scripts on each page are single-threaded (modulo workers), but browsers are multithreaded (otherwise a while loop on one page would block the whole browser).
Also, you can't write an NTP client in JavaScript, well not one that will run in the browser without some kind of ActiveX plugin. Ntp is a tcp protocol, and there's no standard browser API that talks tcp or ntp.
Or jus derive the local time one from he difference between server time and local time. Or from the localized formatted date. Can't be that hard, it's probably been done already.
they did hire the best and brightest. then completely failed to keep them interested or sufficiently compensated. so the incompetent crap bubbled to the top.
Slashdot Mirror
Sultans, please...
WebGL directly exposes the complete OpenGL 2.0 ES API (soon 3.0) to Javascript
where did you get this? this is crap.
WebGL truly is an exposure of GPU hardware and driver software directly to web applications.
this is just complete FUD. WebGL is just an API.
an implementation might blindly forward everything to an apparently compatible hardware device. it would be fucking stupid if it did. especially since it's trivial to statically determine such things beforehand.
it would equivalent to having a "asm(...);" function in your browser's javascript JIT that allowed you to inject arbitrary x86 code into the function, or allowing you to write outside the bounds of arrays. this is perfectly valid javascript, but if your implementation allowed this you would be at fault - not the language.
you can't use WebGL in web safari on the iPhone because that would allow you to write compelling content on the web that would cut into Apple's 30% of everything.
A poorly written 2D graphics driver is likewise. What makes a 3D graphics driver substantially more so?
The 2D graphics driver isn't usable by web content.
The 3D graphics driver isn't usable by web content
no, there never was anything wrong with WebGL. it was just FUD.
The main requirement for WebGL is the driver supports OpenGL ES 2.0
that's bollocks. there's no requirement that the driver support any variant of OpenGL. the requirement is that the browser can perform the operations requested of it by the WebGL program and fragments. the browser is free to ignore them, send them to an OpenGL ES 2.0 driver, transform them into DirectX calls, or send them by carrier pigeon to your grandma.
somewhere along the long the line you might want to check your inputs, but this certainly doesn't need to be a function of any driver.
it's the same with JITing javascript - if you don't check your bounds and send crap code to the CPU then you're probably going to be vulnerable to remote code injection. but that's not the fault of javascript, just of your shitty implementation.
there's nothing about WebGL that's unsafe - just bad implementations. and marketing FUD.
Yay, yet another 'IT guy' that has no clue about the relative costs of developer hours and RAM.
The irony is that the ms java vm passed all sun's compatibility tests except for the JNI ones (which are platform-dependent anyway) and it did so significantly better than sun's sorry attempt. Sun's original awt implementation on win32 was a joke.
We've had a perfect programming language since C.
And a whole bunch of segfaults, too.
They made mshtml implement shdocvw because it made sense to add Internet Uris to the shell namespace.
That's right. Some people haven't learned yet how to be decent human beings.
Indeed. But this really has little to do with games. It's just yet another instance of society failing to reject the self-reinforcing medieval bullshit mindset that treats men like sex crazed animals and women like objects. How is this shit any different than forcing women to walk around in bags? Isn't it time we evolved?
I Meant what I wrote. I'm not making a connection. I'm just pointing out your fallacy: just because some action is an effective method of achieving some goal ('sex sells') doesn't make it morally right. Unless you're a sociopath.
Let me clue you in. Sex sells.
Yeah, and genocide is a good way to cement your political advantage.
Your point was?
yeah, my whole point was that WE as an IT community should stop using unencrypted SMTP for exactly this reason. how do you think the NSA reads all of hotmail/gmail if they don't have a box inside? we've known they have bridge ports on the whole internet since Mark Klein showed us the wiring diagram. we knew back then they could read all our emails and we still haven't done anything about it.
Yeah, isn't it about time we all switched to starttls over port 587 or ssl over port 465 for our mtas?
if you're using port 25, then the NSA pro already has your stuff.
Oh bugger.
How accurate does a clock in a web page need to be?
Btw: JavaScript isn't blocked by other pages. Scripts on each page are single-threaded (modulo workers), but browsers are multithreaded (otherwise a while loop on one page would block the whole browser).
Also, you can't write an NTP client in JavaScript, well not one that will run in the browser without some kind of ActiveX plugin. Ntp is a tcp protocol, and there's no standard browser API that talks tcp or ntp.
That won't work. But you go ahead and spout off your crap.
Ignorant fool.
Care to elaborate? Look like it works just fine.
It uses server time and geo location to avoid local clock error. And it allows the user to override the timezone.
I just tested it by screwing with my system clock setting and it still showed the correct time (3s error).
Or jus derive the local time one from he difference between server time and local time. Or from the localized formatted date. Can't be that hard, it's probably been done already.
Ah ad-hominem. Nice try, troll.
i think you must have hit reply to some other comment, because yours certainly makes no sense as a reply to mine. read it again.
they did hire the best and brightest. then completely failed to keep them interested or sufficiently compensated. so the incompetent crap bubbled to the top.
yeah, or use the $65 to buy a copy of Start8 and install it for them on their machine?
sheesh, he should have just suggested that in the first place! instead of all that XP crap.
oh... wait...