Re:The problem with new URL(), and how URL.parse() fixes that
by michaelcampbell on Monday May 20, 2024 @08:16AM
(#40414631)
> It was easy to miss one of the dozen exceptions and only have the compiler point you at it
This sounds like (one of?) the killer feature of types, though.
> after wasting several minutes on compilation (think 133MHz CPUs and slow HDDs).
Sure, but everything we did was slow then.
Re:The problem with new URL(), and how URL.parse() fixes that
by robertlagrant on Monday May 20, 2024 @08:21AM
(#40414670)
I don't remember Java being that slow even on a 133MHz CPU. Maybe if it was a giant project, though.
Type inference in modern Java makes you forget how long and repetitive type signatures used to be in it 20 years ago.
BTW this makes Result<D, E> more ergonomic anyway: you still have only one E, at least one per invocation level. With checked exceptions, you had to haul a whole garland.