Possessed of a whim or some sort of mental illness, I decided to write a small cross platform app in Java (having not programmed in java for close to 20 years)
Keep encountering pattern-breaking nonconformant stuff
like for the CLI java/javac, it's -version not --version or -v
Eclipse on Mac doesn't store its settings in /Library or ~/Library but in /Applications/Eclipse
Stuff like that. Makes it feel weird and archaic. Not seeing much evolution in the language itself either so far.
=> More informations about this toot | More toots from obscurestar@mastodon.social
@obscurestar I have similar experiences coding in R. I don't code frequently. When I do, I feel like I have to relearn the entire language because changes in the new versions are not backward compatible. Languages used to ensure to a higher degree, conditions of backward compatibility. I have begun to feel like (1) planned obsolescence is intentional, or, (2) nobody gives a flying fuck anymore about anything but their current version.
=> More informations about this toot | More toots from 9CL7T9k8cjnD@mastodon.social
@9CL7T9k8cjnD This, I think turned out to be my process. Seems like probably most java developers don't do a lot of cmdln stuff and use IDEs.
I rebuilt my project so it would run as a Maven project in Eclipse and that made the libraries magically resolve.
Not sure how they automated deploy build for java yet. There are some cmake functions but I've not had any luck getting them to work so far (admittedly, still low priority on this project)
=> More informations about this toot | More toots from obscurestar@mastodon.social This content has been proxied by September (ba2dc).Proxy Information
text/gemini