Hacker Newsnew | past | comments | ask | show | jobs | submit | tanner49's commentslogin

There are a ton. Go on the HTMX subreddit and there is a question basically every week talking about some new styling framework. I'm not an expert but you will find something there for sure.


Ha you're right. My bad (poster). I didn't realize until right now that it kid of implies the opposite. Sorry about that!


Yeah.... got the website up an running a week ago on Heroku and made this post. And what do you know, hacker news crashed it!!


Guess I should upgrade from the hobby postgress tier....


Isn't this an unintentional argument for static, client-side rendering?


Ha no. No htmx here. Just me being dumb with Heroku.


And people still arguing that having a server process every request is a good idea


I think the argument in addition to "makes easy things easy" is "and most things are much easier than you think."

HTMX and the hypermedia philosophy asks you to reconsider whether you need the complexity ever, even at scale.


Hiring is one part of a business, but I don't know if I agree with this, mainly because learning HTMX is so darn easy. You are essentially offloading much of the business logic to other parts of the stack.

So, in my case, if I'm lucky enough to be hiring employees to work on this project, I'd likely be looking for backend django experts or true "front-end" devs with expertise in styling and limited client-side JS.


That's a fair critique. I would say that the Django ecosystem is fairly batteries included though. I used the django-allauth package for this project and it filled in those gaps.

Additionally, in the Python ecosystem your other options are basically flask and fastapi, which are definitely not any form of batteries included.


As a guy who has had a 8 year career largely in Django, I generally agree with this sentiment.

Even though I prefer and am probably much more functional with Django + htmx, my sense is that for general web applications both Rails and Laravel are generally more functional ecosystems.

Most of my Django work has been pretty data heavy or geospatial heavy, in which case I think python and/or geodjango are a great solution. In general, however, if I had a trajectory for more traditional web apps, I’d probably use Rails.


Rails was fun but combined with the uniqueness of Ruby, RoR always felt a little "too magic" for me.


Django people always say this "All you need to do is install this user management lib you're done".

There's at least 10 sophisticated steps to install and configure a user management system for Django and for beginners seeking genuine batteries included they'll have no idea if they are doing it right or wrong, ending up at best with problems and at worst a misconfigured auth system.

Django really should not be recommended to beginners, it's for sophisticated Python devs.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: