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

Rails 6: B-Sides and Rarities

evilmartians.com

Post reply on HN
Print view View original

41–49 of 49 posts

Re: Rails 6: B-Sides and Rarities

#41

Post by brightball »

ksec wrote: post #4
stevenpetryk wrote: post #2

I still see Rails as perhaps one of the best frameworks to start a new generic web project in. The out-of-the-box functionality is just so perfectly tuned, and the fact that they're focusing on features that appeal to larger applications just shows how Rails has helped companies grow.

Any Reason why Rails still does not include an any decent Auth by default? Edit: I remembering keep asking this question but obviously no answer was satisfactory enough that stick to my brain.

Because every application doesn't need it and it's virtually effortless to add Devise, which is the defacto standard at this point.

Re: Rails 6: B-Sides and Rarities

#42

Post by intelliderp »

ksec wrote: post #4
stevenpetryk wrote: post #2

I still see Rails as perhaps one of the best frameworks to start a new generic web project in. The out-of-the-box functionality is just so perfectly tuned, and the fact that they're focusing on features that appeal to larger applications just shows how Rails has helped companies grow.

Any Reason why Rails still does not include an any decent Auth by default? Edit: I remembering keep asking this question but obviously no answer was satisfactory enough that stick to my brain.

Authentication is currently a tire fire all across the web, regardless of framework. It's not unheard of for login issues to consume the efforts of a full-time senior dev on a team. Not including RESTful APIs, the "best practice" for auth has shifted rapidly in the past 10 years from OAuth2 to OpenID to JWT... these frameworks take considerable effort to learn, add to that the fact that the major identity providers (FB, Google, etc.) are undergoing major legal challenges across the world. It's becoming the case that only large teams can actually put together a login page. In this environment, I think hesitancy is warranted.

Re: Rails 6: B-Sides and Rarities

#43

Post by freehunter »

maitredusoi wrote: post #22
c0achmcguirk wrote: post #3

I haven't done heavy work in Rails in four years. I miss all the bells and whistles.

I've decided to never quit those "bells and whistles", other frameworks just aren't good enought in competing with those... That is why I am optimizing my rails stuff with a few trick made in crystal lang (like the websocket server and a bunch of MTTQ like jobs ;) . For me, until ruby 3x3 gets out, crystal is a good help with scaling up processing.

I do a bit of Node.js stuff at work (not a programmer by trade, just lightweight stuff) but on my side project it's Rails first and foremost. As the sole developer, I need to just get stuff done. Performance isn't a concern at the small scale I work on. I've experimented with other frameworks and besides Django I've never found anything that's end-to-end the way Rails is. I don't have to think about the framework or the technologies, I just write some code and I'm done with it. I don't have to interact with the database directly, ActiveRecord handles it for me. It's pure productivity, which as a solo developer is the most important thing for me.

For some front-end pieces where I need more flexibility, Vue nests in nicely with Rails where it's needed and gets out of the way where it's not needed. There's nothing in the JS world that even begins to compete with Rails as an end-to-end solution.

Re: Rails 6: B-Sides and Rarities

#44

Post by Kalium »

ksec wrote: post #4
stevenpetryk wrote: post #2

I still see Rails as perhaps one of the best frameworks to start a new generic web project in. The out-of-the-box functionality is just so perfectly tuned, and the fact that they're focusing on features that appeal to larger applications just shows how Rails has helped companies grow.

Any Reason why Rails still does not include an any decent Auth by default? Edit: I remembering keep asking this question but obviously no answer was satisfactory enough that stick to my brain.

> Any Reason why Rails still does not include an any decent Auth by default?

If memory serves, Rails has quite good authentication built in by default.

If that's not what you meant, could you clarify?

Re: Rails 6: B-Sides and Rarities

#45

Post by mercer »

kev6168 wrote: post #25
pmontra wrote: post #14

Earlier quoted context omitted.

I've been a mentor at a hackathon a few months ago. 90% of the participants were on their twenties. The chances they know Rails are lower than for the same demographic ten years ago.

Interesting. What server side tech stacks are often used by young developers in the recent hackathon? Are there a few dominant ones or many choices?

I'll second that question. I figured Rails would still be pretty popular, and now I'm wondering to what degree that is or isn't true these days.

My guess would be React/Angular or, if it's a particularly hip group, Next.js/Nuxt.js/Serverless with as little back-end as possible.

Re: Rails 6: B-Sides and Rarities

#46

Post by dcosson »

snowwolf wrote: post #35
dcosson wrote: post #12

Earlier quoted context omitted.

Eh. Rails is fine, and lots of other things are fine too. Rails is amazing on day 1, even week 1 of a new project, vs piecing together your favorite separate smaller libraries into a web framework. That can be just what you need for a side project that you want to get up and running fast. But if you’re planning to build a business around it and work on this codebase for years, it’s crazy to optimize for day 1. (Not s…

There is an argument that you should absolutely be optimising for day 1. One of your biggest advantages as a startup is agility. Until you've hit upon product/market fit, you want to choose tools that enable you to iterate fast.

I'm talking about literally day 1, not just like the first phase of the company. If a startup is exactly a single day (or single week) ahead of the competition such that the productivity on that day is make or break, that goes way beyond agility and is probably just not a very good opportunity.

Re: Rails 6: B-Sides and Rarities

#47

Post by faizshah »

kev6168 wrote: post #25
pmontra wrote: post #14

Earlier quoted context omitted.

I've been a mentor at a hackathon a few months ago. 90% of the participants were on their twenties. The chances they know Rails are lower than for the same demographic ten years ago.

Interesting. What server side tech stacks are often used by young developers in the recent hackathon? Are there a few dominant ones or many choices?

React, vue, firebase, express, flask and django at mine.

Re: Rails 6: B-Sides and Rarities

#48

Post by faizshah »

mercer wrote: post #45
kev6168 wrote: post #25

Earlier quoted context omitted.

Interesting. What server side tech stacks are often used by young developers in the recent hackathon? Are there a few dominant ones or many choices?

I'll second that question. I figured Rails would still be pretty popular, and now I'm wondering to what degree that is or isn't true these days. My guess would be React/Angular or, if it's a particularly hip group, Next.js/Nuxt.js/Serverless with as little back-end as possible.

In my experience Angular is out and React is in with some vue people around as well.

For backend, graphql is in, expressjs is still in, firebase is in, flask and django are in.

Ruby on rails is unfortunately out among my peers: https://devpost.com/software/built-with/ruby-on-rails

Not a bad idea to do a blog post analyzing devpost trends, I might do that after exams.

Re: Rails 6: B-Sides and Rarities

#49

Post by _hardwaregeek »

ewalk153 wrote: post #33
mullsork wrote: post #27

Earlier quoted context omitted.

You can opt out of loading the library code for views/mailers/etc. Not sure if there's a way to skip the routing layer though. I'm sure you're aware of that already but just in case, you can skip loading the entire framework.

Use a Sinatra app and include ActiveRecord. There are a few gotchas like making sure to clear connections at the end of requests. https://stackoverflow.com/questions/41400202/replacing-activ... I’d love to see more examples of picking pieces of rails and combining with other libraries.

The only concern I have is that because AR isn't designed as a separate gem, there's no guarantees about breaking changes. But I suppose that's unlikely.
Post reply on HN