• 0 Posts
  • 343 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle






  • This sounds like someone who’s never worked on a large Python project with multiple developers. I’ve been doing this for almost two decades and we never encounter bugs because of mismatched types.

    Have you worked on major projects in other languages in that time period to be able to compare and contrast?

    The last two python projects I had to work on didn’t have bugs because of type issues, but it was much harder to come into the codebase and understand what was going on given that you didn’t have type information in many many places which forced you to go back and comb through the code instead.


  • Yeah, working on python projects professionally is always a nightmare of configuring env variables and trying to get your system to perfectly match the reference dev system. I find Node.js projects to often be the simplest and most pain free to setup, but even compiled languages like C# and Java are often easier to get up and going than python.


  • masterspace@lemmy.catoProgrammer Humor@lemmy.mlBefore and after programming
    link
    fedilink
    English
    arrow-up
    29
    arrow-down
    2
    ·
    edit-2
    22 days ago

    I don’t mean this insultingly because lots of programming jobs don’t require this and for the ones that do we still tend to all start here, but in all honesty this sounds like it’s coming from someone who’s never worked on a large project maintained by multiple people over time.

    First of all, the hysteria over semicolons is ridiculous when JavaScript, Typescript, C#, Java, Go, Swift, etc. etc. wil all automatically highlight missing semicolons, if not automatically insert them for you when paired with an IDE and standard linter. On top of that, JavaScript and Typescript do not require semicolons at all, but they are still used alongside braces, because they make your code more scannable, readable, and moveable.

    Secondly, without type safety your code is no longer predictable or maintainable. If you’re working to quickly sketch out some new fangled logic for a research paper it’s one thing, if you need to write test code so that your codebase can be tested an infinite number of times by other coders and whatever CI/ CD pipelines to make sure that nothing’s broken, then all of the sudden you start seeing the value in strict typing.

    Honestly, complaining about type safety adding “extra code” is a complaint that almost every coder has when they start out, before you eventually realize that all that “extra code” isn’t just boiler plate for no reason but is adding specificity, predictability, reusability, and maintainability to your code base.

    When defining types looked like this it was one thing:

    String name = new String("Charles Xavier");

    But when it looks like this, there’s no reason not to use strong typing:

    const name = "Charles Xavier";









  • It’s not about cheapness, it’s about consistency.

    You wanna set up different dev environments and process for every single language you or someone from your team might use? Oh we need documentation and a license for IDEA when we’re doing Java work, and PyCharm when we’re doing Python work, and WebStorm when we’re doing JavaScript work, or we just all use VSCode for everything.

    I’ve worked on Java teams, Python Teams, JavaScript Teams, C# teams, and quite frankly, I’ve seen no major benefit to a dedicated IDE for that language vs just configuring VSCode plugins and CLI scripts.