11–20 of 20 posts
Have you tried using flask? I think you’ll find it closer to your experience with express.
In my last project, almost half the server code is really just converting REST to SQL. Why don't we just use SQL on the client directly?
If its just about authorisation, why not write an auth system for SQL and be done with all this unnecessary server code, once and for all?
I mean graphql sounds so stupid in this context because it's just cruft over SQL.
i'd be curious to hear more about how you've built a career around something as specific as django (if i'm understanding you correctly). does not seem a broad enough skillset for the sorts of places i've worked, and it makes me wonder if i'm being spread too thin.
Django is fine for web applications but I can understand wanting to learn other things after 7 years. You can try Go which seems to be very popular as a Python replacement for backends. Another option could be Elixir which is very popular here. Also you can try Deno which is written by the creator of NodeJs.
Ive been wondering for a while now -- tell me, do we really need specialized server logic for every little functionality? In my last project, almost half the server code is really just converting REST to SQL. Why don't we just use SQL on the client directly? If its just about authorisation, why not write an auth system for SQL and be done with all this unnecessary server code, once and for all? I mean graphql sounds…
i'd be curious to hear more about how you've built a career around something as specific as django (if i'm understanding you correctly). does not seem a broad enough skillset for the sorts of places i've worked, and it makes me wonder if i'm being spread too thin.
i'd be curious to hear more about how you've built a career around something as specific as django (if i'm understanding you correctly). does not seem a broad enough skillset for the sorts of places i've worked, and it makes me wonder if i'm being spread too thin.
Ive been wondering for a while now -- tell me, do we really need specialized server logic for every little functionality? In my last project, almost half the server code is really just converting REST to SQL. Why don't we just use SQL on the client directly? If its just about authorisation, why not write an auth system for SQL and be done with all this unnecessary server code, once and for all? I mean graphql sounds…
There's a lot of good reasons why you shouldn't just connect straight to the database from client-side code. [1] So you'll always need some form of server sitting in between. Maybe you could store it in a new database system built entirely for this, which handles all of the nuances. However, you nearly always have more complicated logic and constraints that need to be enforced beyond what can be specified in a databa…
I'm suggesting something like a hassura that isn't based on graphql, but works directly on SQL.
And ofcourse for specific logic, you can always run a traditional server in tandem.
Django is fine for web applications but I can understand wanting to learn other things after 7 years. You can try Go which seems to be very popular as a Python replacement for backends. Another option could be Elixir which is very popular here. Also you can try Deno which is written by the creator of NodeJs.
I've been wanting to try out the Erlang/Elixir ecosystem. Guess this weekend's going to be spent doing a few tuts on those.