> Applications that require minimal latency (e.g. animations, games) are not well suited for Purview
It's not actually React compatible.
Just why?
Show HN: Purview – A server-side component framework
11–20 of 56 posts
Re: Show HN: Purview – A server-side component framework
#12normally security would be implemented at an api level. you would have to be careful to implement that in the renderer here.
Re: Show HN: Purview – A server-side component framework
#13> Applications that require minimal latency (e.g. animations, games) are not well suited for Purview It's not actually React compatible. Just why?
Because the DOM is not synchronously accessible, I guess.
Re: Show HN: Purview – A server-side component framework
#14In React, forms are often built with this pattern:
* Type/change events fire on the field (e.g. username)
* Username updates the internal model (this.username = 'karthikksv')
* The submit button fires an event so the parent page can act on the entire data model ({ username: 'karthikksv', password: 'fluffykittens' })
I'm concerned that this model won't work well using server-side React components on a network with high latency – each type event would have to round-trip to the server to update in the DOM.
Re: Show HN: Purview – A server-side component framework
#15Wait, why could we not render the HTML on the server and only let the browser to the compositing? If there only was a protocol that would allow us to exchange input events and some drawing commands over some arbitrary network.. let's phantasize for a moment and call that protocol X. I would use it when it's mature so maybe from X11 on onwards.
Naturally, sending draw commands has a big downside in efficiency. Maybe we could later exchange X with something that only sends bitmaps?
Re: Show HN: Purview – A server-side component framework
#16this is a whole new level of security bugs
Re: Show HN: Purview – A server-side component framework
#17I know this comment is a joke, but this is actually how react was created. Facebook made a templating language in php called xhp ( https://docs.hhvm.com/hack/XHP/introduction ) and some people at fb developed react as a natural extension to xhp but in JavaScript.
Time is a flat circle.
Re: Show HN: Purview – A server-side component framework
#18I'm sure there's a use case for this but, for me, it's pretty rare to need pull new data or persist anything after most events, let alone every event. A single fetch and single save is usually all that's needed.
Re: Show HN: Purview – A server-side component framework
#19I know this comment is a joke, but this is actually how react was created. Facebook made a templating language in php called xhp ( https://docs.hhvm.com/hack/XHP/introduction ) and some people at fb developed react as a natural extension to xhp but in JavaScript.
TIL. Thanks for sharing!
Re: Show HN: Purview – A server-side component framework
#20looks like it's the react version of https://dockyard.com/blog/2018/12/12/phoenix-liveview-intera... ? edit: nvm, it's listed in the readme as inspiration
This looks awesome, thanks for sharing! :)