Eclipse

so yeah, that, that sort of thing grew out of my control, and it also helped.

And this was, you know, back in, this was also in the days where there was this IDs, like Eclipse and NetBeans, and they were very modularly designed to the extreme.

Right.

Almost to the extreme.

... and some of the teams that I worked with are like, "What is that? What is that mess? What are you doing?" Like, "Why do you need all that?" Uh, and I had all my, my shortcuts and my plug-ins, and I had my things that were running locally, et cetera.

Um, and then later there was this phase where the entire team standardized on Eclipse, and not only did they standardize on Eclipse, they standardized on the plug-ins.

So you wanted to, to ride this ride, you wanted to be on this team, you had to have these plug-ins, and you hit these buttons inside of your IDE in order to move things through.

Everything was beyond just the code.

I'm aiming today to cover at least one to two years of history.

And I was sure that the last time the cliffhanger was not Eclipse Collections, but I forgot what it was.

And I found it right now.

It was Clipper.

Yeah.

T is type or what's,

Yeah, so for a function, I think in Eclipse questions, for our function type, we say that's a function over T, and it will return a V as the output.

I asked once why T and V are not proper names.

Yeah.

You know, was a programmer, contributed to Linux, contributed to a bunch of open source projects, Eclipse, JAG, all these things.

Ooh, Eclipse.

Yeah, old school.

Old school.

And that was one of the early days, kind of like open source companies.

Which one? When it was cool.

Eventually it's called Eclipse Source, but we had our, back in the day, remember you're like Spring Source? Spring Source.