While it might be true that Java failed on the client side, I disagree with you on it being server side.
Server side Java was nowhere before. It only existst because of the (previous) hype Java possibilities caused: suddenly there were a lot of programmers who knew the language itself. This was because Java (in this context: applets) filled in a big hole in the browser UIs: client side interaction, graphics, games etc. (most of this is wiped away since then, of course, especially by Flash and stuff)
So, why not put these programmers into work on the server side also? They could be productive. IMHO this was a brilliant idea, despite the fact Java requires a LOT more resources than traditional C/C++ ("now, that's no problem, they will buy more HW, preferably Suns":-)
Even JSP, another server-side technology, is a copy of Microsoft's ASP technology.
Again, I disagree. Show me another server side, HTML embedded language; it will be basically the same... ASP, JSP, PHP, maybe even SSI:-) There's nothing new under the Sun *grin*
One thing that might be interesting when you have problems copying audio CDs is that most DVD players also have digital out channels. Also, most newer sound cards have digital in/out... I guess you don't need much more to make a 'copyable' copy (for yourself, of course:-)
The other good protections that I have seen dealt with having to enter in words from the pages of the instruction manual (which could be defeated by copying the whole manual...) but most people didn't go and copy a 100 page manual.
These weren't any more sophisticated than the other schemes: crackers only needed to tweak the 'is-this-the-good-answer' condition to true (and there had to be an if like this).
Re:Compared to Windows. . . .
on
Is RPM Doomed?
·
· Score: 1
Right, but it's not that hard to conform to all distros if 'all' means 'one':-)
Server side Java was nowhere before. It only existst because of the (previous) hype Java possibilities caused: suddenly there were a lot of programmers who knew the language itself. This was because Java (in this context: applets) filled in a big hole in the browser UIs: client side interaction, graphics, games etc. (most of this is wiped away since then, of course, especially by Flash and stuff)
So, why not put these programmers into work on the server side also? They could be productive. IMHO this was a brilliant idea, despite the fact Java requires a LOT more resources than traditional C/C++ ("now, that's no problem, they will buy more HW, preferably Suns" :-)
Even JSP, another server-side technology, is a copy of Microsoft's ASP technology.
Again, I disagree. Show me another server side, HTML embedded language; it will be basically the same... ASP, JSP, PHP, maybe even SSI :-) There's nothing new under the Sun *grin*
One thing that might be interesting when you have problems copying audio CDs is that most DVD players also have digital out channels. Also, most newer sound cards have digital in/out... I guess you don't need much more to make a 'copyable' copy (for yourself, of course :-)
The other good protections that I have seen dealt with having to enter in words from the pages of the instruction manual (which could be defeated by copying the whole manual...) but most people didn't go and copy a 100 page manual. These weren't any more sophisticated than the other schemes: crackers only needed to tweak the 'is-this-the-good-answer' condition to true (and there had to be an if like this).
Right, but it's not that hard to conform to all distros if 'all' means 'one' :-)