3 ms·

$CLASSPATH pain is one of the first things a new Java developer encounters — maybe the last, in many cases. The only reason it's not quite as bad in .NET is th

by gavinpc 12y ago

$CLASSPATH pain is one of the first things a new Java developer encounters — maybe the last, in many cases. The only reason it's not quite as bad in .NET is that it can usually reference at least the framework in a well-known location. But generally, whatever you call the problem that $CLASSPATH is designed to solve (assembly binding, reference resolution), it's an unsolved problem.

tootie 12y ago
That's a feature, not a bug. It's part and parcel of dynamic linking and dependency management. You certainly can generate a monolithic executable jar file if you want.
platz 12y ago
not sure what .Net issues you're referring to, but they sound sort of obscure