Sometimes I call the numbers on missing dog posters and just bark into the phone. I learn from the mistakes of those who take my advice.

  • 0 Posts
  • 54 Comments
Joined 10 months ago
cake
Cake day: March 28th, 2024

help-circle


  • That’s a rather bold statement to make, especially considering I have headed one of those large-scale deployments. IBM has over 100,000 Macs, up 50% from their previous deployment goal. There are plenty of Mac deployments in the 4 and 5 digit range. I work on several a year!

    Specialist industries have the most trouble switching, but legacy apps are less of a problem these days. Most are either a web app already or slated to become one, largely because mobile has made cross-compatibility a requirement. Things like CAD are the exception because they need native clients and aren’t mobile centric.

    Backend changes usually aren’t the bottleneck for cross-compatibility, if their app was written with decoupling in mind (thank you Agile). Throw that out the window if it’s some ancient SOAP monolith. They have bigger problems than their choice of user OS.

    Assuming your instance name implies you are in the EU, things are just different for IT over there. The cost savings from adopting Macs can’t materialize given the conditions.

















  • Because software monocultures are bad. The vast majority of browsers are Chromium based. Since Google de-facto decides what gets in Chromium, sooner or later the downstream forks are forced to adopt their changes. Manifest V3 is a great example of this. You can only backport for so long, especially when upstream is being adversarial to your changes. We need an unaffiliated engine that corrects the mistakes we made with KHTML/Webkit.