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

61–70 of 176 posts

Re: Ruby on Rails in a week

#61

Post by jrochkind1 »

triangleman wrote: post #15

Years ago I put together a Rails app to store iPhone/iPad apps for curation. There was a backend that connected to the iTunes API and then I parsed the data elements I needed and entered them into the DB. The most infuriating thing was realizing that I needed to update the model with a new data element, or that some API responses didn't include the needed data. There was all this controller and model code and then th…

What other languages/platforms do you have experience with, if any? Yeah, it sounds pretty normal to me.

Yes, storing the entire API response in a single column is an option, and yes I think you stumbled on some of what drew some people to "noSQL", which has it's own downsides, and the pendulum swings to people talking about how terrible "noSQL" is, but it can work.

Re: Ruby on Rails in a week

#62

Post by donw »

siquick wrote: post #31

Asking someone to learn a brand new framework/language in a week as part of a job interview is pretty harsh.

Pivotal expects this as a matter of course.

The interview involves full-time pairing for a day, and you (probably) won't know one of the programming languages.

Pivotal does full-time pairing, and an experienced pairs should expected to pick up languages from new teams on-the-fly. After all, the rest of the team knows the language, and you'll get constant real-time mentorship as part of daily rotations.

This is perhaps the thing that sold me on full-time pairing: you can join a team, not even know the programming language, and contribute value to your team from day one.

Re: Ruby on Rails in a week

#63

Post by zbentley »

tyre wrote: post #41
herpderperator wrote: post #37

I love rails, but despite its presense for over a decade, it doesn't feel mature. Something as basic as a native left join in ActiveRecord wasn't added until Rails 5.0, on June 30, 2016. Something as basic as native multiple database support wasn't released until Rails 6.0, on August 16, 2019, 15 years after its initial release... These are just two examples.

Multi-database support is not "basic". At what point do you need that? What percentage of users do? Regardless, it was fully supported in gems for years before it went into Rails. It's nice to have it in core. But to say that Rails doesn't feel mature without it? Come on.

> At what point do you need that? What percentage of users do?

In my experience, rather a lot.

Re: Ruby on Rails in a week

#64

Post by theptip »

leetrout wrote: post #53

I took a rails job by accident- I knew rails was in use but I was interviewed in Go and talked about new things going on in Go micro services. I didn’t expect 40 hours a week of rails / ember JS work and that’s my fault. I have 12 years with Django and I was shocked there wasn’t the equivalent of the Django tutorial. Everyone says the rails tutorial is good and I’m sure it’s worth the money but no one at work endorse…

Would you say Rspec is better than the Python equivalents like behave or pytest-BDD? Curious as I've never worked with Ruby/Rails but I'm aware there are some things that are way ahead of other toolchains (and others that are way behind as you've noted).

Re: Ruby on Rails in a week

#65

Post by herpderperator »

jrochkind1 wrote: post #57
herpderperator wrote: post #37

I love rails, but despite its presense for over a decade, it doesn't feel mature. Something as basic as a native left join in ActiveRecord wasn't added until Rails 5.0, on June 30, 2016. Something as basic as native multiple database support wasn't released until Rails 6.0, on August 16, 2019, 15 years after its initial release... These are just two examples.

Do you mean it didn't feel mature before June 2016 or August 2019? Cause... those things are there now, so how can they be examples of it not feeling mature now? What's it missing for you now to feel mature? (And also, lots of people and code definitely did left joins and multiple databases in Rails before those dates, without needing to add any sort of plugin/additional dependency. I did myself, plenty of times! Rai…

Well, business don't jump on the latest version right away for many reasons (stability, bugs, upgrade woes...) Maturity is closely correlated to how long things have been around. Just because multiple database support was officially added on August 2019 it doesn't make it mature after that date. It takes a long time to achieve maturity - people to adopt and improve on that functionality without breaking things. We have been using multiple databases for years as well, done our own way, which will now have to be re-done in the upgrade to Rails 6. It's obviously not a plug-and-play replacement.

It's never clear how long gems will be maintaned for, and when a new gem (like multiverse, which is the multi-database gem I suppose others are referring to) comes out, it doesn't mean that businesses are going to jump on it right away. It needs to be around for some time so that support and its reputation start to build up a case to use it in production.

That's why having it in core is important.

Re: Ruby on Rails in a week

#66

Post by viraptor »

theptip wrote: post #64
leetrout wrote: post #53

I took a rails job by accident- I knew rails was in use but I was interviewed in Go and talked about new things going on in Go micro services. I didn’t expect 40 hours a week of rails / ember JS work and that’s my fault. I have 12 years with Django and I was shocked there wasn’t the equivalent of the Django tutorial. Everyone says the rails tutorial is good and I’m sure it’s worth the money but no one at work endorse…

Would you say Rspec is better than the Python equivalents like behave or pytest-BDD? Curious as I've never worked with Ruby/Rails but I'm aware there are some things that are way ahead of other toolchains (and others that are way behind as you've noted).

Define "better". The mocking story and the rspec syntax itself is insanely better than in python. But the actual internals are pretty much comparable in my opinion.

Re: Ruby on Rails in a week

#67

Post by yxhuvud »

tyre wrote: post #41
herpderperator wrote: post #37

I love rails, but despite its presense for over a decade, it doesn't feel mature. Something as basic as a native left join in ActiveRecord wasn't added until Rails 5.0, on June 30, 2016. Something as basic as native multiple database support wasn't released until Rails 6.0, on August 16, 2019, 15 years after its initial release... These are just two examples.

Multi-database support is not "basic". At what point do you need that? What percentage of users do? Regardless, it was fully supported in gems for years before it went into Rails. It's nice to have it in core. But to say that Rails doesn't feel mature without it? Come on.

Of six rails shops I've worked on, half used connection to a secondary sql database in one way or another. Exact use cases has differed but I wouldn't be surprised if it is actually a rather high percentage of medium sized to big apps that use multiples.

Re: Ruby on Rails in a week

#68

Post by b0afc375b5 »

mdoms wrote: post #20
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…

> 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.

Re: Ruby on Rails in a week

#70

Post by leetrout »

theptip wrote: post #64
leetrout wrote: post #53

I took a rails job by accident- I knew rails was in use but I was interviewed in Go and talked about new things going on in Go micro services. I didn’t expect 40 hours a week of rails / ember JS work and that’s my fault. I have 12 years with Django and I was shocked there wasn’t the equivalent of the Django tutorial. Everyone says the rails tutorial is good and I’m sure it’s worth the money but no one at work endorse…

Would you say Rspec is better than the Python equivalents like behave or pytest-BDD? Curious as I've never worked with Ruby/Rails but I'm aware there are some things that are way ahead of other toolchains (and others that are way behind as you've noted).

Yes. I would use the tooling inspired by the Ruby tools like factory boy and stick with pytest over behave, personally. I’ve not used pytest-bdd.

In JS mocha or jest are both great.

Post reply on HN