I remember as a kid strapping a bit of cardboard to the forks so that is hit against the spokes making a "motorbike" noise. Can be done here if need be.
However, a lot of small commuter bikes are pretty quiet - quiet enough that they serve no pedestrian warning purpose - so I don't really see an issue here.
Joe sixpack thinking which choosing a new PC: "Viruses, trojans, spam, phishing, hackers, crackers,..... Hey I think I'll get this one with Trusted Computing".
Microsoft's "stop supporting IE6, Win98 etc" mindset is wrong. So is the "don't need VB" one.
This is unfortunately a mindset that extends into many OSS arenas too. Some Linux kernel projects refuse to support any backporting. Of course you *can* do this yourself, but you're on your own.
Many organisations have a large installed base of legacy systems which are doing just fine as they are. Sometimes these folk need a minor software tweak to add a very small feature. It is unrealistic to expect these people to upgrade their entire system or rewrite their application in C# or whatever. Same goes for some kernel projects. Quite a few systems (and embedded products) are based on more mature kernels like, say, 2.4.18. Changing to 2.6.x is not realistic for these people.
Open source is not the answer in itself. Forking brings pain.
This gizzmo will do some sort of filtering to remove the tremor. This can surely be sone with a software filter built in to the mouse driver etc. That would mean it could be given away or sold at $9.99 rather than as a $100 device.
If someone has to stump up $100 less likely they will want to and less likely they will get the benefit.
C++ is an order of magnitude more complex than C
on
GCC 4.0 Preview
·
· Score: 1
C++ is a very complex language and the compiler therefore needs to track a lot more stuff than a C compiler.
The only way to make you happy would be to build in a slow-down to the C compiler (which would make the kernel folks -- amongst others) a bit sadder.
By the end of this year, the majority of Linux systems will be cell phones and settop boxes/ digital TV etc running on ARM and PowerPC architectures.... not x86. I would have thought that keeping ARM would be a GoodThing.
Perhaps Debian isn't trying to address the embedded segment.
I hunch that if you get really huge volumes of VoIP calls, people will boycott the spamming companies and thereby the feedback will make the whole system self throtling.
VoIP spamming will be far more intrusive than email spamming, since a phone call *demands* an action in real time. This will make it far more annoying.
I don't use a TiVo, but my understanding is that you use this machine to record stuff for playback when you have the time to relax. Do you really want to go relax in front of a desktop PC?
Having wads of cash is not a good indicator of success. Less money makes for better focus. Focussing energy and resources is far more likely to be successful than trying to be all things to all people (something that is more likely to be attempted with huge resources).
This sounds like a nice way to make people shut up and not brag about the fact that they got the info.
Reminds me of when I was at school. Something got stolen. The cops were called and everyone was taken out of class. They said: "We know who stole the [whatever]. We're giving you a chance to own up and be a man about it." Of course they didn't know, nobody owned up and nobody got bust....
There are many call centre operations in India or whereever. If a few get blown up it takes only seconds to divert the call to a new building and a couple of days to say "Check the power cord and reboot".
At the end of the day, Dell (or whomever) don't really care about the quality of the tech support much (and tech support quality is pretty hard to measure). Where there's a buck to be saved, save it!
If the site is run by a kiwi or for the benefit of a kiwi company, with the intention of selling services to people inside kiwiland, then they won't get away with the "the server is in China" approach.
Mugging: you don't go thump the tourist while he's jogging in the park (maybe get a watch and some smelly sneakers), you wait until he's gone back to the hotel for breakfast and comes out again with his camera, Rolex and a wad of cash.
Similarly, if you're going to go litigate against a company for IP damages, you wait for the right moment to strike.
Wait until they've sold many units. This way you can claim the most damages ("By selling xxx units, Apple prevented us from selling xxx units"). And you get the biggest licensing fee since this will be on a per-unit basis.
You also wait until they are vulnerable. When they're trying to roll out a new service that's all hyped up, Apple are more likely to want to settle quickly than have their product stalled by court injunctions etc causing their product to flop.
How soon before/. becomes a Google-bashing society?
The rate Google is making strides to take over and redefine people's www interaction is quite alarming. From the original "just another search engine" beginnings, Google have made a lot of inroads. I see Google ads all over the place. I load the Google toolbar into IE to get an easier search and now I have intrusive "nannyware" that watches over my shoulder like Clippy does: "I see you've done xxxx a few times, do you want to create a shortcut?".
What you should and should not say is not changed by blogging. There is no real difference to making a public statement by any means, including blogging, newspapers, TV etc.
If I were Patterson, I would be proud. Some smug tossers who write a few lines of HTML or Python and think they're he-man programmers know shit -- writing something like MSDOS was a real effort.
I guess I must have used MSDOS for about 15 years or so, much of that writing drivers etc.. For the CPUs available at the time (remember 4.77Mhz 8088 with 128kB of RAM) -- equivalent in CPU grunt to Pentium running about 100kHz, you could not pack in piles of stuff and there was no 32-bit or memory protection available to help with debugging etc. For what was going at the time, MSDOS achieved a lot.
MSDOS was written at the time when there was no C compiler (for x86) worth a damn and everything was written in assembly. There was also very little in the way of debugging assistance - nothing compared to what is available now. Few people could crank out something the size of MSDOS in assmebly these days.
Slashdot Mirror
Perhaps Solitaire is a blessing. Imagine if instead the IRS had nothing to do. They might get bored and start doing an audit on YOU!
However, a lot of small commuter bikes are pretty quiet - quiet enough that they serve no pedestrian warning purpose - so I don't really see an issue here.
Th vendors are just preying on fear.
Easy communications via proprietary protocols etc is just another breeding ground for malware.
This is unfortunately a mindset that extends into many OSS arenas too. Some Linux kernel projects refuse to support any backporting. Of course you *can* do this yourself, but you're on your own.
Many organisations have a large installed base of legacy systems which are doing just fine as they are. Sometimes these folk need a minor software tweak to add a very small feature. It is unrealistic to expect these people to upgrade their entire system or rewrite their application in C# or whatever. Same goes for some kernel projects. Quite a few systems (and embedded products) are based on more mature kernels like, say, 2.4.18. Changing to 2.6.x is not realistic for these people.
Open source is not the answer in itself. Forking brings pain.
No doubt IE7 will include further steps to tilt the playing field.
This gizzmo will do some sort of filtering to remove the tremor. This can surely be sone with a software filter built in to the mouse driver etc. That would mean it could be given away or sold at $9.99 rather than as a $100 device.
If someone has to stump up $100 less likely they will want to and less likely they will get the benefit.
The only way to make you happy would be to build in a slow-down to the C compiler (which would make the kernel folks -- amongst others) a bit sadder.
Perhaps Debian isn't trying to address the embedded segment.
VoIP spamming will be far more intrusive than email spamming, since a phone call *demands* an action in real time. This will make it far more annoying.
I don't use a TiVo, but my understanding is that you use this machine to record stuff for playback when you have the time to relax. Do you really want to go relax in front of a desktop PC?
Having wads of cash is not a good indicator of success. Less money makes for better focus. Focussing energy and resources is far more likely to be successful than trying to be all things to all people (something that is more likely to be attempted with huge resources).
It will be available for GNU/Hurd :-).
Reminds me of when I was at school. Something got stolen. The cops were called and everyone was taken out of class. They said: "We know who stole the [whatever]. We're giving you a chance to own up and be a man about it." Of course they didn't know, nobody owned up and nobody got bust....
Should be called Calf/Linux or something...
There are many call centre operations in India or whereever. If a few get blown up it takes only seconds to divert the call to a new building and a couple of days to say "Check the power cord and reboot".
At the end of the day, Dell (or whomever) don't really care about the quality of the tech support much (and tech support quality is pretty hard to measure). Where there's a buck to be saved, save it!
If the site is run by a kiwi or for the benefit of a kiwi company, with the intention of selling services to people inside kiwiland, then they won't get away with the "the server is in China" approach.
As the first poster said, this is just false advertising. That the medium is the www is irrelevant.
Similarly, if you're going to go litigate against a company for IP damages, you wait for the right moment to strike.
Wait until they've sold many units. This way you can claim the most damages ("By selling xxx units, Apple prevented us from selling xxx units"). And you get the biggest licensing fee since this will be on a per-unit basis.
You also wait until they are vulnerable. When they're trying to roll out a new service that's all hyped up, Apple are more likely to want to settle quickly than have their product stalled by court injunctions etc causing their product to flop.
The rate Google is making strides to take over and redefine people's www interaction is quite alarming. From the original "just another search engine" beginnings, Google have made a lot of inroads. I see Google ads all over the place. I load the Google toolbar into IE to get an easier search and now I have intrusive "nannyware" that watches over my shoulder like Clippy does: "I see you've done xxxx a few times, do you want to create a shortcut?".
Tinfoil hat time folks.
What you should and should not say is not changed by blogging. There is no real difference to making a public statement by any means, including blogging, newspapers, TV etc.
Has not yet said "no"... actually hasn't been asked yet either!
I guess I must have used MSDOS for about 15 years or so, much of that writing drivers etc.. For the CPUs available at the time (remember 4.77Mhz 8088 with 128kB of RAM) -- equivalent in CPU grunt to Pentium running about 100kHz, you could not pack in piles of stuff and there was no 32-bit or memory protection available to help with debugging etc. For what was going at the time, MSDOS achieved a lot.
MSDOS was written at the time when there was no C compiler (for x86) worth a damn and everything was written in assembly. There was also very little in the way of debugging assistance - nothing compared to what is available now. Few people could crank out something the size of MSDOS in assmebly these days.
but I woundn't expect a homie fan to get that right either.
... OK, Bill isn't the biological father, but he's still damn proud.