space_comrade [he/him]

  • 0 Posts
  • 30 Comments
Joined 4 years ago
cake
Cake day: November 11th, 2020

help-circle



  • I don’t like VMs because I need to allocate memory upfront for it, and considering it’s a Windows VM and depending on the dev work you’re doing on it you might need to give it 10Gb+.

    If it’s at all possible for OP I’d recommend getting a separate physical workstation and then just remoting into it with your Linux machine, if you use VSCode the process is pretty much seamless, you use VSCode from your Linux machine normally while all the work is being done on the remote machine.










  • because no compiler can check to see if you thought of everything.

    We can try to get closer to that with better language design. You’ll never get there but I think there are obvious benefits as to why you’d want to do that.

    I write way less bugs in Rust than I have in Java or C++, and that’s mostly thanks to the language design.

    I’m just tired of people entirely dismissing languages like C because they don’t have these features. Especially when the operating systems their code runs on and their languages may even be implemented in C!

    Because that code has been review and re-reviewed and patched by experts in the field for years. You’re not gonna write a backend for an app with short deadlines in C because that would be absolutely fucking insane.








  • Most types force premature design/optimization.

    I disagree. What you’re saying is true for Java-like OOP languages because OOP is actually complete garbage if you want to design good, easy to understand abstractions. Types are way more elegant in functional or functional-inspired languages.

    Most unit tests lock up some specific implementation (increasing cost of inevitable refactors) rather than prevent actual bugs.

    Agreed, unit tests are useless in most cases, they mostly test the bullshit abstractions you built for the unit tests themselves.