If I was building a product focused stack, then I would simply do React+ Typescript. Why bother bringing in two different languages for front end and backend ?
Typescript is pretty awesome in itself.
21–30 of 80 posts
If I was building a product focused stack, then I would simply do React+ Typescript. Why bother bringing in two different languages for front end and backend ?
Typescript is pretty awesome in itself.
EDIT: On the other hand, I wouldn't choose Rails for a project where the main concern is performance/scalability
Wouldn't Python/Django make more sense in 2018 considering that Python could be used for data science and machine learning? I realize this is a Python vs Ruby question, but if you didn't know either Python or Ruby and were trying to pick between Django and Rails for a project, wouldn't you pick Django in 2018 due to future data science and machine learning opportunities?
No. Learning Python is quick and simple compared to learning data science or machine learning. Knowing Python and Django (which I do) does not afford you any ability do to those things.
Wouldn't Python/Django make more sense in 2018 considering that Python could be used for data science and machine learning? I realize this is a Python vs Ruby question, but if you didn't know either Python or Ruby and were trying to pick between Django and Rails for a project, wouldn't you pick Django in 2018 due to future data science and machine learning opportunities?
Earlier quoted context omitted.
Merely knowing python does not a data scientist make.
Of course, but wouldn't one be better preparing themselves for data science by working with python/django on a web app vs working with Ruby/Rails?
Core team takes care of many things like webpack, ActiveStorage, etc for you, many thanks to folks. I've been doing Ruby on Rails since 0.19 as far as I remember and it's been great ever since.
Not that hyped anymore but who cares about hype when you get your shit done. Also as you grow, you appreciate talent availability when it comes to Ruby/Rails.
There’s nothing wrong with Rails in 2018. It’s maybe not the most forward-looking choice you could make but it’ll get you running quickly. But if you have a smart team and a little bit of time for ramping up then I’d suggest Elixir+Phoenix or Node tbh. Rails is good at what it’s designed to be - a one stop shop for fast to develop, kinda dirty, framework magic, webdev. And there is nothing wrong with that.
"I just started using Ruby and omg it's out-of-box everything, rapid development, monkeypatching makes everything super easy, it's like second Jesus coming."
and the second category is this:
"I am working with RoR for years, maintaining/migrating anything is super painful, because everyone is monkeypatching everything, so you cant safely touch anything."
Choose wisely.
No. What does rails have that a different python framework doesn't have? And you'll save yourself the tears of migrating later.
If you are thinking about learning Rails now, probably not.
Yes Rails is great for MVPs, but then so are a lot of other things, like Meteor.