Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

React, but in Python

github.com

Post reply on HN
Print view View original

61–70 of 179 posts

Re: React, but in Python

#61

Post by paulddraper »

Solvency wrote: post #19
quechimba wrote: post #16

Earlier quoted context omitted.

Yep. And nowadays you can deploy apps really close to users so latency is really low. If you have <100ms you don't really notice the latency.

But... 99% of insert-startup-product-built-on-React (or honestly, any framework) is typically super slow (for whatever reason that might be). Sluggish, not super responsive, laggy UI, however you want to describe it. A far cry from the snappiness of desktop apps from 25+ years ago. Something or some collection of people are doing something wrong, somewhere in the chain. So isn't this just yet another way to further e…

> A far cry from the snappiness of desktop apps from 25+ years ago

So apps without network latency are faster? Huh.

Re: React, but in Python

#62

Post by zdragnar »

moritzwarhier wrote: post #25
Solvency wrote: post #19

Earlier quoted context omitted.

But... 99% of insert-startup-product-built-on-React (or honestly, any framework) is typically super slow (for whatever reason that might be). Sluggish, not super responsive, laggy UI, however you want to describe it. A far cry from the snappiness of desktop apps from 25+ years ago. Something or some collection of people are doing something wrong, somewhere in the chain. So isn't this just yet another way to further e…

Your statement is very broad. Might be the startup culture and lacking technological expertise, no? Was insert-startup-product-built-on-.NET fast 15 years ago, for example? Not trying to be controversial, just wondering. I agree that a product built by clueless developers stringing together random libraries or bad custom code in React would create slow products. In your spirit, I might argue that thinking "reactively…

As someone who has had the misfortune of working on poorly tuned WordPress and Drupal websites in a former life I can confirm this is an issue of culture, not and axiom of whether SPAs are intrinsically faster or slower.

Re: React, but in Python

#64

Post by heavyset_go »

motogpjimbo wrote: post #58
roqi wrote: post #44

Earlier quoted context omitted.

> Making a 'server call' on each interaction is also what web apps used to do before SPAs were a thing. One of the reasons behind the popularity around webapps was that they would no longer need to make 'a server call' on each interaction. > And in many cases it's what SPAs do as well. I feel you're grossly misrepresenting what SPAs do. SPAs do calls to send and receive data, not to fetch server-side rendered content…

> One of the reasons behind the popularity around webapps was that they would no longer need to make 'a server call' on each interaction. Ironically, many modern SPAs are significantly slower than the traditional apps they replaced. Try using Twitter's webapp on a non-premium phone, for example. Sometimes it's regrettable that the webdev truck has no rear-view mirror.

Hell, try using the Twitter web app on something with 8GB of memory or that's older than 5 years old.

Re: React, but in Python

#67

Post by kokanee »

motogpjimbo wrote: post #58
roqi wrote: post #44

Earlier quoted context omitted.

> Making a 'server call' on each interaction is also what web apps used to do before SPAs were a thing. One of the reasons behind the popularity around webapps was that they would no longer need to make 'a server call' on each interaction. > And in many cases it's what SPAs do as well. I feel you're grossly misrepresenting what SPAs do. SPAs do calls to send and receive data, not to fetch server-side rendered content…

> One of the reasons behind the popularity around webapps was that they would no longer need to make 'a server call' on each interaction. Ironically, many modern SPAs are significantly slower than the traditional apps they replaced. Try using Twitter's webapp on a non-premium phone, for example. Sometimes it's regrettable that the webdev truck has no rear-view mirror.

The entire internet is slower because it's being squeezed to oblivion for monetization and tracking purposes. No matter what technology you choose to render HTML with, your company is going to have a slew of systems for injecting 3rd party scripts, running A/B tests, collecting analytics that include recording user sessions, etc etc. Back "before SPAs" we just weren't doing as much crap in the browser.

Re: React, but in Python

#68

Post by rmorshea »

agumonkey wrote: post #3

Could be fun to see this replacing jinja in old frameworks like django. Although inheritance had a better feel with templates..

ReactPy dev here. We're actually contributing to a WIP PEP that would add JS-like tagged template literals to Python. We think this will open up a whole new world of templating and DSL possibilities: https://github.com/jimbaker/tagstr

Re: React, but in Python

#69

Post by gkhartman »

robertlagrant wrote: post #65
agumonkey wrote: post #3

Could be fun to see this replacing jinja in old frameworks like django. Although inheritance had a better feel with templates..

Django doesn't use Jinja, does it? I thought it did its own thing.

They have their own template engine, but it can be swapped for Jinja2 optionally.

Re: React, but in Python

#70

Post by nosnah »

garymiklos wrote: post #35

Does anyone have a list of full-stack Python frameworks for building interactive web apps? I feel like a new one comes out each week, and it would be nice to see them together to compare.

Not a list, but I've been trying out django-unicorn, which lets you build components in python and use things like unicorn:model and unicorn:click in your templates.
Post reply on HN