I've read through many negative comments on Labo (esp. on other sites)
But I think - hey this is amazing as I wished to build things when I was a kid. This inspires kids to create, interact and invent. Making connections to machines or instruments we daily use.
My Chromecast works quite well, at least the connection is quite stable casting from my mobile. 10s wait is kinda acceptable for me.
It'd be nice that resolution could improve.
We built our own server for apps in Go- turns out open sourcing it (https://github.com/skygeario/skygear-server) .
Not really popular yet, but we used it for nearly all our internal projects.
I think it's your model of operating the software is more then your source. Open source encourage technical knowledge sharing and collaboration work. However it can't replace one's or a company's dedicated effort. Imagine Uber open-sourced, it's as hard as it is to be to replicate it's business and value.
We are working on a software called skygear (https://skygear.io) as well. It's open-sourced from the first day.
Thanks for the liking the visual. This is a quick hack in an hour to demonstrate how http://skygear.io 's real-time sync and cloud database feature. Yet I am thinking to add more feature to it - markdown support and collaborator marks. Do you have any ideas on that?
Author here - I appreciate the 2.0 version adds the concept of "container-as-a-service" and "function-as-a-service" in, as those are really the latest trends. I actually agree on Traditional on-premise deployment and IaaS. But I still find the right hand side 2.0 is not a good abstraction of X-as-a-Service. Reason: The relationship between Conversation / Friends / Beer / Pizza is not as such in SaaS /FaaS / PaaS and CaaS. They do not illustrate a correct hierarchy of customization and abstraction.