Readit Newsjondot commented on Cloudflare was down cloudflare.com/... · Posted by u/mektrik
Wow, just plain 500s on customer sites. That's a level of down you don't see that often.
its like someone-shut-down-the-power 500s
LinkedIn is down
jondot commented on Ask HN: Would you still choose Ruby on Rails for a startup in 2025? · Posted by u/dondraper36
If you're like me and moved off from Ruby to Rust as your go-to-everything, try Loco which tries to be a faithful Rails on Rust (loco.rs). It has the magical scaffold, the smooth experience, and the features you'd expect from Rails including authentication built in (like Devise).
Disclaimer: I'm one of the authors of Loco.
jondot commented on Ask HN: Would you still choose Ruby on Rails for a startup in 2025? · Posted by u/dondraper36
Loco is awesome! Hoping that the openAPI generation comes soon - then I can generate zod schemas from the openAPI doc! It would be really cool to use something like hygen/plop or maybe tera (idk) to automatically generate svelte or react CRUD pages, similar to what loco is already doing for htmx.
Loco author here.
Thanks for the shoutouts!
We definitely try our best to match the Rails experience. Being that the experience is not something you can just have as a side effect.
We build stuff into Loco that Rails has, try it out, then decide if it's "Railsy" enough in the experience. If it's not, we delete it and try again.
I'm a Rails superfan personally, however as life turned out to me, I like Rust much more than I like Ruby. So the decision was to go "loco" and implement Rails for Rust.
We're looking for more feedback and people to try out Loco, please feel free to do so :-)
Great description of the problem. I enjoyed reading it, it’s almost like prose, great writing.
The solution I’m afraid is only one: solve smaller problems. There is no way a single person can solve a team’s problem as a side project. A small problem does not mean small codebase. It means small as in: focused, simple pain, simple solution, low amount of open questions.
Yes there is value to all of the other strategies mentioned. But if you want the root cause and the solution for this hydra effect it is the one I mentioned.
If you were born anywhere in the 80s, you might have spent the 90s and early 00s building side projects that you actually finished and felt no remorse over. That’s because scope was naturally small, problems were more focused, and there were multiple order of magnitude less options to choose from (in any domain: programming languages, libraries, interfaces, user flows, business workflows — everything was less)
jondot commented on Loco. The one-person framework for Rust for side-projects and startups loco.rs/... · Posted by u/ryandotsmith
Very cool!
I love how you've implemented models, particularly generating the entity from the database. I did something similar with PHP 20 years ago, but abandoned it when Rails came around.
Thanks!
We much prefer to have had Rails' activerecord, but activerecord has hundreds of person-years (maybe thousands?). So what we found was the best for the current lifespan of Rust and its ORM ecosystem
jondot commented on Loco. The one-person framework for Rust for side-projects and startups loco.rs/... · Posted by u/ryandotsmith
jondot commented on Loco. The one-person framework for Rust for side-projects and startups loco.rs/... · Posted by u/ryandotsmith
I love how open this is about following Rails' ideas, in that one simple statement it really helps explain how this will work.
Author here.
Thanks! I think Rails is still great these days. If someone can afford doing Ruby, they should definitely stick to Rails.
However if you're into Rust, this is the best I could do that is as similar to Rails but can preserve some of Rust's strictness