Live data from Hacker News

Is Rails still relevant in 2018?

blog.eq8.eu

181–190 of 346 posts

Re: Is Rails still relevant in 2018?

#181

Earlier quoted context omitted.

...our jobs are to make stuff that works in a predictable, less risky way. Do that. This is very true, but it doesn't mean "Use the thing that's worked in the past because that's less risky." Languages get better and tooling improves, and if you're still using one that isn't keeping up then you're increasing risk. These days if your chosen language doesn't have things like strong typing, interfaces, good debugging to…

> These days if your chosen language doesn't have things like strong typing, interfaces, good debugging tools, a good compiler, etc, then you should definitely be asking yourself if it's the right tool for the job. All of these things existed long before Ruby on Rails gained in popularity. Unless the popularity of Rails, Python, PHP, and Javascript was all just collective insanity, dynamic languages do offer benefits…

Unless the popularity of Rails, Python, PHP, and Javascript was all just collective insanity, dynamic languages do offer benefits in some circumstances over languages with stronger type guarantees.

The benefit they offer is fewer checks so you can deploy things faster.

It's the same benefit you can get if you take your car to a mechanic who doesn't bother to check the wheels are attached properly after they've changed the brake discs.

Re: Is Rails still relevant in 2018?

#183

The need for a build environment itself limits Ruby deployment to developers. This becomes a real problem for end user apps and expecting end users to compile is perhaps expecting too much. And now you need a build environment in deployment. And with this comes potential dependency hell, an app like Discourse pulls in over 140 dependencies. This means either you are a Ruby developer who can debug compile or version c…

A tremendous amount of apps still go the Heroku deployment route, where deployment is a git push.

Re: Is Rails still relevant in 2018?

#184
post #34

Earlier quoted context omitted.

Pretty much no Rails app at these large companies can even do something as basic as concurrent network requests. This is an area Ruby the language is weak in, and it's extremely difficult to graft on something like concurrent-ruby to a large existing codebase that assumes all requests are sequential... Also, in the past the multithreading/concurrency story around ActiveRecord has been "it probably works, might leak c…

Ruby has threads, when networking the GIL doesn't matter since the threads will context switch. For a company like Shopify paying for an extra 50 servers is like hiring one developer, I don't think it has much significance to them.

JRuby can solve that problem. Threading in Ruby. Some companies do use it: https://github.com/jruby/jruby/wiki/SuccessStories

Re: Is Rails still relevant in 2018?

#185

I mean... Let's pause for a minute and remove the year, and remove the language / framework. What are we trying to accomplish? If we know something really well and there are enough developers to support an ecosystem and the talent pool in your is big enough just use whatever you want. PHP in 2018? SURE. C++ in 2018? SURE (You masochist) Rails in 2018? Youre damn right I would. GO in 2018? OK. Fine. Whatever. This is…

>>C++ in 2018? SURE (You masochist)

How exactly do you think AAA games are made? It's all C++ because there's literally nothing else out there which would give you the same performance(and also nothing that is supported as widely by Sony/MS/Nvidia/ATI).

Re: Is Rails still relevant in 2018?

#186

Man these language debates are so irrelevant when you're talking about web apps. I honestly couldn't give a shit what I use, it takes like 2 weeks max to adjust to a new framework/language. Most people I know and work with feel similarly...and it's not some amateur speaking here.

Say that when somebody asks you work on a ColdFusion project with a big bucket of files and 2000 line files mixing data access, logic, and html. :-)

Re: Is Rails still relevant in 2018?

#187
Almost every startup I've worked with still uses Rails, and this includes 3 startups founded in the last few years. Yes many are using React/etc on top of that via the webpacker gem, but on the server side Rails is still super popular among startups. Crystal is also gaining traction especially for microservices among my network.

Re: Is Rails still relevant in 2018?

#188

Earlier quoted context omitted.

I'm 49 years old, and I've been programming since I was 10, on a Vic 20. I've been doing web development for 20 years, from Frontpage to PHP to Rails to .NET to Java. Picking up .NET wasn't terrible, but I've been at the Java/Grails/Spring/Angular stuff for MONTHS, and I'm just barely getting off the ground. I guess I'm just old and/or stupid.

I get you can't escape Angular (and friends) if you are doing front end, but why not just stick to 2 things on the backend? php and java, ruby and .net or whatever. I just don't see the point in doing Grails, Rails, Spring, Laravel, Node etc etc instead of mastering 1-3 technologies really well.

I was told, essentially, that Rails is still too new and scary to be considered secure and mature and ready for enterprise use, and that I had to use either .NET or Java. There's another half of this project that's already written in pure client/server Java, so that's what I chose. If I had it to do over again, I would have chosen .NET.

Re: Is Rails still relevant in 2018?

#189

Earlier quoted context omitted.

Came here to say the same thing, and add that with Django, you have access to the amazingly vast landscape of Python libraries. Just being able to spawn Celery jobs is a huge plus.

Couldn't see any advantage over Sidekiq, Resque and friends. Not saying it's bad but just that the Ruby community has got your back for any web development need you might have...when working with Django I didn't get the feeling I am working with superior libraries.

An advantage of Celery is that it doesn't require payment for an enterprise version to add things like scheduled tasks.

Re: Is Rails still relevant in 2018?

#190
post #66

Earlier quoted context omitted.

"Vulkan/C? Metal/ObjC†/C? " Vulkan and C are a sane option. Although, with C and linear algebra one starts to miss C++ operator overloading and existing libraries like eigen [0] or glm[1] with their graphics and computational geometry targeting API:s really soon. If one deploys only to OS X/IOS, Metal and ObjC, sure. "From C libs you can probably get to bindings to other languages like D, Haskell, Rust, Go†." With th…

For the several dozen EA games I worked on, in C++, all operator overloading was banned. Too many fools play dumb tricks with operator overloading, so it was declared illegal. I don't miss it, as it is a fool's tool.

EA should try banning fools instead . There are many other tools that have to be used appropriately, especially in C++.
Post reply on HN