speedy je napisao/la:
inace kad bi to bilo tako da svatko tko koristi open source MORA i vratit nesto pa gdje bi stigli?? a sto se "zadrtosti" zajednice tice,,,,,, ono de mi sam reci da je MS zajednica nes bolja?? svi su zadrti na svoj nacin i to se nece samo tako promjenit
Pa ne mora vratiti nista, ali mnei bi bilo neugodno biti pijavica koja se kune da to sta sisa je najbolje na svijetu i promictai neku slobodu i superiornost, bas me zanima kad bi win bili besplatni koliko bi korisnika linuxsa bilo!
MS zajednica ima vecu slobodu od bilo koje druge:
Dostupno im je 95 i vise % opensource softwarea!
Dostupan im je sav closed source!
Dostupan im je sav freware!
Dostupan im je sav proprietary software!
Evo jos malo sta sam nasao po netu:
"The problem with Linux is NOT the packages, it is the fact that trying to develop for Linux is like trying to hit a dartboard with a live bumblebee," Slashdot blogger hairyfeet told LinuxInsider via email.
To illustrate: "A friend of mine brought over a scanner the other day," hairyfeet recounted. "It was released nearly 9 years ago, but you know what? It works in XP SP3. That is because the driver for Win2K -- released nearly 9 years ago -- still worked. I run games and programs from the Win98 era. That is 11 years and it still works on XP SP3.
"Now compare that to Linux," hairyfeet added. "Does anyone honestly think they can use a driver from even 3 years ago in Linux? Or that getting a program from even 5 years ago working wouldn't be an exercise in frustration?"
That is why Linux "isn't getting market share," hairyfeet explained. "It isn't the packages, it isn't the lack of exposure, it is simply the fact that hardware manufacturers by and large refuse to support it."
There's also good reason for that refusal, he asserted. "It is because Linux simply isn't stable as a platform, and if it keeps going like this it never will be.
"If I am a hardware manufacturer, competing with all the other manufacturers, I have two choices: I can write three drivers -- Win98/ME, Win2K/XP and WinVista/7 -- and have every single Windows OS covered from 1998 to 2011 at least," he said. "If I write for Linux, exactly WHICH Linux? Red Hat or Debian based? Stable, testing, long term support? How long will my customers be able to use the driver I release today before it no longer functions?"
In short, "If Linux is going to get the crucial hardware manufacturers to support it, then like Windows they need to be able to release a driver today and have it work years and years into the future without maintenance," he concluded. "To truly succeed, Linux needs to have a truly stable long term underlying framework that the manufacturers can target."
What should be done to "fix" Linux?
"It really depends on which side of the Linux divide you are on," Slashdot blogger hairyfeet told LinuxInsider. "There seems to be a bit of a power struggle going on between the hacker types, who like Linux being heavy on CLI and like things the way they are, and the usability types, who realize that to gain market share Linux will have to move away from being so CLI-heavy, as have OS X and Windows."
Speaking from "the usability side of the fence," hairyfeet ticked off a few requirements:
1. Easy privilege management. "There needs to be a simple, GUI-based way to elevate privileges, similar to the 'Runas' that you have in Windows," he said. "Also, if you can't actually use it, don't allow it!"
2. A stable framework to target. "There needs to be a stable core framework that is supported across ALL distros and that anyone can write their drivers and apps to," hairyfeet explained. "Companies like to write once and forget about it. After all, who wants to support last year's widget when you need to be writing drivers for this cycle?"
3. An NDIS style wrapper for all-in-one printers and webcams -- "Lexmark in particular," he said. "Ask any Wal-Mart which are their No. 1 sellers in printers and all-in-ones, and you will have more Lexmark in the top 5 than the other companies combined. Yet they still have virtually zero support in Linux. Since these 'Winprinters' are simply calling on the Windows GDI to do the heavy lifting, there shouldn't be any reason why a wrapper style driver couldn't be written. If the Winmodem could be defeated, so can the Winprinter."
4. The death of CLI. "For the home user, the CLI is simply unacceptable in ANY form," he asserted. "It is too foreign, requires the memorization of too many strange Unix commands, and is frankly simply too powerful. It is a lot harder to break something with checkboxes and radio buttons than it is with a mistyped CLI command."