Holy cow #Java, not only you have to have a class of Date+time in a timezone, but also a _completely different class_ for Date+time in an _offset_?!?
Dammit #Java, you add a new class for date+time that are better then the original Date, but you make it _without_ a timezone, so you have to have _another_ class to have date+time with timezones?
What the fuck is wrong with you?
If #Java Date is not timezone-aware, but LocalDate is, why isn't Date declared deprecated already?
Once again, #Java functional interfaces letting me down.
(I just need to convert one object, an object with some information from our provider [an object, 'cause #Java], to our own data representation.)
Here I am, looking at #Java `Function` so I can apply a `.map()` and all I can think of is "This is a perfect place for Rust `From` trait..."
Maybe I should've never learn stream from #Flink, 'cause now I'm trying to use #Java streams and my business logic is "for this thing, do this, that and that other thing" (where "this", "that" and "that other thing" are completely different and not related) and there isn't a freaking "split" operator.
I never did my #Introductions but...
Software developer for 20 years -- yeah, I started working professionally when I was 12 and didn't drop the field yet. I used most languages around, but I'm a fan of #Python and #Clojure, although these days I work with #Java and I want to play with #Rust.
I'm also a biker, and that's why I hate when it rains.
functional.cafe is an instance for people interested in functional programming and languages.