bluewalt

Not a hindrance, but something like not having a typed database, no auto completion over time, can be a real drawback (I know about django-types).

Finally, in my opinion, the best reason to not use Django is not the project itself (because it will do the job in 99% case), it's because all you learn is tied to Django.

Having learn Pydantic recently was a breed of fresh air, and I would reuse it in lots of projects, not only web projects.

> Django was rarely a hindrance.

+1 on this. Django scales pretty well when adopting a clean architecture like Django Model Behaviours with mixins.

> Otherwise, I've found its ORM quite powerful.

Same. In ten years, the only issue I had is with a very complex query that the ORM was not able to write properly. But a workaround existed.

I'm currently using FastAPI in a project. It's very enjoyable (especially with a strictly typed codebase) but I have to write lots of batteries by myself, which is not very productive (unless you keep this boilerplate code for future projects).

What's a little frustrating with current webdev state if that there is no silver bullet. I can easily think of use case where a Django+htmx stack is much more relevant than a React/Vue one, but the opposite is true too.

People keep genuinely saying it's a good thing to have many tools to apply to the right usage. Personnaly, constantly switching from htmx to vue.js just fucks my brain.

I miss the time where I used Django or Rails and didn't need to ask myself all these questions.

I think he knows that. The comparison with jQuery comes from the fact it is a DOM replacement logic too. Even if the syntax is way better, in the end, it’s still a way of working that scales badly, compared to components which embed their own logic.

htmx shines to add dynamic behaviour on some pages, but is not appropriate to replace a medium-sized SPA in my opinion.

In France it was widely used but now we have new competitors like www.shotgun.live with a modern app, built-in resale feature, stripe payment, etc.

Hey there! I've built a tool that makes it easier for developers to compare different Vue.js UI component libraries. I got the idea after seeing many people struggling to pick the right library.

Feedback and contributions are welcome!

Location: Paris

Remote: Yes, but I would prefer an hybrid mode in Paris.

Willing to relocate: No

Technologies: Django, Nuxt, TailwindCSS, Docker.

Résumé/CV: david-dahan.com

Email: david.dahan3 [a] gmail.com

I built multiple ambitious products from scratch in early-stage startups and created my own startup. I have a deep understanding of the requirements of a startup, and I'd like to become the founding engineer (future CTO) of an early stage startup. I have more than 10 years of experience. You can read my blog: https://david-dahan.com/blog (mix of English and French).

Form my experience with Logitech mouses, dongle has always been way better that bluetooth. I noticed my phone was the most responsible device of all the mess. If I put it far away from my devices, it's better.

Maybe People should take a closer look to dev containers: https://containers.dev/

Yep I do the same. From time to time, I move all my bookmarks to my notes, adding a title as a description, and removing useless bookmarks. I use a classification. It helps keep the bookmarks somewhere and kind of organised, but is very hard to search for.

That's a very good point. I love the "the best solution to your problem is to realise you don't have a problem" mindset.

The thing is, your system requires a lot of discipline. If I had discipline, I would almost not need a tool :/

Thanks! I took a quick look to Raindrop.io, it seems powerful and full of features. At this point I'm wondering why they did not solve the problem of unsorted links. Since there is a browser extension, a simple solution would be to allow user to add optional tags when the user bookmarks the link.

The presentation is 6 years old...

I'm gonna screenshot this and show it to basically every dev I know.

Despite the excellent initial intention, the article itself shows the reasons of the low adoption: if you actually need to kind of hack every new piece of documentation, this is overwhelming. I can have more than 30 external packages for each project. It would be too painful to handle all of them, and particularly frustrating for the ones I can't, and still need to browse from my browsers.

This kind of projects could have a better adoption rate with standards for documentations.

1. Try to clearly identify what you love and what hou hate in tech industry and working on day to day. 2. Be able to prove your value when talking with someone. 3. Use this value to be picky, by curating opportunities to keep the one.

For the last 6 months, I had job opportunities every day and say no to everything until I find the right one. Your family and friends will laugh at you, but in the end you'll be happier than them.

This looks more a TailwindUI alternative, as daisyUI has a different philosophy to abstract utility classes, and makes the code shorter.

Backend: Django / Celery - Front-end: TailwindCSS, daisyUI, HTMX, Hyperscript - Devops: VS Code dev containers than I can duplicate easily between projects to keep configuration.

I think people in comment should not try to compare HTMX to SPA directly, but have a broader view of the whole pros/cons of the tech stack.

For example, let's say you need to write an admin dashboard with many pages, no fancy stuff. Odds are you'll be very productive with a good old Django/Rails, having no API to write and a single simpler project to maintain.

Once that monolithic framework choice is made, before HTMX, as soon as you needed interactivity, you had to mess with jQuery and the code was quickly awful. The only solution was to plug a SPA framework and develop an API (this is not trivial!). HTMX (and other tools like Alpine.js) solve that problem well.

So, the question is not "is HTMX better than SPA frameworks", but rather: "Knowing that I can now build decent front-end with Django/Rails, does a more complex stack with Next worth it?"

HTMX-like tools make SPA frameworks a little less indispensable in some use cases. That's it.

You're missing the point here. It's not "another framework". It's more like "no framework" at all. Please read: https://edofic.com/posts/2022-01-28-low-js/