Only SRR + some javascript (modals, effects, etc).
What I am missing? Serious question, Am I missing TOO much or maybe 20% productivity?
1. I am a one man shop doing Django sites, SRR only.
When I need to interact with front end for more "Reactivity" I use javacript + a view exporting json.
2. About admin: It is good for me or the operator but I dont feel like my user should be using it?
Then I do my own "admin" for the customer.
Please what I am missing?
The #1 I feel once you have 2-3 they may make sense (separating functions).
The #2 the community answer was : "Not for user, only staff or operator and not for general consumption"
I take a similar approach to you, and am also a solo dev. I would take a serious look at client-side frameworks if I was building something more appy than websity. It might also make more sense if I was working with others and there were separate front end and back end people so defining some kind of back/front end interface would make sense.
With regard to the admin, my experience is that usually the customer will have specific tasks that they need a workflow for, and the admin panel is often not a good fit for that (and things get messy quickly if you try to bend the admin panel to be something it isn't).
As someone with a similar skillset, I decided to use React for a the frontend for a new project as a learning experience, since I assumed I'm missing out on something by using JS + JSON from a Django view when something asynchronous or interactive was needed.
After a week of wasting time due to needless complexity caused by React (I don't want an SPA), I took React out of the loop and got on with actually developing features that are needed. I don't feel like anything is missing from the final product nor am I missing out on any productivity gains that would be realized after my initial learning curve.
I’m curious to hear what about creating a multi-page application you found to be limited by react. react-router solves this problem quite well. Personally I’ve had a lot of fun using create-react-app to quickly get rolling on side projects without worrying about the painful setup bits and the documentation is pretty good.
Having said that, I don’t know enough about your use case to say that react is a better choice.
If the site is mostly static then SPA isn't worth it. If you've got a lot of functionality SPA let's you make site way more interactive without hacks.
The best of both worlds is a static site sprinkled with React components where they make sense. Angular can't really do this, but react is designed to work in parts of pages.
So if your customer wants one really crazy sortable filterable list view you can do that in clean react code instead of a bunch of jacky jquery
Having a React / Vue whatever in addition to your Django server allow you to split the "View" from the "Model-View-Control" paradigm that Django respect, when you have django & react, Django is only "MC" and react becomes "V"
Simply put, when you are in the template paradigm you are producing HTML files, when you are using React you are generating HTML.
For instance, I'm not building up an "account" page, i'm building up a "detail" page that can be reused with a query that I'm passing in. That query is a function that defines the call to Django. Eventually I'm passing parameters to the component to drive it's behaviour.
I'd simply suggest you to go learn some react, it is difficult and it takes time, but it will allow you to see more solutions to problems that you might be handling in the "industrial" way (eg: writing 10 templates and having some jquery mixxed in the html)
I've been working with django and react for a while now, and i'm now used to 100% coverage without much hassle and very good productivity (dare I cite my boss :) )
It depends on your use case. I wrote many web apps w/ frameworks like Django before migrating to React several years ago. The point I wanted to add was, when I started using React, (after the very initial hump) it felt like a breath of fresh air. I didn't feel complicated or confusing, it felt like it was de-complicating everything I was doing. My point is, if it doesn't feel that way, you may not have the problems React solves well and probably aren't missing out.
It is always the same thing, someone comes and says, please use Django, then someone comes and say but I'm going to use React in the front, then someone comes and say, why would I need react?
A framework is an opinionated piece of code that helps several people understand the code everyone is creating.
If you are alone, the need for a front end framework is equal to 0
after this week's release of React Server Components I'm feeling even more convinced that having 2 tools to tackle different ends of the problem is better than trying to make 1 tool fit everything.
Hey, thanks for comment and sharing the React Server Components news - have checked https://reactjs.org/blog/2020/12/21/data-fetching-with-react... . 18:02 - "server components can not have any interactivity". So essentially this is (something similar to) renderToStaticMarkup with some bells&whistles.
Would live to share quote from https://news.ycombinator.com/item?id=25358976: "I feel like we're in a transition period where we will eventually get both the nice developer experience and flexibility combined with nice performance".
Am wondering if anyone tried to bundle vanilla js for dom manipulations alongside server-rendered react componenents which deliver html+css server-side. Where do you put js code inside the component folder? What are the patterns and best practices of using react only for html+css composition and using vanilla js for interaction? Thanks a lot for any tips!
But I hope some of HNers illuminated me.
I don't do React/vue .
Only SRR + some javascript (modals, effects, etc).
What I am missing? Serious question, Am I missing TOO much or maybe 20% productivity?
1. I am a one man shop doing Django sites, SRR only. When I need to interact with front end for more "Reactivity" I use javacript + a view exporting json.
2. About admin: It is good for me or the operator but I dont feel like my user should be using it?
Then I do my own "admin" for the customer.
Please what I am missing?
The #1 I feel once you have 2-3 they may make sense (separating functions).
The #2 the community answer was : "Not for user, only staff or operator and not for general consumption"
I would glad hear your points.
Thank You