Interview with Linus Torvalds

Well, historically, the most important lesson from Microsoft - and one they themselves seem to have forgotten - is simply “Give your customers what they want”.

I think the reason Microsoft was so successful was that they filled a niche with some very basic technology (and in this case, early on, that basic technology was literally the BASIC language - that’s how they largely got started), and they sold it cheap and made it “good enough”. They didn’t play games with the customer.

Of course, that seems to have changed. A lot about the last few years of Microsoft seems to very much be playing games with customers: their licensing and what, seven different “versions” of Vista, and all the DRM crap they are trying to push on their customers are not actually what anybody wants.

So Microsoft has always been good about marketing and selling, and their strong hold on the market has also caused them to become a standardized platform. That’s generally all good for customers. They’ve left some of that behind (now they are trying to splinter their market on purpose with Vista and pushing DirectX 10 only on the new platform, for example), but I think their historical successes are worth looking at.



Polish National Interoperability Framework promotes Open Standards


standardy.org | Koalicja na Rzecz Otwartych Standardów
(Coalition for Open Standards)

C# 3.0 - The Evolution Of LINQ

The Evolution Of LINQ And Its Impact On The Design Of C#

Common roadblocks to Linux adoption, Demystified


Interesting introductory links from the article:

Slapt-get - package manager for Slackware

Introductory article to slapt-get:
(article in Polish)

Home page for slapt-get, gslapt and slapt-update-notifier:


Why I am not going to use Slackware - yet

Out of curiosity I installed Slackware 12.0 today. Somehow I haven't really liked it.

The truth about pkgtool is not that it doesn't exist, but that it doesn't do any dependency checking

This is not to say that Slackware packages don't have dependencies, but rather that its package manager doesn't check for them. Dependency management is left up to the sysadmin, and that's the way we like it.

But I don't like it - personally I prefer the Debian package management.

So many things to do manually - when I know better ways to spend my time...

Slackware really got better recently with version 12. It has both good and bad characteristics:
  • 2.6.21 kernel (not to say I run on 2.6 line for three years already)
  • still uses LILO by default (I prefer GRUB, really)
  • the installer looks dated
  • and the overall feel is that if I had no previous experience with Linux, I think I'd be lost
  • default package management is awful, even Gentoo has a better approach
So no plain vanilla Slackware for me now. I will try Zenwalk Linux instead.


Developer.com - Project Management Articles


OpenOffice.org API Tutorial

A useful feature for many business applications is functionality
allowing the user to generate reports from data in an application.
Spreadsheets are ideal for this purpose. Not only does a spreadsheet
lay data out in a structured, scanable format, but it also gives the
user the opportunity to quickly and efficiently perform calculations
on data. As it happens, the OpenOffice.org API exposes a very wide
range of classes and methods that let you, the developer, integrate
the OpenOffice.org spreadsheet application, called Calc, into your
application. A simple click of a button in an application can start
up OpenOffice.org and transfer the application's data to a
customized spreadsheet.



Choosing the Right Architecture - eBook

Choosing the Right Architecture: What It Means for You and Your Business
This custom eBook from DevX and IBM Rational explains why choosing the correct architecture early in your development process is essential for success - both for your business and for you, personally, as a developer.