• 0 Posts
  • 60 Comments
Joined 2 months ago
cake
Cake day: July 29th, 2024

help-circle


  • I’ve found they’re great as a learning tool where decent docs are available. Or as an interactive docs you can ask follow up questions to.

    We mostly use c# and it’s amazing at digging into the MS docs to pull out useful things from the bcl or common patterns.

    Our new juniors got up to speed so fast by asking it to explain stuff in the existing codebases. Which in turn takes pressure off more senior staff.

    I got productive in vuejs in a large codebase in a couple days that way.

    Using to generate actual code is insanely shit haha It is very similar to just copy pasting code and hacking it in without understanding it.





  • The problem with dynamic typing is you can’t always figure out what the type is even with investigation as it can be lots of things based on what is passed or returned. It also allows incorrect values to be passed.

    People will indeed make that readability argument but if the type is not obvious and important to understanding the code then it likely shouldn’t be used there.


  • auto isn’t dynamic typing it’s just type inference. It still has a fixed type you just don’t have to write it. Like var in C#.

    Lambdas are just a way of defining methods in place. It has nothing to do with callbacks.

    But you’re spot on for memory safety. Managing it yourself is risky and if it can be managed at zero cost it seems stupid not to.







  • I think the point is they aren’t forcing it at all. It’s being used with the blessing of Linux Jesus and the others are just throwing their toys out of the pram because they don’t want to learn it.

    Someone else linked the video on this post. They are rude as hell and the rust dev isn’t even asking them to use it.

    Again I think that’s a bad attitude towards technology. Use the best tool for the job and you’d get used to the syntax pretty quickly.

    It’s like someone who started on python not wanting to learn a c style language.


  • It is literally being pushed for its technical merits and traits.

    Memory safe code with comparable performance in the kernel seems like an absolute no brainer.

    Also if you watch the video all he’s asking for is consistent interfaces for the file systems. He’s not even trying to get them to use rust. And the guy starts screeching about how he’ll code however he wants.

    Is it wrong to expect a consistent and well documented interface?

    Pretty sure C is actually being pushed against its technical merits here.




  • I would say being more inclusive is bringing value.

    There’s a massive issue with women being under-represented in STEM and little things like this only further cement that.

    It’s casual sexism. I’m not suggesting they are intentionally hating on women.

    Assuming it’s a man because it’s programming is fundamentally sexist.

    What downsides would they be?