Because they cannot reveal it until some date in the future.

We have >60k users using remote access. They all seem fine with it.

I've never noticed any real latency difference between ssh, RDP, VNC, or the like unless my OWN local Internet connection is starved for bandwidth. Compressed RDP and VNC are relatively small, like 1-3Mbps with a 4k-ish display. It can sometimes peak up to 6-12Mbps because there's some stupid full screen video.

I've yet to see Kotlin outside of Android Apps. I've heard some Fintech startups were using it, but I have not seen it despite my job being Fintech consulting. What I do see is Clojure.

I've seen Swift backends in production serving millions of people (billions even.)

Neither is a particularly difficult to learn Language and TBH, I suspect anyone who knows one can learn the other with minimal investment.

There's apps like that today, with the shared backends written in C or C++.

If the cost to remove the material is less than profit, then they'll do it. (At least based on the bean counter spreadsheet claiming the costs and profits. Brazil has 211 million people, that's a lot of money.)

There's recently been changes to this with a number of larger websites and "high context" design is not universal in the slightest in Japan.

At work I am actually dealing with this quite often unfortunately.

Now how about documents all being created in Excel like it's Word?

They didn't fuck up. This is not a full sized disk format aka my VM's "128GB disk" is not a 128GB+ sized file on the native file system, if it was it would be mostly close to native (still not native because of indeterminate caching and user space vs "kernel" space access issues.) This is basically approaching raw disk performance.

No "thin" provisioned disk format is as fast native, it's not even especially close in many circumstances. The "thick" provisioned disk formats are generally much closer, similar to this one. This is definitely a very fast thin format.

Thin = roughly the size of the data or at least the data marked blocks.
Thick = roughly the full size of the disk volume (sometimes they are compressed or sometimes they are a bit larger than "full size.)

We had this legacy Solaris on SPARC service, 3 layer, sounds similar architecture but more servers, cores, fairly good amount of storage. Recently we had issues with Oracle pegging CPU cores and there's a 2 year late project to replace it with almost 200 servers (because growth and shit.)

I replaced it with 2 containers (for the App itself) running on a 2 VM cluster mounting from our ceph cluster (standard enterprise service) and a containerized postgresql cluster (standard enterprise service). Two week hack-a-thon with 3 developers and myself. We did rewrite the application from ancient C++ to Go.

The App containers are expandable, but in the 60 days in production we haven't had to expand them. The postgresql cluster didn't have any noticeable increase and same with ceph cluster. We did discuss doing a microservices architecture, but that only makes sense in certain circumstances and this was not it.

Unfortunately the holdup in almost all companies is not Word, Outlook, or PowerPoint and in 2025, it's not Access either: it's Excel.

The few orgs I've seen that have moved to LibreOffice or Google Docs have all still had a ton of business analyst using Office because of Excel.

The Arabic decimal separator is of course still not a comma and in cases where it's not convenient, you'll see full stops. Thought it's fun when you get people who cannot decide which they want to use and you end up with documents with all three in one paragraph.

News at 11, Business Tries to Keep Making Money.

Where's the "evil" here? (Also that was Google.)

If part of you business is a giant factory "wheel", then there might be cogs (which employ 1000s of people) that can be replaced by a new cog that's LLM + other software. It's not that the agent magically replaces a human.

There's some parts of brains that mostly look and operate similar to LLM and the question is, do those have some built-in mechanism to deal with LLM Hallucinations? (Or is the difference in operations enough that it doesn't occur in the electro-organic version.)

We have some ideas of why they hallucinate, it's not like we're flying blind.

In the 90s and early 00s, Enterprise land very much depended on IBM and/or RISC Unix vendors. Microsoft was mostly relegated to small businesses and end user machines.