Chrome 35 Launches With New APIs and JavaScript Features
An anonymous reader writes "Google today released Chrome version 35 for Windows, Mac, Linux, and Android. The new version is mainly for developers, especially those building Web content and apps for mobile devices – this release doesn't appear to have any new features targeted at the end user. "
You are not stupid when you develop "web apps" -- you get al your customer's data. You are only stupid when you use them for more serious things than 2048.
Links2 is working just fine, thanks.
Good. Browsers should have stopped adding "features" 5 years ago. Display web pages and shut the fuck up.
Been waiting for that 5 years now... http://forums.informaction.com...
What cross-platform application environment would you recommend other than the HTML stack? Oracle Java and Adobe Flash/AIR don't have a spotless security record either. Or would you prefer to have to write 14 different native applications for 14 different platforms? You could have a web app written, tested, and deployed before you even finish applying to become an authorized developer on half of those platforms.
how about bloody 64bit on mac.?
Chrome was one of the first popular web browsers to use a separate process per tab. This architecture makes 64-bit less necessary because each tab is expected to use less than 2 GB of RAM.
you pretty much need to use java7 today
Which major web sites still use Java applets as opposed to SWF or HTML5?
Been waiting for that 5 years now...
http://forums.informaction.com...
And the three years since some dude called 'glen' took out side tabs; which is why I went back to firefox (treestyle tabs ftw)
46137
So even if my web pages and my web applications are relying on the same technologies (e.g. HTTP, HTML, CSS, Javascript), I'm using them differently and I would prefer that they behave differently. So why must it be that the same web-browser application does both? Why not create a highly efficient cross-platform application framework based on those technologies, and keep the browser simple?
Because by the time you make an HTML5 web application browser usably efficient, it's already also reasonably efficient at displaying web pages. What different behavior would you prefer in a subset browser suitable only for "web pages"? And where should one draw the line between a "web page" and a "web application"? Which is a forum? Which is a wiki? Which is a blog with a comment section? Which is a microblog host like Pump or Twitter? Which is a microblog host that allows adding GPS coordinates to posts?