OK. I'm really worked up now. The statement above is so anti-geek I don't even know how to deal with it.
For example:
Car geeks build them from parts in their garage on the weekend.
Audio geeks spend years building their audio set-up.
Electronics geeks build robots in their spare time.
Computer geeks write scripts, compile stuff, delve into the lowest parts of the computer, and just generally do stuff that "humans" don't do.
Geeks aren't "human" (in the sense of the average human being talked about). That's why they're called geeks, shunned, and have a reputation for not getting laid. I embrace my geekiness. I come to Slashdot to be with fellow geeks.
Is Slashdot now a site for mere "enthusiasts?" Instead of "Guy installs Linux on calculator watch" articles, are we going to start seeing "How to use your calculator watch the way it was meant to be used" articles?
Not trying to bash Ubuntu, but that "coherent interface all the way through" is Gnome, not Ubuntu. Gnome's Human Interface Guidelines (HIGs) are detailed and applications which want to become part of the desktop have to conform. That's the biggest selling point of Gnome, in my opinion: the concepts are carried through everywhere.
Sorry guys, us mortals dont know how to run scripts and compile our own builds.
I've see this kind of comment more and more on Slashdot over the last few years. When did the average Slash user stop being able to do geeky stuff on his/her computer?
Why would you read Slashdot unless you were a hardcore geek?
I don't think so. He needs at least a year and a half (6/08-1/10) to budget for his media center. If he's a shill, he's certainly not doing a good job. Apparently the cost of Vista + the required hardware to run it well is just too much for him to handle. I build media stuff out of spare parts or with more expensive but tiny MBs. Geexbox has extremely modest requirements, though.
About twenty years ago (in the roaring 80s), I overheard some manager who was taking a weekend MBA program on the phone to someone else in his company. The manager was discussing how to legally lay off everyone over 50 and pay the severance out of the pension fund.
Uh... I guess I wasn't clear. I didn't mean to imply that NVidia produced the WRT-series router. I just didn't really want to give Linksys credit as a company since they weren't very good community members when releasing the routers. I wanted to make the two obvious by saying "Other notables," but it wasn't, I guess. Sorry about that.
I meant that you can't "partner with Linux" in the same way that you partner with MS. Sure, you can partner with individual projects, but that's not the same thing.
I'm working on a Debian Lenny preseed file particularly for old computers with 128-256MB RAM. Most 6-8 year old laptops fall in this category. Basically, it sets up an OpenBox session with all the necessary codecs and plugins out of the box. Warning: it's completely destructive. Preseeds for 256-512, 512-1GB, and 1GB+ should appear soon.
Why the requirement for the maker to be in the consumer sector? Even given that restriction, I'd argue that both Via and Intel have increased their market penetration in the low-end market by supporting Linux for their integrated graphics cards (yes, I know that Chrome sucks). They basically created the opportunity for the EeePC to exist. Most other low-end linux appliances use integrated graphics, too.
Other notables... Nvidia has had a lock on the Linux market for years because of their support. The WRT line with Linux support made that router long outlive its normal market time.
Is that enough for you? No? Then take away the silly consumer sector requirement and I'll add fifty more.
Finally, there's no way to "partner" with Linux. Either you support it (at some level) or you don't. Who would you partner with?
Ummm... try leaving out the developers' names in your advertising when using some BSD-licensed software and you'll get in the same boat. The authors there require attribution. If you don't give it to them, they'll come after you in exactly the same way.
That's why the original saying was "Eat your cake and have it, too," meaning once you eat your cake, you no longer have it and are upset like a two-year old. Adults realize that you have to choose.
Wow, Dr. Smithy, this comment and the one below are so antagonistic and insincere that I actually believe you're trolling. Still, I'll explain what you "don't get."
Windows XP set up the default user as an administrator with elevated privileges by default. Since few users have more than one account,
They have complete access to their entire system.
The developer probably has complete access to the system as the only user.
The are, therefore, no or few bugs related to permissions during testing from the 99.99% of users above.
As a result, there are a large number of Windows games (basically all of them before WinXP) which require system access and admin rights.
BONUS: From your other comment, this default user didn't need a password.
Linux desktops, on the other hand, don't run as root. Lindows tried it some time back, and got eaten alive for that. Some distributions don't even have the capability to log in as root. This means that:
Users have an unprivileged account.
Developers also have an unprivileged account.
Any developer who decided to log in as root and make an application which required system access would be flooded with complaints from the 99.99% of users which don't run as root.
As a result, no games in Linux (and there are quite a few) require admin rights. Windows programs running under wine don't require them, either.
This, my friend, is how choice of default permissions affects the software environment. I really think you already understand that, though.
Wine does more than run binaries, you know. It also allows recompiling your Windows application to Unix fairly simply.
As a result, houses that want to "write to wine" would probably be better off writing to libwine and compiling natively.
"and it was open sourced on the mac first I believe?"
No. It was cross-platform as a proprietary app. It was cross-platform when it was released as OSS. You drank the kool-aid and believed what everyone told you.
For the record, I don't hold OO.o up as a great open source app. It's not. It was closed source, then opened, and the community is too small and the code base is not conducive to new developers joining.
>
Mozilla deserves more credit because they basically rewrote Netscape from the ground up, but I still don't want to hold them up, either.
All this KHTML talk shows that Maccies have a short memory or weren't following when it all happened. Let me shine a light on it for you
Apple didn't release their changes to KHTML for a very long time in violation of the license. The KDE folks got really pissy at this and insisted. Once WebKit was finally released, the changes weren't fed upstream as is common and good etiquette with Open Source software. Instead, a fork from two minor versions before was released without a decent changelog.
People claiming that KDE took Webkit from Apple to use it are high. The people like you who think thaat Apple did the bulk of the work are also wrong. Apple took a mostly completed project, forked it, didn't release the code for a couple of versions, then went into compliance by dumping code onto the community.
Exactly my though. The part of the article which said that the new game was aimed more at people raised on WoW gave the example of fighting, killing, improving your character, and fighting more.
I though hack-n-slash was the sign of a bad DM....
Wow. AMD, a company which in 2006 had 10% of the revenue of Intel, managed to hand Intel its hat in the CPU performance game for a couple of years, an you dare to say that they've never innovated?
Moving the memory controller onto the die and making multi-core mainstream is innovative.
Killing Intel's own preferred IA-64 and making them follow AMD's AMD64 is also a sign that AMD innovated where the market wanted to go, even though Intel pushed as hard as it could.
Slashdot Mirror
OK. I'm really worked up now. The statement above is so anti-geek I don't even know how to deal with it.
For example:
Car geeks build them from parts in their garage on the weekend.
Audio geeks spend years building their audio set-up.
Electronics geeks build robots in their spare time.
Computer geeks write scripts, compile stuff, delve into the lowest parts of the computer, and just generally do stuff that "humans" don't do.
Geeks aren't "human" (in the sense of the average human being talked about). That's why they're called geeks, shunned, and have a reputation for not getting laid. I embrace my geekiness. I come to Slashdot to be with fellow geeks.
Is Slashdot now a site for mere "enthusiasts?" Instead of "Guy installs Linux on calculator watch" articles, are we going to start seeing "How to use your calculator watch the way it was meant to be used" articles?
Not trying to bash Ubuntu, but that "coherent interface all the way through" is Gnome, not Ubuntu. Gnome's Human Interface Guidelines (HIGs) are detailed and applications which want to become part of the desktop have to conform. That's the biggest selling point of Gnome, in my opinion: the concepts are carried through everywhere.
Sorry guys, us mortals dont know how to run scripts and compile our own builds.
I've see this kind of comment more and more on Slashdot over the last few years. When did the average Slash user stop being able to do geeky stuff on his/her computer?
Why would you read Slashdot unless you were a hardcore geek?
I don't think so. He needs at least a year and a half (6/08-1/10) to budget for his media center. If he's a shill, he's certainly not doing a good job. Apparently the cost of Vista + the required hardware to run it well is just too much for him to handle. I build media stuff out of spare parts or with more expensive but tiny MBs. Geexbox has extremely modest requirements, though.
That's sick. By extrapolation, radios in a house, in a car, on a boat, and in a plane would all be separately patentable.
About twenty years ago (in the roaring 80s), I overheard some manager who was taking a weekend MBA program on the phone to someone else in his company. The manager was discussing how to legally lay off everyone over 50 and pay the severance out of the pension fund.
So, yes, I can imagine the situation, too.
"You got your 'insightful' in my 'funny.'"
"No, you got your 'funny' in my 'insightful.'"
"Delicious"
Uh ... I guess I wasn't clear. I didn't mean to imply that NVidia produced the WRT-series router. I just didn't really want to give Linksys credit as a company since they weren't very good community members when releasing the routers. I wanted to make the two obvious by saying "Other notables," but it wasn't, I guess. Sorry about that.
I meant that you can't "partner with Linux" in the same way that you partner with MS. Sure, you can partner with individual projects, but that's not the same thing.
I'm working on a Debian Lenny preseed file particularly for old computers with 128-256MB RAM. Most 6-8 year old laptops fall in this category. Basically, it sets up an OpenBox session with all the necessary codecs and plugins out of the box. Warning: it's completely destructive. Preseeds for 256-512, 512-1GB, and 1GB+ should appear soon.
Why the requirement for the maker to be in the consumer sector? Even given that restriction, I'd argue that both Via and Intel have increased their market penetration in the low-end market by supporting Linux for their integrated graphics cards (yes, I know that Chrome sucks). They basically created the opportunity for the EeePC to exist. Most other low-end linux appliances use integrated graphics, too.
Other notables... Nvidia has had a lock on the Linux market for years because of their support. The WRT line with Linux support made that router long outlive its normal market time.
Is that enough for you? No? Then take away the silly consumer sector requirement and I'll add fifty more.
Finally, there's no way to "partner" with Linux. Either you support it (at some level) or you don't. Who would you partner with?
Ummm ... try leaving out the developers' names in your advertising when using some BSD-licensed software and you'll get in the same boat. The authors there require attribution. If you don't give it to them, they'll come after you in exactly the same way.
That's why the original saying was "Eat your cake and have it, too," meaning once you eat your cake, you no longer have it and are upset like a two-year old. Adults realize that you have to choose.
The Wine website has your answer.
- Windows XP set up the default user as an administrator with elevated privileges by default. Since few users have more than one account,
- They have complete access to their entire system.
- The developer probably has complete access to the system as the only user.
- The are, therefore, no or few bugs related to permissions during testing from the 99.99% of users above.
- As a result, there are a large number of Windows games (basically all of them before WinXP) which require system access and admin rights.
- BONUS: From your other comment, this default user didn't need a password.
- Linux desktops, on the other hand, don't run as root. Lindows tried it some time back, and got eaten alive for that. Some distributions don't even have the capability to log in as root. This means that:
- Users have an unprivileged account.
- Developers also have an unprivileged account.
- Any developer who decided to log in as root and make an application which required system access would be flooded with complaints from the 99.99% of users which don't run as root.
- As a result, no games in Linux (and there are quite a few) require admin rights. Windows programs running under wine don't require them, either.
This, my friend, is how choice of default permissions affects the software environment. I really think you already understand that, though.Wine does more than run binaries, you know. It also allows recompiling your Windows application to Unix fairly simply. As a result, houses that want to "write to wine" would probably be better off writing to libwine and compiling natively.
Yeah, but if you buy that laptop for your with next year and install Ubuntu on it, MS will probably still get a sale. No lost customers for them.
Public performance!!! Did you pay your fee?
Did you forget to post this one as AC, too?
"and it was open sourced on the mac first I believe?"
No. It was cross-platform as a proprietary app. It was cross-platform when it was released as OSS. You drank the kool-aid and believed what everyone told you.
For the record, I don't hold OO.o up as a great open source app. It's not. It was closed source, then opened, and the community is too small and the code base is not conducive to new developers joining.
> Mozilla deserves more credit because they basically rewrote Netscape from the ground up, but I still don't want to hold them up, either.
All this KHTML talk shows that Maccies have a short memory or weren't following when it all happened. Let me shine a light on it for you
Apple didn't release their changes to KHTML for a very long time in violation of the license. The KDE folks got really pissy at this and insisted. Once WebKit was finally released, the changes weren't fed upstream as is common and good etiquette with Open Source software. Instead, a fork from two minor versions before was released without a decent changelog.
People claiming that KDE took Webkit from Apple to use it are high. The people like you who think thaat Apple did the bulk of the work are also wrong. Apple took a mostly completed project, forked it, didn't release the code for a couple of versions, then went into compliance by dumping code onto the community.
Oh the irony of the troll moniker....
... unless you don't consider BSD or Solaris Unix.
OO.o was not Mac first. OO.o was released by Sun from the StarOffice code base. Before that, there was no OO.o.
"...How much you bitches have given back to Unix..."
Yeah. Just about every modern desktop environment used on Unix
The sign of a troll is parading half-truths around as fact.
Exactly my though. The part of the article which said that the new game was aimed more at people raised on WoW gave the example of fighting, killing, improving your character, and fighting more.
....
I though hack-n-slash was the sign of a bad DM
Wow. AMD, a company which in 2006 had 10% of the revenue of Intel, managed to hand Intel its hat in the CPU performance game for a couple of years, an you dare to say that they've never innovated?
Moving the memory controller onto the die and making multi-core mainstream is innovative.
Killing Intel's own preferred IA-64 and making them follow AMD's AMD64 is also a sign that AMD innovated where the market wanted to go, even though Intel pushed as hard as it could.
There's a big gap between "not a good idea" and "illegal."