Platypus

In my experience, very, but it’s also not magic. Being able to package an application with its environment and ship it to any machine that can run Docker is great but it doesn’t solve the fact that modern deployment architecture can become extremely complicated, and Docker adds another component that needs configuration and debugging to an already complicated stack.

I’ve been migrating one of my company’s apps from microservices back to monolithic Java. It’s wonderful. I haven’t touched a line of yaml in weeks.

Because cross-platform apps inevitably feel out of step with the OS they run on. Native apps can use system components and behaviors and will almost always run better because they don’t need to be wrapped in a cross-platform framework. Admittedly a platform-locked app isn’t going to be a universally perfect Lemmy app, but it can certainly be a platform-specific perfect Lemmy app.

With no disrespect to Voyager, its devs, or its users, this is why I can’t use that app despite its impressive feature set and high level of polish–the ui feels fundamentally wrong on iOS, and the fact that it’s a very direct Apollo clone but not written in native swift makes it feel like a knockoff.

doesn’t understand that this is a useful first step in debugging

reacts with anger when devs don’t magically have an instant fix to a vague bug

Yep, that’s a manager

In my experience refactoring lots and lots of crappy code left by devs long gone, a dev who can write useful comments is by and large a dev who can write code clean and simple enough not to need them. If the code doesn’t have informative names and clear separation of concern, chances are a comment won’t help because the dev didn’t really know what they did that worked in the first place.