is it scalable? no.

is it maintainable? no

is it portable? not really

we rewrote our codebase around... 9 times this month :data-laughing:

  • Neckbeard_Prime [they/them,he/him]
    ·
    3 years ago

    I once started re-writing a (small-ish) enterprise codebase from PHP to Java (mix of Spring and EE). Then the NodeJS hype bubble hit, and I conned my IT director into letting me try that out as an alternative option, on the basis that it should be easier to do rapid development in JS, and that finding JS developers should have been easier than finding Java devs. (The real reason was resume-driven development, but I digress.)

    About three months into the project, I threw up my hands and said fuck it because of this kind of shit -- it was the same kind of bullshit as any long-lived PHP project, just happening in real time. I migrated the backend back to Spring, this time with Kotlin instead of Java, and kept the frontend as JS. Maven is so goddamned flexible that yes, you can invoke NPM builds from a Maven module, and bundle that with your final output JAR. Between Spring Data REST and a decent frontend framework, it was great; I just wish I'd had time to learn TypeScript and React for the frontend stuff. Something something, a pox on the house of jQuery.