Live data from Hacker News

Bullet Train – Rails-based SaaS framework

bullettrain.co

131–140 of 148 posts

Re: Bullet Train – Rails-based SaaS framework

#131
post #113

Earlier quoted context omitted.

Yes that's what I meant. All you have is a variable and IDEs can't figure it all if there's no type on it. Not just that, let's say even if type is known but some of the methods are generated on runtime than IDE has no idea about it.

That’s not unique to Ruby though, I imagine most dynamic languages fall into this bucket.

Exactly, they do including JavaScript.

Re: Bullet Train – Rails-based SaaS framework

#132

Earlier quoted context omitted.

They seem to have their own 'reactive' way of doing it called Sprinkles but I don't think they've open sourced it yet https://www.youtube.com/watch?v=7NqjpInVIjc&t=181s

Update on this: We do now include Turbo by default and the "Cable Collections" feature in the linked video has been completely reimplemented by the CableReady team in a feature called "Updatable", which we now use in Bullet Train. You can learn more about it at https://cableready.stimulusreflex.com/guide/updatable.html . Very grateful for the work they did on this and grateful to not have to maintain a proprietary re…

This looks awesome thanks, and thanks to the CableReady team. Does anyone know how the equivalent would be done as best practice with Turbo?

Re: Bullet Train – Rails-based SaaS framework

#135
post #64

Earlier quoted context omitted.

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.

>> "fundamentally bad design" They literally wrote the book on good design[1] [1] https://www.refactoringui.com/

[flagged]

Re: Bullet Train – Rails-based SaaS framework

#136
post #124
post #122

Earlier quoted context omitted.

How on earth can styling every **damn hyperlink inline over and over again be a time saver?

You don’t have to if you define it globally.

Then you're just reimplementing CSS classes in Tailwind.

Re: Bullet Train – Rails-based SaaS framework

#137
post #64

Earlier quoted context omitted.

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.

>> "fundamentally bad design" They literally wrote the book on good design[1] [1] https://www.refactoringui.com/

The book included some useful rules for people new to interaction design.

These can be applied without the use of tailwindcss.

Use of the framework tailwindcss has nothing to do with the book.

The framework itself goes against the intended use of css. It ignores the power of the cascade and leads to a pile of incomprehensible

Re: Bullet Train – Rails-based SaaS framework

#138
post #64

Earlier quoted context omitted.

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.

>> "fundamentally bad design" They literally wrote the book on good design[1] [1] https://www.refactoringui.com/

The book included some useful rules for people new to interaction design.

These can be applied without the use of tailwindcss.

Use of the framework tailwindcss has nothing to do with the book.

The framework itself goes against the intended use of css. It ignores the power of the cascade and leads to a pile of incomprehensible css repeated over and over again.

It is convenient and unreadable at the same time.

Handy if you don’t want to learn css and use it properly and completely unacceptable if you do.

Re: Bullet Train – Rails-based SaaS framework

#139
post #116

Earlier quoted context omitted.

>> "fundamentally bad design" They literally wrote the book on good design[1] [1] https://www.refactoringui.com/

No, that's not true; a 2023 book giving advice like "don't use borders" is definitely not in any way a seminal source of "good design". Besides, I'm not saying I think it's a fundamentally bad design, I'm saying those voices are drowned out by the people on-board with it - for a great example, consider how you just came into the conversation, squished the nuance I was discussing, and gave hyperbolic praise to their b…

Exactly.

Millions of engineers are now more empowered to make design decisions - and given more convenient tools. The price - ignoring how CSS was designed to work, unreadable mess of classes in the markup, a bootstrap-like cookie cut approach to everything, and yes, the color purple.

Re: Bullet Train – Rails-based SaaS framework

#140

I haven't used Bullet Train, but I've found their "Teams should be an MVP feature" blog post [1] a really great overview of how to model team structures in relational databases before. Worth a read! [1]: https://blog.bullettrain.co/teams-should-be-an-mvp-feature/

Do you have any recommendations for more resources like this? I've had a hard time searching for patterns and tips for modeling common data/features for web applications.

I really like Derrick Reimer's blog[0] for these types of posts. You might have to go back in time to find something a little more technical. On second glance, it seems the older articles are no longer available. You can find most of them[1] on the Wayback Machine though.

0: https://www.derrickreimer.com 1: https://web.archive.org/web/20181001000000*/https://www.derr...

Post reply on HN