The arrogance and ignorance of this post is massive. There is nothing wrong with rails or django or symfony or any other server side rendered web framework, whether it's 2012 or 2019. The author seems to think that somehow react SPAs are the only modern apps. The case against SPAs is still huge and for most use cases, they are the wrong tool for the job. This type of cargo cult, fashionable trend thinking undermines his entire argument and questions his qualifications as an engineer. There's no logical explanation for not using rails or something like it. He's complaining about a problem with literally dozens of proven solutions, including rails, that he's even aware of, and yet refuses. What ever happened to use the best tool for the job rather than what's fashionable and popular in 2019? I would not want such an engineer anywhere near my company, that's for sure. I can't think of a worse trait than knowing the right solution to a problem and deciding to use something else just because "everyone else is doing it." Absolutely bonkers.
I Miss Rails
191–200 of 522 posts
Re: I Miss Rails
#192Earlier quoted context omitted.
Actually, this stack is deployed as a serverless function ! "Serverless for API" means i could use any language to develop API. Serverless provides better scalability in my opinion.
Do you have any code samples for this? Sounds interesting.
It's private code. I'm writing a book on this topic and will release once it's done.
Re: I Miss Rails
#193Earlier quoted context omitted.
coming from the django-world, i had the same complain with rails. It was a little too fast for a me.
I just updated a rails app through about 3 years worth of versions and it was minimal effort. Not sure what you mean by this. Rails seems to be very stable at this point.
Rails is definitely way more stable over the past 3 years than it was the 3 years before that. It's settled down. For better or worse.
Re: I Miss Rails
#194Earlier quoted context omitted.
If JavaScript is weird I have no idea what Ruby is. Callback hell and Christmas tree indenting have not been a part of JavaScript for many years since the wide adoption of promises, and now async/await. What makes it order of magnitudes more performant than Ruby is that it's non-blocking, and now comes with a very pleasant syntax to accommodate.
> What makes it order of magnitudes more performant than Ruby Source for the "orders of magnitude" anywhere in the last year or so? Ruby with EventMachine outperformed Node significantly when I tested websocket chat servers.
We had huge performance issues with ActionCable that basically made it unusable for more than 100 concurrent users. We considered EventMachine however ended up going with AnyCable in conjunction with AnyCable-Go which got us up to 1000 concurrency users without any performance impact.
Re: I Miss Rails
#195Earlier quoted context omitted.
Static-typing seems so at odds with Ruby/Rails that I can't even imagine what that would look like.
I'm waiting for a chance to try out Crystal/Amber, which is type-checked (not sure how safe?) and can be pre-compiled like Go apps. It looks really close to Rails: https://github.com/ChangJoo-Park/amber-realworld-example-app... (I couldn't find any code snippets on the official Amber framework page, I hope this is representative.)
Crystal is definitely type safe, I’d recommend taking a look at the Lucky web framework also written in Crystal.
Re: I Miss Rails
#196Earlier quoted context omitted.
GitLab rewrote some parts in Go, because Ruby was too slow on a big scale.
So “use rails until you raise a C round?” heh
I'd say it's more use Rails for all of your standard CRUD operations and then use Go as a module in Rails using Quartz/FFI if you have any algorithms that need to be high performance. Of course you could always go down the microservice route and spin up a Python/Go service for your more intensive data processing modules.
Re: I Miss Rails
#197What’s the harm in using rails purely as an API? You’ll still get a lot of functionality out of the box and maybe have to write just a little bit more glue code for the JS-backed front end than what rails provides out of the box.
Because its justturning rails into a huge (compared to say postgrest or prest) database and auth api.
Re: I Miss Rails
#198Earlier quoted context omitted.
I just updated a rails app through about 3 years worth of versions and it was minimal effort. Not sure what you mean by this. Rails seems to be very stable at this point.
Rails is definitely way more stable over the past 3 years than it was the 3 years before that. It's settled down. For better or worse.
The last few versions added a bunch of really nice features but it seems the existing features are considered still good and not in need of change.
Re: I Miss Rails
#199I don't use rails, but I agree with sentiment in general. I first learnt front-end stuff with desktop UI libraries and I hated it. Creating UIs with programming languages sucks. The first time I used the web environment, I really enjoyed it and it was the reason I decided to focus on programming for the web. I was using PHP and server-side rendering, with some javascript to do some interactive things. I liked that the design aspect (html and css) was completely separate from the programming, and that there were no compile steps.
Then eventually the requirement for more application-like experiences led me to adopting client-side frameworks because server-side just wasn't able to do those things very well. I like the idea of a json-based api talking to a client application, but the client-side libraries have bought back all the things I hated about desktop UI programming.
I think html is great and should be left on its own, not combined with the programming language. That is the reason I don't like React. I can't read all of that jsx/pseudo-javascript together. It looks like a mess. Vue is better, but it is just a big hack of stuffing things into html attributes. Both of them also require a compile step if you want to use them to their full potential. So now all the things I hate are back, and I don't like web programming anymore.
Re: I Miss Rails
#200Earlier quoted context omitted.
I know this is the opposite of what you asked but I find Rails to be keeping pace with modernity much better than its conemporaries! Django seem to have given up on integrating websockets (ActionCable has been in Rails for literally years now), nor is there trivial integration for JS assets/asset pipeline functionality. I don't write much of either anymore, but I'd still reach for Rails the instant I need to get some…
I'm interested in hearing about applications successfully using ActionCable for what and how. It's unclear to me how much use it's getting, or how well it meets actual use cases.
ActionCable is super easy to use out of the box to get WebSockets running, but it's incredibly non-performant. Anything more than 100 concurrent users took the time taken to a send a message to the socket from milliseconds to seconds. Replacing it with the AnyCable gem in conjunction with AnyCable-Go got us to over 1000 concurrent users without a hitch.