| |||||||||||||
|
| |||||||||||||
Sun yanks FreeBSD's Java licenseSun yanks FreeBSD's Java licensePosted Jan 11, 2005 0:14 UTC (Tue) by dang (subscriber, #310)In reply to: Sun yanks FreeBSD's Java license by landley Parent article: Sun yanks FreeBSD's Java license
Odd how I've never really had any trouble running Java on linux for years.
(Log in to post comments)
Sun yanks FreeBSD's Java license Posted Jan 11, 2005 1:32 UTC (Tue) by khim (subscriber, #9252) [Link] I had. A lot of trouble. With resolver, with threads, etc, etc. To the level when we discussed switch to Windows (where problems are not so acute) or rewriting everything in C/C++ (where we at least can properly debug problems).
Sun yanks FreeBSD's Java license Posted Jan 11, 2005 20:55 UTC (Tue) by error27 (subscriber, #8346) [Link] If you only run Free software then Java is a reall pain.
It's not just that the Free java tools suck, it's that they suck in different incompatible ways. Code that works under gcj doesn't work with jikes and vice-versa.
At least if you use Mono under Linux and you distribute your code to someone else who uses Mono under Linux then you have a chance the the code will run on both systems.
For massive dedicated installations you just install Sun's non-Free JAVA, do your work, get paid and try to find something fullfilling to do in your free time. That's OK. But I still see java used for stuff like ICQ clients and source code analysis tools and people expect them to work under Debian. That's just not happenning.
Yeah -- no problems at all. On i386. Posted Jan 12, 2005 8:23 UTC (Wed) by smurf (subscriber, #17840) [Link] Things get worse very very fast if you dare to use amd64, or powerpc, or ...
Freedom doesn't mean freedom to run on vendor-approved hardware only -- it means freedom to run the code ANYWHERE, even if it's an old m68k Amiga.
|
|
||||||||||||