I am thinking about completely stopping reading Hacker News. I enjoy the community a lot but every time I am learning something new I read about how its old and shitty and will cause hair loss when you try and invest any time in it. It puts the breaks on actually learning with the distraction of going and trying to find that new ambiguous stack that the author is hinting at.
If you learn a library, you will always be in the driving seat. If you learn a framework, well, better buckle up, because it is a bumpy ride. Frameworks are like hamburgers at maccy ds - consumption for the masses, no thinking required. Later in life those decisions can be a problem.
Today I accept that Rails is yesterday’s software
71–80 of 166 posts
Re: Today I accept that Rails is yesterday’s software
#72Re: Today I accept that Rails is yesterday’s software
#73I…don’t understand the point of the article? Ok Ruby is duck typed and has a dynamic runtime. It has for…all of the time since it was created. Rails has magic… since…all of the time since it was created. I’m not even defending Ruby or Rails here. Use at your own benefit/risk…as with every other programming language and framework.
This was one of the mistakes Django made and - to their credit - got over relatively quickly. It began as a kind of imitation of Rails but they stripped out the magic pretty quickly and made it a lot more explicit.
Re: Today I accept that Rails is yesterday’s software
#74Re: Today I accept that Rails is yesterday’s software
#75Being "yesterday's software" is a necessary step. It's the final part of the Gartner hype cycle: maturity. https://speakerdeck.com/tehviking/surviving-the-framework-hy...
Yep! Nothing wrong with yesterday's technology if you're solving yesterday's problems! I don't mean that in a sarcastic or glib way, most of your problems really are yesterday's problems. Or even yesteryear's problems…. now that I think of it, when I depart from rails in a rails project (which is common), it's usually to use raw sql, unix, various networking protocols, or other programming languages that predate rail…
Re: Today I accept that Rails is yesterday’s software
#76I am thinking about completely stopping reading Hacker News. I enjoy the community a lot but every time I am learning something new I read about how its old and shitty and will cause hair loss when you try and invest any time in it. It puts the breaks on actually learning with the distraction of going and trying to find that new ambiguous stack that the author is hinting at.
Plus I hate the forced corporate atmosphere. I've noticed anyone with strong philosophical opinions on software are typically shunned in favor of the corporate narrative.
I feel like a couple of years ago HN had a pretty diverse culture when it came to OS and software stacks, the past few months it seems EVERYONE is shoving corporate shit down my throat: VSCode, "Bash on Linux", Azure, TypeScript, Windows 10, and don't forget real programmers spend 90% of their time editing decades old MSWord files so they can't possibly go without MS office.
If it has a big corporation behind it HN will shove it down your throat, if it's a small open source project HN will circlejerk around it like it's the next big thing, if it's an OSS project that threatens some big corporate project you can bet money that HN will shit all over it.
Re: Today I accept that Rails is yesterday’s software
#77Re: Today I accept that Rails is yesterday’s software
#78Being "yesterday's software" is a necessary step. It's the final part of the Gartner hype cycle: maturity. https://speakerdeck.com/tehviking/surviving-the-framework-hy...
After 30+ years of coding, my first encounter with Rails, a summer morning I received a ripped draft of a very early book on it remains one of the seminal moments of my career - so many elegant solutions to so many issues I'd grappled with since the mid-90s
As with any tool it's got some quirks and areas I could criticise - but it's got a place in my toolkit and will have for some time
Re: Today I accept that Rails is yesterday’s software
#79Honest question. What technology are people enjoying on the server-side with sites built in React or Angular? I've seen some of these done with Rails, and some done with Node, neither of which I personally enjoy a whole lot. (Note, I'm not making an argument that either are BAD - just that I don't really like working with them). I'm curious to hear what other people are having success with in production.
I almost learned Rails in 2007 when it was at the peak of its hype cycle but after reading a series of (not very well publicized) tirades about pain that Rails' magic caused I learned Django instead.
I think node is at the peak of its hype cycle right now.