81–90 of 193 posts
Earlier quoted context omitted.
Personally I consider 1.4.2 the point where java got stable, and had a true IO (java.nio), along with a decent JIT (hotspot)
Phew, that was around the internet Java applets phase, if I recall it correctly?
Not to be snarky but 2011 is yesterday for programming, no major shift. I'd imagine almost all code written there would be able to run today.
In the Java world, sure. Other programming language ecosystems tend to have tons of churn. For an anecdote, every TypeScript project I find from 2021 or earlier is simply impossible to build nowadays, meanwhile the ClojureScript code I dealt with in a previous job was able to survive 8 years worth of updates to libraries and the core language. I frequently ran into code that was last modified around 2013 because it j…
This is the fault of all the bullshit tools that were never any good to begin with (Webpack, Babel, etc) and the Node ecosystem generally causing pain. If you had a package-lock.json you should (in theory) be able to install all of those and it should work. Of course, this relies on dependencies of dependencies actually following semantic versioning but I'm fairly sure many packages on npmjs.org do not follow semantic versioning.
Worst case scenario, you can take your TS files and put them in a newly created project. Preferably the project has a minimal number of build tools, eg, 1. Such as Vite, for example. This effectively replaces easily 5 or 6 major load bearing dependencies that used to be necessary.
Even better: Just use Deno, where it doesn't need any of this to build and run TS files!
Earlier quoted context omitted.
There are many other languages with a better lindy effect rating ( https://en.wikipedia.org/wiki/Lindy_effect ), common lisp, erlang, fortran and more. I won't doubt how java doing well, but other languages have it beat.
Except they're not in widespread usage, so aren't relevant. No grads are going "gee, do I go with a .NET shop, a JVM shop, or a BEAM shop?" And as for Common Lisp, which implementation? They can't even be compatible amongst themselves, so I'm dubious that SBCL CL from 13 years ago would just work.
I don't know any java programmers either. Apparently people use java, I just dont know any that do it willingly. I'm sure they -must- use it, but erlang/fortran/etc as mythical to you as java is to me.
> No grads are going "gee, do I go with a .NET shop, a JVM shop, or a BEAM shop?"
Fresh grads don't know better, they take whatever pays. Businesses choose the cheapest (not the best) option and grads don't have the experience to choose better. Grads choices are not a measure of quality or desirability.
> And as for Common Lisp, which implementation? They can't even be compatible
> amongst themselves, so I'm dubious that SBCL CL from 13 years ago would just
> work.
My SBCL from 2010ish works, I've patched it up and improved it over time, but I haven't tried to run the original, it probably does. Its been through svn to git so I've lost the history, all of this is as anecdotal as anything else. Previous lisp code that I wrote was trivial and ran out of the box on SBCL, however the code is very self contained and not 'networked' or 'modern'.
My erlang code however has been running in a cluster since the early 2000's, it has also been through several releases for additional features, however I no longer have access to that code so I can't validate what has been done to it for the last decade.
I like your arguments, I just dont think we're coming from the same historical viewpoint.
Earlier quoted context omitted.
There are many other languages with a better lindy effect rating ( https://en.wikipedia.org/wiki/Lindy_effect ), common lisp, erlang, fortran and more. I won't doubt how java doing well, but other languages have it beat.
> common lisp, erlang, fortran That's a pretty esoteric list. Javascript would have been a better choice because of widespread deployment by multiple vendors and heavy legacy.
Boggles my mind when coders don't save everything they've ever written. It's easy to be a digital pack-rat without much consequence. That said, my first Java 1.02 programs from the 90's still compile and the old jars run surprisingly well too. Color me impressed!
It was quite different before the internet. I'm still holding out hope of finding some of my old BASIC programs from the 80s on a 5¼-inch floppy disk in my parents' basement. But they are probably gone.
The programs weren't fancy: one was for picking lotto numbers for my mam (the national lottery had recently launched in Ireland so it was a novelty.) Also I was 10.
Not to be snarky but 2011 is yesterday for programming, no major shift. I'd imagine almost all code written there would be able to run today.
You've had a very different experience of the past 13 years if you've experienced no major shifts. Even the past year has had a whole big change with the advent of LLMs, nevermind the rise of the web, VSCode, typescript, rust, and more. In 2011, Java was on version 7. We're on 22 now in 2024. There have been some paradigm shifts in Java during that time. Streams (Java 8), Lambda expressions (Java 9), the var keyword…
Returns:
> Not Found
currently
> Download the jar file > https://github.com/khiner/CrosswordFiller/WordFillVer2.jar Returns: > Not Found currently
Earlier quoted context omitted.
You've had a very different experience of the past 13 years if you've experienced no major shifts. Even the past year has had a whole big change with the advent of LLMs, nevermind the rise of the web, VSCode, typescript, rust, and more. In 2011, Java was on version 7. We're on 22 now in 2024. There have been some paradigm shifts in Java during that time. Streams (Java 8), Lambda expressions (Java 9), the var keyword…
The rise of the web? In the past 13 years? Gosh does that make me feel old...