|
|
Log in / Subscribe / Register

A 2018 retrospective

By Jonathan Corbet
December 19, 2018
The December 20 LWN.net Weekly Edition is the final one for the year; as usual, we will be taking the last week of the year off for a brief rest. LWN, which is about to conclude its 21st year of publication, has had the time to build up some traditions, one of which is a year-end retrospective that evaluates the predictions we made back in January. As usual, some of those predictions aged rather better than others; read on for our report card.

Revisiting the predictions

We started with a vague prediction that there would be an increase in introspection as we think about what our projects and our industry should be trying to achieve in the world. On the industry side that has certainly happened; technology companies have lost their halo and find themselves under increasing levels of scrutiny, and some have had to change course as a result. Whether that process has extended to the free-software community is debatable, though. Some actions, such as the removal of the questionable Speck encryption algorithm from the kernel, show concern about the world we are creating, but there aren't a huge number of examples to point to.

The prediction that we would see more hardware vulnerabilities was published before the disclosure of Meltdown and Spectre, so we could perhaps claim a major success there. By January 2, though, when that article was published, it was obvious that something of that nature was about to surface, so the amount of credit that is due is limited. Whether the level of interest in open hardware has increased as a result is not really clear. The RISC-V architecture has indeed seen such an increase, but that may be more a result of commercial forces than security concerns, and whether RISC-V processors will truly be more secure has yet to be proven.

Concerns about a major security incident at a cloud provider were not realized — so far as we know. Even the various rounds of hardware vulnerabilities appear to have been handled well enough. Serious security breaches continued to surface elsewhere, of course, to nobody's surprise.

Work on alternative container runtimes continued as predicted, as did blockchain hype; no surprises there. The collapse in the prices of many cryptocurrencies and the lack of other convincing blockchain applications suggests that some of the shine has come off of some blockchain-based technologies, though.

The prediction that vendors would move closer to mainline kernels was a bit controversial at the time, but things do indeed seem to be moving in that direction. The Android project, in particular, is working hard to make that happen. We are still some distance from being able to run mainline kernels on our mobile devices, but there is a glimmer of hope on the horizon.

Did alternative kernels like Fuchsia gain prominence this year? That may or may not have happened, but those projects have certainly not gone away. It is still true that Linux developers take our domination of small, embedded systems for granted; they can be heard saying that no vendor will want to bother qualifying another kernel for its hardware. Perhaps that is true, but perhaps that is the pride that goes before the fall in that piece of the market.

Wayland support did grow as predicted, but "the long reign of the X Window System" seems far from an end. It probably is true that Python 3 adoption has reached a turning point; those who are still running Python 2 applications are generally thinking seriously about moving forward.

What was missed?

One thing that was certainly missing from the list of predictions was that Linus Torvalds would take a one-month break from running the kernel project and a new code of conduct would be adopted. This change came out of the blue, and has caused quite a bit of controversy both within the kernel project and beyond it. Even developers who have no particular disagreement with the code that was adopted are somewhat unhappy with the way that change came about. So far, though, the sky has not fallen, and kernel development continues pretty much as it did before.

Perhaps Microsoft's rebasing of its Edge browser on top of the Chromium engine could have been foreseen, but we didn't see it coming. The result is a browser ecosystem that increasingly looks like a monoculture, with all of the associated risks. Due to some of the forces mentioned above, the company that now appears to control much of the web (and beyond) is not quite as well trusted as it once was. Once again, Firefox is our main line of defense against this scenario; perhaps the project can come through for us again.

The era of big-money stock deals involving Linux seemed to have ended with the dotcom crash, but then IBM surprised the world by buying Red Hat for $34 billion. It could well be that Red Hat will bring value to IBM that far exceeds the massive premium above the company's valuation that IBM agreed to pay. Or maybe we are seeing another occasion where history rhymes with itself, and an over-the-top valuation of a free-software company is the harbinger of the end of a long, technology-driven boom.

