What exactly sucks about it? If it's integrated well enough, why do you care? If anything, it's nice to know it's sandboxed by default.
The installer could pull the images, create the stack and run migrations, then shut down. The app could then up the stack, show a loading screen that would likely be shorter than any Adobe program, then open a webview. When the last window is closed, down the stack.
You wouldn't be able to tell the difference. And what is the difference exactly? Most big apps are composed of multiple components doing IPC, it just so happens to be TCP/IP here.
Not sure if your serious? I don't want a fucking SaaS stack running on my macbook for a small graphics tool? It's about the resource, the power, the battery, the heat, the CPU I care about. I don't want that.
Yes, and? I quoted that part. But why do I want a full backend stack running via docker on my machine for this? That sucks.
What exactly sucks about it? If it's integrated well enough, why do you care? If anything, it's nice to know it's sandboxed by default.
The installer could pull the images, create the stack and run migrations, then shut down. The app could then up the stack, show a loading screen that would likely be shorter than any Adobe program, then open a webview. When the last window is closed, down the stack.
You wouldn't be able to tell the difference. And what is the difference exactly? Most big apps are composed of multiple components doing IPC, it just so happens to be TCP/IP here.
Not sure if your serious? I don't want a fucking SaaS stack running on my macbook for a small graphics tool? It's about the resource, the power, the battery, the heat, the CPU I care about. I don't want that.
1 reply →