Raspberry Pi Gets a Brand New Browser
sfcrazy writes The Raspberry Pi team has announced a new browser for Raspberry Pi. They had worked with Collabora to create an HTML5-capable, modern browser for Pi users. While announcing the new browser, Eben Upton said, "Eight months and a lot of hard work later, we're finally ready. Epiphany on Pi is now a plausible alternative to a desktop browser for all but the most JavaScript-heavy sites."
You're doing it wrong.
Anyone who uses their RbPi for web browsing is just asking for trouble. It's way underpowered for today's Web 3.0. In order to browse the web you need a lot more horsepower than this. (I never thought I'd see myself type those words. I think it means there's something seriously wrong with the WWW.)
So because they insisted on using a crappy 12-year-old design ARM11 CPU, they need a custom browser to compensate.
Why not make a Raspberry Pi model C, with a Cortex based CPU? If they used a modern A17 at 1.4Ghz, it would be just as low-power and have ~8x more performance.
I'm actually using Epiphany, the new browser, to post this. Slashdot was one of the first sites I visited and co-incidentally there was an article about it right at the top! So far, it does seem to be a nice upgrade to the previous Midori browser, which I found essentially unusable.
Does it run Slashdot?
modern computers start with 8gig of memory
Is the ASUS Transformer Book, a 10" convertible laptop computer, not "modern" because it ships with only 2 GB of RAM?
Besides, not all computers still in use are modern. I do most of my web browsing on a four-year-old Dell Inspiron mini 1012, a 10" laptop that came with only 1 GB of RAM and runs Xubuntu. Flashblock helps keeps Firefox below half a GB, after which point the bottleneck is not memory but the fact that Firefox uses only half of the CPU. Though an Atom has two-way simultaneous multithreading, Firefox is still single-threaded which brings a longer wait for complicated JavaScript and CSS to finish processing, especially on things like Cracked.com or Slashdot beta. My first-generation ASUS Nexus 7 tablet computer is stuck at 1 GB as well.
and then there's the page file/swap space.
A lot of computers without a rotating hard drive, such as my Nexus 7, can't afford to swap. Instead, they have a harsher OOM killer.
Firefox is a browser meant for browsing... and if that's what you're doing with it, that 1gig of memory is nothing. What background apps are using up the other 7gig?
I'm guessing that when no application is using part of the RAM, the chipset could power down unused RAM to prolong battery life.
Rasome. (As in, Jhon Carter movie)
Indeed. That's why nobody with good brains who has an embedded application would choose the Raspberry Pi for it, since the Raspberry Pi is 90% GPU + DSP (its VideoCore IV) with just a tiny old ARM11 core tucked in one corner. Unless you need video or OpenGL ES capability, this board is a waste of money on inappropriate functions and results in wasted high power consumption too.
That's why the Raspberry Pi is so good as a media centre, and so useless for embedding and hardware interfacing --- as you point out, it's the wrong choice for that.
It's no longer called "Epiphany". In what seems like an epiphany, the GNOME developers decided that it's much, much, easier to search for help for a browser called "Web". Great idea, there, guys. Was this intentional, to prevent intelligible bug reports from less sophisticated users?
One wonders whether they actually "eat their own dog food", or if they do, if they understand that the average user of GNOME isn't a GNOME developer.
It's no longer called "Epiphany". In what seems like an epiphany, the GNOME developers decided that it's much, much, easier to search for help for a browser called "Web". Great idea, there, guys. Was this intentional, to prevent intelligible bug reports from less sophisticated users?
One wonders whether they actually "eat their own dog food", or if they do, if they understand that the average user of GNOME isn't a GNOME developer.
FireFox thus far have refused to implement a configuration feature where they themselves limit the amount of memory they use. They say it's already built in and auto-tuning based on the amount of memory the OS reports. It's about time that FireFox stop being so arrogant and just let me set a limit, because I don't want them to eat all memory that I want to use for other applications that now have to resort to swap because a browser eats over 2G of my ram.
I was promised a flying car. Where is my flying car?
People and programmers have been spoilt by multi-GHz multi-core CPUs. People used to edit video, design space ships, simulate physics, ray trace liquid metal and just about everything else on far weaker machines. It good to see that some people can achieve good performance on limited hardware. The raspberrypi foundation are funding work all over the free software stack, which will benifit plenty of people who have never seen or used a pi.
Xombrero
Sorry, but web pages get rendered into images before displaying them. (Though at least Firefox's semi-recent versions don't bother rendering web pages until needed when you crash&restart Firefox, which I do all the time - usually not on purpose, though I'll occasionally do it to scavenge memory or when performance has become unbearably slow.)
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
Anyone else having trouble with it being slower than an infected IE running on a 386? Fast doesn't come to mind with a two-minute initial startup time and minute long page loads for Google searches. I'm running raspbian with a medium overclock.
noi that phong thi nghiem, bÃn thà nghiám