Tuesday, October 30, 2012

Fragmentation

More evidence of cluelessness. In a weird late night rage, against my better judgement, I found myself reading this article over at Phoronix, about how Ubuntu is thinking about an SDK.

A proper Ubuntu Software Development Kit would be nice for developers targeting Ubuntu SDK with a standard set of libraries/interfaces that are stable, but this isn't likely to please non-Ubuntu Linux users. This SDK that Canonical will look to push to application developers will likely be centered just around Ubuntu's needs and not the Linux ecosystem as a whole with other Linux distributions not being a focus, which could potentially lead to greater Linux desktop fragmentation.
Anyone who's been around long enough knows that any time some one of people tries to move the ball forward by doing something different, everyone thinks it's their right to crap on them. Worrying about fragmentation is the fucking dumbest thing you could do at this particular moment.

Desktop Linux is already heavily fragmented. The benefit of potentially getting major app developers to sign up far outweighs any incremental fragmentation this might create. In fact, if this actually works, I predict that suddenly every other freetard distriution will offer SDK compatibility, and then spew on about how open source is great because it allows all kinds of variation while keeping compatibility. In other words, you will see someone writing a blog post about how you can run Steam in XMonad. Because that's totally relevant, and it's the one thing that desktop Linux is missing.

It's not about how many incompatible choices there are, it's about how your users are distributed. Nobody gives a shit about how Ubuntu creating a stable SDK makes life harder for some crack-laced minty fresh Ubuntu derivative. Ubuntu already has a lot of users, if not the majority of desktop Linux users. That means this move could make desktop Linux better for the majority of users. If some big ISV signs on, it could mean that there are now 5x more Ubuntu users, making it by far the biggest majority. When Ubuntu grows the market by 5x, and owns 80% of it, the Linux desktop userbase is now less fragmented than where it started.

Fragmentation doesn't mean shit when the market is so small. Freetards argue about how things are fragmented for the 1%. Well, when you only have 1%, the problem isn't that you're too fragmented. The problem is you're not doing the right things to grow beyond 1%. Fragmentation is a problem for Android. Not desktop Linux.

Sunday, October 21, 2012

skunkworks

It appears as if good ol' Mr. Shuttleworth has finally seen the light.

The skunkworks approach has its detractors. We’ve tried it both ways, and in the end, figured out that critics will be critics whether you discuss an idea with them in advance or not.
In other words: freetards will be freetards.

Friday, July 27, 2012

Your free software website, for dummies

There is a certain art to buidling a website for your open source project.Before you create your own, make sure you know and follow the rules. You’ll thank me later.

It’s simple, really. It’s all about the first impression.

In particular, your site’s first page must communicate the following points:


  • It must mention the fact that your software is open source or free, or whatever bastardly combination of the two, even before explaining what your software does. Extra points if you mention exactly which license you use, and if you help educate the masses about how speech and beer are in fact, different worldly entities. Studies show that if your users do not understand exactly whether binary linking is allowed with your software, they will not use it.
  • If the name of your software is an acronym, you must explain what the acronym stands for, with even more confusing terms.
  • You must note which programming language your software is coded in, because that’s the first thing that any potential user will care about.
  • You must note how your program is modularized, and anyone can add modules and customize it to actually do what it was supposed to just do in the first place.
  • You must mention that your software is localized. Because, crappy software is somehow better when it speaks your language.
  • You must immediately jump into a “recent announcements” section, which has items that only the 3 developers on your project would possibly understand or derive any value from. Extra points if you have an embedded commit log.
  • You must mention that your software runs on at least 5 irrelevant platforms.
  • A personal favor, please note whether your application is multithreaded. I only download multithreaded software.
  • Refer to your application as a framework. Since all good great applications are framework. Firefox is a browsing framework. Gimp is a image processing framework. iTunes is a music listening framework. See?
  • Don’t ever call it an installer. Call it a binary distribution. Better yet, make sure the only way to install is through github. Make sure your github page offers no clues on what to do once you’re there.

There. Now you’re equipped to go create a site can compete with the best of ‘em. You’re welcome.

Saturday, March 17, 2012

Pester mingo


Sigh. About 7 years too late, buddy.

Tuesday, March 13, 2012

Ahahahaha

http://arstechnica.com/gadgets/news/2012/03/idealism-vs-pragmatism-mozilla-debates-supporting-h264-video-playback.ars


Dear Mozilla. Your users don't care. Please make a useful browser. kbyethx.

Wednesday, February 15, 2012

DBus! It's Evil!


So, please support choice and freedom by implementing programs the right way instead of the Linux/Gnome/DBus way.
Oh boy.

http://blog.ngas.ch/archives/2011/12/13/the_destructive_desktop__mdash_linux_in_trouble/index.html