Show HN: Purview – A server-side component framework
1–10 of 56 posts
Re: Show HN: Purview – A server-side component framework
#2No post body was provided.
Re: Show HN: Purview – A server-side component framework
#3This smells a lot like meteor. Would love to see an actual semi-large app built with this approach.
Re: Show HN: Purview – A server-side component framework
#4looks 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
Re: Show HN: Purview – A server-side component framework
#5Haha, I saw people using it in WebWorkers, no nothing prevents them from using it on the back-end.
One Lambda per component would be interesting tho, haha.
Re: Show HN: Purview – A server-side component framework
#6I 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.
Re: Show HN: Purview – A server-side component framework
#7here we go again
Re: Show HN: Purview – A server-side component framework
#8so it's a next.js clone?
Re: Show HN: Purview – A server-side component framework
#9Re: Show HN: Purview – A server-side component framework
#10looks 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
I was thinking the same. I expect elixer/phoenix to easily outperform js/node. I believe with phoenix it actually makes sense what they are going, which I can't really say from this "thing".