4 ms·

I strongly agree with the article's points. While I haven't used Rails, I'm a Django developer and have never built something with Rails; I like the benefits of

I strongly agree with the article's points. While I haven't used Rails, I'm a Django developer and have never built something with Rails; I like the benefits of sticking with full-stack frameworks. Rails is a solid choice, but Django, especially when combined with htmx, also enables quick and robust application development. It's refreshing to read about someone who prefers a straightforward approach (using boring technology) rather than dividing work across multiple teams and technologies. Using a single, full-stack framework not only simplifies the development process but also enhances the overall enjoyment when working :)

graypegg 2y ago
I would totally expand "Rails" to "Django or Rails or Laravel or any other well-maintained mature full-stack web framework in the language you are the most comfortable with". There's a lot of awesome options for boring technology! Even javascript has next.js which is pretty boring at this point, even if it is missing some things.
- deleted 2y ago
  [deleted]
- W3cUYxYwmXb5c 2y ago
  AdonisJS is also really great, very much inspired by Laravel (which was inspired by Rails)
  - axelthegerman 2y ago
    First time hearing of that, not sure it passes the "battle tested" sniff test here. No offense, might be a great framework but the gist of the blog post is A) what you know or B) Rails (if you don't know what to choose)
    - omnimus 2y ago
      It might also mean that if you know JS then use AdonisJS. Which has become Rails of JS and is pretty old and mature too.
      - axelthegerman 2y ago
        Wow I'm surprised I never heard of it - probably because it's boring and "old" for JS standards... And not backed by FAANG. Thank you for sharing! Though I couldn't find out any well known companies using it (re battle tested) but some might just not disclose which is fine.
        W3cUYxYwmXb5c 2y ago
        Yeah, my organization does not disclose, but I can say I've used AdonisJS in production in the financial industry for about for about 6 years now.
dv35z 2y ago
What is your ideal Django stack (from front-end, to backend, APIs, database, hosting, etc), using well-supported, solid tech?
- mariocesar 2y ago
  One ideal setup I have is: Django + htmx + templates with jinja2 (to use macros) and styling with tailwindcss The good part is that if you start early with a good design, it's fairly clear how to move from views to a REST API (DRF or Django-ninja) later and split the front end if you need to.
  - dv35z 2y ago
    That's interesting - I'll have to explore HTMX and TailWindCSS further - one thing that has held me back is just looking at the HTML source, with all the odd tags, looks messy. I know that's an emotional reaction and not a technical one, but I do appreciate looking at code which just looks clean and neat to me... I've been learning React / Django / Bootstrap (open to ideas on that, but it's just been "there" for me) / SQLite, Postgres / Stripe for payment, Docker, and hosting on AWS and exploring Fly.IO for hosting. I haven't dug into APIs, but curious your thoughts DRF / FastAPI / Django-ninja). I know this is a Rails thread, so there might be a better place to have a discussion about it... Thanks for your insights!
    - mariocesar 2y ago
      For templating, that is why I prefer Jinja2 with macros instead of Django templates. {% macro IssueCard(issue, type) -%} ... lot of HTML {% endmacro -%} {% for issue in myissues %} {% macro IssueCard(issue, 'myissue') %} {% endfor %} The alternative is creating template tags, which can be a lot of work, and it gets you out of the templates. I have a folder called macros/ where I put all the macros I need, and then I use the import call from Jinja2. I agree with you; having long and deeply nested HTML templates creates too much noise when developing. Jinja2 Macros help with that.
hobotime 2y ago
The article said you should stick with what you know and are productive with. For you, the article recommends Django as your first choice.

graypegg 2y ago

I would totally expand "Rails" to "Django or Rails or Laravel or any other well-maintained mature full-stack web framework in the language you are the most comfortable with". There's a lot of awesome options for boring technology! Even javascript has next.js which is pretty boring at this point, even if it is missing some things.

deleted 2y ago
[deleted]
W3cUYxYwmXb5c 2y ago
AdonisJS is also really great, very much inspired by Laravel (which was inspired by Rails)
- axelthegerman 2y ago
  First time hearing of that, not sure it passes the "battle tested" sniff test here. No offense, might be a great framework but the gist of the blog post is A) what you know or B) Rails (if you don't know what to choose)
  - omnimus 2y ago
    It might also mean that if you know JS then use AdonisJS. Which has become Rails of JS and is pretty old and mature too.
    - axelthegerman 2y ago
      Wow I'm surprised I never heard of it - probably because it's boring and "old" for JS standards... And not backed by FAANG. Thank you for sharing! Though I couldn't find out any well known companies using it (re battle tested) but some might just not disclose which is fine.
      - W3cUYxYwmXb5c 2y ago
        Yeah, my organization does not disclose, but I can say I've used AdonisJS in production in the financial industry for about for about 6 years now.

dv35z 2y ago

What is your ideal Django stack (from front-end, to backend, APIs, database, hosting, etc), using well-supported, solid tech?

mariocesar 2y ago
One ideal setup I have is: Django + htmx + templates with jinja2 (to use macros) and styling with tailwindcss The good part is that if you start early with a good design, it's fairly clear how to move from views to a REST API (DRF or Django-ninja) later and split the front end if you need to.
- dv35z 2y ago
  That's interesting - I'll have to explore HTMX and TailWindCSS further - one thing that has held me back is just looking at the HTML source, with all the odd tags, looks messy. I know that's an emotional reaction and not a technical one, but I do appreciate looking at code which just looks clean and neat to me... I've been learning React / Django / Bootstrap (open to ideas on that, but it's just been "there" for me) / SQLite, Postgres / Stripe for payment, Docker, and hosting on AWS and exploring Fly.IO for hosting. I haven't dug into APIs, but curious your thoughts DRF / FastAPI / Django-ninja). I know this is a Rails thread, so there might be a better place to have a discussion about it... Thanks for your insights!
  - mariocesar 2y ago
    For templating, that is why I prefer Jinja2 with macros instead of Django templates. {% macro IssueCard(issue, type) -%} ... lot of HTML {% endmacro -%} {% for issue in myissues %} {% macro IssueCard(issue, 'myissue') %} {% endfor %} The alternative is creating template tags, which can be a lot of work, and it gets you out of the templates. I have a folder called macros/ where I put all the macros I need, and then I use the import call from Jinja2. I agree with you; having long and deeply nested HTML templates creates too much noise when developing. Jinja2 Macros help with that.

hobotime 2y ago

The article said you should stick with what you know and are productive with. For you, the article recommends Django as your first choice.