vanderbilt

Fun fact this is how I learned a coworker pegged her husband. He wasn’t gay, but had no interest in topping her either. C’est la vie.

I took can make up fanciful ideas that don’t pass the smell test.

ROCm certainly has gotten better, but the weird edge cases remain; alongside the fact that merely getting certain models to run is problematic. I am hoping that RNDA4 is paired with some tooling improvements. No more massive custom container builds, no more versioning nightmares. At my last startup we tried very hard to get AMD GPUs to work, but there were too many issues.

Unfortunately getting an AI workload to run on those XTXs, and run correctly, is another story entirely.

My plan is to wait a few months for the software quality to mature, then migrate from my Deck to this one.

Yup, $100 too much and I get what out of it? I have a 12 Pro and there hasn’t been a single compelling feature in the past 3 generations.

I’ve been second guessing WP deployments as well, but I think the most likely outcome is a community fork once Mullenweg’s brain rot affects commercial interests too much.

In your second link it contradicts what you say about it not mattering if it’s true, right below the section you quoted:

“If the act relates to matters of public interest and has been conducted solely for the benefit of the public, the truth or falsity of the alleged facts shall be examined, and punishment shall not be imposed if they are proven to be true. (See Article 230-2 of the Criminal Code). Article 32 of the Criminal Code provides for the Statute of Limitations for filing a criminal action for defamation which shall prescribe in ten (10) years.”

The mistake was applying logic to a position they didn’t use logic to arrive at. Their talking heads say renewables bad. The thought process ended there.

Maybe. The average Joe looks at the price tag and makes up their mind, but it’s a trap. You also have to factor in the support costs. IT staff, device insurance, breach costs, etc. A device costs much more (2x, 3x or even more) than what you pay the OEM on the PO. The biggest sink is the human costs of supporting the fleet. Macs have higher capex but lower opex. In the end I see savings between 20-40% for well fitted clients.

It’s not for every org or team. I often work with small IT teams to provide the expertise until they are able to gain the institutional knowledge themselves. It’s usually a slow process, with transitions on the scale of years for the large companies.

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.