Well it is owned by Oracle now

I don’t know rust, but for example in Swift the type system can make things way more difficult.

Before they added macros if you wanted to write ORM code on a SQL database it was brutal, and if you need to go into raw buffers it’s generally easier to just write C/objc code and a bridging header. The type system can make it harder to reason about performance too because you lose some visibility in what actually gets compiled.

The Swift type system has improved, but I’ve spent a lot of time fighting with it. I just try to avoid generics and type erasure now.

I’ve had similar experiences with Java and Scala.

That’s what I mean about it being nice to drop out of setting up some type hierarchy and interfaces and just working with a raw buffers or function pointers.

I actually do like that C/C++ let you do this stuff.

Sometimes it’s nice to acknowledge that I’m writing software for a computer and it’s all just bytes. Sometimes I don’t really want to wrestle with the ivory tower of abstract type theory mixed with vague compiler errors, I just want to allocate a block of memory and apply a minimal set rules on top.

Reminds me of java

I have Toolkit toolkit = Toolkit.getDefaultToolkit(); seared into my brain. Then there were the bean factories…

Oh wow, I didn’t know you were having these problems with him.

But since you’re in my office let’s start you on a PIP and I have to write you up for this hostility against a fellow employee.