Chrome 39 Launches With 64-bit Version For Mac OS X and New Developer Features 67
An anonymous reader writes "Google today released Chrome 39 for Windows, Mac, and Linux. The biggest addition in this release is 64-bit support for OS X, which first arrived in Chrome 38 beta. Unlike on Windows, where 32-bit and 64-bit versions will both continue to be available (users currently have to opt-in to use the 64-bit release), Chrome for Mac is now only available in 64-bit. There are also a number of security fixes and developer features. Here's the full changelog.
For me: Videos (Score:4, Informative)
First, HTML5 videos. I watch a lot of lectures on Youtube, and HTML5 videos have a speed option that most lectures benefit from (30min instead of 1 hour lecture). Sure, Firefox plays HTML5 too - but not as many. Some options are not available.
Second, Flash on Firefox has been *horrible* at least for me lately (I have the latest version of everything, Windows 7 system). After the latest Flash update all I have to do to crash the Flash plugin is right-click over a Flash area. And it's been crashing a lot for me for a long time.
On the other hand, (from a user point of view, not web developer) I often run across bugs in Chrome while the same doesn't happen (to me) with Firefox. So if I could I'd stay with Firefox.
I think as a web developer, especially when you develop modern apps and not just intranet enterprise apps (that are very conservative in what functions they use) Chrome may be more tempting at this point. I'm guessing - I only develop those "boring" apps where the intelligence is in the business logic and on the server and I don't need to do as much in the browser.
Re: (Score:2)
Flash on linux and firefox might suck, old version, but at least it stays the same over time (security fixes only)
So it's reasonably good. Wait, get firefox x+1 and flash 11.2 updates through the package manager, no need to care much about the videos (if the vid is html5 only, it appears to work. everything is unaccelerated on that PC save for linux/windows games and buggy/slow WebGL).
Re: (Score:2)
> I didn't know Chrome could change the playback speed of videos.
It is not limited to Chrome though. It is a feature of Youtube's HTML5 player. So it works on Firefox and other browsers too, only that Chrome supports all HTML5 video features that Youtube needs while Firefox does not (yet) - check with https://www.youtube.com/html5 [youtube.com]).
> The other way to do that is to use VLC
Sure, as always there are many ways. Chrome is the most convenient way to view Youtube though, that's all.
Re:Any reason? (Score:5, Informative)
Each web tab runs in its own process; you can see the CPU, Memory, per tab. Use: More tools > Task Manager
Looks like Chrome removed the FPS column [chromium.org]
Re:Any reason? (Score:5, Informative)
Safari now does this in Mac OS X Yosemite 10.01, each website has it's down process named after it that shows up in the Operating System's activity monitor.
1.5GIG for facebook? (Score:2)
Fing stupendous.
Re: (Score:2)
This shouldn't surprise anyone who's actually used Facebook. It's a case study in JS abuse.
Re: (Score:2)
Although it is hard to justify where an use of JS _isn't_ abuse. ;-) /me ducks
Re: (Score:2)
Re: (Score:1)
IE is a complete disaster. I use Windows 8.1 and that's the case there.
So yeah, vs that it's fucking obivous. IE is slow, unstable, nasty.
VS Firefox - Firefox is single threaded and mine bugs out completely with the Graphics sometimes or it run some loop where it switches around between the tabs forever. I don't know why and maybe that's due to some add-on but regardless of why it does that and it completely suck.
Chrome is more reliable.
The question is why one should use 64 bit Chrome though. They claim it'
link is wrong? (Score:2)
points to the stable channel release notes, last update October 7 and says nothing about 64 bit.
Re: (Score:2)
You couldn't be farther from the truth.
So the only people that are hurt (Score:2)
Are the people running unsupported versions of OS X. I guess it's back to firefox on my MBP 1,1 (running OS X 10.6).
Re: (Score:2)
Mainline Firefox will drop support for your OS at some point too. There'll probably be a project like TenFourFox for older Intel-powered Macs, though.
Re:So the only people that are hurt (Score:4, Interesting)
The Macbook Pro 1,1 has a 32-bit CPU.
Re: (Score:3, Funny)
It's not my computer. Are you illiterate?
Re: (Score:3)
What about those of us that are still running Mac OS 7?
Re: (Score:3)
I think you've got bigger issues....Very few things still support Mac OS. I don't think Firefox or Chrome ever ran on even on OS 9.
Re: (Score:3)
Then you're yelling at the kids "GET OFF MY LAWN!!!!
Correct link (Score:1)
http://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html
Re: (Score:3)
When you go to google.com/chrome , it will detect your OS and provide you with a appropriate link. however, if you want the 64-bit version of Chrome, you have to click the link below the download link to manually switch it to the 64-bit. Also, very little changes to the page, so it doesn't look like it changed anything when you select it
Must be a slow news day (Score:1)
Must be a slow news day. Didn't anyone ask BH what he thinks of the number "39"?
NPAPI hanging on (Score:2)
I keep waiting for the other shoe to drop for them Maybe then we'll see PPAPI versions of common browser plugins.
Re: (Score:2)
You can install the PPAPI version of Flash on Chromium pretty easily, and it's obviously included in Chrome by default. So the only NPAPI plugin that's truly missing is Java, and good fucking riddance, I say.
Any chance they implemented the 'let' keyword? (Score:2)
Chrome Soon? FireFox on the other-hand... (Score:2)
Re: (Score:1)
Firefox has already had "let" for ages, they just haven't started exposing it to web content outside of their alpha/beta/nightly versions. That Bugzilla ticket is talking about them removing unofficial extensions to the "let" keyword that might cause confusion. By contrast see http://kangax.github.io/compat-table/es6/ to know just how far behind Chrome is on ES6 (they have half-implemented stuff they haven't turned on yet, but the same is true for everyone else except Safari/WebKit, which is frankly an utte
Re: (Score:2)
The "let" keyword is not the same thing as "let blocks" and "let expressions".
The keyword looks like this:
let x = 5;
and is in ES6. A let block or let expression (neither of which is in ES6) looks like this:
let (x = 5) alert(x);
so that "x" is only in scope for the duration of the let block. It's syntactic sugar for:
{
let x = 5;
alert(x);
}
Should have been 64-bit from the start... (Score:4, Interesting)
If only Apple had postponed the Intel transition for about 6 months, their machines and software could have been 64-bit across the line, and this mess would have been avoided completely. Instead, we are eight years into yet another transition, with plenty of legacy 32-bit software out there, any of which require an entire duplicate set of shared libraries to be loaded.
Re: (Score:2)
Maybe. Plenty of older Macs with 64-bit CPUs and 32-bit firmware, though, which at least prevents newer OS X from booting a 64-bit kernel, and it's been more recently that computers have had enough RAM to make 64-bit truly worthwhile.
Re: (Score:1)
More recently.. 6-7 years ago.
Whatever.
Re: (Score:1)
Some Mac lines didn't get upgraded with 64-bit EFI until early 2009. Arguably you need a minimum of 4GB of RAM to really use 64-bit due to the ~30% tariff long pointers impose, and maybe you want 6GB for really good performance depending on what you run; further, the early '09 Mini topped out at 4GB officially.
Anyway, point is that even if Apple had waited for the Core 2 Duo to switch to Intel the early Intel Macs would probably still not run 64-bit-only programs today.
Re: (Score:2)
Apple had already for three whole years been asking developers to make the leap to 64-bit at the time they made the Intel transition.
The industry should have been able to cope just fine with OS X being shipped only on 64-bit Intel processors.
Those that hadn't already adapted, well, their 32-bit PowerPC code would have run just fine using the Rosetta code translation layer.
The real issue was though that Apple needed to ship new laptops that were competitive with PCs. They couldn't afford to wait around anot
Java in Chrome on Mac? (Score:1)
As long as it fully supports Flash (Score:2)
As long as the 64-bit version fully supports Flash on all platforms, I'm all for it. Like it or not, you need to support Flash, 64-bit or not.
I guess Red Hat and CentOS 6.x users are left in the lurch on this one.
Re: (Score:1)
Do I?
For ads?
I don't know about the game sites I'm watching (what about Steam and PC gamer?) but by now I assume most of the YouTube content plays through HTML 5 if one want to?
Firefox even have H.264 support now.
Re: (Score:2)
but by now I assume most of the YouTube content plays through HTML 5 if one want to?
True. All clips can be watched in HTML5 now in YouTube, including live broadcasts.
I think there's still many local TV broadcast services which require Flash. For example in Finland I still need Flash to use YLE Areena [areena.yle.fi], the public TV/radio broadcaster's online clip hive.
Re: (Score:2)
Sad to see a 4-digit-ID post this kind of drivel. How the mighty have fallen.
Re: (Score:2)
Ad hominem attack much? How's that debate strategy working out for you, there?
Re: (Score:2)
As long as the 64-bit version fully supports Flash on all platforms, I'm all for it. Like it or not, you need to support Flash, 64-bit or not.
Umm...Chrome comes always with the integrated PPAPI Flash plugin. Actually it's the only way to use a modern Flash plugin under Linux. As far as I know, the crusty NPAPI Flash plugin on Linux (package flashplugin-installer in Ubuntu, for example) still gets security updates, but is otherwise stuck on some ancient version number.
Hope google and China can cooperate (Score:1)
Re: (Score:1)
Chrome works fine here on Ubuntu [ubuntu.com] 64 bit.
Another version, still can't do gradients... (Score:2)
Time and time again, they just refuse to properly implement CSS3 gradients.
Version after version, no progress on https://code.google.com/p/chro... [google.com] at all
See http://slashdot.org/comments.p... [slashdot.org] from version 38.
It's pretty clear at this point, use Firefox or IE10+ if you want good HTML5/CSS3 support. Chrome only cares about what benefits Google and their ability to advertise to you.