Profile cover photo
Profile photo
Joachim Noreiko
Joachim Noreiko's posts

Post has attachment

Post has shared content
I knew it was hideously expensive, but didn't think it was THAT hideously expensive. Via +Robin Clarke.

Post has attachment
Finally found a decent guide to rooting my android.

Post has shared content
Seen on, of course.
Technology: What ails the Linux desktop? Part I.

The basic failure of the free Linux desktop is that it's, perversely, not free enough.

There's been a string of Linux desktop quality problems, specific incidents reported by +Linas Vepstas , +Jon Masters , +Linus Torvalds and others, and reading the related G+ discussions made me aware that many OSS developers don't realize what a deep hole we are in.

The desktop Linux suckage we are seeing today - on basically all the major Linux distributions - are the final symptoms of mistakes made 10-20 years ago - the death cries of a platform.

Desktop Linux distributions are trying to "own" 20 thousand application packages consisting of over a billion lines of code and have created parallel, mostly closed ecosystems around them. The typical update latency for an app is weeks for security fixes (sometimes months) and months (sometimes years) for major features. They are centrally planned, hierarchical organizations instead of distributed, democratic free societies.

What did the (mostly closed source) competition do? It went into the exact opposite direction: Apple/iOS and Google/Android consist of around a hundred tightly integrated core packages only, managed as a single well-focused project. Those are developed and QA-ed with 10 times the intensity of the 10,000 packages that Linux distributions control. It is a lot easier to QA 10 million lines of code than to QA 1000 million lines of code.

To provide variety and utility to users they instead opened up the platform to third party apps and made sure this outsourcing process works smoothly: most new packages are added with a few days of latency (at most a few weeks), app updates are pushed with hours of latency (at most a few days) - basically it goes as fast as the application project wishes to push it. There's very little practical restrictions on the apps - they can enter the marketplace almost automatically.

In contrast to that, for a new package to enter the major Linux desktop projects needs many months of needless bureaucracy and often politics.

As a result the iOS and Android platforms were able to grow to hundreds of thousands of applications and will probably scale fine beyond a million of apps.

(Yes, we all heard of the cases where Apple or Google banned an app. Don't listen to what they say but see what they do: there's literally hundreds of thousands of apps on both of the big app markets - they are, for all practical purposes, free marketplaces from the user's point of view.)

The Linux package management method system works reasonably well in the enterprise (which is a hierarchical, centrally planned organization in most cases), but desktop Linux on the other hand stopped scaling 10 years ago, at the 1000 packages limit...

Desktop Linux users are, naturally, voting with their feet: they prefer an open marketplace over (from their perspective) micro-managed, closed and low quality Linux desktop distributions.

This is Part I of a larger post. You can find the second post here, which talks about what I think the solution to these problems would be:

Post has attachment
Might actually give iTerm another try if this is possible. (And to hardcode geeks who don't even know about this: explore your UI!)

Post has attachment

Post has attachment

I finally took the plunge and reset my Firefox profile. The result is impressive: much quicker to launch, and feels faster throughout. But while the documentation on the procedure warns you that not everything is transferred to the new profile, it omits among other things that your preferences (such as your home page) get zapped. It's a good idea to go digging in your original profile folder for certain important bits. Here's what I retrieved:
- mimeTypes.rdf: Download actions.
- cert8.db: site security settings.
- content-prefs.sqlite, permissions.sqlite: site-specific permissions, such as pop-ups.
- localstore.rdf: toolbar settings.
- prefs.js: All the other little preferences. This may be full of cruft too though, so it's probably best to copy and paste selected lines from the old file to the new, with Firefox closed of course.

There's also the userChrome.css and userContent.css files, in the chrome folder within the profile. I had a look in those and found a few customizations I'd made over the years, mostly to turn off annoying CSS in specific sites.

Save current work before you start tidying up and making clean commits: git co -b yay-it-works; git add .; git commit -m 'yay it works'; git co [original]; git merge --squash yay-it-works;

I heard there's an upgrade?
Wait while more posts are being loaded