I knew the whole time it was them, and chatbots like chatGPT prove me correct. I think i was experiencing a mixture of people pretending to be retarded and retarded people, especially professors.
The chatbots will even find flaws in THE JAVA APIs for fuck's sake.... I knew there were issues with some of those libraries, but i got beat down early on by a pompous professor who would neglect to give feedback to students, intentionally withhold praise or feedback (he mostly spoke up when he could talk shit to students) and he would duck and dodge answering questions all the time. I thought I was ignoring/dodging most of his hostility as well as passive aggressiveness, but I guess not.
I also like that I can use complex english to phrase my queries and thoughts and it always understands what I'm saying. I can't even have conversations with other humans like this. At. all. I'm able to get information out of it that won't even turn up in search results.
Not used java for quite a while, I remember getting annoyed at the instanceof pattern matching because this refuses to compile:
String get_str() {...} if (get_str() instanceof String s) ...
It complains because it thinks the function call returns a string, so the check is deemed useless, and the maintainers are faggots who think useless code should be an error rather than a warning.
Problem is it could also return null, which never passes instanceof, so the check isn't useless. It literally compiles and works if you wrap the call with a cast to Object.
I also once caught the pattern matching evaluating expressions twice, causing side effects and breaking if 2nd call returns null; I think that's been fixed though.
[ + ] registereduser
[ - ] registereduser 0 points 8 hoursJun 7, 2025 09:27:48 ago (+0/-0)
[ + ] SithEmpire
[ - ] SithEmpire 0 points 8 hoursJun 7, 2025 09:44:10 ago (+0/-0)
Not used java for quite a while, I remember getting annoyed at the instanceof pattern matching because this refuses to compile:
if (get_str() instanceof String s) ...
It complains because it thinks the function call returns a string, so the check is deemed useless, and the maintainers are faggots who think useless code should be an error rather than a warning.
Problem is it could also return null, which never passes instanceof, so the check isn't useless. It literally compiles and works if you wrap the call with a cast to Object.
I also once caught the pattern matching evaluating expressions twice, causing side effects and breaking if 2nd call returns null; I think that's been fixed though.
[ + ] Master_Foo
[ - ] Master_Foo 0 points 7 hoursJun 7, 2025 11:06:19 ago (+0/-0)
[ + ] FreeinTX
[ - ] FreeinTX 1 point 10 hoursJun 7, 2025 07:40:34 ago (+1/-0)