Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ruby on Rails in a week

simplethread.com

Post reply on HN
Print view View original

131–140 of 176 posts

Re: Ruby on Rails in a week

#131

Post by masa331 »

halfmatthalfcat wrote: post #80
ritchiea wrote: post #23

Earlier quoted context omitted.

This 10,000 times. And it’s not just Rails, the quality of the Rails documentation made an impact on the Ruby community that was generally replicated. Compare that to the JavaScript world where cornerstone, insanely popular libraries will have documentation that covers roughly 10% of a library’s API surface area and maybe one simple example that doesn’t cover production use cases. And dozens of out of date Medium blo…

I've been doing Javascript for a long time and have rarely run into issues with a lack of documentation. Maybe in projects with like 10 stars on Github ran by a single developer but in all of the major Node projects, you're going to have ample documentation and support for implementing said libraries. Just my take.

My question is why Node docs on nodejs.org don't have search

Re: Ruby on Rails in a week

#132

Post by moepstar »

nickjj wrote: post #14

Rails is in a really good place. When I learned it back in 2015 there were so many resources for learning, it felt like every time I had a specific problem related to a feature I was implementing there was either a railscasts or gorails video on it, along with 10 blog posts and stack overflow results. I can only imagine how much better it is now. It has been one of the only semi-modern learning experiences where I wa…

FWIW, when i toyed a bit with Rails (gotta pick it up again, seriously) i used Heroku but quickly migrated over to a Dokku instance ran on my local NAS.

Getting Dokku running on something like Digital Ocean should be easy as pie...

Re: Ruby on Rails in a week

#133

Post by joelbluminator »

afhammad wrote: post #130
jaredcwhite wrote: post #129

I hesitate to state that Ruby is making a comeback, because I don't think it ever really faded (isrubydead.com ;-) )…but it definitely feels like the momentum is picking up. 2021 is going to be amazing . Ruby 3. Rails 6.1+ along with new HEY-derived innovations. ViewComponent + StimulusReflex is quickly becoming a powerhouse combo. A ton of useful gems coming out all the time. I myself am furiously working on making…

The market (job vacancies) seem to imply otherwise, I rarely see it mentioned in comparison to Python, Go, PHP.

At least in the U.S there are more Ruby jobs than PHP, so what you're saying isn't accurate. In Europe (outside UK) Ruby is weaker I agree; php/.net seem to be way more popular.

Re: Ruby on Rails in a week

#134

Post by sgustard »

ModernTabulator wrote: post #90
pqdbr wrote: post #2

Having picked up Rails 9 years ago and having been using it literally daily ever since, it's joyful to read from someone that is just starting. I also started with https://www.railstutorial.org/book , highly recommend it. I also loved Metaprogramming Ruby (Paolo Perrotta) - it's more advanced and starts to open your mind to how Rails magic DSL's were built. I just bought today "Rebuilding Rails" ( https://rebuilding-…

I see that Rebuilding Rails doesn't mention a version number of the book, and sales page is actually very uninformative about the actual content. Elsewhere I see it was first published in 2012- How relevant do you find the 'latest' version to modern development? And what is the latest version, has it been updated for rails 6? Have you got any other recommendations for intermediate to advanced rails topics?

I just downloaded the free chapter. I don't see a Rails version number, but it does mention Ruby 2.6 and the book is dated thusly:

> This Version: April 2020 (Free-Chapters Edition)

> Rebuilding Rails is copyright Noah Gibbs, 2012-2020

Re: Ruby on Rails in a week

#135

Post by paublyrne »

afhammad wrote: post #130
jaredcwhite wrote: post #129

I hesitate to state that Ruby is making a comeback, because I don't think it ever really faded (isrubydead.com ;-) )…but it definitely feels like the momentum is picking up. 2021 is going to be amazing . Ruby 3. Rails 6.1+ along with new HEY-derived innovations. ViewComponent + StimulusReflex is quickly becoming a powerhouse combo. A ton of useful gems coming out all the time. I myself am furiously working on making…

The market (job vacancies) seem to imply otherwise, I rarely see it mentioned in comparison to Python, Go, PHP.

Anecdotally I still see it listed a huge amount, as much as ever. Much of the time the apps are more than a couple of years old. I do think the number of startups who will create a new Rails application today as their primary application is much lower, but Rails work is hardly going to dry up anytime soon.

Re: Ruby on Rails in a week

#136

Post by viraptor »

mathnmusic wrote: post #116
viraptor wrote: post #58

Earlier quoted context omitted.

That's just per-model database annotation. It's not enough for use cases like: data sharding, switching reader/writer endpoints at runtime, and a few others. I wouldn't count the basic case as "multi-db support"

I built a Rails app with exactly that set up: sharding, dynamic switching of read/write queries across multiple slaves 10 years ago. It wasn't hard at all. Ruby's full dynamic nature makes many things easy.

Yes, I mentioned it too https://news.ycombinator.com/item?id=24937220 - it's relatively easy to add this if needed. But I would not describe it as supported natively.

Re: Ruby on Rails in a week

#137

Post by mekster »

cambalache wrote: post #91
halfmatthalfcat wrote: post #79

Earlier quoted context omitted.

Just curious why the (negative) callout for Node-based frameworks like express? How, technically, were they inferior to Ruby (or any of the other languages you listed)?

I like Javascript and Express, so in that sense they are OK. I hate the brittleness of the ecosystem, the "flavor of the month" character, and the explosion of options, there are people who like that setup: small programs that you can plug and play to create your whole stack, I find that tiresome, I prefer big monoliths in which the best options and practices are universally agreed upon. Ah and I hate Typescript, nic…

If you have to end up using "any" on something not too weird, then you probably aren't getting TypeScript right.

The typing system is way better than php, ruby or swift I feel like I'm using a language of a generation behind after using TypeScript.

Re: Ruby on Rails in a week

#138

Post by mekster »

jaredcwhite wrote: post #129

I hesitate to state that Ruby is making a comeback, because I don't think it ever really faded (isrubydead.com ;-) )…but it definitely feels like the momentum is picking up. 2021 is going to be amazing . Ruby 3. Rails 6.1+ along with new HEY-derived innovations. ViewComponent + StimulusReflex is quickly becoming a powerhouse combo. A ton of useful gems coming out all the time. I myself am furiously working on making…

If they had brought in a more intuitive typing system that is inline typing, I would have considered to use it for something as I like ruby itself but guess not.

Re: Ruby on Rails in a week

#139

Post by afhammad »

joelbluminator wrote: post #133
afhammad wrote: post #130

Earlier quoted context omitted.

The market (job vacancies) seem to imply otherwise, I rarely see it mentioned in comparison to Python, Go, PHP.

At least in the U.S there are more Ruby jobs than PHP, so what you're saying isn't accurate. In Europe (outside UK) Ruby is weaker I agree; php/.net seem to be way more popular.

Yeh, i'm going off London job market.

Re: Ruby on Rails in a week

#140

Post by jurre »

b0afc375b5 wrote: post #68
mdoms wrote: post #20

Earlier quoted context omitted.

> It's definitely noticeable when you try to learn a newer framework with a much smaller community and less opinions. You could end up Googling for what you might think is a common thing to solve only to find zero answers in sight I have felt this exact way when I'm Googling for problems running Rails in modern cloud environments. It seems like there are loads of problems that are largely unsolved in the community at…

If anyone has any tips or documentation that might help with regards to Rails containerization, I'm interested in knowing as well.

What specifically are you running into? I may have trouble seeing any gaps in documentation because I’ve been running rails in a containzerized environment for years and it seems to just work
Post reply on HN