• 0 Posts
  • 38 Comments
Joined 2 years ago
cake
Cake day: March 4th, 2024

help-circle

  • I personally haven’t looked at the port myself, but generally LLM/AI agents generate “slop” until a human expert reviews all of it. Which in most cases never happens. Instead they just review with another “higher tier” model.

    As someone on hacker news put it regarding a subject about using LLMs for everything:

    A decent proxy right now is that if you have zero external dependencies then your solution is probably a toy.

    This can be related because unless they are actually using the best libraries in the ecosystem while they are porting then it’s going to be a mess to maintain and also alienates the ecosystem.


  • These kinds of struggles with JavaScript and TypeScript are part of why I moved to Rust. I value the sanity checks the compiler provides: warning when a Result is ignored and refusing to compile when a match on an enum is missing a branch.

    Also, in Rust, Result is for recoverable failures, while panic! is generally reserved for bugs, broken internal assumptions, or cases where the program has reached a state that it believed should be impossible.




  • I skimmed the article and they just say:

    • Don’t roll your own page scrolling.
    • Don’t roll your own link navigation.
    • Don’t roll your own text selection.
    • Don’t roll your own context menu.
    • Don’t roll your own copy and paste.
    • Don’t roll your own password field.
    • Don’t roll your own date picker.

    For a date picker I initially disagreed but then their argument about how you can just use 2x input type=date for the start and end date and then it’s consistent across every site was pretty reasonable. I’m not gonna go read mdn on its capabilities right now so maybe there’s still some valid use cases for not using one, like conveying to the use what valid ranges they can select.

    But yes I agree you shouldn’t use a library for something simple like left-pad


  • This always grinds my gears. When I was hosting custom Minecraft servers back in 2011 we had so many server side anti cheat measures in place. Prevented people from moving too fast. Randomized blocks until you exposed them so xray wouldn’t work. Logblock to identify griefers and do immediate rollbacks.

    I remember this one time we had a group get on and grief someone that didn’t set up a claim yet and they thought they were so sneaky by distributing the loot amongst friends and chests. We just followed the stacks in the logs and restored everything then banned them. We actually had more people end up joining because how much auditing we could do, they probably felt like they could invest time into the server.

    Now it’s like just trust the clients for everything and “oh we can’t ban them until the next ban wave because we don’t want them to know how we caught them”. It’s lazy. Back in the pubg days I remember seeing someone get 75 kills in a matter of 3 minutes. They didn’t get banned. They didn’t even have line of sight. Ban waves still allow peoples experiences to be compromised.






  • My experience might not match others but honestly I would recommend avoiding this trap. It’s just compromise and disappointment all the way up. Then you’ll be blamed for anything that goes wrong despite only 15% of your plan being accepted by executives. If the company culture is different and fosters leadership instead of stifling it then maybe it could work. At the end of the day you’re probably still going to be making someone else’s dreams come true until you start your own company.



  • Rust is a fantastic language for game dev. It just requires you to think completely differently if you want to have a good time. You can totally write the traditional game loop or my preference ECS (bevy as one example). ECS still let’s you do the crazy mutations without having to worry about ownership. Each system can focus on the components they care about and you can specify the order they run. If you want to be reckless and mutate global state, then you need to explicitly decide between things like RwLock<T> and RefCell<T> for example. I’m not saying everyone should drop whatever they prefer to instead use rust. It’s ok to stick with what you know or enjoy. Good games are agnostic to the tools used to make them. I just don’t think Rust deserves to be dismissed the way your statement does.