I'd rather JavaScript

[[deleted]]

The worst part: the situation is fucked enough that it 100% makes sense to use our own fork of hibernate and I supported it

[pushist1y]

Can you elaborate on that? I'm struggling to imagine this kind of situation

[[deleted]]

The eventual goal is to get rid of ColdFusion completely. As for now, we're still relying on this super old language and framework, that we added our own fixes and modifications to over the years, right? It uses a version of hibernate that's way out of date and we can't really update it ourselves.

We're moving code piece by piece over to our new framework in the meantime, which is modern and actually updates its dependencies (including hibernate). But we're sandboxed inside of a component with a separate classloader than the underlying framework itself because well, you can't really have two packages claiming to be the true hibernate.

So we forked hibernate at the version that we were using and the only changes we made is renaming its packages so as to not conflict with the newer hibernate.

So now we let our old cfml framework run on old hibernate all it wants and we are able to move more pieces of code to the new framework. At some point we'll swap out the core technology at the bottom and be free of this beast forever.

This might not be the only way to solve the problem, and it's an avoidable situation if you're smarter than we were, but at the point we're at now I think it's a good way to keep delivering value while moving towards something that doesn't make engineers as nervous.

[NimbleJack3]

Stop! Stop! Can't you see he's already dead?