Chromium 64bit for MacOSX

Chromium 64bit for MacOSX

Reading Time: 3 minutes

I was browsing for the solution for my failing Neon installation when I found Chromium 64bit for MacOSX at

Chromium vs Google Chrome

In 2008, Google created a project using embryonic source code from Chromium. After that Google broke away from Chromium and continued the development of Chrome.

However, Chromium is not a dormant project, as its developers continue to open Chromium projects and are named Chromium projects.

Google provides automatic update feature and also embedded the media player in it. After that Google also put Chrome into the laptop market, with a product called Chromebook.

Read more history of Chromebook, Chromebit, Chromebase, and Chromebox.

Google also added file formats that can be run by Chrome and also drivers for hardware that is made in closed-source. For me, the fatal difference is the absence of Flash Player in Chromium. But that can be solved using this way.

Chromium browser has:

  • only open-source licenses (BSD license, MIT license, LGPL, MS-PL and MPL/GPL/LGPL tri-licensed code) plus unlicensed files. It is a FOSSproject. A full list of software developed by third-parties is available within the browser at chrome://credits (similar to this online page)
  • a blue-colored logo
  • the similar sandbox as Google Chrome (For info, Firefox also uses it)
  • the similar user interface and settings as Google Chrome
  • the similar support for Extensions, Themes and Web Apps as Google Chrome
  • the similar user agent as Google Chrome
  • the built-in Chrome PDF Viewer (known as PDFium), on Windows OS
  • the built-in Chromoting Viewer (To use it, you need to first install the Chrome Remote Desktop app)
  • the built-in Google Native Client
  • the built-in Print preview and print system
  • no stable version offered by the official team (aka The Chromium Authors)
  • no digital signature
  • no auto-update system (Solutions: Use an #updater • Use PPA on #linux)
  • no Google API keys (Solution: Check #google-API-keys)
  • no built-in Flash player (Solution: Check #flash)
  • no support of proprietary codecs (AAC, MP3, H.264) (Solution: Check #html5-audio-video)
  • no user RLZ identifier
  • no user metrics (usage statistics) (opt-in option)
  • no crash report (opt-in option)
  • More details on the official site focused on Linux.

Some developers maintain forks of Chromium that offer more features and enhancements. Thanks a lot to developers! 😉

And if you want to follow new Chromium features, check the Google+ posts of the Chromium Evangelist at Google

To install it, double-click on Chromium_OSX.dmg file you have downloaded. Then drag its icon on Applications folder. You may then “Eject” and throw away this disk image.

Get Chromium for MacOSX here or perhaps you want to install Windows on your Chromebook?

Chrome Exceeding Chromium In:

  • Is compiled, linked and packaged into an installer
  • Has an auto-update system (some, such as the Debian or Ubuntu community builds of Chromium, rely on the package management system of the OS as an alternative)
  • Has an integrated PPAPI version of Adobe Flash Player.[10] This can be downloaded and installed separately in Chromium.
  • Has licensed media codecs to support the patent-encumbered H.264 and AAC formats. These can be downloaded and installed separately in Chromium. By default, Chromium only supports VorbisMP3Theora and WebM formats for the HTML5 Audio and HTML5 video tags.[11] Due to the way Chromium implements support for media formats, it is difficult to split up codecs to ship legally dangerous ones from ones that are safe to ship without paying for patent licenses. It relies on an FFmpeg-based library that contains the codecs with which it was built, instead of modularizing them into a plug-in based system like GStreamer does. Because of this, Fedora ships the library containing legally safe codecs but allows for the user to install a “Freeworld” package from somewhere else (RPM Fusion, for example) to override the default library, so that users who live where software patents don’t apply can make full use of Chromium.
  • Supports Widevine, a digital rights management (DRM) module. A dummy package that doesn’t enable Widevine support is built by default for Chromium.[12]
  • Disables extensions not hosted on the Chrome Web Store for macOS and Windows users on all Chrome channels[13]
  • Bears the Google and Google Chrome brand names and logos, both of which are registered trademarks[14][15][16]
  • Features an opt-in option for users to send Google their usage statistics and crash reports
  • Implements RLZ tracking when Chrome is downloaded as part of marketing promotions and distribution partnerships. This transmits information in encoded form to Google, including both when and from where Chrome was downloaded. In June 2010, Google confirmed that the RLZ tracking token is not present in Chromium or Chrome versions downloaded from the Google website directly. The RLZ source code was also made open-source at the same time, so that developers can confirm what it is and how it works.[17]
  • Licensed as freeware, as opposed to free and open-source[18]
Just my 2 cents. Wanna show me yours?