Y u no Mamaleek

  • 35 Posts
  • 470 Comments
Joined 1 month ago
cake
Cake day: November 3rd, 2025

help-circle










  • Wow, that’s amazing crock of a shit of a speech you have there. You don’t know anything about anything, but you’re ready to pump out a whole pageful about it. It’s quite impressive.

    You didn’t study shit, but you bet it’s all fine. You bet the database stays the same, and the protocol is all fine, and nothing is ever bothered by anything. It’s all some ‘SQL’ bullshit, why bother about it when smelly nerds can bother about it all they want, right? It’s just some ‘SQL’ fucking nonsense, it means nothing anyway. Just style the UI and process the comment, and it all goes away, you fucking nerd, why are you ever bothered about anything?

    sniff

    Oh maybe it might in fact make more sense to have it processed by the post instead of the semantics being attached to the fuck of the comment, what the fuck do I know. Just edit the fuck out of it, it makes more sense on the other hand. We need to trust processing by the semantics of the sense, why not. Who can edit it, incoming parties, yeah! Admins or mods, I’m not even sure.

    sniff

    Then there’s the skin the cat, we can have many long meetings, the specifications, choose a bit, make mistakes, what the fuck do I know. A bit more explorative, make mistakes, fix them, it’s all fine. That’s the great thing. Fixing mistakes. sniff That’s the great thing with programming. It’s very cheap compared to, uh for example to, uh a mechanical, who maybe likes uh to avoid. But that also means. The opportunity. There’s a time bang for each bang of the methods. bang

    sniff

    I really can’t make a good statement here. It’s regularly not as simple. The trick is to apply the correct one.




  • I have a bit over twenty years with some of them spent at a site that had a million users daily. Seeing as we’re measuring dicks here.

    We’re not building a space shuttle, here. Lighten up.

    Come on man. It should be a mantra for web devs to never ever lose or bungle users’ data. You know, the thing that gives the web its entire worth, one person sharing with others their personal experience in overcoming the daily grind and tedium: them asking “how do you deal with this shit?” and others replying “well if you contort just so to keep your back from giving out, and press these buttons, you can in fact live to the end of the day”. This should persist on the web for years to come and for everyone to discover. But somehow you think that if you save five minutes on ruminating through your decisions, that’s worth a whole lot and everyone should cheer on you for implementing that change despite the fact that I could overwrite that reply with “you greedy schmuck need to shut up and do your miserable job because you suck”, and this is entirely okay with you.


  • The issue with the Stack Overflow that you refer to, despite Rimu’s somewhat cheerful comment in that chain has been noted. I suspect it won’t stay that way.

    This is more informative that what you said above.

    Since you appear to be knowledgeable: out of curiosity, has this feature been released to the public? Another commenter wrote that it’s only in testing yet, but idk myself how to take the original posts from Rimu.




  • things often get fixed or changed around once necessary. Not sure if that’s a wise decision here. The JSON exchanged between the servers is probably extra work if changed around later.

    Exactly, changing a protocol is not like changing centralized functionality. Not only it introduces mess that could’ve been avoided and mandates some compatibility measures while every client picks up the modified protocol, but it also allows posts to be messed up while this is fixed — without a way to restore the data as it should be, because false data on the comments is indistinguishable from the user changing the selected answer.

    Messing up or losing users’ data should be the biggest no-no in web programming, but some people are remarkably carefree about it.



  • break the server for a few hours every once in a while

    That’s not what botching the protocol does. It opens the way to mess up the posts that shouldn’t be messed up, until the devs get around to fixing it in the protocol and implement the fix on the server and all the clients change their implementation. By that time data on the posts can be irretrievably borked unless someone sits down and retroactively reassigns which answer is the the ‘selected’ one, which again might need an addition to the protocol because it isn’t a central database, except the dev also can’t actually unilaterally decide which is the ‘selected’ answer because the user might’ve changed the selected answer themselves.

    Does this sound like ‘breaking the server for a few hours’?

    This smells of fresh college-grad coding with people who can’t foresee how their programming decisions affect the software’s workings in the future.