Thanks. And sorry I meant to say I don’t believe in buzzwords!
Just watch 20m of the video will finish off later. Some thoughts:
* Sounds like it has some good qualities of Elm (domain specific language that reduces complexity) and Phoenix (in the channels etc.)
* I work somewhere where they do a OS process mirroring the front end and there is a bunch of issues you don’t have to worry about. I have not looked at a single SQL query plan since working there, whereas it is regular elsewhere. It does come with challenges for “big data” though as RAM is costly vs. disk space. But maybe you have ideas for that.
* Your system would probably add some ops challenges around load balancing processes and RAM but that could be offloaded to the cloud. Maybe Kubernetes could help here?
* But for most apps it is probably not an issue!
* After thinking Firebase makes web dev simple and realizing no it makes it way more complex I sympathise with a lot of points. Firebase makes the atoms so small that you are constantly worrying about 2, 3, 4 phase commits and how to tell the user that you partially fucked up!
* Seems very promising!
* I have questions but i’ll watch more see if they get answered
Thanks for checking out the video. It's a work in the progress.
On the note about load balancing, it's exceptionally hard. However, I have the ability to migrate traffic (poorly tested) and re-balance. In general, stream load balancing is a challenge on many fronts. However, I consider myself an expert as I was the architect of https://dl.acm.org/doi/10.1145/3477132.3483572 at Facebook. On this topic, my only regret is that I have to outdo myself since I (foolishly) patented an awesome protocol ( https://patents.google.com/patent/US11228626B1/en ).
Just watch 20m of the video will finish off later. Some thoughts:
* Sounds like it has some good qualities of Elm (domain specific language that reduces complexity) and Phoenix (in the channels etc.)
* I work somewhere where they do a OS process mirroring the front end and there is a bunch of issues you don’t have to worry about. I have not looked at a single SQL query plan since working there, whereas it is regular elsewhere. It does come with challenges for “big data” though as RAM is costly vs. disk space. But maybe you have ideas for that.
* Your system would probably add some ops challenges around load balancing processes and RAM but that could be offloaded to the cloud. Maybe Kubernetes could help here?
* But for most apps it is probably not an issue!
* After thinking Firebase makes web dev simple and realizing no it makes it way more complex I sympathise with a lot of points. Firebase makes the atoms so small that you are constantly worrying about 2, 3, 4 phase commits and how to tell the user that you partially fucked up!
* Seems very promising!
* I have questions but i’ll watch more see if they get answered