Live data from Hacker News

Bullet Train – Rails-based SaaS framework

bullettrain.co

71–80 of 148 posts

Re: Bullet Train – Rails-based SaaS framework

#71
post #40

Wow, hi everyone! Was just about to walk over for the first day of RailsConf when a friend let me know we were #1 here! Honored! I'm the original creator of Bullet Train, although a number of people now work on it. It's been a fun journey to this point! When I first started building Bullet Train, it was a relatively unique offering. There weren't that many full-featured "SaaS starter kits" out there, although there w…

It's so amazing to see how the tech community inspires and learns from one another. Laravel found inspiration from Rails. Then, seeing Bullet Train was inspired back from the Laravel ecosystem with Laravel Spark.

In the past, I was jealous of the Ruby ecosystem with an extremely large community (the grass is always greener on the other side?). And, thinking the JavaScript ecosystem was left behind, but now I am hopeful that the JavaScript ecosystem has finally caught up.

I can totally confirm Bullet Train is an inspiration for many SaaS Boilerplates. I was personally inspired by Bullet Train to build Nextless.js [1], a Next.js based SaaS Boilerplate, bringing SaaS starter kits in Next.js/React/JavaScript ecosystem.

--- [1]: https://nextlessjs.com

Re: Bullet Train – Rails-based SaaS framework

#72
post #65

This might be a good place for a Java programmer to say thank you to the Rails community for your relentless mocking of Spring and Enterprise Java back in the days. Java is wonderful these days, and seriously I think you guys are a one of the major reasons why Java is so great today.

I recall when I started even with Rails pre Rails 2.0, the Spring framework was a horror show. Good luck with XML plumbing and then annotations wiring and then dependency injection container and AbstractBusinessProxyFascadSingletonFactory whereas in contrast, Rails seems light years ahead from controllers to templating to ORM.

Why the downvotes?

Re: Bullet Train – Rails-based SaaS framework

#75
post #64
post #18

Earlier quoted context omitted.

I’ve only heard good things about tailwind. Did you have a bad experience with it?

That's the nature of how these things go. People that like Tailwind praise it. People that think it's fundamentally bad design avoid it and don't say too much, or are drowned out by the people praising it. People who just write SCSS don't even think about it.

Companies like tailwind

Engineers learn to work with it due to that simple fact.

It's OK tbh, and it's easily interoperable between stacks so not really hard to pick up and useful if your project already uses it.

I tried to fight it at first, but I've only seen it being used more and more. Why fight the stream if there's no good reason for it?

Re: Bullet Train – Rails-based SaaS framework

#76

This might be a good place for a Java programmer to say thank you to the Rails community for your relentless mocking of Spring and Enterprise Java back in the days. Java is wonderful these days, and seriously I think you guys are a one of the major reasons why Java is so great today.

Spring is still awful. Play, Javalin, and other frameworks are leagues better. Even Spring boot isn't a great framework which has way too much annotation soup. Worst thing with Spring/Spring Boot is that the framework and ecosystem breaks extremely often with updates.

Re: Bullet Train – Rails-based SaaS framework

#78
post #72
post #65

Earlier quoted context omitted.

I recall when I started even with Rails pre Rails 2.0, the Spring framework was a horror show. Good luck with XML plumbing and then annotations wiring and then dependency injection container and AbstractBusinessProxyFascadSingletonFactory whereas in contrast, Rails seems light years ahead from controllers to templating to ORM.

Why the downvotes?

May be the enterprise developers don't like convention over configuration[0].

[0] https://en.wikipedia.org/wiki/Convention_over_configuration

Re: Bullet Train – Rails-based SaaS framework

#80
post #69

If you are doing an MVP prototype or the code would be the client's problem once you're done with your consulting, such bulk boilerplate is fine. I have extensively worked with Python and Ruby in past but my conclusion is that even though they ramp you up in the beginning but as the code base grows, it becomes harder to guess deeper in the codebase to guess what objects you're dealing with. Specifically in case or Ru…

> to guess what objects you're dealing with

I don't understand, why are you guessing? Do you mean the parent objects of things you've written? Like ActiveRecord, etc. I would think that mental overhead is the same in any web+CRUD+ORM type of framework.

Post reply on HN