You couldn't for example restrict a company in France selling to someone in the UK for cheaper than a UK company can (eg. I got my KVM from Germany for only 60% of the market rate for the UK). Apple got into a bit of trouble with that initally (apparently they wanted to charge a different price in different european countries).
Indonesia isn't within the EU trading zone though and can make up its own rules.
I think there's a US/Canada trading zone too with similar rules but not really sure.
That didn't stop DVD manufacturers from creating 'zones' for their products, did it?..and it didn't stop the DVD owners from completely ignoring the 'zones' and buying from the cheapest country available.
Haven't paid full retail price for a DVD in years...
Try Pykrete instead... Woodpulp & Ice mixture - the stuff is as tough as reinforced concrete and takes ages to melt. Could make a nice case out of that. Your PC would be temporarily bulletproof too.
There are 3 types of users... those that just use the app and, if something doesn't work, go and use something else - these are the majority and you never get feedback from them.
Then there's the ones that are helpful and feedback problems. It's good to build up a core of them.. they're a scarce resource. If you want a subset of those who actually send patches.. well I've had 5 patches since January, from approx, 250,000 downloads.
Then there are the ones who demand a fix *now* and get really pissy that the app they downloaded for free doesn't do exactly what they want it to do (bonus points for those who have deployed in a mission critical app without testing first). There probably aren't more of those than in the second group but they take up a disproportionate amount of time.
I usually reckon for every bug report I hear about maybe 100 people have tried it and not bothered to report it (the ratio is probably much higher). It's kind of annoying when someone finds something 2 months after a release and 50 people add to the thread saying they had the same bug and were waiting for a fix...
The South Park movie surely is proof that half hour sit-com does *not* translate.
The just had a standard half hour story and had the characters burst into song every couple of minutes.
It's the only film I've seen where there were only about half the number of people watching at the end of the film than there were at the beginning. I only stayed because I was able to amuse myself timing the gaps between the songs (a bit less than 2 minutes on average.. closer to 1 minute 45).
OTOH quite a few Simpsons episodes have tried to pull the same stunt... ran out of storyline so lets put in a load of gratuitous unfunny singing (lucky Tivo has a fast forward!). It isn't hard to guess what the movie will be like...
If developers DO require more functionality, they can put that extra code into libraries that are inside the application bundle
OSX has/usr/local/lib just like every other Unix. It has library dependencies and LD_LIBRARY_PATH just like every other Unix as well.
If you need libraries you're going to have to install them. OSX might want you to put everything into a single statically linked binary but it really doesn't work that way, except for very simple applications.. that's why you build.pkg scripts to install things into the right places on the hard drive.
Unfortunately because there's no uninstall your hard drive gets clogged up with all the apps you've installed and you eventually have to reformat. I've had to do this twice since I got my Mini due to libraries and whole applications sticking themselves on the disk and unable to remove them.
OSX has none of these problems because it has no package system to speak of..dmg files are just raw disk images, and you drag/drop them into your home directory..pkg files are closer, but IMO no packager is worthy of the name unless it supports *uninstall*. Currently the only way to uninstall apps on OSX is to reformat the drive... not exactly user friendly.
There'll be a few million of these on motherboards, and it only takes *one* person to get the private key and DRM is toast. The same thing happened to DVD, and that didn't take long (DVD encryption sucked though).
Sure, DRM is unobtrusive until your machine goes fubar and you suddenly have to prove that you've *really* paid for all your music to a sceptical record executive so he'll let you reregister it on the new hardware.
Heaven help you if you decide to buy a Mac or install Linux.
Don't get me started on that damned printing press. Sure, it'll *start* with Bibles, but you can bet that soon they'll be printing all sorts of things.
If that happens it's the end of the writing industry and *no more books will ever be written*. The entire world will be plunged into darkness!!!
I don't find macos easy *or* stable (well, actually OSX itself is but finder falls over if the wind changes), but that's not the point.
To support osx releases of my software I had to buy a mini mac. With x86 osx even if the hack is fiddly to get working I can run it on commodity hardware... maybe even under vmware or a slightly modified version. That's great for develpment.
Wrong. you've never worked for a small/medium size company have you?
If you're producing an app then as a developer you have to fight for *Every* penny that gets spent. That means if you have the choice of using GTK for $0 or QT for $500 (or whatever it costs) you'll use GTK. Not because it's too expensive, but because the pain of justifying the expense is too great, will take about a month and cause you to miss your deadline.
(example: At one job we had 5 developers working for 2 weeks to track down a memory leak that boundschecker could have found in about an hour. We'd already spent 6 months trying to justify the cost of devpartner and it had been thrown out again... companies have a strange view of costs - by my reckoning that one bug cost them $50,000 out of the developer (or 'resources') budget but spending $1000 out of the software budget was too much... different line in the spreadsheet).
It wouldn't be hard to write an emulator that did it (anything from a custom boot sequence to a whole VMWare-alike)... of course they'd just update OSX so that it could detect the emulation.
1. autoconf tries to have logic for every single supported architecture within it, but of course it only supports the ones that were known at the time of building, and can't handle quirks. You have to build the in manually... compile flags can be particularly evil.. (Digital Unix take a bow!), plus multiple linux distros do things in different ways even if the core OS is the same (Redhat is particularly bad for this... if you don't include certain headers in certain orders if screws up eg. kerberos is dependent on SSL (or is that the other way around? I forget.).
A much better way would be for each distro/platform to have its own autoconf core, containing all the rules it needs for its paths, quirky library building, etc. That could be installed once by default then a simple autoconf script in each package that interfaces with it/reads config files/whatever will be able to do the right thing without (or rarely) having to do platform specific stuff in the package.
2. Libtool. The package that the 'rm' command was designed for. Tried to be all things to all systems and 90% of the time does the wrong thing (and on some platforms - HPUX, AIX - doesn't actually work properly at all).
Blew up Firefox + XP SP2 + NVidia without even a bluescreen... it just reset the box.
The error report apparently was that the graphics driver exploded, but if it happens to ATI too it's definately an OS bug - userspace should *not* be able to cause out of bounds information to be sent to a driver.
A lot of my friends have Mac laptops... they use them for presentations/flash animations, music, etc.
I have a mini, which mostly sits there in middle of the pile of PCs unused (need to keep OSX on it to build software releases otherwise I'd put debian on it... never got on with OSX at all).
Mine does that. If it isn't continuously plugged into power it eventually goes flat, which means it's not useful if I'm not around the computer for long.
They drain battery whilst switched off, and because it's nonremovable you can't just pop it out to conserve it, which means I'm looking at a brick in 18 months or less because it has to be charged every day, even though I probably listen to it for maybe a couple of hours a week.
Slashdot Mirror
Only within the EU.
You couldn't for example restrict a company in France selling to someone in the UK for cheaper than a UK company can (eg. I got my KVM from Germany for only 60% of the market rate for the UK). Apple got into a bit of trouble with that initally (apparently they wanted to charge a different price in different european countries).
Indonesia isn't within the EU trading zone though and can make up its own rules.
I think there's a US/Canada trading zone too with similar rules but not really sure.
That didn't stop DVD manufacturers from creating 'zones' for their products, did it? ..and it didn't stop the DVD owners from completely ignoring the 'zones' and buying from the cheapest country available.
Haven't paid full retail price for a DVD in years...
Try Pykrete instead... Woodpulp & Ice mixture - the stuff is as tough as reinforced concrete and takes ages to melt. Could make a nice case out of that. Your PC would be temporarily bulletproof too.
That's not really true in general.
There are 3 types of users... those that just use the app and, if something doesn't work, go and use something else - these are the majority and you never get feedback from them.
Then there's the ones that are helpful and feedback problems. It's good to build up a core of them.. they're a scarce resource. If you want a subset of those who actually send patches.. well I've had 5 patches since January, from approx, 250,000 downloads.
Then there are the ones who demand a fix *now* and get really pissy that the app they downloaded for free doesn't do exactly what they want it to do (bonus points for those who have deployed in a mission critical app without testing first). There probably aren't more of those than in the second group but they take up a disproportionate amount of time.
I usually reckon for every bug report I hear about maybe 100 people have tried it and not bothered to report it (the ratio is probably much higher). It's kind of annoying when someone finds something 2 months after a release and 50 people add to the thread saying they had the same bug and were waiting for a fix...
Oh purleeze.
He was just trying to put a more moderate point of view and you come up with some kind of strawman argument to put him down?
Or are you just only happy when someone believes exactly the same things you do? Who's not being reasonable now?
The South Park movie surely is proof that half hour sit-com does *not* translate.
The just had a standard half hour story and had the characters burst into song every couple of minutes.
It's the only film I've seen where there were only about half the number of people watching at the end of the film than there were at the beginning. I only stayed because I was able to amuse myself timing the gaps between the songs (a bit less than 2 minutes on average.. closer to 1 minute 45).
OTOH quite a few Simpsons episodes have tried to pull the same stunt... ran out of storyline so lets put in a load of gratuitous unfunny singing (lucky Tivo has a fast forward!). It isn't hard to guess what the movie will be like...
If developers DO require more functionality, they can put that extra code into libraries that are inside the application bundle
/usr/local/lib just like every other Unix. It has library dependencies and LD_LIBRARY_PATH just like every other Unix as well.
.pkg scripts to install things into the right places on the hard drive.
OSX has
If you need libraries you're going to have to install them. OSX might want you to put everything into a single statically linked binary but it really doesn't work that way, except for very simple applications.. that's why you build
Unfortunately because there's no uninstall your hard drive gets clogged up with all the apps you've installed and you eventually have to reformat. I've had to do this twice since I got my Mini due to libraries and whole applications sticking themselves on the disk and unable to remove them.
OSX has none of these problems because it has no package system to speak of. .dmg files are just raw disk images, and you drag/drop them into your home directory. .pkg files are closer, but IMO no packager is worthy of the name unless it supports *uninstall*. Currently the only way to uninstall apps on OSX is to reformat the drive... not exactly user friendly.
Of course you can... just get the private key.
There'll be a few million of these on motherboards, and it only takes *one* person to get the private key and DRM is toast. The same thing happened to DVD, and that didn't take long (DVD encryption sucked though).
Sure, DRM is unobtrusive until your machine goes fubar and you suddenly have to prove that you've *really* paid for all your music to a sceptical record executive so he'll let you reregister it on the new hardware.
Heaven help you if you decide to buy a Mac or install Linux.
Don't get me started on that damned printing press. Sure, it'll *start* with Bibles, but you can bet that soon they'll be printing all sorts of things.
If that happens it's the end of the writing industry and *no more books will ever be written*. The entire world will be plunged into darkness!!!
I don't find macos easy *or* stable (well, actually OSX itself is but finder falls over if the wind changes), but that's not the point.
To support osx releases of my software I had to buy a mini mac. With x86 osx even if the hack is fiddly to get working I can run it on commodity hardware... maybe even under vmware or a slightly modified version. That's great for develpment.
Most american indian tribes are extinct.
All of your examples still live in their homeland.
Wrong. you've never worked for a small/medium size company have you?
If you're producing an app then as a developer you have to fight for *Every* penny that gets spent. That means if you have the choice of using GTK for $0 or QT for $500 (or whatever it costs) you'll use GTK. Not because it's too expensive, but because the pain of justifying the expense is too great, will take about a month and cause you to miss your deadline.
(example: At one job we had 5 developers working for 2 weeks to track down a memory leak that boundschecker could have found in about an hour. We'd already spent 6 months trying to justify the cost of devpartner and it had been thrown out again... companies have a strange view of costs - by my reckoning that one bug cost them $50,000 out of the developer (or 'resources') budget but spending $1000 out of the software budget was too much... different line in the spreadsheet).
OK who rated this 'interesting'?
It's just a troll that posts the same damned thing in every story he can find.
Debian doesn't ship mplayer - it's not in unstable or even non-free.
.deb packages for it. They're unofficial though.
It's just that some people have made
Runs the windows code semi-natively...
OS/2 tried that tactic.... it backfired big style - everyone just realized that they were running Windows apps most of the time and installed Windows.
It wouldn't be hard to write an emulator that did it (anything from a custom boot sequence to a whole VMWare-alike)... of course they'd just update OSX so that it could detect the emulation.
I predict an arms race..
Not at all.. something like the 'desk lamp' mac with x86 will be prime Windows territory.
Outside the reality distortion field OSX isn't *that* great, and market inertia counts for a lit.
1. autoconf tries to have logic for every single supported architecture within it, but of course it only supports the ones that were known at the time of building, and can't handle quirks. You have to build the in manually... compile flags can be particularly evil.. (Digital Unix take a bow!), plus multiple linux distros do things in different ways even if the core OS is the same (Redhat is particularly bad for this... if you don't include certain headers in certain orders if screws up eg. kerberos is dependent on SSL (or is that the other way around? I forget.).
A much better way would be for each distro/platform to have its own autoconf core, containing all the rules it needs for its paths, quirky library building, etc. That could be installed once by default then a simple autoconf script in each package that interfaces with it/reads config files/whatever will be able to do the right thing without (or rarely) having to do platform specific stuff in the package.
2. Libtool. The package that the 'rm' command was designed for. Tried to be all things to all systems and 90% of the time does the wrong thing (and on some platforms - HPUX, AIX - doesn't actually work properly at all).
Blew up Firefox + XP SP2 + NVidia without even a bluescreen... it just reset the box.
The error report apparently was that the graphics driver exploded, but if it happens to ATI too it's definately an OS bug - userspace should *not* be able to cause out of bounds information to be sent to a driver.
A lot of my friends have Mac laptops... they use them for presentations/flash animations, music, etc.
I have a mini, which mostly sits there in middle of the pile of PCs unused (need to keep OSX on it to build software releases otherwise I'd put debian on it... never got on with OSX at all).
If they played Crazy Frog it'd probably explode in protest!
(btw. do you get that in the US too? I thought it was a UK affliction).
MS still give away the 2003 eval at MSDN roadshows last time I checked.
Disabling the timebomb is pretty easy, but the most of the people at MSDN roadshows already have copies of all the OS CDs anyway.
Mine does that. If it isn't continuously plugged into power it eventually goes flat, which means it's not useful if I'm not around the computer for long.
They drain battery whilst switched off, and because it's nonremovable you can't just pop it out to conserve it, which means I'm looking at a brick in 18 months or less because it has to be charged every day, even though I probably listen to it for maybe a couple of hours a week.