61–70 of 80 posts
Earlier quoted context omitted.
Why would you need to migrate to Python later? I can understand needing to migrate to something more performant/easy to scale, but Python doesn't have any advantage on Ruby in that department.
Not migrate to python, migration away from Rails. I'm suggesting Python as an alternative to Rails to start with.
No. Long time rails developer, but if you can green-light a project I'd highly recommend node all the way. I've found it much easier to comprehend a pure javascript stack (or even better an all-Typescript stack) due to substantially less cognitive overhead, find other people to work with (very important as your project scales), and the fact I can deploy node with a serverless implementation on Azure, GCP, and AWS mak…
Rails's out-of-the-box React integration [1] should get you _exactly_ as far as React these days.
Earlier quoted context omitted.
What web dev languages/frameworks aren’t deeply flawed and teach you more portable skills?
Unfortunately I would say Javascript. Unlike Ruby, you will learn about compilers, static analysis, linting (eslint is more useful than rubocop), type systems, function composition, and have a good alternative to OO based programing built into the language (as opposed to your `UnboundMethod` lambda block proc whateverthehell design flaw Ruby has now). Javascript also gives you decent jumping off points into languages…
Function composition and partial function application is totally supported in Ruby so not sure what your complaint is there. Here is one rather forced example: http://genua.github.io/ruby/2015/03/17/ruby-function-composi...
I don’t know anything about Elm and Purescript but I’ll look into them. They aren’t hugely popular (as far as I know, feel free to correct me) so I’m not sure that’s a major win for portable skills versus Ruby engineers learning Scala or Python. If you don’t get too wild with the symbols, Scala can actually look quite familiar to Ruby programmers. Twitter had people use a subset of Scala when they transitioned many services from Ruby to Scala so that it would be an extra easy transition.
JavaScript has come a long way though and is certainly the lingua franca of the Internet.
No. Long time rails developer, but if you can green-light a project I'd highly recommend node all the way. I've found it much easier to comprehend a pure javascript stack (or even better an all-Typescript stack) due to substantially less cognitive overhead, find other people to work with (very important as your project scales), and the fact I can deploy node with a serverless implementation on Azure, GCP, and AWS mak…
What framework do you use on node.js?
My experience with nodejs has been pretty poor. I'll give some examples;
* The language and runtime is constantly updating - there is no such thing as stability
* Even npm couldn't produce deterministic installs until this year
* npm dependency hell
* there are lots of ways to do any task, so there is much fragmentation with advice / community
* the repls in node suck compared to pry
* I can't find a good opinionated framework - so everyone lays out each application differently, with different standards etc. That means you end up spending a ridiculous amount of time configuring everything.
* most apps i've needed to make don't actually benefit from being a SPA. It's a cargo cult thing.
* javascript as a language sucks!
No. Long time rails developer, but if you can green-light a project I'd highly recommend node all the way. I've found it much easier to comprehend a pure javascript stack (or even better an all-Typescript stack) due to substantially less cognitive overhead, find other people to work with (very important as your project scales), and the fact I can deploy node with a serverless implementation on Azure, GCP, and AWS mak…
It seems like you're comparing a framework with a language? What framework do you use on node.js? My experience with nodejs has been pretty poor. I'll give some examples; * The language and runtime is constantly updating - there is no such thing as stability * Even npm couldn't produce deterministic installs until this year * npm dependency hell * there are lots of ways to do any task, so there is much fragmentation…
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.
Node with which framework? By itself it's not comparable to Rails.
But that sort of reinforces the point I was making tbh. Want something that makes all those choice for you? Right or wrong? Rails.
Nothing wrong with that as such, but it will cause issues eventually.
If you already know Rails, yes. 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.
Earlier quoted context omitted.
Volatile in comparison to what exactly?
Django. I'm not doing software these days but still following the news etc., and it seems to me that the general knowledge of the tool is still operable since very early releases. I'm not very familiar with Rails itself but when an environment changes very quickly it's both a big distraction and a great inconvenience. I've last worked with django around January 2014, today when I look at a Django app it's the same be…
Rails 5 was the easiest upgrade yet. ActionCable was the big change, but it’s an addition to Rails, not a replacement for some existing tech. As a result, it doesn’t disturb much existing code.