121–130 of 178 posts
> Acid3, in particular, contains some controversial tests and no longer reflects the consensus of the Web standards it purports to test, especially when it comes to issues affecting mobile browsers. The tests remain available for historical purposes and for use by browser vendors. It would be inappropriate, however, to use them as part of a certification process, especially for mobile browsers.
Source: http://www.acidtests.org/
That's wonderful! How much RAM does it need? My biggest complaint about modern browsers is that I can't load a web page in less than 64 MiB, which is more than my entire computer had when I was running Netscape 3. The browsers are better now, but not in ways that necessarily use more memory.
The pages you look at also have gotten ‘better’ in ways that necessarily use more memory. I don’t think you regularly loaded megabytes of JavaScript.
Finally, your browser usage likely has gotten ‘better’ in ways that necessarily use more memory. I guess you have more tabs open than you ever had in that 64 MiB.
Earlier quoted context omitted.
We haven't really begun to optimize for memory usage yet, so it swings wildly depending on the content you're viewing. At this stage, we're primarily focusing on correctness and compatibility, and performance is mostly a luxury. It's an area I look forward to eventually dealing with though, as it used to be my full-time job at Apple years ago and I have many fun ideas. :^)
What's a rough minimum for a page with some text on it? Are we talking about 64MiB like Chromium, WebKit, or Gecko, or more like 16KiB, 256KiB, 4MiB, or 1 GiB? I think of memory usage as being more about correctness than performance, though I know that isn't how most people see it. Trying to run a 512MiB process on a 64MiB computer, or a 512GiB process on a 64GiB computer, is just never going to run at a usable speed…
And what language(s) do they use?
Earlier quoted context omitted.
> I get this is his passion project, but part of me wonders what he could accomplish working on the rough edges of linux. I've watched/listened to more than a few of his videos. Something that he has expressed on more than one occasion is an appreciation for the kind of deep vertical integration that he saw at Apple because they control the entire stack. He's going for something in that direction in Serenity and it,…
He's also talked about this on the CoRecursive Podcast: Andreas: Well, I don’t know that I ever had a real direction with it. But in the beginning, I remember feeling kind of frustrated with finding myself using Linux again and thinking it’s nice to be back on Linux. Everything is snappy. And the developer experience is really great, but I sure do miss having the source code for everything. Adam: This is a fascinatin…
There probably are hundreds of linux distributions exactly because people do not want to wait years for their change to ship, so they create their own project ...
Earlier quoted context omitted.
For reference, this page+assets are 187kB. I'd guess the bulk of that 44MB comes from having css and javascript on this page, but a breakdown of what it's using 44 MiB on would be interesting!
Obviously I don't know anything about the Serenity browser, but in the Gecko/WebKit/Blink cases it's mostly startup overhead. A page with a single word on it ends up being more than 44MB. The DOM is a braindead abortion that should never have been standardized. There's no plausible way to implement it with reasonable efficiency.
Earlier quoted context omitted.
The old version ( http://acid3.acidtests.org/ ) will reach 97/100 on modern compliant browsers. There is a newer version ( https://wpt.live/acid/acid3/test.html ) which incorporates the changes made to the specs in the meantime, so modern browsers will reach 100/100 on this one again. The test was carried out against this version, as you can see in the address bar in the screenshot.
Hmm, I'm seeing 99/100 in Chromium (mobile and desktop). I wonder what test is failing.
I've watched a few of this guy's videos, and it's deeply impressive. He reminds me of the grizzled old guys from the 1980's that actually know the deep internals of an OS. They didn't just take it in school, they lived and breathed it. He's the guy that made the 'myth' of a 10x coder a reality for me. I get this is his passion project, but part of me wonders what he could accomplish working on the rough edges of linu…
By his own admission he basically did nothing but coding all day long for most of his life, to the point where if he took a long vacation he'd be worried about getting rusty. For SerenityOS he basically holed up in a cabin for 6 months coding. At dayjob it was "60-80 hours a week", not forced but because he wanted to do it. That kind of sustained and focused work compounds over time and you just get better and better…
SerenityOS is an amazing accomplishment but it's just a hobby project without massive resources like major projects have.
Most real world apps have tons of devs that don't do 60 hours, the modern dev process just doesn't need it, unless you're doing large things entirely done by small teams.