liveviews VS Graphene

If you want to try the liveview approach but not ready to work with Elixir / Erlang / Beam runtime, you can use liveview in 17 popular languages (Java / C# / Javascript / Typescript / PHP / Python, e.t.c.).

https://github.com/liveviews/liveviews

Below are introduction directly quoted from this list:

> This is a list of libraries for creating web applications that handle user interaction with the DOM on the server. These libraries take a different approach from older server-driven browser UIs that simulated a desktop GUI toolkit. They do not lock the developer into working with predefined components; most operate at the level of HTML (DOM) rather than GUI widgets.

> The list strives to be complete rather than awesome. You may see libraries that are not maintained or ready for production.

This approach allows you to handle business logics on the server, and update the screen in browser from the server as well.

[1] https://github.com/liveviews/liveviews

That's a conflation. I'm certain for at least some, the choice is more about using a single language than avoiding JS. I'm sure there are people using htmx who use a JS backend. There are at least 5 LiveView clones for JS for instance: https://github.com/liveviews/liveviews#javascripttypescript

Nuxt, Next, SvelteKit, Phoenix(Elixr), Blazor, and various liveview-likes are popular full stack frameworks. So, although many devs are becoming specialized, there certainly still are full stack developers with demand enough to strongly support several frameworks.

The list is seeking a maintainer. https://github.com/liveviews/liveviews/issues/23

> "different" platform with it's own unique patterns and quirks

Everything OP listed was a criticism directed at LiveView, the 'Live App' functionality, not Phoenix, the web framework. Live Apps are not exclusive to Phoenix either, as there are now imitators for every other web framework now, which at least speaks to its broader appeal amongst developers. So the criticism could be leveled towards the far less mature 'Live App' libraries on PHP/Python/JS/C# and so on and on:

https://github.com/liveviews/liveviews

However there are two ways you can do this server side: 1. Use a tool similar to live view: https://github.com/dbohdan/liveviews

And gqlgen is not alone in this. We found several more GraphQL frameworks that don’t take it upon themselves to address this problem. Widely used GraphQL server implementations, such as graphql-go/graphql and Python’s graphene, have the exact same gap of exposing messages of unexpected errors by default.

There are multiple Python-based GraphQL libraries and they all vary slightly from each other. For the longest time, Graphene was a natural choice as it was the oldest and was used in production at different companies, but now other newer libraries have also started gaining some traction.

> But you need to know that Wasmer and its sibling projects will stay free forever. We are open source lovers, all of us, and we have a strong background on working on open source projects before joining Wasmer too.

That's great. I'm sure the closed source paid 10x faster editions of the graphene Python GraphQL server written by Syrus "CEO of Graphene" and CEO of wasmer will be open sourced in this spirit.

https://github.com/graphql-python/graphene/issues/268#issuec...

http://graphql-quiver.com/

CloudinaryField is a custom model field not a django built in one and graphene-python doesn't know what do with it. See the list of types it does https://github.com/graphql-python/graphene/tree/master/graphene/types

Thanks for the reply, I was looking at Strawberry a bit but not enough documentation for a graphql noob like me... Hate to turn this into tech support but could you potentially answer a question for me? I'm having a really hard time figuring out how to do this. Given this example: https://github.com/graphql-python/graphene/blob/master/examples/simple_example.py and a slight modification:

Graphene was one of the first (if not the first) lib built on top of graphql-core to provide an easy to use api to build graphql applications. It's been around since 2015 and has a lot of integrations built for it (e.g. Django, SQL Alchemy, etc).