MVVM is an antipattern
1 0 comments 11 Feb 2020 23:20 u/flapjack_charlie (self.programming) in v/programmingComment on: COGTFO Code of Conduct Proposal
Wow... a code of conduct I actually agree with. Holy shit Batman!
Comment on: golang code of conduct proposal
Fuck everything about this and every "code of conduct." Since their inception coders have generally been a bunch of loud-mouthed opinionated dorks because we're fanatical about what we do. It's what makes us good at it. We don't need "safe spaces" because frankly how fucking much safer can you get than reading words on the other end of a screen?
If you're a fuckwit you deserve to get called out on it. We are engineers and we deal in what works, not what feels. Literally the only code of conduct anyone should need is "don't be too much of a dick unless you need to."
Comment on: This Is Not Your Fathers FORTRAN
Does it support recursion yet?
Comment on: These Are the Highest-Paying Programming Languages (do you agree?)
I'm a C++ guy with about 15 years experience in that language. Yes, you can find high paying jobs in C++ but that's because nobody's learning it anymore. I would be concerned that it's going to be phased out eventually, leaving the C++ gurus high and dry.
This may not hold for gaming, but from where I stand even low-latency real-time applications can be written in languages like Java and C# these days.
No, I've worked for the past 20 years in the industry and been everything from a jr dev to a CTO. My experience well predates mvvm and yes, I've had to rewrite the spaghetti code you've mentioned. I still think mvvm is an anti pattern. Quite simply, the amount of time I spend having to engineer it is far greater than the time it saves me having to re-engineer things.