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

Rails for everything

literallythevoid.com

Post reply on HN
Print view View original

41–50 of 250 posts

Re: Rails for everything

#41

Post by tyre »

WD-42 wrote: post #32
rich_sasha wrote: post #12

As someone who doesn't do enough web dev to justify learning Ruby just for Rails: how does it compare to Django? That's the only batteries-included web backend framework I'm familiar with... Asking out or curiosity.

The biggest difference is python vs ruby. Python’s ecosystem is massive, so if you want to pull in any third party libs you have plenty of choices for whatever you may need. Django also has auth and the admin interface built in, both of which are very nice.

Ruby and rails’ ecosystems are also massive. Devise and ActiveAdmin are options for those two, though I haven’t used either in years.

With much of the AI development happening in python and typescript, you might be right about those areas.

Re: Rails for everything

#42

Post by fragmede »

kuduebrahim wrote: post #40
rglover wrote: post #38

> Rails is not dead; It's better than ever. Try using it to make something new this year. I hope as an industry we can move away from this "___ is dead" talk. The OP shouldn't even need to say this. If something is being worked on (in any capacity) and has at least one user, it isn't "dead." "Is it dead" is groupthink questioning that leads to great ideas being swept under the rug because they're not perceived as pop…

Right, I agree. But Perl is dead…

Raku's doing alright though

Re: Rails for everything

#43

Post by jwcooper »

hk1337 wrote: post #22

I’m curious on others thoughts on whether or not to use Devise? With the recent Rails updates, even in Rails 7, Devise didn’t seem that useful and seemed to over complicate the user authentication, registration, lost password experience and also seemed like I had to do a lot of work overriding their views to fit with my application. It seemed easier to not use Devise? It had its usefulness in earlier versions of Rail…

I figure if it's good enough for login.gov [1], it's good enough for my sites as well.

I also find devise pretty simple to get setup and use. It's so easy to mess up some small thing while writing your own auth. I've always pretty much trusted myself to at least get devise setup properly.

[1] https://github.com/18F/identity-idp/blob/main/Gemfile#L30

Re: Rails for everything

#44

Post by rglover »

kuduebrahim wrote: post #40
rglover wrote: post #38

> Rails is not dead; It's better than ever. Try using it to make something new this year. I hope as an industry we can move away from this "___ is dead" talk. The OP shouldn't even need to say this. If something is being worked on (in any capacity) and has at least one user, it isn't "dead." "Is it dead" is groupthink questioning that leads to great ideas being swept under the rug because they're not perceived as pop…

Right, I agree. But Perl is dead…

Is it? https://jobs.perl.org/

I don't use it and you may not but it still has an active community and job listings. The last release was on December 20th [1].

This is what I'm talking about: it may not be popular in a "bleeding edge" sense, but it's still being used and developed.

[1] https://dev.perl.org/perl5/news/

Re: Rails for everything

#45

Post by dismalaf »

rich_sasha wrote: post #12

As someone who doesn't do enough web dev to justify learning Ruby just for Rails: how does it compare to Django? That's the only batteries-included web backend framework I'm familiar with... Asking out or curiosity.

Ruby doesn't really have a learning curve... Maybe block syntax but that's super easy.

Rails gives you way more structure than Django.

Re: Rails for everything

#46

Post by kylecazar »

rglover wrote: post #38

> Rails is not dead; It's better than ever. Try using it to make something new this year. I hope as an industry we can move away from this "___ is dead" talk. The OP shouldn't even need to say this. If something is being worked on (in any capacity) and has at least one user, it isn't "dead." "Is it dead" is groupthink questioning that leads to great ideas being swept under the rug because they're not perceived as pop…

I agree with the general sentiment. But, ecosystem/popularity can matter (you didn't claim it doesn't, just saying).

Specifically, it might be useful to know if a once very popular (dominant in some circles) framework is significantly less so. That downward trend might be relevant for someone, somewhere. "Dead" is still probably not the right word.

Re: Rails for everything

#47

Post by rednafi »

Rails is awesome, and so is Django. I’ve built mission-critical apps in both and still do with Python. That said, I’d love to switch to Go for building large monoliths since it has a tighter type system and better concurrency constructs.

The problem is, Go community has never really filled that gap. I love Go, but the whole "Go doesn’t need a Rails or Django" mindset is part of why it hasn’t taken off in this space. Building networking tools and CLIs in Go is great, but when it comes to quickly building a full-stack web app, I still reach for Rails or Django. So this whole "X is dead" doesn't apply to Rails at all.

Re: Rails for everything

#48

Post by gjsman-1000 »

kylecazar wrote: post #46
rglover wrote: post #38

> Rails is not dead; It's better than ever. Try using it to make something new this year. I hope as an industry we can move away from this "___ is dead" talk. The OP shouldn't even need to say this. If something is being worked on (in any capacity) and has at least one user, it isn't "dead." "Is it dead" is groupthink questioning that leads to great ideas being swept under the rug because they're not perceived as pop…

I agree with the general sentiment. But, ecosystem/popularity can matter (you didn't claim it doesn't, just saying). Specifically, it might be useful to know if a once very popular (dominant in some circles) framework is significantly less so. That downward trend might be relevant for someone, somewhere. "Dead" is still probably not the right word.

More accurately: “Established” versus “Trendy” technology.

Maybe it’s stereotyping, but I strongly suspect users of Trendy technology are more likely to be vocal about it, including by answering surveys, and especially in online forums. I’m personally a PHP developer, one of the least Trendy technologies, and you’ll never see me loudly talking about it like a JavaScript developer. The internet, and frankly HN, would tell you that a language with over a billion Docker pulls isn’t worth learning.

Re: Rails for everything

#49

Post by [deleted] »

kuduebrahim wrote: post #40
rglover wrote: post #38

> Rails is not dead; It's better than ever. Try using it to make something new this year. I hope as an industry we can move away from this "___ is dead" talk. The OP shouldn't even need to say this. If something is being worked on (in any capacity) and has at least one user, it isn't "dead." "Is it dead" is groupthink questioning that leads to great ideas being swept under the rug because they're not perceived as pop…

Right, I agree. But Perl is dead…

[deleted]

Re: Rails for everything

#50

Post by rednafi »

najarvg wrote: post #31
jilles wrote: post #14

If you replace the title with Django it still works. I’m doing the same as the author, but with Django.

Not hands on with Django (or other Python based frameworks) so pardon the basic question. How do the speed of the generated application compare with the speed of a generated rails application? I know the latter has made some strides recently..

Python is generally faster than Ruby, especially in the newer versions. That said, we’re still talking about two of the slowest languages out there, so the performance gap probably isn’t that big.
Post reply on HN