5 ms·
2010 - Making switch from PHP to Ruby 2013 - Making switch from Ruby to Node 2016 - Making switch from Node to Go 2019 - Making switch from Go to {hype}
by romanovcode 11y ago
2010 - Making switch from PHP to Ruby
2013 - Making switch from Ruby to Node
2016 - Making switch from Node to Go
2019 - Making switch from Go to {hype}
- tptacek 11y ago"So what I'm saying is, we should all still be using PHP."
- mwcampbell 11y agoOr Perl, or C. After all, even PHP was once a new hipster language. Of course, it's good to be skeptical of the current hyped flavor of the moment. But some languages really are better than others for specific tasks, and new languages do sometimes improve on their predecessors.
- collyw 11y agoC is still the choice language for many things. Perl is still cool to me, though seems to have been replaced by Ruby for web development.
- bliti 11y agoWhat is star fighter written in? Curious, no bad intentions.
- dikaiosune 11y agoIIRC, it's got some Go infrastructure and the trading chapters have bots written in Ruby.
- tptacek 11y agoGo, Ruby, and React.
- brightball 11y agoIronically enough, given the recent improvements, performance and productivity...that's not really out of the question...
- noir_lord 11y agoStill using PHP (and Python and some other stuff) in 2016. I make it a rule to only jump on the new bandwagon when I know it's not going to explode in 3 months and currently isn't on fire.
- deleted 11y ago[deleted]
- touristtam 11y agoGo has been out for quite a while now, so I'd say it is pretty safe to try it out if you feel like it. I wouldn't swap PHP for Go personally.
- ungzd 11y ago2013 - switch from sane, stable, mature language to weirdest scripting engine extracted from web browser. Because lol that's cool to tear out javascript from browser and put to server lol rofl. 2016 - switch to low-level language, much lower-level than PHP, Ruby and Javascript. Because computers became slow lol. 2019 - switch to PL/1 and raw disk sector addressing because bigdata smoothie silicon googley disrupt the world
- cloverich 11y agoAnd as long as new ideas come about (in the form of languages / platforms), people will keep trying, learning, and sharing. Thankfully.
- collyw 11y agoThe problem is most of the ideas are not new, they are rehashes of old ideas. Many people aren't learning, they are just jumping on the hype wagon without much reasoning.
- 0xmohit 11y agoThis is inevitable. However, not everything is {hype}. Consider rust, for example. People have managed good stuff using that. Dropbox, Servo are widely known examples.
- AsyncAwait 11y agoSpot on, while I see problems with many of the latest technologies myself, not EVERYTHING is hype and I am getting tired of people labeling it as such just because they don't want to learn it/make the switch but want to mask it like they would if it wasn't just hype. I've seen this very recently personally, where I was accused of adopting hype for switching to Swift for a major rewrite of my app, where I'd pretty much start over in Objective-c anyways so I may just as well do it in a safer, much nicer language that's going to be the future of the platform eventually anyway... It turns out that you don't have to switch - if your current stack works well for you stick with it. It doesn't make you "less cool". But it also doesn't mean that somebody else doesn't have a legitimate reason to adopt the new technology, and this is a pretty textbook example of what I'd call a justified switch.
- ciokan 11y agoResults talk. We make the switch to whatever works. I don't take the hype, I'm just grateful we can consider options.
- dustingetz 11y agoBack to Node - all new languages will target node and browsers via compile to js, and many modern languages are gaining js as a target platform as we speak.