I don't think we are nowhere near low enough on the internet latency thing for the delay that going to a high refresh rate would make any difference on lag. High refresh rates are still nice though for completely unrelated reasons.
Chrome has the best debugger I have seen. I find easier to debug Javascript code than Java code on Eclipse. It is one of the reasons I don`t like TypeScript and its similars, they compile down to Javascript which makes harder to debug the original code because the debugger only sees the Javascript code.
Why don't they just put the python runtime sandboxed? Why create a new language? Why not Lua or Ruby? Why not all of them so I can choose? All these languages have run-times on most major platforms (except iOS because, you know, Apple). Can't each browser just come up with a way to sandbox the language and provide the hooks to the DOM?
But really, the main problem isn't even javascript. The REAL problem is the DOM, it sucks manipulating it at run-time. The DOM was made to build documents, not applications. We need some real desktop-like api for building applications that allows little boxes on the screen to open html documents.
It seems the graphics for the notebook chips are pretty good:
http://www.notebookcheck.net/Intel-HD-Graphics-4600.86106.0.html
One step above nVidia 540m (the one I have on my laptop)
http://www.notebookcheck.net/Mobile-Graphics-Cards-Benchmark-List.844.0.html
For reference this could play recent games on medium settings very well. For gamers that can't afford (or don't want to bother with) two computers it seems this chip will provide enough horse power to play most games, a thrown back to the era (486 dos days) where you could simply play all available pc games if your rig was not older than 2 years.
These days you have to actually buy a dedicated (and expensive) gaming pc to play games, I think this is what gave the console makers the edge on the market. Intel can change that.
Many people here are completely missing the point. First the ones that say that Java is insecure (it's not) and the ones correcting them saying that the Java Browser Plugin/Java Applets that are insecure (they are right on this) and should be removed from Java.
The problem with Java Applets is the same problem that you have with ActiveX, they suck because they run third party code in a sand-box like manner and isolating that kind of code from your precious system is pretty hard. The people that implemented these technologies are not incompetent, they just lacked the foresight to see this is unfeasible.
Now the people who says that Java Applets should be removed are right, BUT they can't see the legacy code that needs the functionality. Java has always been strong on the corporate world where it powers many, many applications. For a long time those applications used Java Applets to present end-user interfaces. If you ever worked at a corporation you know how slow they are to change their legacy systems, I mean, I live in an IBM world (as in I have to integrate lots of their solutions with solutions from another companies) and the amount of stuff they put out that requires the Java plugin on the browser astonishes me.
My company provide solutions to other companies, sometimes developing them from the ground-up and sometimes adapting solutions from other big companies (IMB, BMC, Oracle) to their clients. Now you have to deal with the IT department of the target company and man you would be surprised how often the only approved browser for internal use is Internet Explorer 8. And now you have three options, either you convince them that you have to install a desktop application on all their machines (crazy hard since they can have multiple operating systems), install a new browser on everyones system (crazy hard because they have tons of legacy systems that only run in ie9 and they don't want to provide support for two browsers) or simply to suck it up and develop for ie8 (you don't have to convince their IT departments since they already support that). Now if you want to show a little chart there you can either mess around with Javascript libraries that still support ie8 (good luck with that) or you can make a java applet (they already support the java browser plugin).
The biggest problem with Java Applets is that they are better than ActiveX. Crazy no? The biggest security problems of Java is that it's better than ActiveX. Since they are better they were used for more stuff and for a longer time and it's a lot harder to move away from them.
Some people say that they should just make two versions of java, or one with an optional to install the applet side. This would be nightmarish for users. The RIGHT way to do it is exactly what Oracle is doing, patching the stuff they find and moving people away from applets. But NEVER remove them from the JVM, just put a big, bold deprecated keyword on all applet-related classes.
So short story, Java Applets will go away when ie8 goes away. ie8 goes away when Windows XP goes away (Windows XP does not support ie9). So yeah, it's all Microsoft fault. I know you were all hoping for a +5 funny post, but I guess I will have to settle for +1 Informative.
Slashdot Mirror
to Computer Science graduate? You know, down from kernel hacker?
What? I still count as a nerd and this IS news for nerds...
Valve wants to sell software, they are pushing open platforms that you can buy from anyone as long as you buy the software as well.
I don't think we are nowhere near low enough on the internet latency thing for the delay that going to a high refresh rate would make any difference on lag. High refresh rates are still nice though for completely unrelated reasons.
Chrome has the best debugger I have seen. I find easier to debug Javascript code than Java code on Eclipse. It is one of the reasons I don`t like TypeScript and its similars, they compile down to Javascript which makes harder to debug the original code because the debugger only sees the Javascript code.
Why don't they just put the python runtime sandboxed? Why create a new language? Why not Lua or Ruby? Why not all of them so I can choose? All these languages have run-times on most major platforms (except iOS because, you know, Apple). Can't each browser just come up with a way to sandbox the language and provide the hooks to the DOM?
But really, the main problem isn't even javascript. The REAL problem is the DOM, it sucks manipulating it at run-time. The DOM was made to build documents, not applications. We need some real desktop-like api for building applications that allows little boxes on the screen to open html documents.
It seems the graphics for the notebook chips are pretty good: http://www.notebookcheck.net/Intel-HD-Graphics-4600.86106.0.html One step above nVidia 540m (the one I have on my laptop) http://www.notebookcheck.net/Mobile-Graphics-Cards-Benchmark-List.844.0.html For reference this could play recent games on medium settings very well. For gamers that can't afford (or don't want to bother with) two computers it seems this chip will provide enough horse power to play most games, a thrown back to the era (486 dos days) where you could simply play all available pc games if your rig was not older than 2 years. These days you have to actually buy a dedicated (and expensive) gaming pc to play games, I think this is what gave the console makers the edge on the market. Intel can change that.
Many people here are completely missing the point. First the ones that say that Java is insecure (it's not) and the ones correcting them saying that the Java Browser Plugin/Java Applets that are insecure (they are right on this) and should be removed from Java.
The problem with Java Applets is the same problem that you have with ActiveX, they suck because they run third party code in a sand-box like manner and isolating that kind of code from your precious system is pretty hard. The people that implemented these technologies are not incompetent, they just lacked the foresight to see this is unfeasible.
Now the people who says that Java Applets should be removed are right, BUT they can't see the legacy code that needs the functionality. Java has always been strong on the corporate world where it powers many, many applications. For a long time those applications used Java Applets to present end-user interfaces. If you ever worked at a corporation you know how slow they are to change their legacy systems, I mean, I live in an IBM world (as in I have to integrate lots of their solutions with solutions from another companies) and the amount of stuff they put out that requires the Java plugin on the browser astonishes me.
My company provide solutions to other companies, sometimes developing them from the ground-up and sometimes adapting solutions from other big companies (IMB, BMC, Oracle) to their clients. Now you have to deal with the IT department of the target company and man you would be surprised how often the only approved browser for internal use is Internet Explorer 8. And now you have three options, either you convince them that you have to install a desktop application on all their machines (crazy hard since they can have multiple operating systems), install a new browser on everyones system (crazy hard because they have tons of legacy systems that only run in ie9 and they don't want to provide support for two browsers) or simply to suck it up and develop for ie8 (you don't have to convince their IT departments since they already support that). Now if you want to show a little chart there you can either mess around with Javascript libraries that still support ie8 (good luck with that) or you can make a java applet (they already support the java browser plugin).
The biggest problem with Java Applets is that they are better than ActiveX. Crazy no? The biggest security problems of Java is that it's better than ActiveX. Since they are better they were used for more stuff and for a longer time and it's a lot harder to move away from them.
Some people say that they should just make two versions of java, or one with an optional to install the applet side. This would be nightmarish for users. The RIGHT way to do it is exactly what Oracle is doing, patching the stuff they find and moving people away from applets. But NEVER remove them from the JVM, just put a big, bold deprecated keyword on all applet-related classes.
So short story, Java Applets will go away when ie8 goes away. ie8 goes away when Windows XP goes away (Windows XP does not support ie9). So yeah, it's all Microsoft fault. I know you were all hoping for a +5 funny post, but I guess I will have to settle for +1 Informative.