first draft of open source insider for Feb

1 files changed, 39 insertions, 0 deletions

diff --git a/open-source-insider-1702.txt b/open-source-insider-1702.txt
new file mode 100644
index 0000000..a16a4fb
--- /dev/null
+++ b/open-source-insider-1702.txt
@@ -0,0 +1,39 @@
+The Mozilla Foundation recently announced it will refocus its development efforts on Firefox. Again.
+
+I know what you're thinking, what the heck else does Mozilla have to focus on? Firefox is and likely will be the only viable product the company has, and that it lost focus of it's only viable product tells you a lot about the leadership of Mozilla in recent years, or lack thereof.
+
+Before I completely eviscerate Mozilla though, let me be clear about something: I like Firefox. I use it everyday. I find it to be not quite as fast as Chrome, but easier on the RAM. 
+
+That's anecdotal of course and based on the Developer Edition, which is my daily browser. I also use and really like Mobile Firefox for Android, though I freely concede that it's much slower than Chrome for Android. 
+
+My point is that I really want Mozilla to succeed. I even support the attention Mozilla gives to "defending" the open web because they're one of the only companies out there that doesn't have much in the way of ulterior motives for doing so.
+
+But in the last three years Mozilla has gone from a company at the top of its game, with a web browser that constantly pushed the envelope of standards support and kept pace with Chrome in terms of performance to a shattered smoldering heap of embarrassment that clings to life via a browser that can barely keep pace with today's web. 
+
+Even Brendan Eich, creator of JavaScript and one of Mozilla's founders -- who was later forced out of the company after it came out that he had donated money to support anti-gay rights legislation in California -- has gone on to create a new web browser dubbed Brave. Guess what codebase Brave is based on? Hint, not Firefox. 
+
+Brave will fizzle before the year's over -- it's value proposition is that is swaps out ads your favorite websites are earning good money with and replaces them with ads your favorite sites will earn little to no money from... uh, okay -- but it's telling that even Mozilla's founder have lost faith in the Firefox codebase.
+
+Given this state of affairs, you'd think that Mozilla's announcement, which amounts to the company saying, "hey, sorry, we screwed up and we're going to try fixing this", would make me happy, but honestly, it makes me more nervous than happy. 
+
+If the ill-advised thinking that led to three years wasted on head scratching ideas like Firefox OS turns its attention to the web browser proper, what sort of disaster is coming to Firefox?
+
+Last month I wrote about Vim and the value of software that doesn't update unless it really needs to. 
+
+I'd like to see Mozilla embrace that sort of thinking. I'd like to see Mozilla continue to forget about the Firefox UI and focus their attention lower down in the stack. The Firefox UI isn't broken, it works quite well, it's stable, don't go messing with it. Don't go "innovating", don't add something stupid like rounded tabs just because you hired some new designer who needs something to do.
+
+Some people objected to last month's column comparing Vim and Firefox, saying that Firefox has to update because the web is a moving target while text files really have changed since Bram Moolenaar released Vim in 1991. That's a valid argument and I never suggested that Firefox shouldn't update, rather that it shouldn't go changing it's base feature set and user interface all the time. It shouldn't add Pocket support for no discernible reason; it shouldn't round tabs for no discernible reason.
+
+It should update to get separate processes for each tab, which took an embarrassingly long time to be released. It should also start developing a rendering engine that's faster than Gecko since it seems plain at this point that Gecko isn't getting any faster than it is now. The good news is that appears to be happening with <a href="https://medium.com/mozilla-tech/a-quantum-leap-for-the-web-a3b7174b3c12#.sas419jjm">Quantum</a>.
+
+But here's why I'm nervous about Mozilla "refocusing" on Firefox, developers are already <a href="https://medium.com/@osunick/context-graph-its-time-to-bring-context-back-to-the-web-a7542fe45cf3#.f2ssglw9o">talking about messing with the Firefox UI again</a>. This is exactly the sort of thinking that got Mozilla where it is: "What if there was a better forward button?". Wait, isn't that the button no one users so Firefox made it tiny? Right, problem solved. Next.
+
+Even more alarming is this thinking later on in that piece: "What if web browsers were immediately useful instead of demanding input when you launched them?"
+
+Well, what if Mozilla made a browser that was immediately useful when it launched because it was fast enough to accept input right away? 
+
+What if Firefox didn't hang immediately on launch because it was processing through a bunch of tabs (which aren't even loading, just displaying page titles)?
+
+I feel pretty safe speaking for the masses here: we don't need a web browser that does any thinking for us. Web browsers are task driven software, when people open a web browser it's because they want to do something on the web. They don't want a better forward button. They want a faster web browser and currently 85 percent of them have solved that problem by choosing something other than Firefox.
+
+That is your problem Mozilla. Your bug number one is that Firefox is slower than Chrome. Refocus on fixing that and spare us the ill-advised UI "improvements". Who knows, people might start using Firefox again.