If they had to use bolt cutters, they'd either reap 1/4 of the merchandise or take 4 times longer to clean it all.
One way or another, it's a (small) deterrent.
"Any post that starts out with an assumption about what another person thinks or doesn't think, understands or doesn't understand, is flawed from the beginning. We may have differing opinions on the merits of WINE, but don't for one minute assume anything, because you don't know." OK, so you got pissed, I get the point. Whatever - let's tone down the abrasion factor and move on...
Improving photogimp (a gimp version whith a user interface more similar to photoshop for people who do not want to learn another application) would imho be a better option than wine. Or even funding a native photoshop port. And to me both would still be mistakes.
"All you are restating is the argument that postulates that WINE support may erode native application support for Linux, and that position is not unreasonable." It's not unreasonable, but it has a negative incentive on further development of the existing alternatives.
"However, it is also not unreasonable to help users to use applications they are familiar with." I which case it would make perfect sense for said users to stick with an OS they are familiar with. Most if not all of the arguements/complaints/religious flamewars/... boil down to this : 'Linux does not behave like Windows'. Well, why not use Windows then ? I never heard anyone complaining that an msx was not behaving like a C64 or that a spectrum was not behaving like an amiga, it made perfect sense for anyone at the time that switching to a different platform would mean using different applications. Now everyone wants all platforms to look and feel exactly the same, and run exactly the same applications. What is the point of having different platforms, then ? What has become of the common sense ?
NB Funny you point out transparent GIFs, I had to do that a couple weeks ago and had never done it in gimp before. It proved quite intuitive : create image with no background, paste/edit my picture in it, save as gif image, and it was done. What's so complex/unintuitive there ?
"What is needed is a smooth integration of Windows executables with Linux execution code."
First, I think you're missing the point of using an open source system and applications. There are native, and free alternatives. Why not rather commit resources to making these prgrams (such as Gimp or Krita) more suitable ? I could use the extra development on Gimp, instead of forking out a grand for a license of Photoshop that will at best run as well as on windows, and at worst still be mostly unsupported since I'd be out of the 'normal use' boundaries, using wine on Linux to run it. (And just don't get me started on the unlicensed copies issue.)
Second, let's forget the opensource/free aspect for a second. All applications, especially 'killer' applications, are initially developped on a single platform, then sometimes ported to other platforms as well. Photoshop used to be a mac thing, now it's a windows thing (I mean I think now the dev teams at adobe develop using windows boxes initially rather than on macs, as was the case earlier.) Some time ago there was also a unix version of Photoshop (see http://en.wikipedia.org/wiki/Adobe_Photoshop_release_history) which was eventually dropped. It would be far better to inject resources in a native version than using a version from another OS on top of a compatibility layer such as wine. A native application always performs and integrates better, this just makes sense on a technical point of view.
Providing a 'windows version that runs better using Wine/Linux' has several side effects that I see as detrimental : - it reduces the chances to ever get a native version developped - adobe will not know whether sold copies are used on windows or linux/wine, thus all sales will be accounted for as 'windows sales' - support will still be an issue (oh you use it under wine on linux ? not our problem then, see with codeweavers. Even though codeweavers certainly offers good support, the risk of ping-pong issues between adobe and codeweavers is obvious) - this shows no support, nor respect for the teams that made Gimp, Cinepaint, Krita,... which are free and open source alternatives who could get much more done with the same amount of money
Try to get him to understand that some deliverables are 'negative' deliverables.
Uptime (lack of downtime) or security (lack of intrusions) are good examples. They are partly the expression of your due diligence, good practices, savoir faire, and flair. These will never be piechart-able.
If he does not understand that or does not want to understand it, pack away and get working somewhere they deserve you better.
A job is not just an exchange of money for work. You have to get some consideration and self-fulfillment out of it.
"Apparently, my previous assertion that you don't work at a large store is true - none of the major stores allow customers to return opened software."
yup, great ways to do commerce : customer buys products, opens it at home, reads end user license agreement, eventually decides to disagree for whatever reason (incompatible, too restrictive, requirements not stated on the box/documentation that only appears while installing,... not to mention the all too classic oem preinstalled on the machine wether you like it or not stuff.) and get a refund AS STATED IN THE EULA, and gets turned down at the retailed (we don't refund opened software) AND at the software maker (you must get your refund at your point of sales)
This abuse has been going on for years, it's disgusting.
"I wonder if it would be legal to revoke someones liscence or CD-KEY for playing a game developed and liscenced for Windows on a Linux platform (therefore violating the EULA)?"
Wait for the first 'my VISTA deactivated itself' lawsuit and you'll get an interesting answer:p
There have been DNS security concerns lately, specifically the 'cache poisoning' vulnerabilities reported by cert, sans et al. Maybe some ISPs have altered their DNS servers to provide better protection, and in the process caused the 'ttl' problem ? (improbable imo, but who knows...) It'd be interesting to know if this is recent or if it's already an old problem. Knowing if it appeared suddenly or progressively would help as well.
Too bad there isn't such a thing as the wayback machine for dns and other services...
Whan I shell out hard-earned cash for something, be is physical or digital, I want to BUY it. Which means it's mine, _forever_ or at least until I choose to resell it, or dispose it.
DRM means that I'm dependant on a combination of software and hardware, or (even worse) hardware + software + availability of a service by a supplier (for verifications purpose, a la valve or XP activation.) It also means I won't buy it. Because later on, I want to be able to use it, no matter if the supplier company went tits up, or worse changed its policy along the way and eventyally decided the thing I bought is now obsolete and removes my rights to use it.
I owned a rocket ebook, and it was an eye-opening experience in DRM. The only DRMed thing I ever bought is a copy of Dan Brown's angels and demons. Should my device stop functionning, I'm SOL. Even tough I paid paperback price for the DRMed ebook, I cannot lend it, and I'm dependent on the device still being available to be able to read it.
DRM means dependency, slavery to the supplier. No, thanks.
It's true that _many_ aspects of MS windows' TCP-IP stack smell BSD-ish:-) (and since it's from an old codebase, there's lots of old bugs that were fixed long time ago in bsd netstack but which are still present in windows'...)
I'd actually be very glad to see them do so. More hassles in activation/installation means more opportunities to inform people about the alternatives.
A friend of mine had to help an old guy in a rural and remote part of greece last summer. The guy had bought a PC in a supermarket, and it was his first PC. After a while, the PC 'stopped working' so the old guy asked around in the younger members of the family for help. My pal having some knowledge of PC's was asked by his girlfriend (family of the old guy) to check it out. It eventually turned out the guy had winXP preinstalled, and that it needed 'activation'.
The old guy didn't understand crap about that, and of course had no internet connection, nor telephone. He eventually returned the PC to the store, calling them robbers.
If you come from a windows background, and have a few years of experience, the biggest hurdle you face is not learning the technicalities of linux, but getting a grip of the overall unix philosophy.
The worst error someone in your position could ever do is learn linux system administration, then "try to do the same thing" as was done using windows.
Linux (and unix, bsd,...) is a diffeent beast. The main concept you'll need to grasp is that programs and utilities have a limited scope by design. That's unix atomicity : one program that does one and only one thing, but does it well. Every single utility is a lego building brick that you'll use time and over again in various circumstances (especially in shell scripting)
That alone is very diffrent from windows 'all-in-one', monolithic, approach.
I strongly suggest you get involved in your local linux user group. Helping out people solve basic problems and mixing with more experienced admins is a very good way to learn the non purely technical aspects.
EU ruling quote: Microsoft abused its market power by deliberately restricting interoperability between Windows PCs and non-Microsoft work group servers
work group servers are not restricted to file servers and user authentication. This will most probably have connections to exchange server, calendar sharing and the like. Maybe soon will evolution be eventually able to talk to exchange without a proprietary connector:)
Seems sourceforge is an obvious place to host that GPLed project of yours.
The interoperability purpose of the software should be enough to avoid dmca related problems
(plus the eff could give a hand:)
Slashdot Mirror
If they had to use bolt cutters, they'd either reap 1/4 of the merchandise or take 4 times longer to clean it all. One way or another, it's a (small) deterrent.
get an eee or similar cheap, portable machine and use it instead of the public terminal.
"Any post that starts out with an assumption about what another person thinks or doesn't think, understands or doesn't understand, is flawed from the beginning. We may have differing opinions on the merits of WINE, but don't for one minute assume anything, because you don't know."
OK, so you got pissed, I get the point. Whatever - let's tone down the abrasion factor and move on...
Improving photogimp (a gimp version whith a user interface more similar to photoshop for people who do not want to learn another application) would imho be a better option than wine. Or even funding a native photoshop port. And to me both would still be mistakes.
"All you are restating is the argument that postulates that WINE support may erode native application support for Linux, and that position is not unreasonable."
It's not unreasonable, but it has a negative incentive on further development of the existing alternatives.
"However, it is also not unreasonable to help users to use applications they are familiar with."
I which case it would make perfect sense for said users to stick with an OS they are familiar with. Most if not all of the arguements/complaints/religious flamewars/... boil down to this : 'Linux does not behave like Windows'. Well, why not use Windows then ?
I never heard anyone complaining that an msx was not behaving like a C64 or that a spectrum was not behaving like an amiga, it made perfect sense for anyone at the time that switching to a different platform would mean using different applications.
Now everyone wants all platforms to look and feel exactly the same, and run exactly the same applications. What is the point of having different platforms, then ? What has become of the common sense ?
NB Funny you point out transparent GIFs, I had to do that a couple weeks ago and had never done it in gimp before. It proved quite intuitive : create image with no background, paste/edit my picture in it, save as gif image, and it was done. What's so complex/unintuitive there ?
"What is needed is a smooth integration of Windows executables with Linux execution code."
... which are free and open source alternatives who could get much more done with the same amount of money
First, I think you're missing the point of using an open source system and applications. There are native, and free alternatives. Why not rather commit resources to making these prgrams (such as Gimp or Krita) more suitable ? I could use the extra development on Gimp, instead of forking out a grand for a license of Photoshop that will at best run as well as on windows, and at worst still be mostly unsupported since I'd be out of the 'normal use' boundaries, using wine on Linux to run it. (And just don't get me started on the unlicensed copies issue.)
Second, let's forget the opensource/free aspect for a second. All applications, especially 'killer' applications, are initially developped on a single platform, then sometimes ported to other platforms as well.
Photoshop used to be a mac thing, now it's a windows thing (I mean I think now the dev teams at adobe develop using windows boxes initially rather than on macs, as was the case earlier.) Some time ago there was also a unix version of Photoshop (see http://en.wikipedia.org/wiki/Adobe_Photoshop_release_history) which was eventually dropped. It would be far better to inject resources in a native version than using a version from another OS on top of a compatibility layer such as wine. A native application always performs and integrates better, this just makes sense on a technical point of view.
Providing a 'windows version that runs better using Wine/Linux' has several side effects that I see as detrimental :
- it reduces the chances to ever get a native version developped
- adobe will not know whether sold copies are used on windows or linux/wine, thus all sales will be accounted for as 'windows sales'
- support will still be an issue (oh you use it under wine on linux ? not our problem then, see with codeweavers. Even though codeweavers certainly offers good support, the risk of ping-pong issues between adobe and codeweavers is obvious)
- this shows no support, nor respect for the teams that made Gimp, Cinepaint, Krita,
Try to get him to understand that some deliverables are 'negative' deliverables. Uptime (lack of downtime) or security (lack of intrusions) are good examples. They are partly the expression of your due diligence, good practices, savoir faire, and flair. These will never be piechart-able. If he does not understand that or does not want to understand it, pack away and get working somewhere they deserve you better. A job is not just an exchange of money for work. You have to get some consideration and self-fulfillment out of it.
Porting the plugin makes sense, but will the dev tools be available on other platforms than windows ?
If not, move around, nothing to see.
"Apparently, my previous assertion that you don't work at a large store is true - none of the major stores allow customers to return opened software." yup, great ways to do commerce : customer buys products, opens it at home, reads end user license agreement, eventually decides to disagree for whatever reason (incompatible, too restrictive, requirements not stated on the box/documentation that only appears while installing, ... not to mention the all too classic oem preinstalled on the machine wether you like it or not stuff.) and get a refund AS STATED IN THE EULA, and gets turned down at the retailed (we don't refund opened software) AND at the software maker (you must get your refund at your point of sales)
This abuse has been going on for years, it's disgusting.
"I wonder if it would be legal to revoke someones liscence or CD-KEY for playing a game developed and liscenced for Windows on a Linux platform (therefore violating the EULA)?"
:p
Wait for the first 'my VISTA deactivated itself' lawsuit and you'll get an interesting answer
"broadcast quality NTSC" is an oxymoron.
There have been DNS security concerns lately, specifically the 'cache poisoning' vulnerabilities reported by cert, sans et al.
Maybe some ISPs have altered their DNS servers to provide better protection, and in the process caused the 'ttl' problem ? (improbable imo, but who knows...)
It'd be interesting to know if this is recent or if it's already an old problem.
Knowing if it appeared suddenly or progressively would help as well.
Too bad there isn't such a thing as the wayback machine for dns and other services...
Whan I shell out hard-earned cash for something, be is physical or digital, I want to BUY it.
Which means it's mine, _forever_ or at least until I choose to resell it, or dispose it.
DRM means that I'm dependant on a combination of software and hardware, or (even worse) hardware + software + availability of a service by a supplier (for verifications purpose, a la valve or XP activation.)
It also means I won't buy it. Because later on, I want to be able to use it, no matter if the supplier company went tits up, or worse changed its policy along the way and eventyally decided the thing I bought is now obsolete and removes my rights to use it.
I owned a rocket ebook, and it was an eye-opening experience in DRM. The only DRMed thing I ever bought is a copy of Dan Brown's angels and demons.
Should my device stop functionning, I'm SOL. Even tough I paid paperback price for the DRMed ebook, I cannot lend it, and I'm dependent on the device still being available to be able to read it.
DRM means dependency, slavery to the supplier. No, thanks.
It's true that _many_ aspects of MS windows' TCP-IP stack smell BSD-ish :-)
(and since it's from an old codebase, there's lots of old bugs that were fixed long time ago in bsd netstack but which are still present in windows'...)
I'd actually be very glad to see them do so.
More hassles in activation/installation means more opportunities to inform people about the alternatives.
A friend of mine had to help an old guy in a rural and remote part of greece last summer. The guy had bought a PC in a supermarket, and it was his first PC.
After a while, the PC 'stopped working' so the old guy asked around in the younger members of the family for help. My pal having some knowledge of PC's was asked by his girlfriend (family of the old guy) to check it out.
It eventually turned out the guy had winXP preinstalled, and that it needed 'activation'.
The old guy didn't understand crap about that, and of course had no internet connection, nor telephone. He eventually returned the PC to the store, calling them robbers.
If you come from a windows background, and have a few years of experience, the biggest hurdle you face is not learning the technicalities of linux, but getting a grip of the overall unix philosophy.
...) is a diffeent beast. The main concept you'll need to grasp is that programs and utilities have a limited scope by design. That's unix atomicity : one program that does one and only one thing, but does it well. Every single utility is a lego building brick that you'll use time and over again in various circumstances (especially in shell scripting)
The worst error someone in your position could ever do is learn linux system administration, then "try to do the same thing" as was done using windows.
Linux (and unix, bsd,
That alone is very diffrent from windows 'all-in-one', monolithic, approach.
I strongly suggest you get involved in your local linux user group. Helping out people solve basic problems and mixing with more experienced admins is a very good way to learn the non purely technical aspects.
EU ruling quote :
:)
Microsoft abused its market power by deliberately restricting interoperability between Windows PCs and non-Microsoft work group servers
work group servers are not restricted to file servers and user authentication. This will most probably have connections to exchange server, calendar sharing and the like.
Maybe soon will evolution be eventually able to talk to exchange without a proprietary connector
Seems sourceforge is an obvious place to host that GPLed project of yours. The interoperability purpose of the software should be enough to avoid dmca related problems (plus the eff could give a hand :)