The name is poorly chosen. Many people use gunicorn as a WSGI server in combination with Django, it might even be the most commonly used one (with uwsgi), and I feel like this name is much too close.
Just yesterday started exploring sockpuppet[1] and was impressed with the speed. Websockets made any change feel instant. Also liked how it uses data attributes to specify dynamic behavior. It should be powerful enough to build simple interactions but has clear way to extend for complexity.
Will try today how sockpuppet works with django-tenants[2], if it does it will become my go-to toolset for web development.<p>[1]: <a href="https://sockpuppet.argpar.se/" rel="nofollow">https://sockpuppet.argpar.se/</a>
[2]: <a href="https://github.com/django-tenants/django-tenants" rel="nofollow">https://github.com/django-tenants/django-tenants</a>
This shit looks cool<p>As do some or many of the other competing technologies<p>I've been struggling to pick a stack that is super gd simple<p>But still let me do some SPA stuff for certain parts of the app<p>I might never actually write a line of code myself, but even so I want to easily be able to tell what my contractor is doing<p>And fix if necessary<p>Guide architecture<p>Maybe choose the initial stack in the first place<p>I'm overwhelmed at this point as to which stack I can use that will suck the least<p>Prob the biggest issue I have is just that '80%' number I often see thrown around with these new front end non-js js frameworks<p>That is, this will probably be able to handle about 80% of your use cases<p>Tf?<p>Noooooo<p>100%, please<p>At least, 100% of all up-to-medium-or-high complexity use cases<p>Not that I'm planning on rocket science<p>The question I want answered for any new tool like this is<p>Can it do basic UI interactivity like Duolingo?<p>Ok, then I'm in<p>Other than that<p>How to really compare this unicorn for django with livewire for laravel, inertia and or vue for everything, nuxt (which looks interesting), etc.<p>And my preferred contractor prefers rails, gd.
What? This example code contains so many issues...<p>- why would you write every character to the backend? Do they really encourage storing UI state in the backend?
- this approach fails greatly if a second user starts typing
- it says "no need to learn an additional template language" but continues to define it in the input tag<p>It looks like the developers of this framework aren't too much into actual client development. Example code should be at least valid to a certain point.