i think it does satisfy fair use, it just doesn't exercise the fullest extent of fair use as you mention. i really think the "content providers" have a right to do whatever they want to protect their works, but they also should have no recourse against any types of fair usage. including decss, anti-macrovision, whatever.
they don't have to make it easy for you to make a backup of your stuff, but they shouldn't take that right away altogether.
java allowed you to increase productivity, substantially?
according to this whitepaper, when developers are given their preferance of language to use to implement a solution, they're most productive. ie, someone who knows c++ and enjoys working in c++ will be just as productive as someone who knows java and enjoys working in java.
i'd be extremely interested to see some concrete independant studies showing otherwise.
the everyday win/mac users don't really know what options are available. the big things keeping linux off the desktop are:
drivers: people are using new hardware all the time and have a perceived image that linux doesn't have drivers for their hardware (wireless network, usb mouse, video, sound, etc).
installation: the install programs NEED to be able to identify hardware on a users system and configure drivers w/o user intervention. being asked what type of network card i have on my box isn't something i should know much about, let alone what integrated sound chip i have, or what kind of mouse i have. to sum it up, linux will find more spaces on the desktop when the installers and drivers are as upto date as possible.
have the shrink wrapped license agreements been held up under court? i realize that all software vendors put them there, but can you really purchase something that you can't use unless you agree to terms that aren't disclosed prior to purchase time?
to my knowledge a hardware dvd player is just that harware that reads media. pretty basic. one should be free to modify the haredware (with addidional hardware or software if needed) as they see fit to get their particular needs met. it may void warranties but that's no big deal
hey now... as a hard working FTE software developer i have also had my hand in some massive system issues (vms page issues due to some c program testing;)). please don't give the contractors, vendors, and interns all the credit. us FTE's earn our keep as well!!
do you have any benchmarks for kde's less responsiveness than W2k/XP? my guess is that they're about the same on exact same hardware (they both need decent harware to execute comfortablally). sure there's somethings that w2k can do quicker, and some tasks that kde will handle quicker. all in all they're about the same.
to you're other nonsubstanciated commment, yes, lightweight wm's can be good. especially when you're not after a complete desktop environment. a kiosk needs some sort of a wm, but needs only one window w/ limited functionality. network access also needs lightweight access (vnc, term serve, remote X display, etc). unfortunately, with win, lightweight on the desktop isn't easily available. you don't have much of a choice.
Re:My Biased Opinion...
on
Perl & XML
·
· Score: 1
sure, migrating languages it costly. so, if you've got legacy code in perl, leave it alone. but... if you're putting together a new web based "application", you have the choice to use java,.NET, or legacy technologies such as perl/php/asp, etc. My first choice would be java. There wouldn't be a second choice.
i guess i'm too lazy to search google for "remove code scsi higher level". ok. ok. ok.
the original post was regarding the complexity of using linux scsi drivers to access ATAPI CDROM drives, specifically CDRW drives. i don't see the relavence of moving any code, or the "drag of the whole SCSI interface".
at any rate, you seem to be suggesting an ide-super-duper-scsi interface. how would using this interface make setting up the device for the user any easier? they're still not using an IDE device, and the applications are all written to take advantage of the SCSI interface. maybe if the ide-super-duper-scsi interface would talk to both ide and scsi devices, and applications would use the new interface, we'd be all set.
guess what... windows cd-burning software also uses scsi emulation. that's what the atapi is all about on those cd-rom drives. it give software developers a common interface to program to.
which "upper level" are you referring to? to my understanding the (scsi) emulation layer is an upper level. this makes all the code common. as others have mentioned, most big distros will recognize your cdrw and load the scsi modules on boot. launch xcdroast and your in business.
if only you had mentioned debian/gentoo distros. the source is stong in that one i can tell, but there is still much fear from the masses in building their own box...
a box is a box. when it all boils down to it, do the applications work? do they work together? does it get the job done?...
it's not illegal to say you have feelings twords kernels, though in Penn. your ISP might be required to report you saying such to the state authorities. let's just hope the traffic between/. and Marcelo doesn't have to hop through pittsburg;).
ATI does release specs, yes, but what is the timelieness of that release? from what i read on the gatos-devel mailing list, the ati driver writers need to ask for the docs then wait months for a reponse. eventually, they might get what they're after, but it's certainly not ideal. closed source drivers that are free (beer) and released with the hardware is much more desired than open source drivers 2 years after the fact since no-one even saw a document until the product has been on the market for 6 months.
you're obviously not from west virginia or kentucky...
as for leaving to go to the kitchen? i wouldn't want to risk the opportunity to post nonsense posts to/. for a story that didn't stand up long enough for any/.ers to grab a mirror...
most of us are taking coffee on a daily basis to get ready for work (and to get through the morning, and the afternoon, and evening). it would be a rather interesting environment if those on decaff switched to eating paper/shrooms in the morning before venturing to their place of employment.
i don't understand the decaff thing either, same as the neer(sp?)-beer type stuff (coors NA, etc). i remember being like 13 or so and the guy at the local carry-out would sell us neer-beer. we thought we were the shit (and so was the tast of that crap).
just a thought, but if the webserver isn't serving pages properly, it's probably not serving images either;). i didn't get the image on the more reliable google cached site either.
3. ease of interacting with other web based "applications"
sure it "works" now, and will continue to work this way in the future the way it currently does, but porting to newer technologies allows the "business" to grow quickly and to adapt to an ever changing environment.
i don't think a port of slashcode would be too bad, in fact it would probably clean it up a lot.
perl/mod_perl was fine back in the early slash days. that was about the best there was. now there's a j2ee environment that provides flexability and feature rich components. you can develop to a model much easier. you can also scale a lot better from what i can tell. all software that doesn't get ported eventually gets outdated and rots, why don't the/. admins feel like keeping up with innovation?
what "features" does M$ IE provide that you must use that aren't able to be written for w3c standards?
from my experience, web devels (myself included) are too lazy to code correctly. we're using IE for testing, and when it looks good, we ship it out. if we were using a w3c browser (mozilla) for testing, we wouldn't have to worry. it would *er rather should* look ok in IE. if it doesn't, it's IE's problem.
well said. it is the protocols we need. unfortuately, it's nearly impossible to get the IM big 3 (aim, y!, msn) to sit down and draft a proposal. jabber attempted to put something together, but i fear their "renegade" movement will not add up to much. the best thing about jabber is its availability for internal networks. most corps are implementing a no messenger policy for their own protection. jabber lets work groups communicate securely and within corp security policies.
the constitution doesn't say you can gather/hang out where ever/ whenever you want. it merely says you have the right to "peaceably assemble", meaning they can't lock you up or charge you with a crime merely for gathering together. in most places, you have to apply for a permit to hold an assembly.
i'd say the cops are telling you to move along because you're in, or will be in someone elses way.
no console windows? i used Xfree on cygwin about a year ago (don't recall the version numbers), but X was started from a.bat file. the thing i didn't like about X was that it seemed to be full screen only. i haven't used XWin32, but it seems to be 250$ more than Xfree...
Slashdot Mirror
i think it does satisfy fair use, it just doesn't exercise the fullest extent of fair use as you mention. i really think the "content providers" have a right to do whatever they want to protect their works, but they also should have no recourse against any types of fair usage. including decss, anti-macrovision, whatever.
they don't have to make it easy for you to make a backup of your stuff, but they shouldn't take that right away altogether.
the "high quality" units are typically made by larger US companies who might have an interest in blocking these types of features.
java allowed you to increase productivity, substantially?
according to this whitepaper, when developers are given their preferance of language to use to implement a solution, they're most productive. ie, someone who knows c++ and enjoys working in c++ will be just as productive as someone who knows java and enjoys working in java.
i'd be extremely interested to see some concrete independant studies showing otherwise.
the everyday win/mac users don't really know what options are available. the big things keeping linux off the desktop are:
drivers: people are using new hardware all the time and have a perceived image that linux doesn't have drivers for their hardware (wireless network, usb mouse, video, sound, etc).
installation: the install programs NEED to be able to identify hardware on a users system and configure drivers w/o user intervention. being asked what type of network card i have on my box isn't something i should know much about, let alone what integrated sound chip i have, or what kind of mouse i have. to sum it up, linux will find more spaces on the desktop when the installers and drivers are as upto date as possible.
have the shrink wrapped license agreements been held up under court? i realize that all software vendors put them there, but can you really purchase something that you can't use unless you agree to terms that aren't disclosed prior to purchase time?
to my knowledge a hardware dvd player is just that harware that reads media. pretty basic. one should be free to modify the haredware (with addidional hardware or software if needed) as they see fit to get their particular needs met. it may void warranties but that's no big deal
hey now... as a hard working FTE software developer i have also had my hand in some massive system issues (vms page issues due to some c program testing ;)). please don't give the contractors, vendors, and interns all the credit. us FTE's earn our keep as well!!
doh. i smell a troll 'round here.
do you have any benchmarks for kde's less responsiveness than W2k/XP? my guess is that they're about the same on exact same hardware (they both need decent harware to execute comfortablally). sure there's somethings that w2k can do quicker, and some tasks that kde will handle quicker. all in all they're about the same.
to you're other nonsubstanciated commment, yes, lightweight wm's can be good. especially when you're not after a complete desktop environment. a kiosk needs some sort of a wm, but needs only one window w/ limited functionality. network access also needs lightweight access (vnc, term serve, remote X display, etc). unfortunately, with win, lightweight on the desktop isn't easily available. you don't have much of a choice.
this is the best 404 page i've ever come across..
sir, please setp away from the vehicle.
sure, migrating languages it costly. so, if you've got legacy code in perl, leave it alone. but... if you're putting together a new web based "application", you have the choice to use java, .NET, or legacy technologies such as perl/php/asp, etc. My first choice would be java. There wouldn't be a second choice.
i guess i'm too lazy to search google for "remove code scsi higher level". ok. ok. ok.
the original post was regarding the complexity of using linux scsi drivers to access ATAPI CDROM drives, specifically CDRW drives. i don't see the relavence of moving any code, or the "drag of the whole SCSI interface".
at any rate, you seem to be suggesting an ide-super-duper-scsi interface. how would using this interface make setting up the device for the user any easier? they're still not using an IDE device, and the applications are all written to take advantage of the SCSI interface. maybe if the ide-super-duper-scsi interface would talk to both ide and scsi devices, and applications would use the new interface, we'd be all set.
guess what... windows cd-burning software also uses scsi emulation. that's what the atapi is all about on those cd-rom drives. it give software developers a common interface to program to.
which "upper level" are you referring to? to my understanding the (scsi) emulation layer is an upper level. this makes all the code common. as others have mentioned, most big distros will recognize your cdrw and load the scsi modules on boot. launch xcdroast and your in business.
if only you had mentioned debian/gentoo distros. the source is stong in that one i can tell, but there is still much fear from the masses in building their own box...
...
a box is a box. when it all boils down to it, do the applications work? do they work together? does it get the job done?
it's not illegal to say you have feelings twords kernels, though in Penn. your ISP might be required to report you saying such to the state authorities. let's just hope the traffic between /. and Marcelo doesn't have to hop through pittsburg ;).
Gene Kan, co-author to Gnutella protocol dies
looks like a self inflicted gun shot from what i read. he semeed to be doing nicely working for Sun too. some folks just don't get it.
ATI does release specs, yes, but what is the timelieness of that release? from what i read on the gatos-devel mailing list, the ati driver writers need to ask for the docs then wait months for a reponse. eventually, they might get what they're after, but it's certainly not ideal. closed source drivers that are free (beer) and released with the hardware is much more desired than open source drivers 2 years after the fact since no-one even saw a document until the product has been on the market for 6 months.
like firearms and alcohol
/. for a story that didn't stand up long enough for any /.ers to grab a mirror...
you're obviously not from west virginia or kentucky...
as for leaving to go to the kitchen? i wouldn't want to risk the opportunity to post nonsense posts to
most of us are taking coffee on a daily basis to get ready for work (and to get through the morning, and the afternoon, and evening). it would be a rather interesting environment if those on decaff switched to eating paper/shrooms in the morning before venturing to their place of employment.
i don't understand the decaff thing either, same as the neer(sp?)-beer type stuff (coors NA, etc). i remember being like 13 or so and the guy at the local carry-out would sell us neer-beer. we thought we were the shit (and so was the tast of that crap).
just a thought, but if the webserver isn't serving pages properly, it's probably not serving images either ;). i didn't get the image on the more reliable google cached site either.
maybe tomorrow..
1. maintenance cost.
2. ease of adding lots of new features.
3. ease of interacting with other web based "applications"
sure it "works" now, and will continue to work this way in the future the way it currently does, but porting to newer technologies allows the "business" to grow quickly and to adapt to an ever changing environment.
i don't think a port of slashcode would be too bad, in fact it would probably clean it up a lot.
/. admins feel like keeping up with innovation?
perl/mod_perl was fine back in the early slash days. that was about the best there was. now there's a j2ee environment that provides flexability and feature rich components. you can develop to a model much easier. you can also scale a lot better from what i can tell. all software that doesn't get ported eventually gets outdated and rots, why don't the
what "features" does M$ IE provide that you must use that aren't able to be written for w3c standards?
from my experience, web devels (myself included) are too lazy to code correctly. we're using IE for testing, and when it looks good, we ship it out. if we were using a w3c browser (mozilla) for testing, we wouldn't have to worry. it would *er rather should* look ok in IE. if it doesn't, it's IE's problem.
well said. it is the protocols we need. unfortuately, it's nearly impossible to get the IM big 3 (aim, y!, msn) to sit down and draft a proposal. jabber attempted to put something together, but i fear their "renegade" movement will not add up to much. the best thing about jabber is its availability for internal networks. most corps are implementing a no messenger policy for their own protection. jabber lets work groups communicate securely and within corp security policies.
the constitution doesn't say you can gather/hang out where ever/ whenever you want. it merely says you have the right to "peaceably assemble", meaning they can't lock you up or charge you with a crime merely for gathering together. in most places, you have to apply for a permit to hold an assembly.
i'd say the cops are telling you to move along because you're in, or will be in someone elses way.
no console windows? i used Xfree on cygwin about a year ago (don't recall the version numbers), but X was started from a .bat file. the thing i didn't like about X was that it seemed to be full screen only. i haven't used XWin32, but it seems to be 250$ more than Xfree...