davidkell

4 tahun yang laludiscuss

Agreed and well put.

Lack of a decent Rails/Django option for JS/TS is part of the issue IMO, since that ecosystem is so popular atm.

I also wonder if you have to get burned a few times rolling your own and that's just part of the journey :)

davidkell

4 tahun yang laludiscuss

For junior developers reading this: frameworks are great, learn to love them, they will save you much time and stress when shipping real products.

davidkell

4 tahun yang laludiscuss

If you like Python, I can recommend this:

  - Start with SaaS Pegasus https://www.saaspegasus.com/
  - Deploy to Heroku
  - Get comfortable with "X-in-HTML" frameworks - Tailwind, HTMX, Alpine
  - Deliver your mobile app as a PWA https://web.dev/what-are-pwas/

Opinionated thoughts -> https://davidkell.substack.com/p/davids-opinionated-guide-fo...

(Nowadays I'd replace Turbo/Stimulus -> HTMX/Alpine)

Special thanks to Cory for his excellent guides on Django + JS: https://www.saaspegasus.com/guides/

davidkell

4 tahun yang laludiscuss

Happy SaaS Pegasus customer here! Reasons to love it:

- Cory’s writing on low JS alternatives to single page web apps was game changing for us. And that’s all built in. 10x faster to develop.

- You get access to a wonderful community of Django devs. Any question gets 3+ independent responses.

- The framework is non-opinionated. You get the same examples in both HTMX and React + APIs, many versions of CSS frameworks (Bulma, Tailwind, Bootstrap), multiple deployment methods, etc. This gives you a valuable toolkit to fit your solution around the needs of the problem.

davidkell

4 tahun yang laludiscuss

Thanks folks, much needed! Where is the list of destinations today?

davidkell

5 tahun yang laludiscuss

Many of your integrations talk about “syncing” rather than event collection, which to me sounds like what Fivetran is doing. Does that distinction make sense and how are you thinking about that?

davidkell

5 tahun yang laludiscuss

+1 for SaaS Pegasus. In particular, Cory has done a wonderful job in introducing a more pragmatic approach to Javascript with Django [0]. Plus he's built a strong Slack community and is always around to support and listen to any feedback.

We re-built our SaaS product using this boilerplate and wrote about the experience [1]. TL;DR: would recommend!

[0] https://www.saaspegasus.com/guides/modern-javascript-for-dja...

[1] https://davidkell.substack.com/p/davids-opinionated-guide-fo...

davidkell

5 tahun yang laludiscuss

+1 For this recommendation, an exceptional book. In particular chapters 2-3 demystify how databases work, and provides an intuition on when to use different kinds of databases and query languages without the typical hype (spoiler alert - use an RDBMS!)

davidkell

5 tahun yang laludiscuss

OK, that's an interesting POV.

To be honest, I was surprised that you advocated writing so many tests for each view, easily 10-20 per view.

Part of the beauty of Django's various class based interfaces is that you can be confident that if you add a validator to a model field, then it will be validated by the corresponding ModelForm in the corresponding CreateView.

But then again, you advocate against OOP in python including CBVs. If you do write all your endpoints as functions, it makes more sense you need to test it because it's easy to forget to include a line of validation or whatever it is.

FWIW I love the fact that various Django classes are like DSLs. DSLs are less powerful by construction, so less buggy. It is almost like using low-code. But I do see your point about tracking inheritance and control flow, it can be a challenge at scale.

davidkell

5 tahun yang laludiscuss

We recently started working with "traditional" Django + Hotwire + React wrapped into web components for interactivity.

We've previously tried React+Hasura/Postgraphile and React+DRF/GraphQL, but this is next level productive and a joy to use, and bugs are rare. Particular love for Django CBVs.

davidkell

5 tahun yang laludiscuss

As the sibling comment says, while I disagree with specifics this article is full of gems.

@Alex3917 What do you think of using Django-rendered templates for views that don't require significant frontend interactivity?

You seem to advocate the "everything is an SPA + Rest API" approach, which I thought was interesting.

davidkell

5 tahun yang laludiscuss

Has anyone found a frontend JS framework + backend combination with the developer ergonomics of say Rails, Django or Phoenix? Would love to hear.

Submissions

The easy way and the hard way

comments