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

91–100 of 176 posts

Re: Ruby on Rails in a week

#91

Post by cambalache »

halfmatthalfcat wrote: post #79
cambalache wrote: post #78

I am one of those obnoxious people who is trying all the time new web technologies, without deepening the skill for years in just one. Out all the frameworks I have used (Django,Phoenix,Node/Express in all its flavors,.NET Core, Echo) Rails is by far the one in which I feel more productive. Ruby is a lovely language, the ecosystem is mature, there is always a gem for everything and for the kind of applications I do (…

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, nice idea, but when you spend 30% of your time looking after all those custom types and end up using an ":any" hack to make it work, this leaves a bad taste in your mouth. If I am going to use strong types I would choose an actual strongly-typed language for that, C# is great.

Re: Ruby on Rails in a week

#92

Post by anonytrary »

siquick wrote: post #40
pugio wrote: post #34

Earlier quoted context omitted.

That's actually exactly the kind of skill I'd look for in a new hire. I don't care which crunchy items you list on your resume so much as your ability to learn and integrate new technical information quickly (as well as a host of other skills, of course). That said, learning a new thing does take a lot of time, so if I were asking a person to do that I would either commit to hiring them if they complete the learning…

> That's actually exactly the kind of skill I'd look for in a new hire. I don't care which crunchy items you list on your resume so much as your ability to learn and integrate new technical information quickly (as well as a host of other skills, of course). Of course, but asking someone to spend a lot of hours on this in a week, with no guarantee of a job at the end of it is not a direction this industry needs to go.…

> Of course, but asking someone to spend a lot of hours on this in a week, with no guarantee of a job at the end of it is not a direction this industry needs to go

I have never seen this from any serious employers. If someone is asking you to do this, then go work somewhere else. Employers are expecting that you learn on the job.

Re: Ruby on Rails in a week

#93

Post by kjsthree »

aledalgrande wrote: post #87
halfmatthalfcat wrote: post #80

Earlier quoted context omitted.

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.

Ever used Sequelize?

Haha! That’s the one that immediately came to mind. What a dumpster fire.

Re: Ruby on Rails in a week

#94

Post by cortesoft »

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 really should try Rails again. I LOVE ruby, but have been anti-rails for a while and I am not sure I am right for that.

I got into Ruby programming through Rails... but in 2005. Rails was brand new (I think I was on version like 0.12 or something?), and I slowly moved away from it to things like Sinatra and Sequel. Rails had some huge performance issues, and active record was pretty unusable at any sort of scale unless you did a lot of custom SQL.

I know it has come a long way in 15 years, I should try again

Re: Ruby on Rails in a week

#95

Post by halfmatthalfcat »

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…

Somewhat ironic but not sure if you know, Typescript is made by Microsoft and the lead Typescript language architect is Anders Hejlsberg who also was heavily involved in the creation and architecture of C#.

Re: Ruby on Rails in a week

#96

Post by dstorm1 »

Is it just me or is Rails really complex? Its abstractions are so far removed from anything familiar (HTTP, SQL) that its difficult to understand what is happening unless you deeply understand the framework.

Re: Ruby on Rails in a week

#97

Post by AlchemistCamp »

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 read all of those and would like to add two more:

1) Learn to Program, by Chris Pine. It's the best book I've read on learning to program in any language.

2) Practical Ruby Projects: Ideas for the Eclectic Programmer, by Topher Cyll. In a sense it wasn't "practical" at all. But it was a joyous eye-opener to all kinds of applications that turned me into a whirlwind of enthusiasm for months!

Re: Ruby on Rails in a week

#99

Post by Mavvie »

cortesoft wrote: post #94
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 really should try Rails again. I LOVE ruby, but have been anti-rails for a while and I am not sure I am right for that. I got into Ruby programming through Rails... but in 2005. Rails was brand new (I think I was on version like 0.12 or something?), and I slowly moved away from it to things like Sinatra and Sequel. Rails had some huge performance issues, and active record was pretty unusable at any sort of scale un…

I'm sure it depends on the complexity of the app you're building. For simple crud-ish apps (ecommerce, online auctions, etc) I've found that I don't need to write even a single line of custom SQL, and performance is generally good (lots of N+1s, but these are easy to avoid with things like bullet). I also love being able to let Rails render most HTML, and the few things that need to be very dynamic you can just throw a single react component in without worrying about the usual SPA problems.

If you're just prototyping stuff, I don't think you can beat Rails for productivity. But if you're targeting something more enterprise or large scale, I don't think it's a good choice. Go/Rust are so much faster (not that that matters a lot), and even things like C#/Java pretty nice to use nowadays.

Re: Ruby on Rails in a week

#100

Post by amw-zero »

lubesGordi wrote: post #82

I'm a back end C++/rust type and I script with Python. If I wanted to build a front end, is there any reason I'd use Ruby/Rails over Django? I'm not familiar with Rails but I'm curious if it's worthwhile to pick up.

All web frameworks are equivalent.
Post reply on HN