pie_flavor goes to a lot of effort for no reason
-
@pie_flavor said in The Official Status Thread:
status: God damn, I'd forgotten just how awful NodeBB was. Considering making a GUI client just so I can use the forums without getting a headache.
https://i.imgur.com/zwuc1Zm.png
Next step: reading threads.
-
@pie_flavor Front page WTFs are .
-
If you're going to waste your time making a redundant GUI, you should at least give it an Up Up Down Down Left Right Left Right B A Start easter egg.
-
https://i.imgur.com/x3S0zhV.png
https://i.imgur.com/WJusxVy.png
https://i.imgur.com/aoiJcoU.pngEvery five seconds I find another one of these. Goddammit.
Well, if I have to provide default values for every single field then at least I don't need like five different versions of, say, User, depending on what context it's appearing in.
-
What fucking deserialization library doesn't use the default value for a nonnullable defaulted field when it encounters JSON null, or doesn't assign null to a nullable non-defaulted field if the field isn't present?
-
@pie_flavor I give up. What fucking deserialization library doesn't use the default value for a nonnullable defaulted field when it encounters JSON null, or doesn't assign null to a nullable non-defaulted field if the field isn't present?
-
@boomzilla kotlinx.serialization, apparently.
-
@pie_flavor said in pie_flavor goes to a lot of effort for no reason:
What fucking deserialization library doesn't use the default value for a nonnullable defaulted field when it encounters JSON null, or doesn't assign null to a nullable non-defaulted field if the field isn't present?
I'd expect the library to blow up since the data doesn't match the data structure definition. I'd also expect/want the default-having field definition to allow you to say "accept null as default value". But not by default. By default assume garbage is garbage.
-
@pie_flavor said in pie_flavor goes to a lot of effort for no reason:
Every five seconds I find another one of these. Goddammit.
Yes, 90% of code is about handling unexpected conditions. Every 5-minute task takes 50 minutes to debug and fix all the details.
And if that's what you found just implementing the basic rendering stuff, imagine how many annoying tiny little things you'll find while building the editor, notifications, user profiles, navigation, groups, chats, search, etc.Also what GUI library is that? Looks like you're just manually drawing text on a blank canvas. Aren't there any widgets you could use?
-
@anonymous234 TornadoFX. I dunno what makes you say that it doesn't look like I'm using controls.
-
@pie_flavor yeah...dunno...but your screenshot gives me geocities flashbacks.
-
@boomzilla said in pie_flavor goes to a lot of effort for no reason:
@pie_flavor yeah...dunno...but your screenshot gives me geocities flashbacks.
You say that like it's a bad thing. Geocities, before Yahoo bought it and ruined it, was great, for its time.
-
-
@SlackerD
Reason why Git is fundamentally broken #23158: Only files are considered "real". Directories only matter insofar as they're a place to put files.
-
@SlackerD Unrelated but funny:
-
My favorite
bugfeature of NodeBB's API is that, depending on what endpoint you call, a post object'scontent
property is either the fully rendered HTML to be displayed in the page, or the raw text the user has written. And there is no way to get the posts in a topic without providing the first one, and there is no way for me to display anything other than the second one. Hello, fifty-requests-a-second.
-
@pie_flavor said in pie_flavor goes to a lot of effort for no reason:
there is no way for me to display anything other than the second one.
False! Simply embed an HTML renderer, one for each post!
-
@Mason_Wheeler said in pie_flavor goes to a lot of effort for no reason:
Only files are considered "real".
I believe there's a way to tell the github UI to not do that (or there used to be) but you don't usually want it. You particularly don't want it when you have deep directory hierarchies, such as is common in some languages/systems. (A big shout-out to Java and Maven, here!)