We are currently releasing older YOW! videos to serve as a valuable archive, preserving historical content. It is possible that a video is perceived as outdated. We believe it offers insightful glimpses into the past, enriching our understanding of history and development.
It is clear to me that JITs have a lot of benefits for squeezing out extra performance at runtime, but these managed runtimes seem to do poorly when it comes to short lived applications. For example, command line applications written in Java tend to be pretty clunky and slow. IMO, the benefit of a compiled language is that you get consistent performance.
And it's totally fine that it wasn't! What I'm saying is that the performance model does preclude some workloads. It has higher highs because it can do clever stuff on your program, but it doesn't work for every situation (e.g. short lived processes) and can have fragile optimization (e.g., if you have unexpected mixes of subtypes messing with your caching). I don't think it's a problem with java or C#, just something to consider.
We are currently releasing older YOW! videos to serve as a valuable archive, preserving historical content. It is possible that a video is perceived as outdated. We believe it offers insightful glimpses into the past, enriching our understanding of history and development.
The bit about polymorphism was interesting because that's how Rust does things but at compile time. Generics always get monomorphized.
It is clear to me that JITs have a lot of benefits for squeezing out extra performance at runtime, but these managed runtimes seem to do poorly when it comes to short lived applications. For example, command line applications written in Java tend to be pretty clunky and slow. IMO, the benefit of a compiled language is that you get consistent performance.
Java was not supposed to be used for scripting.
And it's totally fine that it wasn't! What I'm saying is that the performance model does preclude some workloads. It has higher highs because it can do clever stuff on your program, but it doesn't work for every situation (e.g. short lived processes) and can have fragile optimization (e.g., if you have unexpected mixes of subtypes messing with your caching). I don't think it's a problem with java or C#, just something to consider.
It's a problem with runtimes. 😊