Open Source Anniversaries: 6 Years of Go, 11 of Firefox (golang.org)
digitalPhant0m writes: Six years ago today the Go language was released as an open source project. Since then, more than 780 contributors have made over 30,000 commits to the project's 22 repositories. The ecosystem continues to grow, with GitHub reporting more than 90,000 Go repositories. And, offline, we see new Go events and user groups pop up around the world with regularity
And Opensource.com notes that Mozilla Firefox has just hit 11 years of age, too.
When Firefox was the hot new thing, it was mindbogglingly awesome. I remember just how happy I was when I first installed it (I think 2004?) and realized it was about twice as fast as Internet Explorer 6. I just about shit myself when I first installed Adblock Plus and saw it skip video ads.
Dark times followed. I think the manufactured outrage over Brandon Eich was the shark that Mozilla jumped over. After that, our fast, secure, modular, FLOSS browser became a shitheap and is now inferior in just about all ways to Chromium and Pale Moon.
Might as well throw this out there too: GStreamer's first release was 16 years ago on Halloween - 0.1.0 "gscreamer".
GStreamer - The only way to stream!
Remember when the #1 selling point of Firefox, though, was that it was lean, mean, and efficient (at least compared to the browser then-called Mozilla...)?
You are not alone. This is not normal. None of this is normal.
And what will you install instead, chrome? A browser that will also support WebVR, has multiprocess browsing and a revamped add-on platform?
Honestly, Firefox was dragging behind badly with an unsecure plugin architecture and single process thread that would lock up the browser when it was loading an heavy page.
Weren't Firefox's precursors also open-source? This would make it the (roughly) 17th anniversary for them.
Bueller?
Bueller?
Bueller?
I remember when one of the marketing points of Opera was that it was so lightweight and portable that the entire installer fit on a single 1.44M floppy disk.
It would be super cool if browsers could handle this new reality of JS scripts by not allowing them to block the UI.
A simple timeout is insufficient.
I was using Firefox as my primary browser since 0.7, which is about 12.5 - 13 years ago.
Damn, that makes me old.
Before they started bundling crap like "Hello", and changing the UI every 45 seconds to try and copy Chrome, while ignoring 11 year old bugs.
I feel 3.0 was peak Firefox. I remember the buzz and the huge counts of Downloads on release day. 3.6 was the last reasonable version before the whole project went off the rails.
while ignoring 11 year old bugs.
As in they are not fixing them or they are ignoring pull requests from OSS contributors that fix them?
Before they started bundling crap like "Hello"
It wasn't what you were looking for? I can see it in your comment; I can see it in your words. It's nothing you ever wanted, and your arms aren't open wide.
The user interface should always be on and prioritized so we can cancel anything or go back. I am looking at Safari mobile too.
More like "Bugzilla reports repeatedly marked 'won't fix', and reopened several times over the past decade".
Unfortunately I can't post examples right off.
If they're actually bugs then perhaps the community should submit fixes (or fund fixes).