The creation of new free-software licenses has been frowned upon for many years, so one might be forgiven for thinking that innovation in this area had stopped. This innovation resurfaced this year, though, as companies created new licenses intended to increase their incoming revenue from their flagship projects while keeping those projects as something that at least vaguely looks like free software. It is fair to say that these new licenses have gotten a chilly reception, but it is probably also fair to say that this will not stop companies from trying to craft licenses in ways that will improve their bottom line.

Nobody expects the Spanish Inquisition, and almost nobody expected Guido van Rossum's abrupt abdication, in July, of his role as the benevolent dictator for life of the Python project. As a result, the project was unprepared for this change and spent the last six months figuring out how its governance will work going forward. Python the language has never been stronger; Python the project is in no danger, but its developers clearly have some things to work out.

All told, it would be hard to argue that this was not yet another good year for Linux and free software — like the years before it. LWN has been privileged to enjoy a ringside seat for 21 years of this community's growth. We owe this privilege to an engaged and supportive community of readers; no publication could ever ask for a better audience. As this year comes to a close, we would like to thank you all for your continued support of LWN, and to wish you the best of the holiday season, however you may celebrate it.


to post comments

A 2018 retrospective

Posted Dec 19, 2018 22:22 UTC (Wed) by JohnLenz (guest, #42089) [Link] (4 responses)

Two other big things in 2018:

* Steam/Valve announcing Proton, funding development of DXVK, and contributing to Wine. This currently allows a large swath of games to run on Linux. As DXVK matures gaming on Linux will get better and better, but 2018 is when DXVK became viable and Linux gaming expanded by a lot.

* Flatpak 1.0 becomes usable and installed by default in Fedora. We will see if Flatpak actually becomes a primary way of installing programs or not, but 2018 is the beginning of a end-user viable and usable Flatpak. I have used it to install a few applications to get the newest version. Perhaps a good prediction for 2019 is if Flatpak will take off or not.

A 2018 retrospective

Posted Dec 19, 2018 23:44 UTC (Wed) by admalledd (subscriber, #95347) [Link] (3 responses)

I agree with Proton/DXVK/Wine changes this year (few months really!) are probably things worth mentioning. VR for linux worked out-of-box for me.

Personally, a majority of my friends who were stuck on windows due to specific games are trying Linux once again. Still a number of bleeding edges around, but I wonder how much more it will change in the coming year. Along with that was AMDGPU+mesa being complete and stable enough that running without (gpu) blobs means that the last four computers I have built (one for my desktop refresh, three for friends/family) are now all proudly AMD+Linux only machines *that just work*. What a change! (glares at a certain green team)

Still have to get my brother to take the plunge though. Hopefully soon with how much he loves to complain about lack of options/settings...

I can't speak to flatpak since that is outside my uses still, but I do hope something in that space works out and becomes a de facto standard of sorts for upstream projects.

Proton sea change

Posted Dec 22, 2018 2:46 UTC (Sat) by jeffcook (subscriber, #119964) [Link] (2 responses)

Always expected something like Proton eventually, but the timing is an important indicator of Valve's thought process: it shows that Valve is at least _somewhat_ confident that Microsoft will allow large-scale WINE rollouts from well-known companies without unleashing an unholy lawsuit apocalypse.

CodeWeavers, Cedega, et al have always been too small to bother launching a big lawsuit against -- Streisand Effect would've done more damage than those groups posed -- but Valve pushing this is serious business.

Whatever the outcome, it marks a crucial milestone, and IMO shows that Microsoft may have actually internalized a post-Windows future for itself.

Proton sea change

Posted Dec 24, 2018 18:55 UTC (Mon) by raven667 (subscriber, #5198) [Link] (1 responses)

What would be funny would be for MS to work on WINE as a way to preserve Win32 software as they probably can't relicense every bit of their legacy code to open source and WINE license is free and clear. It would be a weird world where WSL is a backup implementation of Linux and WINE of Windows. Is MS today a bigger data center hosting company than software?

Proton sea change

Posted Dec 24, 2018 23:45 UTC (Mon) by flussence (guest, #85566) [Link]

MS is having a hard time even giving Windows away gratis in the newly post-Ballmer era, so they're mostly counting on being a service and SaaS provider (Office 365 etc) for revenue. They also make money off the games division (or at least, I believe it's not $5bn in the red any more…)

A 2018 retrospective

Posted Dec 19, 2018 22:27 UTC (Wed) by roc (subscriber, #30627) [Link] (41 responses)

Ask not whether Firefox can come through for you again, but what you can do for Firefox.

A 2018 retrospective

Posted Dec 20, 2018 12:11 UTC (Thu) by tsavola (subscriber, #37605) [Link] (40 responses)

I think this is very important.

After I read the Edge announcement, I switched from Chrome to Firefox. The diminishing market share of Firefox needs to be reversed somehow or we are doomed - no matter how good the dominant browser technology is.

Firefox

Posted Dec 20, 2018 14:01 UTC (Thu) by garrison (subscriber, #39220) [Link] (37 responses)

It is remarkable to me how my choice of a web browser really just comes down to a few, somewhat minor, behavioral differences. I tried switching from Chromium to Firefox earlier this year, and I experienced two dealbreaking issues:

  1. It is easy to accidentally hit Ctrl+Q instead of Ctrl+W when intending to close a tab, resulting in the entire browser and all open tabs being closed. This has been widely discussed, but there is still no solution on [GNU/]Linux as far as I am aware.
  2. After I run apt-get upgrade, Firefox will often crash. After this occurred a few times, I noticed that the output of apt says "Please restart all running instances of firefox, or you will experience problems." Indeed, this is true. But it is also true that if I use Chromium, I can upgrade my system without my web browser crashing.

Firefox

Posted Dec 20, 2018 14:39 UTC (Thu) by garrison (subscriber, #39220) [Link]

Following up on my own comment:

I also switched from Chrome to Firefox on my Android device earlier this year. At first it was a wonderful change, the main immediate benefit being that I could install browser extensions. Over time, though, performance degraded to the point that it became unusable (presumably due to a large number of open tabs?), and I am back to Chrome for now.

Here's to hoping future improvements allow Firefox to become my default browser on both desktop and mobile in 2019.

Firefox

Posted Dec 20, 2018 14:40 UTC (Thu) by mathstuf (subscriber, #69389) [Link]

> It is easy to accidentally hit Ctrl+Q instead of Ctrl+W when intending to close a tab1

I use Vim bindings, so closing a tab is `x` for me, but when I do accidentally hit C-q, I get a prompt asking for confirmation. I don't know where that setting is off hand, but it does exist.

> After I run apt-get upgrade, Firefox will often crash

On Fedora, I don't see crashes so much as the inability to open new tabs. This is probably due to the multiprocess stuff and a new tab using an executable which is now incompatible. I don't know of a good way to fix this (AFAIK, Chromium multi-process is mediated via `fork` from its zygote process rather than `fork/exec`, so new binaries aren't that much of an issue).

Firefox

Posted Dec 20, 2018 15:00 UTC (Thu) by tao (subscriber, #17563) [Link] (9 responses)

There's an add-on intuitively named "Disable Ctrl+Q and Cmd+Q". I'd recommend it; I'm using it on my machines.

Firefox

Posted Dec 20, 2018 15:11 UTC (Thu) by tao (subscriber, #17563) [Link] (8 responses)

Scratch that. It seems that it no longer works with newer versions of Firefox. I must've managed to avoid pressing Ctrl+Q the last year or so...

Firefox

Posted Dec 21, 2018 7:37 UTC (Fri) by k8to (guest, #15413) [Link] (7 responses)

And this scenario where firefox killed all their own addons is why I am not much interested in Firefox anymore.

None of the browsers are really for user goals at all anymore. That happened a long time ago.

Firefox

Posted Dec 21, 2018 11:36 UTC (Fri) by pizza (subscriber, #46) [Link]

> None of the browsers are really for user goals at all anymore. That happened a long time ago.

If "user goals" are what you truly care about, then even at its worst, Firefox remains vastly superior to its alternatives.

(Granted, there are some FF derivatives out there that may be "better" but if FF itself goes away, so will they..)

Firefox

Posted Dec 21, 2018 19:19 UTC (Fri) by roc (subscriber, #30627) [Link] (5 responses)

The addons model was changed for sound technical reasons.

I can't even imagine the conspiracy-theory explanation that makes dropping XUL addons some kind of evil plot.

Firefox

Posted Dec 21, 2018 21:49 UTC (Fri) by k8to (guest, #15413) [Link] (4 responses)

I'm very familiar with all the many trade-offs that have been made. Sound technical reasons are a common way that engineers screw over users in open source and in corporate development.

However, there's many simple wins that could exist. Any infrastructure that allows users to avoid data loss in textareas now that addons are dead would be a good start. Functionality to make sites more accessible by expanding the box where the text is at the expense of the chrome on all sides of the screen would be not TOO hard to deploy. Safety things like "this domain seems to be constantly changing certs" would be readily implemented but aren't.

Basically the entire effort of enormous amounts of engineering time is spent only on adding developer focused features. That's a strategy for sure, but it's not convincing to me.

Meanwhile a very large amount of engineering time is spent on reorganizing the UI over and over, defeating user learning. There's a good rule of thumb on UI redesigns. If you're making the UI 2x as good or better (how much effort is required to do the common tasks), go ahead and redesign, otherwise it's not worth it. Firefox isn't anywhere near this good maxim. Chrome is doing a better job here, which is a pretty low bar.

Yes, a browser monoculture is bad, but multiple browsers would be better if any of them were showing sanity in the face of these types of things.

Firefox

Posted Dec 21, 2018 22:55 UTC (Fri) by roc (subscriber, #30627) [Link] (3 responses)

> Any infrastructure that allows users to avoid data loss in textareas now that addons are dead would be a good start.

Addons aren't dead and insisting on saying that they are just makes you look foolish. For example there are many WebExtension addons to manage textarea contents, e.g.:
https://addons.mozilla.org/en-US/firefox/addon/formsave/
Took me about five seconds to Google that.

> Functionality to make sites more accessible by expanding the box where the text is at the expense of the chrome on all sides of the screen would be not TOO hard to deploy.

Would be easy in a WebExtensions addon if one doesn't already exist.

> Safety things like "this domain seems to be constantly changing certs" would be readily implemented but aren't.

Maybe your favourite "safety thing" isn't implemented but lots of security work keeps getting done. Better sandboxing for example.

> Basically the entire effort of enormous amounts of engineering time is spent only on adding developer focused features.

That's not true at all. For example lots of work is going into machinery and UI for blocking trackers and other stuff.

It's true that an enormous amount of work is going into Web-developer-facing features (both implementing and standards work), but that's table stakes for Gecko to be a viable independent browser engine, without which the open Web is doomed.

An enormous amount of work goes into performance too, which is the most important user feature.

There's actually not much work going into UI reorganization currently AFAICT. Funnily enough Chrome just revamped their UI to look more like Firefox.

Firefox

Posted Dec 31, 2018 20:38 UTC (Mon) by k8to (guest, #15413) [Link] (2 responses)

The method used to manage text areas involves installing a custom webserver to act as an addon-specific enabler, to execute commands on http request. It's more secure for people to run cobbled together http servers? Surely it would be vastly more secure for the browser to simply have a editor configuration setting.

Suggesting third parties can write extensions to handle pretty common user goals is not terribly compelling now that firefox has broken extension compatability so many times.

You're drawing a very narrow timeline to support your claims. For example, maybe this year maybe the firefox UI hasn't been redesigned. I still don't recognize the UI Firefox gives me today. The experience is wildly inconsistent across platforms (worse than in the past), with highly strange decisions like using a hamburger menu when there's a full menu bar across the screen. If firefox had some consistency with the base platform or itself, and was stable in UI operation for a few more years, then I'd believe there's been a change in priorities.

Firefox

Posted Dec 31, 2018 20:47 UTC (Mon) by Cyberax (✭ supporter ✭, #52523) [Link]

> Suggesting third parties can write extensions to handle pretty common user goals is not terribly compelling now that firefox has broken extension compatability so many times.
Uhm. The new extension API is by design stable and doesn't require plugins to access the inner workings of FireFox.

Firefox

Posted Dec 31, 2018 23:02 UTC (Mon) by pizza (subscriber, #46) [Link]

You want a stable base platform, UI, and plugin API? Try Mozilla Seamonkey. Barely changed for the better part of two decades.

And a market share that's little more than a rounding error of a rounding error. So much to stability mattering.

Firefox

Posted Dec 20, 2018 16:12 UTC (Thu) by excors (subscriber, #95769) [Link] (3 responses)

> It is easy to accidentally hit Ctrl+Q instead of Ctrl+W when intending to close a tab, resulting in the entire browser and all open tabs being closed.

You need to train your fingers by playing multiplayer FPS games in which W is "walk forwards" and Q is "activate rare expensive ability which can kill the whole enemy team, or save your own team, if used correctly; but if you accidentally waste it in the spawn room then every player on the server will think you're very silly and you will be embarrassed". That should teach you pretty quickly.

Alternatively, make sure you have the "show your windows and tabs from last time" mode selected, and don't write long comments directly into web pages (write in a separate text editor then copy-and-paste), so that accidentally quitting is just a mild annoyance for a few seconds until you restart the browser with no significant data loss, followed by happiness when you see how much less RAM and CPU it's using after the restart.

Firefox

Posted Dec 20, 2018 21:19 UTC (Thu) by roc (subscriber, #30627) [Link] (1 responses)

If the Web page doesn't suck then restoring it after close in Firefox should restore any form control state as well.

Firefox

Posted Dec 21, 2018 13:17 UTC (Fri) by excors (subscriber, #95769) [Link]

That's a pretty big "if" :-)

Firefox

Posted Dec 21, 2018 8:58 UTC (Fri) by marcH (subscriber, #57642) [Link]

> don't write long comments directly into web pages (write in a separate text editor then copy-and-paste),

They say emotions good or bad are what trains memory. A lot of pain is for sure what taught me to do this systematically.

As this habit "accidentally" extended to cloud documents, an interesting side-effect is to stop the distraction of starting to pretty the form before the content is mostly ready.

Firefox

Posted Dec 20, 2018 20:00 UTC (Thu) by mcatanzaro (subscriber, #93033) [Link] (2 responses)

Epiphany: still around, and at least capable of remembering your tabs when you hit Ctrl+Q....

Firefox

Posted Dec 20, 2018 20:43 UTC (Thu) by roc (subscriber, #30627) [Link] (1 responses)

Firefox remembers tabs on quit unless you configure that off.

Firefox

Posted Dec 20, 2018 21:34 UTC (Thu) by mcatanzaro (subscriber, #93033) [Link]

So what is the complaint about then... hmm... OK, I see Chrome doesn't respect Ctrl+Q at all. That's pretty wild; you'd think that'd be the one standard shortcut all desktop apps would understand....

Firefox

Posted Dec 20, 2018 20:42 UTC (Thu) by roc (subscriber, #30627) [Link]

I wonder if #2 is a distro issue. Try running a Mozilla build of Firefox and see if it has the same problem.

Firefox

Posted Dec 21, 2018 12:58 UTC (Fri) by RX14 (subscriber, #123970) [Link] (5 responses)

Set browser.showQuitWarning=true and browser.warnOnQuit=true in about:config to solve ctrl-q

The "firefox crashes after an apt-get upgrade" issue is also fixed in firefox 64.

I suggest you try firefox again!

Firefox

Posted Dec 21, 2018 13:00 UTC (Fri) by RX14 (subscriber, #123970) [Link]

Note, you need to disable "restore previous session" in the settings to make the ctrl-q fix work. See https://superuser.com/a/1352295/285546

Firefox

Posted Dec 21, 2018 13:16 UTC (Fri) by excors (subscriber, #95769) [Link] (3 responses)

showQuitWarning was removed (as of Firefox 63, I think): https://bugzilla.mozilla.org/show_bug.cgi?id=1438499#c14 looks like a relevant comment. And the remaining options intentionally don't warn on quitting if you have session restore enabled: https://bugzilla.mozilla.org/show_bug.cgi?id=1438499#c34

Firefox

Posted Dec 21, 2018 15:29 UTC (Fri) by garrison (subscriber, #39220) [Link] (2 responses)

From the link:
Is there a follow-up plan here to add a warning when closing Firefox even with session restore on?

In short: no plan for that.

Reason: Firefox saves everything, so there is no risk of data-loss, and therefor no need to warn.

Seems short-sighted to me. What if I have an incognito window open? It's certainly not coming back after the restore.

Firefox

Posted Dec 24, 2018 18:20 UTC (Mon) by garrison (subscriber, #39220) [Link]

Another issue is that I use awesomewm, and I put a fair amount of cumulative effort into making sure each browser window is associated with the appropriate awesomewm tag(s). Even if all my open Firefox windows and tabs are restored after I accidentally press Ctrl+Q, I still need to go through and manually assign them all to the intended awesomewm tags again. So claiming there is "no risk of data-loss, and therefore no need to warn" is not consistent with my experience.

Firefox

Posted Dec 25, 2018 4:33 UTC (Tue) by garrison (subscriber, #39220) [Link]

Oh interesting. It seems the warning/confirmation I desire has hit master in the past month. Together with the fix of crashing after upgrade (as mentioned elsewhere in this thread, it is fixed in Firefox 64), I may actually be switching to Firefox in 2019. My best guess is that this will land in Firefox 66? Marking my calendar for March 19 to try Firefox again.

Firefox

Posted Dec 28, 2018 2:22 UTC (Fri) by nevets (subscriber, #11875) [Link] (4 responses)

This is the first I heard about the Ctrl-W vs Crtl-Q issue. But then again, I use a Dvorak layout where Q and W are far apart ;-)

Firefox

Posted Dec 28, 2018 15:10 UTC (Fri) by mathstuf (subscriber, #69389) [Link] (2 responses)

C-q staying the same makes sense, but C-w sounds like one of those bindings you want to be scan code based (like A-Tab and A-~) since it isn't a mnemonic.

Firefox

Posted Dec 28, 2018 16:13 UTC (Fri) by halla (subscriber, #14185) [Link] (1 responses)

I am pretty sure the W in Ctrl-W stands for "Window", and in an MDI application it will close a window.

Firefox

Posted Dec 28, 2018 16:27 UTC (Fri) by mathstuf (subscriber, #69389) [Link]

Ah, I guess so. I probably skipped over that solution since "window" isn't a verb :) .

Firefox

Posted Dec 30, 2018 17:41 UTC (Sun) by apoelstra (subscriber, #75205) [Link]

But now Ctrl+V is right next to Ctrl+W, which is even worse! :)

Firefox

Posted Dec 28, 2018 16:45 UTC (Fri) by Lekensteyn (subscriber, #99903) [Link]

I used to have the Disable Ctrl-Q Shortcut extension installed, but this stopped working since Quantum. Since then I always have a tab open with this URL:
data:text/html,<body onbeforeunload=return!0><title>Disable Ctrl-Q
Whenever I accidentally press Ctrl + Q (which has happened a non-zero number of times), it will prompt before closing the page (and by extension, before closing the browser).

Firefox

Posted Dec 28, 2018 18:48 UTC (Fri) by jezuch (subscriber, #52988) [Link]

Chromium used to have a ctrl+shift+q shortcut to close, but apparently this was still too easy to hit so recent releases prompt you to go through the menus instead. Well, whatever, it's not mission critical after all...

(It reminds me of the time when I played Quake using the keyboard and tried to simultaneously shoot (ctrl), strafe (alt) and lower my crosshair (del). This was interpreted by the program as the "quit" command. I decided then I had enough for the day.)

Firefox

Posted Dec 29, 2018 4:54 UTC (Sat) by flussence (guest, #85566) [Link] (3 responses)

Regarding #2, Firefox does a few dirty mmap/IO tricks with its resource files to reduce its runtime RAM usage. E17 is another piece of software doing those things, with similar problems.

For me the crashes usually come at cold startup. It's about a 50/50 chance whether I'll get a browser window or a crash handler window each day.

Firefox

Posted Dec 29, 2018 11:41 UTC (Sat) by halla (subscriber, #14185) [Link] (1 responses)

I'd run a memory checker if I were you, because this is very obviously not normal: something on your system is broken. When I has similar problems, it did turn out to be a rotten memory stick.

Firefox

Posted Dec 31, 2018 5:12 UTC (Mon) by flussence (guest, #85566) [Link]

It sounds that way, but given the rest of the system has no problems compiling itself on a regular basis I doubt it…

Firefox

Posted Jan 3, 2019 12:25 UTC (Thu) by sdalley (subscriber, #18550) [Link]

If it's after cold startup, maybe it's something in the video/graphics stack which isn't initialized properly, and firefox is the first thing to trip over it.

A 2018 retrospective

Posted Dec 20, 2018 23:29 UTC (Thu) by dskoll (subscriber, #1630) [Link] (1 responses)

I've always used Firefox on my desktop boxes. I switched my Android devices to Firefox also. Mobile Firefox is much slower than mobile Chrome, even though desktop Firefox seems about as fast as desktop Chrome.

Nevertheless, I will stick with Firefox because it's too important not to yield complete control to Google.

A 2018 retrospective

Posted Jan 11, 2019 16:40 UTC (Fri) by nix (subscriber, #2304) [Link]

Mobile Firefox is much slower than mobile Chrome
And then you install an adblocker, and mobile Firefox is suddenly blindingly fast because you're not blocking waiting for massive piles of crap on every webpage. (I installed it because I had to: on a 10GiB/month satellite connection you do not want to be downloading 10MiB of useless advertising rubbish and horrible uninteresting autoplaying videos on every other page you visit.)

A 2018 retrospective

Posted Dec 19, 2018 22:59 UTC (Wed) by karkhaz (subscriber, #99844) [Link] (4 responses)

> Perhaps Microsoft's rebasing of its Edge browser on top of the Chromium engine could have been foreseen, but we didn't see it coming.

I predict that Microsoft will administer a blindfold and cigarette to their compiler and replace it with Clang at some point. By 2025, Windows will just be Ubuntu with a start button.

> This innovation resurfaced this year, though, as companies created new licenses intended to increase their incoming revenue from their flagship projects while keeping those projects as something that at least vaguely looks like free software.

I don't remember it being reported here, but Confluent has done a similar thing for KSQL: they created a license that prevents it from being used in Software as a Service products.

https://www.confluent.io/blog/license-changes-confluent-p...

A 2018 retrospective

Posted Dec 19, 2018 23:31 UTC (Wed) by mpr22 (subscriber, #60784) [Link]

> they created a license that prevents it from being used in Software as a Service products.

My reading of that article is that you can use KSQL *in* a SaaS product, but you can't offer KSQL *itself* as a SaaS product.

A 2018 retrospective

Posted Dec 20, 2018 8:54 UTC (Thu) by voltagex (guest, #86296) [Link]

Is there an objective comparison between Clang and whatever the MS C compiler is called? Microsoft's other big compiler, Rosyln, is already open source.

A 2018 retrospective

Posted Dec 20, 2018 17:03 UTC (Thu) by iabervon (subscriber, #722) [Link] (1 responses)

If they replace parts individually, Windows is more likely to end up as a new Linux distro with its own very different behavior, rather than actually being related to Ubuntu. If you separate behavior into policy and mechanism, Microsoft has been adopting a lot of code that does mechanism, and keeping the policy their own, and I think that is probably a good way of providing a system that conforms to the long history users have built up of expectations as to how to use Windows while also running the best implementations available.

A 2018 retrospective

Posted Dec 21, 2018 9:08 UTC (Fri) by marcH (subscriber, #57642) [Link]

> Windows is more likely to end up as a new Linux distro with its own very different behavior, rather than actually being related to Ubuntu. If you separate behavior into policy and mechanism

I don't have a clue what that means. On the other hand I use Microsoft's subsystem for Linux all the time and I can attest that: 1) it is outstanding work 2) it doesn't really care which Linux distro you use - no more than Linux containers do.

A 2018 retrospective

Posted Dec 20, 2018 0:14 UTC (Thu) by klindsay (guest, #7459) [Link] (1 responses)

Is the lack of mention of Microsoft's acquisition of github intentional, perhaps for being out of scope, or an oversight?

A 2018 retrospective

Posted Dec 20, 2018 18:15 UTC (Thu) by epa (subscriber, #39769) [Link]

I think the bigger change was when Microsoft started publishing code on Github. That happened a few years ago.

A 2018 retrospective

Posted Dec 20, 2018 3:17 UTC (Thu) by kjp (guest, #39639) [Link] (4 responses)

> are still running Python 2 applications are generally thinking seriously about moving forward.

As someone pained with 50K LOC of python2, yeah I'm thinking about moving "forward" to C# / .Net core. Honestly, python has been terrible for large codebases anyway, and a move would have been good even without the stupid python 2/3 split. But I'm _very_ glad I didn't waste time converting to python 3. Also, RHEL 8 will support python 2 for 10 more years anyway...

Also notable mentions for 2018:

- Oracle "clarifying" licensing for Java vs OpenJDK (which is honestly fine, btw).
- Amazon supporting Java for free (Corretto)

A 2018 retrospective

Posted Dec 20, 2018 3:45 UTC (Thu) by kjp (guest, #39639) [Link]

n/m, RHEL 8 says python 2 will have a "shorter" life cycle.

A 2018 retrospective

Posted Dec 20, 2018 9:57 UTC (Thu) by smurf (subscriber, #17840) [Link] (2 responses)

Well … let's just say that this experience is not universal. We're quite happy with our 100+K lines of Python3.

A 2018 retrospective

Posted Dec 20, 2018 14:43 UTC (Thu) by mathstuf (subscriber, #69389) [Link]

Is that a single repo or a series of repos split into logical libraries? The former I think is less tenable than with proper library splitting. Lots more overhead, but also more thought goes into things when the API boundaries are very clear.

A 2018 retrospective

Posted Dec 20, 2018 18:26 UTC (Thu) by kjp (guest, #39639) [Link]

Are you using mypy / type hints? PS We also have problems with the GIL vs high concurrency.

A 2018 retrospective

Posted Dec 20, 2018 5:46 UTC (Thu) by wblew (subscriber, #39088) [Link]

Merry Christmas! To the entire LWN staff, their families, and their friends.

May the New Year bring the best, to all of you and yours.

A 2018 retrospective

Posted Dec 20, 2018 6:33 UTC (Thu) by mtaht (guest, #11087) [Link] (1 responses)

FQ_codel on OSX. Made. My. Year. It was great to get it running on nearly everything linux derived, but every time I get a bit down about the open source and standardization processes... I just

daves-MacBook-Air-3:~ d$ netstat -I en0 -qq

en0:
[ sched: FQ_CODEL qlength: 0/128 ]
[ pkts: 0 bytes: 0 dropped pkts: 1404 bytes: 452387 ]

A 2018 retrospective

Posted Dec 21, 2018 9:02 UTC (Fri) by marcH (subscriber, #57642) [Link]

I think it was before 2018 but I still cannot believe how fast and easy it was to apply this HOWTO to my router and workaround the bufferbloat in my cable modem:

https://openwrt.org/docs/guide-user/network/traffic-shapi...

Thanks for all the hard work, well done.

A 2018 retrospective

Posted Dec 28, 2018 22:09 UTC (Fri) by buck (subscriber, #55985) [Link]

The Linus hiatus and its offshoots could plausibly be considered as instances of the open source community doing some introspection, if only in regards to the standards it sets for its culture and not necessarily for the standards that its products set for the world, though one can imagine that the former will rub off on the latter (though, as you like to say, "how, it remains to be seen"). The community/contributior guidelines/standards/codes of conduct that open source projects adopt, to the extent that they signal a cultural shift, is significant in and of itself, though, insofar as the open source development community is a prominent Internet "commons" that can be a beacon for online communities impregnable to subversion by the malefactors riving the "social network" fabric with controversy and scandal, by contrast.

The cloud provider compromise prediction could be validated if Bloomberg's Super Micro story is somehow vindicated, though everybody but Bloomberg is probably rooting against you on that one.


Copyright © 2018, Eklektix, Inc.
This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds