[-] firelizzard@programming.dev 1 points 5 months ago

Ok… but we’re comparing Linux, Windows, and macOS. Talking about something that can only be done on one of them is kind of pointless. You said “I’d run Windows over Mac any day” and then shat on Xcode. That makes it sound like you prefer Windows because you hate Xcode. From my perspective - the context of things that could also be done on Windows - the solution is obvious: don’t use the tool you hate.

[-] firelizzard@programming.dev 1 points 2 years ago

Two cocktails will get me tipsy, two beers if they’re strong, but I can drink an entire bottle of vodka (over the course of 2-3 hours) without blacking out. Or at least I could in college, I’m not looking to try again.

[-] firelizzard@programming.dev 1 points 2 years ago

Ah, well that’s great for folks who already know or want to learn Rust

[-] firelizzard@programming.dev 1 points 2 years ago

I’d rather spend my free time doing something I enjoy

[-] firelizzard@programming.dev 1 points 2 years ago

I thought there was security code to stop that kind of thing. Granted, it's been over 10 years since I've done anything with Java more than tinkering with Minecraft mods.

[-] firelizzard@programming.dev 1 points 2 years ago

Go is just as easy. Install the compiler, write a file, compile it, get an exe. And a lot less foot-guns.

[-] firelizzard@programming.dev 1 points 2 years ago

VSCode has tons of features that save a lot of time. Unless Zed manages to get close to feature parity, I don’t see how it can complete from a productivity point of view. VSCode’s UI performance isn’t stellar but it’s not nearly bad enough to counteract the productivity boost I get from its features.

[-] firelizzard@programming.dev 1 points 2 years ago

*when I'm doing debugging that requires commenting out code.

Most of the time, I don't comment out code. I run the code in a debugger, step through it, and see how the behavior deviates from what I expect. I mostly only resort to commenting out code if I'm having trouble figuring out where the problem is coming from, which isn't that often.

[-] firelizzard@programming.dev 1 points 2 years ago

You get used to it. The only time I really notice it these days is when I’m debugging and commenting out code.

[-] firelizzard@programming.dev 1 points 2 years ago

I think the degree of footgun danger depends a lot on the language and the application. I agree that C and C++ are dangerous until you really know what you're doing, though IMO most of the danger comes down to memory management and that's a portable skill, once you've learned it. That being said, I don't have a lot of experience with C++. C was my first language so I'm used to plain old normal boring pointers (are those "dumb pointers"?) and I've never understood why C++ needs 9 billion types of pointers.

Go has one particular footgun - loop range variables. Other than that, IMO high-level, garbage collected languages don't have major footguns like that. My first job was writing a bespoke inventory system for a manufacturing company, and I wrote it in a language I'd never used before - C#. In five years the only major issue that had was due to my inexperience with SQL and had nothing to do with C#. And though I haven't written nearly as much code, I'd say the same about Java, Ruby, Python, and JavaScript.

[-] firelizzard@programming.dev 1 points 2 years ago

Did I find another Sanderfan in the wild?

[-] firelizzard@programming.dev 1 points 3 years ago

We are already using GitLab

view more: ‹ prev next ›

firelizzard

0 post score
0 comment score
joined 3 years ago