I very intentionally have all memory turned off for chat. The amount of times I want to discuss an approach for it to pull memory out and have that steer the decision making is so obnoxious
Reminds me few months ago I asked it about a TV model specs, then later I was doing a UI for something, response was “I modified xyz and now should works perfectly with the HDR in your TV model!!”
When casually a friend asks you to ask your Claude something about topic you chatted about earlier and then Claude brings back a secret you didn't want anyone to know yet.
Yes you can set up a project and then ask a question, but this is tedious.
I understand the need for it to be in Siemens NX, but do they really run it in Windows VMs? As far as I know NX isn't certified to run in VMs without Nvidia GPU passthrough (aka Macs). It seems more sensible to maintain a fleet of Windows desktops specifically for CAD and industrial control.
Yeah, a couple years ago (sorry, no citation handy) I wasn't too surprised to learn that a Windows desktop can run faster in a VM on Intel Mac hardware than directly on a similarly-priced PC.
That was my experience during the Intel Mac era, when I did a lot of Windows development inside of a Mac VM.
IMO, the reason is all of the 3rd party fluff and poorly-written drivers that come with Windows PCs: Apple takes driver stability very seriously, and the drivers on a Windows VM are as vanilla (no fluff or features) as possible.
So this is all pure speculation, but seeing as they are a hardware company I wonder if they have some sort of internal only server chassis to house apple motherboards for their backend, tolerate asahi linux for this? No real external market for apple servers so they don't develop it past "Ok for internal use"
The more I think about it the more I doubt it, even if you make your own hardware it is hard to compete with a commodity server, but it is an interesting thought.
Update: or perhaps they do, a sibling comment had a picture of such.
Your public website / blog? Sometimes you want services that are accessible publicly, like your observability and logging servers (eliminates the VPN point of failure).
I have multiple public sites that are running through vpn+reverse proxy, for example, vaultwarden, and it’s more secure because in the reverse proxy I can have rules to pass the connection to specific end points so clients can access it securely but the actual webpage is locked behind SSO. I never encountered a VPN failure, if the connection is up it is up, and it’s an encrypted tunnel too. Another example, if you use something like coolify, you can pair it with another reverse proxy on top of traefic one builtin, and if you browse that service in coolify, your packet is going through an encrypted link all the way to the docker image behind coolify.
Last time I used DDNS i think was around 2012 in an NVR where I needed to access some cameras publicly.
I own one and there's nothing shameful about it. It's basically CNCed to Apple's standards, just without the logo. The cool thing is since Studio Displays work on Windows too, with Thunderbolt motherboards you can have a setup that's visually the same as a Mac but is actually a PC.
P.S. Does anyone know how well Studio Displays now work on Linux? The best I could get it to work was on Ubuntu, where it basically worked out of the fresh install. X11 KDE on Fedora was a close second. Couldn't get it working on Wayland whatsoever.
I have a suspicion most of these types of agent-targeted SaaS will die out once the human equivalents implement their agent layers / MCPs.
Agents having no way to pay for their use is one thing; lack of deep integration within the business domain is another (e.g. if you're a Git provider, you'd probably want to offer CI/CD, PR workflows, release management, publicly discoverable repos etc., and boom - you just copied GitHub)
We're actually meant to be less of a consumer product than i think you mean by this (but i may have misunderstood).
We're more targeting enterprise as storage infrastructure provider – selling directly to platforms who generate a bunch of code and need a place to put it.
There's probably still going to be a box of hard drives in a datacenter somewhere, it does make sense to have a layer to manage the agent interface, rather than letting agents completely loose on all your storage.
Agreed, but I'm making a distinction between the platform (whether it be Cloudflare Moltworker or a Mac Mini), which a human chooses for the agent to run on (for now), and tools designed to be discovered and consumed by the agents themselves (e.g. code.storage, AgentMail).
I'm so sorry for you and your wife's loss. At the same time, I'm struck by how strong your wife and you are navigating this tough situation. From an Internet stranger to another, may the loving memories of your daughter live on.
reply