Tsikbal: from my perspective

One would think that chipsets manufactures would benefit greatly by supporting all three major operating systems out there. Yet, you find out that Nvidia and ATI chipsets drivers are lacking on Linux. Which is ratter baffling, since it would seem logical that supporting drivers for Linux would be beneficial to them in order to sell more chipsets. Linux might have a small share of the market, yet when you see the number of people and companies who run Linux on their systems it starts to make a lot of sense to support Linux. And if they actually made the Linux drivers open source as the OS itself, they could rely more on the Linux developer community to maintain and develop the drivers needed for the chipsets to be run on Linux. Not only that, some of the developments that could be ported to other OS because they give more stability or security for benefit to a wider sector of users. If chipset manufactures really collaborated with the Linux community, and the wider FLOS...

I like how FLOSS projects allow people to come together to build communities around projects that they want to work on because they believe in them. This turns out far better software, because individuals are allowed to contribute as the can. They can either contribute their time and expertise to work directly work on the code or help manage the project, or contributing money is an option if the individual doesn't have the skills or time to contribute to the project. There is also a possibility to help by reporting the bugs that you find along the way, either by filing the report manually or using an automated tool to do so. This facility to be able to create communities to work on a certain project, or to create either a new project or a fork of an exiting one, give the FLOSS community its unique flavor and strengths. There are several projects at a time aiming to better, or solve, a particular problem or issue, making it progress faster and more since you have people...

It's somewhat sad to see how many tech commentators don't seem to get that Linux is the core than runs all the various distros out there. In a sense, Linux is the engine that powers all the distros, while each distro picks what parts will it use to give the usability and looks the distro's team is looking for. That's why there are several user interfaces, like GNOME, Unity, and KDE, from which distros can pick the one they feel is right to get their flavor of Linux to work and look a certain way. To some extend, the development of the Linux core and the different user interfaces are on separate tracks. Mainly because Linux interacts with the machine itself, and the user interface interacts with the person using the computer. So, their development has different targets to hit. But, that's where Linux sets itself apart. Since each distro has the choice to use any of the different users interfaces out there, the user get a real choice of what suits his com...

Linus Torvalds, the creator of Linux, was awarded today Finland's Millennium Technology Prize. This prize is awarded every second year, and it's awarded to life-enhancing technological innovations. For me that Linus Torvalds was awarded with the Millennium Technology Prize is a well deserved recognition. After all, the operating system that he created not only powers the Internet and some of the most important stock exchanges in the world. It also powers the supercomputers on which most of modern scientific research is carried out. This way, Linus Torvalds' OS is on the forefront of the things that contribute to the betterment of our quality of life. And not only that, it has proven that free and open source software is a legitimate development platform on which people can work together and contribute to create something larger than the sum of its parts. Personally as a Linux users, it makes me proud that the who created the core of the OS I use and love was re...

I wonder why people runs to walled gardens, and convinces themselves that there is no better way to do things other than they way fed to them by the owner of the walled garden. Even though they know at some level that they are giving up many freedoms, they gladly do it just to have the most pretty gadget on the blog. They'll anything to comply to what the owner of the walled garden wants them to comply with, even when they don't fully understand what they are giving up to be part of the walled garden. What bothers me the most of this system is the fact that you have to give any freedom to even modify, or install, third party apps that aren't approved to begin with by the vendor by default. The choice of whether doing it or not is taken from the user without the ability to opt out without voiding the warranty, or being liable of being taken action against by the vendor. The truth is that walled gardens are desirable on only a few cases, and for a minority of use...

One would think that in time, software companies keep trying to keep people from at least freely studying the source code of their products. The benefits from this far outweigh any concern, and most of the benefits would be for the users themselves. Users would get better software with less cost and development time, than with the current model. Not only that, users would have the opportunity to implement code that better suits their needs if there is a need of doing so. Locking the source code doesn't lock the code itself, it also locks the user options to have the best software the user could possibly have. Since there is no way to know how the source code functions, there is no way for the user to know if there is a way to make the software a better suit for what the user needs the software for. Not only that, there is no way to check if the software does what the vendor says it does and nothing more. The user has to blindly trust that there is no malicious code, or...

One of the worst thing that comes out of not being able to see how software works from the inside, is that it becomes harder to understand how it works. Not only that, it prevents to make modifications to make it work on how the users want it or to make another program all together. What's more, it prevents any work to make any software better. In order to understand how a certain piece of software works, one need to be able to see how it's put together and how those parts interact with each other. Without that know how it becomes impossible to study and learn how it works, therefore it's not possible to work to improve or modify it by any one that doesn't have access to the source code. This situation puts the users on the losing side, since they completely depend on a third party to keep the software not only current and safe from attacks. They depend on that third party to keep the software available to them at any moment, and have to trust that it doesn...

The tactics that many tech companies use to handle to try to stop competitors, and how they lock the devices or software they sell. It's sad to see that in order to keep successful products from competing with theirs, many companies use patents and copyright law to try to take them out of the market. Instead of coming out with something better and take it to the market for the people to decide what they want to buy for themselves, it has come an almost standard practice to have the courts to decide what options should the people find in the market. The moment laws set limits to what the people can find on the market place, other than on safety and health grounds, they get in the way of having a healthy market with the options that the people are willing to sustain. At the end, the market is the one who should have the last word on what is consumed and it's value. Companies and governments have no business doing so, their business is making the choices that should b...

It's sad that tech companies are using patents in order to keep competitors from doing business. To make matter worse, companies that are known to be leading innovators are the ones that engage on patent wars the most often. The current system seem to be putting a premium on those who can defend the current state of things, instead of putting that premium on actually brining forth innovative products to the marketplace. Because of this, is no wonder than in some areas innovation seem to be at a standstill. The threat of being closed by bigger players with deeper pockets to play the system, keeps many small innovative players from even trying to put their products out. The system needs to balance things. There should be protections to keep people from taking ideas and not compensate the one who originally put it out, while making it easy enough to use ideas on different products. Laws need to benefit the most people, and not protect just a narrow band of groups. Thi...

Going after people that tinker with products has been proven to be impossible. They always find a way to make whatever product they choose to tinker with, work in ways that the original manufacturer or producer never intended it to do. In some cases, they actually make it work better than it did out do the box. So, why waste resources going after those tinkerers when they could be used of a source of knowledge and hands on experience to make those products better. The value that they bring to the table, is the insight they have to see how they can make things work better. Or, to add functionalities that for one reason or another the original creator didn't think of. Shooting them down is a case of shortsightedness. Tinkerers are an asset, since they have all what it's needed to help you accelerate the development of your product in a much faster way. And the feedback they give back is, more often than not, more useful than the feedback of the average user. Not ...

I can't find a reasonable explanation on why software companies won't open themselves, and seek to use the experience or expertise of the people that form the community of users. They are losing more than what they could be winning by keeping them out. Not only on profits, but most importantly on expertise that they could tap on to make breakthroughs that are difficult to get from people working in the company itself. Mainly because people on the outside have a different view, and can bring it to the table. Users can see things than developers inside can't, since users have a completely different viewpoint. From it, they can see things that insiders can't just because they are in a position to actually see that part of the work flow. Not interacting with the communities that use your software can lead you too loose vital insight on how to better develop it. Instead of trying to cut people from making any change to the software, be the one who leads those ef...