WildFly

Uh, they've got underlying enterprise support at the operating system layer, usually something like RHEL, and then they'll have some platform support higher than that.

You know, maybe that's a, a JBoss or something like that.

Um, but more than half of the code is kind of running as dependencies in between those stacks or on those stacks.

And, uh, for us, the, the real question was, um- Understanding and talking with customers that unless that full stack is secured somehow, they're always going to have problems and vulnerabilities.

Ang- Angular, yeah.

We actually never got to Angular 2 because React was there, right? And then React took over, and then it was like, you know, on the, on the back end we also went through everything from PHP and, you know, the LAMP stack, uh, then it was like more like Java and JBoss stuff, and then kind of we landed on Node, which was like typical, uh, and Mongo for the database and stuff, right? So I would say, I would say like we quickly burned through all the stacks which we're kind of developing in, you know, these like four, five, six years, and then it was like typical framework fatigue, I, I would say, right? When you start feeling, ah, I can't, I can't.

It's like a, you know, like a new hardness now every day.

That's, yes.

was just like CRUD boring.

And what was the stack? JBoss or...

I remember my first big Java project for a company was JBoss Sim.

Uh-huh.

The Angebo theme was very popular and this was like the seamless integration between user interface and backend.

Not with the actual output or with the framework itself, but more with integration.

Yeah, tooling.

And you spent your time with JBossim and JavaE or...

people

building application server integrations, JBoss, IBM and BEA and Oracle at the same time, and suddenly And there's even, you could do WTP for like FTP servers too.

It wasn't just app servers.

It was like any deployment target, right? Like, so yeah, it was a good mini thing.