Earlier quoted context omitted.
.NET's LTS releases are supported for 3 years and STS are supported for 18 months. I wish LTS support was 5 years, it seems like ecosystem has matured enough post-going-OSS-wild-ride starting with .NET 6 release and is ready for such a support timeframe. Or at least they could have every other LTS be ELTS? Also, I do wonder if RoRs perceived productivity is by inertia? I have a hard time believing you can top the pro…
On the flip side, within the last few years, upgrading .NET versions has become typically a very easy exercise. The ASP.NET team tends to churn stuff wayyy more often than I'd like for questionable reasons, which can make keeping more painful than I'd like - but tbh I often just keep using the older ways of doing things in ASP.NET since it's almost always still supported...
Ruby on Rails: The Documentary [video]
191–200 of 248 posts
Re: Ruby on Rails: The Documentary [video]
#192I remember fondly when RoR was the hottest thing, so elegant and easy to understand, but I haven't touched it in ages. Is it still good compared to the more up-to-date stuff? Is it still relevant?
Re: Ruby on Rails: The Documentary [video]
#193Earlier quoted context omitted.
I've been a Rails dev for a long time. I've tried a bunch of things and keep coming back to it for the same reasons as you. I'm incredibly productive in it. For the longest time, my primary complaint has been a lack of documentation/conflicting information when you break from convention. It can be extremely challenging to find/understand the "blessed" way of doing things. Thankfully, ChatGPT is extremely good at prov…
Could you give an example of how ChatGPT helped you specifically with Rails?
Same thing with some of the more advanced Model relationships. I just don't write _that_ many relationships, so I tend to forget how Rails wants certain things defined. Since a lot of things rely on config, rather than "normal" runtime code, it can be frustrating to debug. ChatGPT just gets me to the right answer.
---
It's also pretty useful at gut checking DB design. There's been a few times where it's suggested a different approach than what I expected and I've preferred it's suggestions.
Re: Ruby on Rails: The Documentary [video]
#194Earlier quoted context omitted.
It's cool. Another similar option is Platformatic by the creator of Fastify. https://platformatic.dev/ But still... There are no queues or jobs. No HTML over the wire. No colocation of presentation logic. Etc.
All of that stuff can be easily added using 3rd party packages, just like Laravel, Rails, Django, etc all have userland addons. https://packages.adonisjs.com
https://packages.adonisjs.com/?category=Rendering
And the fact that these aren't official is kind of the point I've been making. In the JS world there isn't a holistic fullstack framework. You have to stitch it all up yourself. In Adonis, Express, Fastify, Next, SvelteKit, etc.
Re: Ruby on Rails: The Documentary [video]
#195Earlier quoted context omitted.
I must be misunderstanding the question because anything that queries in rails uses AR and that's often done in both lib code and controller code rather than behind a dedicated module boundary. What is it that's not making sense to you?
> because anything that queries in rails uses AR and that's often done in both lib code and controller code How is that different from any other framework ever? You have to query the DB somewhere. Rails makes it incredibly easy to swap out databases. Much more so than any other platform I can think of. Nothing is making you use AR at all. This is a non issue.
If it needs to be explained you've never seen anything but a gocart.
Re: Ruby on Rails: The Documentary [video]
#196Re: Ruby on Rails: The Documentary [video]
#197Re: Ruby on Rails: The Documentary [video]
#198Earlier quoted context omitted.
> Typical deficit in reading comprehension is the hallmark of the mediocre mind. Are you insulting the person who responded to your comment?
only if he's multi accounting
Re: Ruby on Rails: The Documentary [video]
#199Earlier quoted context omitted.
his 'artsyness' was the main reason I avoided learning Ruby for years-- wrongly thinking people who code in Ruby speak like him. I know this is a possibly unpopular opinion but I don't think one should glorify a sophomoric book as a key Ruby book-- there are others that deserve that title, PickAxe is close, but I'd have liked a book like Whittaker's "C#, Player Guide" for Ruby.
I absolutely loved _why's guide, not the least because it made certain very serious, over the top professional people very uncomfortable. Bullshit in the guise of Very Serious Business Software Engineering is still bullshit, but if you present something like it's a big joke to you, and it still shines, there probably is something to it. I feel a lot of present-day IT wouldn't pass that test.
Re: Ruby on Rails: The Documentary [video]
#200> if you open up any Rails application, it looks basically the same in structure whether it is the biggest Rails app there is or a new one. I used to love this, untill I started to hate it. I am convinced this is a major contributor to why so many Rails apps turn into an unmaintainable mess over years. Who measures onboarding in hours? It's fine if it takes a day or two to understand the domain. And the framework. An…