3 ms·
I think it sounds like a wicked clever idea. It also sounds like a recipe for bad-blood in the open source world. It emphasizes owning a repo rather than contr
by collint 15y ago
I think it sounds like a wicked clever idea.
It also sounds like a recipe for bad-blood in the open source world. It emphasizes owning a repo rather than contributing to one that already exists.
It also seems to push for over utilization of resources. Once you get to say 1-10K installs a multi-tenant solution would probably make more sense. What happens then? Does bushido help you roll your customers into one big app? Even if it's not good for bushido's bottom line?
Don't get me wrong, I see a lot of good and interesting things coming from this. I just also see some sticky situations.
- SingAlong 15y agoIt emphasizes owning a repo rather than contributing to one that already exists. Something that's been under discussion for a while at Bushido. Does bushido help you roll your customers into one big app? No. Each instance of an app runs in it's own sandboxed environment. That helps you keep your app simple and not worry about scaling for those 10k users. If you want a simpler perspective to look at the service - it sort of provides web apps like mobile apps. Separate instances like how they run on your phone. So tomorrow if there's an online editor app (like Google Docs. Just saying...) on Bushido and you have a Chromebook-like device, you can launch your own instance and that'll all be yours like a separate app. Once there's support for more platforms it'll be easier to see it as "app store for the web". All apps on the web and all you do is launch an instance of apps for yourself. P.S: I work for Bushido