Yeah... Usually if you join a company with bad practices it's because the people who already work there don't want to do things properly. They tend to not react well to the new guy telling them what they're doing wrong.
Only really feasible if you're the boss, or you have an unreasonable amount of patience.
No I'm good with smart IDEs. Anyway don't people set up Vim as practically an IDE these days anyway? That's what Vim users always tell me.
Yeah IIRC it deletes them, which is as mad as you would expect. Maybe they've fixed that since I used it last which was some years ago.
Yeah I think it's trauma due to C/C++'s awful warning system, where you need a gazillion warnings for all the flaws in the language but because there are a gazillion of them and some are quite noisy and false positives prone, it's extremely common to ignore them. Even worse, even the deadly no-brainer ones (e.g. not returning something from a function that says it will) tend to be off by default, which means it is common to release code that triggers some warnings.
Finally C/C++ doesn't have a good packaging story so you'll pretty much always see warnings from third party code in your compilations, leading you to ignore warnings even more.
Based on that, it's very easy to see why the Go people said "no warnings!". An unused variable should definitely be at least a warning so they have no choice but to make it an error.
I think Rust has proven that it was the wrong decision though. When you have proper packaging support (as Go does), it's trivial to suppress warnings in third party code, and so people don't ignore warnings. Also it's a modern language so you don't need to warn for the mistakes the language made (like case fall through, octal literals) because hopefully you didn't make any (or at least as many).
Yeah most uses of the factory pattern are unnecessary and it's mild code smell IMO. If your factory only returns one type you should definitely just use that type's constructor.
This can work for junior devs who aren't stuck in their ways. Unfortunately there are too many "senior" devs who are happy making crap. It's hard to fight them constantly to do things properly (e.g. write actual commit messages rather than just "Fix #836") so using tools like linters where possible is definitely a big improvement.
I liked Netbeans much more than Eclipse. It didn't have that stupid workspace system at least.
If you consider that "pretty close" then I think you're going to dismiss anything else I say as insignificant anyway.
You can't have a full integrated debug session with a watch window, locals (with an expandable tree for objects), stack, breakpoint list all visible at once. I.e. something comparable to this.
They're not significantly different. Maybe it takes you 1s and me 2s. Not worth the effort of learning. Especially because Vim comes with significant downsides compared to full IDEs that will make you slower overall.
you really think its a giant conspiracy from elitists lying about their experience
Pretty much, yes.
You think thousands of developers are handicapping themselves for bragging rights?
Absolutely. That's completely normal human behaviour.
Yeah I kind of agree but I also think when it gets to that point we'll have much bigger problems than programmers losing their jobs. Like, most of society losing their jobs.