4 ms·

Because the core system dates back to jre... 1.4, has had ~2 decades of painful testing and big chunks of code dont currently work on anything newer than 8. a

Because the core system dates back to jre... 1.4, has had ~2 decades of painful testing and big chunks of code dont currently work on anything newer than 8. a bug that takes 100 hours to manifest takes multiples of that to fix. compute and ram is crazy cheap these days, developers are not, and finding good ones is harder than ever.

stuff4ben 5y ago
Yeah I'm gonna say you're an edge case and that the majority of users will see performance benefits. Maybe not you, but that's legacy code for ya and an awful lot of technical debt that's likely not worth it.
- DarkmSparks 5y ago
  every java dev was an edge case, from small houses building blockbusters like triage through to the likes of gazprom and google building their entire backend on it with tens of thousands of devs. since you threw them out, which "majority of users" are you thinking of?
  - stuff4ben 5y ago
    Nah, I'm just saying you have a lot of legacy code you're either incapable of fixing or not willing to fix. And no, not every java developer is an edge case. If that were true then no one would be able to upgrade and they wouldn't bother creating more Java releases, we'd still all be on 8. See I too can make sweeping assumptions with no basis in reality. Sorry your codebase sucks, good luck!
    - DarkmSparks 5y ago
      I know you have a lot of freshly written code that will crash multi times a week for the first few years its used in the wild. If you are wondering why no one wants to pay for it, that is why.
      - stuff4ben 5y ago
        LOL, you know nothing about what I do. And it sounds like you have experience with "freshly written code that crashes multiple times a week for the first few years"... here's a hint, it's probably you and your development team to blame, not the JDK. Maybe you should quit being lazy, learn the new JDK APIs and features, and convert that POS legacy codebase into something that's not dependent upon a platform released 7 years ago. But then again, maybe you're not a competent enough developer to do so, so you blame the JDK developers instead.
        DarkmSparks 5y ago
        heres a real hint. Im in a yacht in the med, will fly my private helicopter home soon. I also dont want to know anything about you. Well done.
        stuff4ben 5y ago
        Sure you are buddy, keep dreaming. One day you'll learn enough Java to upgrade your POS legacy codebase so you're not on-call 24x7.
        DarkmSparks 5y ago
        I really didnt need to know you live of the wrong side of the 24x7 oncall employment curve. But now that I do, i still have no interest in anything you think you know, you sound like the kind of dev I could replace with a 14 year old on $2 an hour.
        stuff4ben 5y ago
        Hah! Good luck dude, I feel sorry for you and your POS app that you can't upgrade. Stuck on JDK8 for the rest of your life while the rest of us have moved on. Must suck doing legacy support for such an ancient app. And by the sounds of it, you must have been hiring those 14 year olds @ $2/hour. Kinda explains why you're in the mess you're in, hahahahaha!!!
krzyk 5y ago
What will you do with this system when Java 8 stop being supported (no more security fixes)?
- DarkmSparks 5y ago
  thats actually less of an issue than it sounds for a jvm build that hasn't had a relevant and important security issue found for over a decade, is now open source and all the others found and fixed any time recently give better assurance over any recent code that hasnt had the same scrutiny.

stuff4ben 5y ago

Yeah I'm gonna say you're an edge case and that the majority of users will see performance benefits. Maybe not you, but that's legacy code for ya and an awful lot of technical debt that's likely not worth it.

DarkmSparks 5y ago
every java dev was an edge case, from small houses building blockbusters like triage through to the likes of gazprom and google building their entire backend on it with tens of thousands of devs. since you threw them out, which "majority of users" are you thinking of?
- stuff4ben 5y ago
  Nah, I'm just saying you have a lot of legacy code you're either incapable of fixing or not willing to fix. And no, not every java developer is an edge case. If that were true then no one would be able to upgrade and they wouldn't bother creating more Java releases, we'd still all be on 8. See I too can make sweeping assumptions with no basis in reality. Sorry your codebase sucks, good luck!
  - DarkmSparks 5y ago
    I know you have a lot of freshly written code that will crash multi times a week for the first few years its used in the wild. If you are wondering why no one wants to pay for it, that is why.
    - stuff4ben 5y ago
      LOL, you know nothing about what I do. And it sounds like you have experience with "freshly written code that crashes multiple times a week for the first few years"... here's a hint, it's probably you and your development team to blame, not the JDK. Maybe you should quit being lazy, learn the new JDK APIs and features, and convert that POS legacy codebase into something that's not dependent upon a platform released 7 years ago. But then again, maybe you're not a competent enough developer to do so, so you blame the JDK developers instead.
      - DarkmSparks 5y ago
        heres a real hint. Im in a yacht in the med, will fly my private helicopter home soon. I also dont want to know anything about you. Well done.
        stuff4ben 5y ago
        Sure you are buddy, keep dreaming. One day you'll learn enough Java to upgrade your POS legacy codebase so you're not on-call 24x7.
        DarkmSparks 5y ago
        I really didnt need to know you live of the wrong side of the 24x7 oncall employment curve. But now that I do, i still have no interest in anything you think you know, you sound like the kind of dev I could replace with a 14 year old on $2 an hour.
        stuff4ben 5y ago
        Hah! Good luck dude, I feel sorry for you and your POS app that you can't upgrade. Stuck on JDK8 for the rest of your life while the rest of us have moved on. Must suck doing legacy support for such an ancient app. And by the sounds of it, you must have been hiring those 14 year olds @ $2/hour. Kinda explains why you're in the mess you're in, hahahahaha!!!

krzyk 5y ago

What will you do with this system when Java 8 stop being supported (no more security fixes)?

DarkmSparks 5y ago
thats actually less of an issue than it sounds for a jvm build that hasn't had a relevant and important security issue found for over a decade, is now open source and all the others found and fixed any time recently give better assurance over any recent code that hasnt had the same scrutiny.