4 ms·

This comes across as an angry rant that the author chose the less popular toolset. We’ve all done that. We all learn some toolset that seems great and then it g

This comes across as an angry rant that the author chose the less popular toolset. We’ve all done that. We all learn some toolset that seems great and then it gets plowed over by something else. As I recall, Angular was plowing over itself for a few years. People have been arguing about languages, OS’, platforms, architecture for decades. I bet you can even find a grumpy engineer who thinks our tech should all be TTL instead of CMOS. It sucks when your investment doesn’t pay off, but there’s not some grand conspiracy to deny your preference. People just like what they like.

BaseballPhysics 4y ago
> It sucks when your investment doesn’t pay off, but there’s not some grand conspiracy to deny your preference. You... really didn't read the article, did you? In the opening they state: "My skills as a Ruby on Rails developer today are by far more valuable than any skills I would have gained pivoting to full-time AngularJS development in ~2014". Doesn't sound like someone who's worried that their "investment [didn't] pay off". Hell, they even close it with: "In the year 2033, I am 100% convinced my skills as a Ruby web developer will be by far more valuable than any skills gained learning React…" Seriously, I get it. You don't agree with the author. Cool. But why make up some fictional motivation like this?
- sircastor 4y ago
  I did really did read the article. And I stand by my statement. Even though they're comfortable with their Rails skills, the whole article reads to me like someone who didn't pick the winning horse. > We were told writing apps... using our preferred language/tech stack of choice, was outdated and bad for users. > how do you trust developer communities which have been overrun by people who are giving you false and misleading information on a regular basis > No, YOU—the JS-framework-stans—intentionally created a world that excluded those of us I guess we took different things away from the article.

BaseballPhysics 4y ago

> It sucks when your investment doesn’t pay off, but there’s not some grand conspiracy to deny your preference. You... really didn't read the article, did you? In the opening they state: "My skills as a Ruby on Rails developer today are by far more valuable than any skills I would have gained pivoting to full-time AngularJS development in ~2014". Doesn't sound like someone who's worried that their "investment [didn't] pay off". Hell, they even close it with: "In the year 2033, I am 100% convinced my skills as a Ruby web developer will be by far more valuable than any skills gained learning React…" Seriously, I get it. You don't agree with the author. Cool. But why make up some fictional motivation like this?

sircastor 4y ago
I did really did read the article. And I stand by my statement. Even though they're comfortable with their Rails skills, the whole article reads to me like someone who didn't pick the winning horse. > We were told writing apps... using our preferred language/tech stack of choice, was outdated and bad for users. > how do you trust developer communities which have been overrun by people who are giving you false and misleading information on a regular basis > No, YOU—the JS-framework-stans—intentionally created a world that excluded those of us I guess we took different things away from the article.