What skills do you use with your library job? How useful was the technological stuff you learned in everyday library life? Also, asking as one who is thinking of doing the same, what school did you go to?
I agree completely. There's the ones who know everything about Linux history, the distros, and the ones that have wet dreams about it at night. Then there's people like me six months ago, who just enter and want to explore it. And then there's Joe Shmo.
Joe sees some of the geeks yelling and saying they're not welcome, but then get's welcomed by Lycoris, Lindows, etc. Then they have to make a choice between those, and etc. By this point, they'll either let M$ run all over them with their software and licensing fees or go Mac. There's too much confusion, too many people unwilling to change the way they look at Linux. In order to see the M$ 'Revolution' through, everyone has to be on the same team, yet there's still room for different approaches (the navy is to the army as the server is to the desktop). sorry, corny, I know.
Thank you for your intelligent observation about my post.
I've tried both RH and Mandrake, thank you. I know they automatically configure. However, my machine, for whatever reason, did not like Red Hat at all. If I was an experienced Ford Mechanic, I could get under the hood and figure out the problem. However, I'm a relative newbie and I'm speaking for the people who want to get in the car and drive. Sure, I know you have to maintain it and put some work into it (still on the car analogy), but generallly it works. Lycoris worked like a charm for me. Red Hat didn't, and I won't know why until I spend some quality time with it or have someone look at it. That's the market Lycoris is shooting for.
By automatically blasting me from your high place as linux experts, you drown out and turn away millions of people who I spoke for who would consider leaving M$.
For many linux junkies and whatnot, Red Hat
and Mandrake seem really easy to configure
and whatnot. The only problem is that most
users don't want to configure their system. Even these two distros seem hard.
All users want is applications that will work
and fairly compatible with everyone else.
They want the OS to automatically configure
everything. Lycoris does that, and allows you
to play solitare during setup. Most desktop users
don't use Win2000 or NT, they use 98 or XP
Home. They automatically configure your system
in minutes. Joe Shmo doesn't want any hassle or have to think about his computer. He wants to put the CD in, hit a few buttons, and w/in 30 minutes have a nice desktop where he can work. Users don't want to take a week to configure their system, for they could care less. It's a tool, not a toy. Lycoris is easier to setup than Microsoft products and most other distros out there.
Yes there's problems with Lycoris, but it's a step in the right direction if linux has any hope undermining M$ in the desktop market.
True, but at what point does the industry turn around and follow this mantra? Can it turn around and develop a simple, effective product, or are we too far down the spiral toward chaos?
The article asks why no one is suing these companies for bad products, yet answers itself: The customers are demanding newer products/features/gizmos. Another example the article gives is that like mechanical/electrical engineering, developers constantly refine their product. Until customers priorities are re-focused, the resources of software companies will focus on refining the features/gizmos rather than the stability and quality.
Slashdot Mirror
No, they'll make the spammer wear funny clothes and put them on the flag to shame them.
What skills do you use with your library job? How useful was the technological stuff you learned in everyday library life? Also, asking as one who is thinking of doing the same, what school did you go to?
Joe sees some of the geeks yelling and saying they're not welcome, but then get's welcomed by Lycoris, Lindows, etc. Then they have to make a choice between those, and etc. By this point, they'll either let M$ run all over them with their software and licensing fees or go Mac. There's too much confusion, too many people unwilling to change the way they look at Linux. In order to see the M$ 'Revolution' through, everyone has to be on the same team, yet there's still room for different approaches (the navy is to the army as the server is to the desktop). sorry, corny, I know.
I've tried both RH and Mandrake, thank you. I know they automatically configure. However, my machine, for whatever reason, did not like Red Hat at all. If I was an experienced Ford Mechanic, I could get under the hood and figure out the problem. However, I'm a relative newbie and I'm speaking for the people who want to get in the car and drive. Sure, I know you have to maintain it and put some work into it (still on the car analogy), but generallly it works. Lycoris worked like a charm for me. Red Hat didn't, and I won't know why until I spend some quality time with it or have someone look at it. That's the market Lycoris is shooting for.
By automatically blasting me from your high place as linux experts, you drown out and turn away millions of people who I spoke for who would consider leaving M$.
They want the OS to automatically configure everything. Lycoris does that, and allows you to play solitare during setup. Most desktop users don't use Win2000 or NT, they use 98 or XP Home. They automatically configure your system in minutes. Joe Shmo doesn't want any hassle or have to think about his computer. He wants to put the CD in, hit a few buttons, and w/in 30 minutes have a nice desktop where he can work. Users don't want to take a week to configure their system, for they could care less. It's a tool, not a toy. Lycoris is easier to setup than Microsoft products and most other distros out there.
Yes there's problems with Lycoris, but it's a step in the right direction if linux has any hope undermining M$ in the desktop market.
The article asks why no one is suing these companies for bad products, yet answers itself: The customers are demanding newer products/features/gizmos. Another example the article gives is that like mechanical/electrical engineering, developers constantly refine their product. Until customers priorities are re-focused, the resources of software companies will focus on refining the features/gizmos rather than the stability and quality.