Yes, I guess the one-ways are what has mostly bitten me in the past, not necessarily the street layout. The consolation is that there are so many streets that you can usually just go down to the next one if you miss a turn.
The Wii isn't relying only on the remote, but also on the new direction that Nintendo is taking with it compared to past video game consoles. The remote is one facet of the focus on non-hardcore gamers.
It was the same with SMB3. On quite a few levels, if you had a tail, you could just fly over the entire level. Some levels were made trivial by using the tanuki suit's stone ability. Why not give people the option? If someone wants to bypass a level in a lame way, let them. They're only ruining it for themselves. But part of the fun of gaming is exploring possibilities. "I'll just try this and see what happens." Sometimes it turns out to be the most fun part of the game.
Perl is like an armored truck modified to be an F1 racecar. Experienced drivers that know how to handle it properly don't need to worry about any other driver on the track. Inexperience drivers will probably injure the crowd, although rarely themselves.
Since it's GPL software, any employee who gets their hands on it can then redistribute it for free.
Although this point is probably true[1], it still makes a couple of assumptions. The largest is that the employee will even know it is GPL software. Why would JoeEmployee know or care? If BigCorp sends its own technicians to install the software, even the IT staff of LargeCompany may not realize.
The second assumption is that JoeEmployee will know what the GPL is and care about it. It's pretty likely that most people outside of software development have never heard of the GPL, and wouldn't really care about it if they did.
For this scheme to work indefinitely it'd need to be a quite obscure piece of software
Not really. What about software for managing employee payroll? That's pretty widely useful. But a payroll manager has training in and cares about financial matters. He only cares about software as far as making his job easier, not the pursuit of Software Freedom. What incentive does he have to distribute it?
and there should be a reason to get the software from the company and not from me.
I already covered this point. First, there's the great enhancements that BigCorp has added, which your product doesn't have. Second, BigCorp doesn't have to tell anyone that most of the product was written by someone else. Their customers would have to actively investigate that to find it out, and they aren't going to do that because they have better things to do. Like get on with using the software to make more money. So they won't even know about you.
since any company attempting to do this can't distribute it very widely, so any potential gains from it won't be large.
It depends on the business sector. If BigCorp sells to large companies that would need large licensing contracts, they only have to sell to a few to make large gains.
It's a quite contrived example
I don't know what type of software you write, maybe it's only useful for other software developers. In that case, I agree.
But I was speaking more generally. There are a lot of companies that don't have in-house programmers. They don't do any kind of software development. Their IT staff is mostly concerned with keeping the general tech infrastructure running, and they have support contracts for when the software bugs out. Those companies and their employees don't care about the GPL. It's not in their field of operation, and they're busy doing things that are in their field.
Anyway, I won't argue the point further. The fact that you think the example is so contrived means you don't have the experience to understand that it isn't, so the discussion can't move any further.
At least you realize that anyone making changes to your software is not automatically obliged to return them to you. Most GPL lovers don't even understand that.
[1] I've seen discussions on this that argue employees can't redistribute GPL software, because they aren't legal entities in regards to company matters. The company is given the license, etc. I haven't seen a definitive legal answer, but it's beside my point, so I grant the assumption.
You wouldn't have to stop the processes if you were smart about the setup. Store your mail in a directory that the mail processes access through a symlink. To drop a bunch of mail atomically: 1) create a new directory, 2) copy over the mail you want to keep, 3) move the symlink. Only the last operation affects the mail processes, and it's atomic. Then you can delete the other directory at your convenience. Granted it's less efficient, but still possible.
The GPL on the other hand is perfect, because if a competitor ever does any improvement, you'll be able to use it.
You're wrong. You'll only be able to use any improvement if your competitor distributes the changes to you. Only the recipient of the modified GPL software is entitled to the changed source.
Here's an example: You write GPL software that is used by LargeCompany, and sell the support to them. BigCorp takes your software, makes some great enhancements, and sells it to the same LargeCompany saying, "Hey, this software does everything that guy's does and more!" Do you think, because of the GPL, you're entitled access to those changes? You aren't. Only LargeCompany is, and they're not going to share them with you, because why should they? They're getting better features and support from BigCorp. In fact, they probably don't even know the product is just an enhancement of your product, because they don't care about reading the source, they're busy with their actual business.
So guess what? You just became an unpaid employee of BigCorp, even though you used the GPL. Welcome to enlightenment.
Guess what other system had a really high shit-to-good ratio? The PS2. That's because the most popular console is going to draw the most games, and most of those will be crap.
MY general point: the Nintendo "gimmick" systems gets a higher volume of shit-to-good than any other console.
Because they are more popular than the other consoles (or portables).
Looser and loser also have different pronunciations and very different meanings. I'd say the pronunciations of looser and loser are less similar than then and than, because the different s sound is obvious.
No offense, but a device that could revolutionize the way people communicate would be a lot more important than some pictures of Mars's surface. Unfortunately, when such a device is created, other countries will have it before we do, because our current communication overlords have heavy lobbies.
Did you read the part of the article where they tried using the break-down lane to pass while it was raining? Do you want to guess why it's called the break-down lane?
"Well, it's raining, so I have pretty low visibility, but I might as well use this space for passing that might have someone trying to change their tire, who I won't be able to see until they're dead."
In addition to what your other responder said, daemons are sometimes configured to notify the admin user of critical errors by sending mail, in case the admin isn't a vigilant log-checker. This is why Debian asks what user should be mail-aliased to root. In this case, that user would probably be you, and you might want to know when/why your cron'd apt update failed.
And Slashcode is still written in PERL? RUfuckingKiddingMe?
I can't believe it either. Perl is 20 years old! Sheesh, that's like letting your Grandma plan your birthday party. Let's get some of these young, hip, languages in on things. According to this list on Wikipedia, F# is the youngest, hippest language. It's already 2 years old, so we've got to work fast. Hurry before the next language shows up.
I wonder if you'd last longer if your heart simply stopped right away.
If your heart stopped, your brain wouldn't be getting any new oxygen at all. If your heart keeps going, your brain at least gets the oxygen in the blood that hasn't been to the lungs yet. Maybe if you could stop your lungs from working temporarily, but keep your heart working. That might buy you another half minute.
I'm saying it's highly unlikely Microsoft is doing this out of the good of their heart.
Maybe you're anti-capitalist because you don't understand how capitalism works. Of course they aren't doing out of the kindness of their heart. The point of capitalism is that the self-interest of each party works to the eventual benefit of the other, because they each have something the other wants. In this case, Microsoft has a potentially useful file format. Consumers have money. Microsoft wants money. Whether consumers want this new file format enough to make the trade is the rub.
Slashdot Mirror
Yes, I guess the one-ways are what has mostly bitten me in the past, not necessarily the street layout. The consolation is that there are so many streets that you can usually just go down to the next one if you miss a turn.
The Wii isn't relying only on the remote, but also on the new direction that Nintendo is taking with it compared to past video game consoles. The remote is one facet of the focus on non-hardcore gamers.
Ann Arbor?
It was the same with SMB3. On quite a few levels, if you had a tail, you could just fly over the entire level. Some levels were made trivial by using the tanuki suit's stone ability. Why not give people the option? If someone wants to bypass a level in a lame way, let them. They're only ruining it for themselves. But part of the fun of gaming is exploring possibilities. "I'll just try this and see what happens." Sometimes it turns out to be the most fun part of the game.
This quote from the article also shows that you're wrong, and he's right:
If a message is sent to 100,000 protected users, the system has the rating power of 100,000 receiver reputations to rate the sender and the message.
Please read the bold portion.
Perl is like an armored truck modified to be an F1 racecar. Experienced drivers that know how to handle it properly don't need to worry about any other driver on the track. Inexperience drivers will probably injure the crowd, although rarely themselves.
(How's that?)
Henry Higgins was a professor of phonetics, not grammar.
Maybe $, and/or $\ have been changed, so it wouldn't give identical output.
Since it's GPL software, any employee who gets their hands on it can then redistribute it for free.
Although this point is probably true[1], it still makes a couple of assumptions. The largest is that the employee will even know it is GPL software. Why would JoeEmployee know or care? If BigCorp sends its own technicians to install the software, even the IT staff of LargeCompany may not realize.
The second assumption is that JoeEmployee will know what the GPL is and care about it. It's pretty likely that most people outside of software development have never heard of the GPL, and wouldn't really care about it if they did.
For this scheme to work indefinitely it'd need to be a quite obscure piece of software
Not really. What about software for managing employee payroll? That's pretty widely useful. But a payroll manager has training in and cares about financial matters. He only cares about software as far as making his job easier, not the pursuit of Software Freedom. What incentive does he have to distribute it?
and there should be a reason to get the software from the company and not from me.
I already covered this point. First, there's the great enhancements that BigCorp has added, which your product doesn't have. Second, BigCorp doesn't have to tell anyone that most of the product was written by someone else. Their customers would have to actively investigate that to find it out, and they aren't going to do that because they have better things to do. Like get on with using the software to make more money. So they won't even know about you.
since any company attempting to do this can't distribute it very widely, so any potential gains from it won't be large.
It depends on the business sector. If BigCorp sells to large companies that would need large licensing contracts, they only have to sell to a few to make large gains.
It's a quite contrived example
I don't know what type of software you write, maybe it's only useful for other software developers. In that case, I agree.
But I was speaking more generally. There are a lot of companies that don't have in-house programmers. They don't do any kind of software development. Their IT staff is mostly concerned with keeping the general tech infrastructure running, and they have support contracts for when the software bugs out. Those companies and their employees don't care about the GPL. It's not in their field of operation, and they're busy doing things that are in their field.
Anyway, I won't argue the point further. The fact that you think the example is so contrived means you don't have the experience to understand that it isn't, so the discussion can't move any further.
At least you realize that anyone making changes to your software is not automatically obliged to return them to you. Most GPL lovers don't even understand that.
[1] I've seen discussions on this that argue employees can't redistribute GPL software, because they aren't legal entities in regards to company matters. The company is given the license, etc. I haven't seen a definitive legal answer, but it's beside my point, so I grant the assumption.
You wouldn't have to stop the processes if you were smart about the setup. Store your mail in a directory that the mail processes access through a symlink. To drop a bunch of mail atomically: 1) create a new directory, 2) copy over the mail you want to keep, 3) move the symlink. Only the last operation affects the mail processes, and it's atomic. Then you can delete the other directory at your convenience. Granted it's less efficient, but still possible.
The GPL on the other hand is perfect, because if a competitor ever does any improvement, you'll be able to use it.
You're wrong. You'll only be able to use any improvement if your competitor distributes the changes to you . Only the recipient of the modified GPL software is entitled to the changed source.
Here's an example: You write GPL software that is used by LargeCompany, and sell the support to them. BigCorp takes your software, makes some great enhancements, and sells it to the same LargeCompany saying, "Hey, this software does everything that guy's does and more!" Do you think, because of the GPL, you're entitled access to those changes? You aren't. Only LargeCompany is, and they're not going to share them with you, because why should they? They're getting better features and support from BigCorp. In fact, they probably don't even know the product is just an enhancement of your product, because they don't care about reading the source, they're busy with their actual business.
So guess what? You just became an unpaid employee of BigCorp, even though you used the GPL. Welcome to enlightenment.
OT: is there a way to escape greaterthan/lessthan signs?
You have to use the HTML escape codes, which are < and > .
Guess what other system had a really high shit-to-good ratio? The PS2. That's because the most popular console is going to draw the most games, and most of those will be crap.
MY general point: the Nintendo "gimmick" systems gets a higher volume of shit-to-good than any other console.
Because they are more popular than the other consoles (or portables).
I can see looser/loser
Looser and loser also have different pronunciations and very different meanings. I'd say the pronunciations of looser and loser are less similar than then and than, because the different s sound is obvious.
How far are we supposed to go?
e-z-r
No offense, but a device that could revolutionize the way people communicate would be a lot more important than some pictures of Mars's surface. Unfortunately, when such a device is created, other countries will have it before we do, because our current communication overlords have heavy lobbies.
Did you read the part of the article where they tried using the break-down lane to pass while it was raining? Do you want to guess why it's called the break-down lane?
"Well, it's raining, so I have pretty low visibility, but I might as well use this space for passing that might have someone trying to change their tire, who I won't be able to see until they're dead."
In addition to what your other responder said, daemons are sometimes configured to notify the admin user of critical errors by sending mail, in case the admin isn't a vigilant log-checker. This is why Debian asks what user should be mail-aliased to root. In this case, that user would probably be you, and you might want to know when/why your cron'd apt update failed.
I've usually heard it as, "In theory, there's no difference between theory and practice. In practice, there is."
<i>frankly, the colors hurt my eyes.</i>
:syn off
"Precedes" means "came before;" it does not mean "cannot be lamer than."
And Slashcode is still written in PERL? RUfuckingKiddingMe?
I can't believe it either. Perl is 20 years old! Sheesh, that's like letting your Grandma plan your birthday party. Let's get some of these young, hip, languages in on things. According to this list on Wikipedia, F# is the youngest, hippest language. It's already 2 years old, so we've got to work fast. Hurry before the next language shows up.
Pretty obvious that Sailor Mars had the red skirt. Also, she was much hotter.
I wonder if you'd last longer if your heart simply stopped right away.
If your heart stopped, your brain wouldn't be getting any new oxygen at all. If your heart keeps going, your brain at least gets the oxygen in the blood that hasn't been to the lungs yet. Maybe if you could stop your lungs from working temporarily, but keep your heart working. That might buy you another half minute.
I'm a bit of an anti-capitalist...
I'm saying it's highly unlikely Microsoft is doing this out of the good of their heart.
Maybe you're anti-capitalist because you don't understand how capitalism works. Of course they aren't doing out of the kindness of their heart. The point of capitalism is that the self-interest of each party works to the eventual benefit of the other, because they each have something the other wants. In this case, Microsoft has a potentially useful file format. Consumers have money. Microsoft wants money. Whether consumers want this new file format enough to make the trade is the rub.