241–250 of 329 posts
Earlier quoted context omitted.
I'm in exactly the same boat. Ive managed to keep inntouch with core tools on the backend, but frontend has just withered on the vine, so to speak. Learning all the JS stuff is just too hard when combined with back end, data, auth, layout, display, responsive, etc.
> ...when combined with back end, data, auth, layout, display, responsive, etc... Exactly! Glad to hear I'm not alone in that boat! :-)
Using Android and Samsung internet.
Edit: I took a video screenshot https://voicer.com/v/HSpS9
I went to the button component page [1] and to the section of the counter and two increment and decrement buttons. Clicking on either takes something like 0.5 seconds for the counter to update it's value. Using Android and Samsung internet. Edit: I took a video screenshot https://voicer.com/v/HSpS9 [1] https://pynecone.io/docs/library/forms/button
On this page [1] when I press Decrement / Increment it feels like there's well over a second delay.
I went to the button component page [1] and to the section of the counter and two increment and decrement buttons. Clicking on either takes something like 0.5 seconds for the counter to update it's value. Using Android and Samsung internet. Edit: I took a video screenshot https://voicer.com/v/HSpS9 [1] https://pynecone.io/docs/library/forms/button
At least the site and the example counter app seem heavily dependant on low latency. I'm overseas and it took a second or so for the hamburger menu (on mobile) to open.
Maybe pairing this with edge hosting service like fly.io would make sense.
I went to the button component page [1] and to the section of the counter and two increment and decrement buttons. Clicking on either takes something like 0.5 seconds for the counter to update it's value. Using Android and Samsung internet. Edit: I took a video screenshot https://voicer.com/v/HSpS9 [1] https://pynecone.io/docs/library/forms/button
Edit: Seeing the comment about websockets and server location, I am in the EU so it's possibly that. I don't get why state of the frontend is stored on the backend though. Seems an obvious performance issue.