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

141–150 of 250 posts

Re: Rails for everything

#141

Post by Syntaf »

I’m building a member management platform [1] with Rails + Turbo + Stimulus and it continues to surprise me how easy it is to just… do things with rails.

* Want to allow your users to write rich text? Easy just use ActionText * Storage and attachments? ActionStorage is easy to setup * Job queue, asynchronous work? No problem with ActiveJob

Today I learned about Rails system tests and found it so cool. With almost no configuration I can write tests that interact with my app through a headless browser.

Rails is the ultimate solo developer and hobby project tool for me

[1] https://embolt.app

Re: Rails for everything

#142

Post by chooma »

dzonga wrote: post #133

for auth - instead of devise or the rails 8 auth - you can also opt for authentication-zero. what's hardly ever mentioned is how great hotwire is. it takes time getting used to, documentation is sparse but oh man oh man - hotwire is nice. you get to skip a majority of spa shenanigans.

I am really struggling to get hotwire running to be honest. I now just postponed implementing it till after the launch. Any good ways of getting up to speed on hotwire and debugging it?

Re: Rails for everything

#143

Post by masklinn »

ezekg wrote: post #10

After using SQLite in production for a little while, I don't think "SQLite is all you need." Migrations are a pain, so any long-lived app will eventually experience pain. As an example, SQLite doesn't have a way to add a NOT NULL constraint to an existing column; you have to rebuild the entire table using a temp table.

> As an example, SQLite doesn't have a way to add a NOT NULL constraint to an existing column; you have to rebuild the entire table using a temp table.

Or any other constraint for that matter, every few months I look for ADD CONSTRAINT again, only to rediscover there isn't anything.

The lack of any sort of PL language (or even just trivial stored procs aliasing queries) also makes migrations more annoying, CTE can handle some of the load but the verbosity and limitations of basic SQL make that awkward, and needing to round-trip through the host language for everything is frustrating (even more so when the host language is statically typed and thus requires adaptation out).

Re: Rails for everything

#144

Post by josegonzalez »

block_dagger wrote: post #112
schneems wrote: post #75

Earlier quoted context omitted.

If you like dokku, have you seen Cloud Native Buildpacks? You can build an OCI image from them as a first class feature https://github.com/heroku/buildpacks/blob/main/docs/ruby/REA...

Buildpacks look cool, but Dokku is perfect for single-server projects with its plugin system. It has one-command setup for Postgres and Redis, auto-backups to S3, built-in nginx reverse proxying, and an easy Let's Encrypt plugin. My current server has an uptime of 1,912 days (~5.3 years) with near 100% app availability. With reliability like that, I plan to stick with Dokku when I upgrade to a new server next month.…

Dokku uses heroku buildpacks by default and supports cloud native buildpacks by changing the builder to pack via builder:set.

Re: Rails for everything

#145

Post by dewey »

Syntaf wrote: post #141

I’m building a member management platform [1] with Rails + Turbo + Stimulus and it continues to surprise me how easy it is to just… do things with rails. * Want to allow your users to write rich text? Easy just use ActionText * Storage and attachments? ActionStorage is easy to setup * Job queue, asynchronous work? No problem with ActiveJob Today I learned about Rails system tests and found it so cool. With almost no…

Same feeling, I’m usually a Go developer but all my side projects are in Rails. It’s just fun to work with and see how fast things are up and running. Using gorails.com and Copilot helped a lot too.

Re: Rails for everything

#146

Post by aantix »

bleuchase wrote: post #134
aantix wrote: post #125

Earlier quoted context omitted.

If you're looking to build a SaaS app, start with a professionally curated Rails template. It will save you months of development time. Payments/Auth/etc are built in and there are solid patterns in place to extend from. Jumpstart Pro is great. https://jumpstartrails.com/ So is Bullet Train. https://bullettrain.co/

Do projects like Jumpstart Pro or Bullet Train exist for other languages? Like Go?

Not sure about the Go ecosystem.

Re: Rails for everything

#147

Post by peteforde »

rednafi wrote: post #86
sigzero wrote: post #51

Earlier quoted context omitted.

I don't think Go was trying to capture that space really.

Go initially tried to capture the C/C++ space and failed miserably. Rob Pike lamented[^1] over that in a famous blog post. It got the most love from people coming from Python and Node. Then it became the defacto language for writing networking tools, and to this day, it holds that crown. Go is in an awkward spot—it’s not dethroning Python because it’s not as expressive, academics hate it, and it’s not as fast as Zig…

Kudos: I find this to be an exceptionally helpful and concise description of the Go meta.

I would offer that Erlang did a good job of capturing the [concurrency?] space, though some of the tooling is showing its age.

It's therefore interesting to see Elixir straddle the divide between Erlang and Ruby.

I'm still Rails all day, but I've never stopped thinking Elixir is cool.

Re: Rails for everything

#148

Post by peteforde »

gavmor wrote: post #92
nomilk wrote: post #76

> if you follow (the Rails Guides) start to finish, you'll have a Rails app in production. And it isn't just hello world. Your app will have authentication, caching, rich text, continuous integration, and a database. That's a real application. These features are great for established apps like GitHub and Airbnb, but if you're making a tiny startup, and want to test ideas quickly, I wouldn't spend time on CI, caching,…

When do you switch from Flask/Express/Sinatra/Gradio/Hono to Rails?

When you realize that all you need to add to X to make it great is a crappy reimplementation of all of the things that ship with Rails before you can start building your app.

Re: Rails for everything

#149

Post by lylo »

Rails is wonderful and I’m thankful for what the community (and DHH) has done over the years.

My company (founded 2007) was built on Rails and that B2B app now has 200,000 customers… all on a Rails monolith, the same code base that has evolved with Rails over the years. It’s not just for side projects!

That’s said, I run my current side project on Rails 8 and Postgres (I don’t get on with SQLite). You can do so much with so little code! Inspect the source code here if you like :) https://github.com/lylo/pagecord

Re: Rails for everything

#150

Post by ajmurmann »

neeleshs wrote: post #62
ajmurmann wrote: post #4

I've been building some apps with stacks lately that are supposed to be more modern and performant. Namely an app with Spring Boot and another with Micronaut. Both had a React frontend. It really made me appreciate Rails' omakase approach. Just having a form that shows validation errors from the backend and having something as simple as Rails' flash messages isn't solved by the frameworks themselves and requires you…

Spring boot has form validations pretty much out of the box, via validation annotations.

It does have validations but the integration of then in Rails goes much further. In Rails you associate the form with the model and the validation errors somatically show up on the form.
Post reply on HN