posted in Technology

Microsoft announces Project Zenith, a clutter-free Windows experience meant to entice developers - Engadget

But you’ll need a powerful system with 64GB of RAM to use it.

Microslop thinks that “Clutter free” means “bundled with an always on LLM” 😸

www.engadget.com/2251018/microsoft-announces-project-zenith-clutter-free-windows-experience/
enPage

Replying to @⁨axh@lemmy.world⁩

Like for example selecting Linux distro, downloading it and saving on an USB.

Using an USB thing is the somewhat decadent newfangled way to do things. The more classy way was to download the whole distro to an 1.44 MB floppy drive. \installation was by dd … of=/dev/fd0. Yeah, it required 16 megabytes of RAM. It was possible to boot it on an 386 PC. Though kernel compiles were a bit lengthy.

en.wikipedia.orgMuLinux - Wikipedia

Replying to @⁨lawks@aussie.zone⁩

Lol I just found my burned CD-ROM of windows 10. I seem to remember asking on reddit how I can get a disk copy when they were offering a free upgrade from windows 7 to windows 10. Everyone clowned on me and downvoted and saying I was ridiculous for asking such a thing. Looks like I figured it out somehow.

Is asking for a physical copy such a ridiculous request lol? It gives me peace of mind that I can reinstall whenever.

Whatever, I’ve since moved onto Linux only for the last 5 years or so. The days of dual booting are long behind me. Funny enough in that pile of CD-ROMs was Ubuntu 10.04, the first distro I ever used. I remember doing a bunch of convoluted bullshit to get Oblivion to run on WINE haha.

Replying to @⁨schipelblorp@sh.itjust.works⁩

I don’t get it either.

If they said “requires a beefy dGPU or one of the handful of high-bandwidth APUs” that feels like it would make more sense than just 64G RAM. I thought most models weren’t optimized to run on a CPU even with gobs of RAM.

And plenty of firms don’t ship their devs 64G machines, especially in ghe current RAM crunch. Mine sent me a 16G machine in like 2023 and only replaced it with 32 on request because Win11+Docker were heavier than the old Win10/external server workflow.

Replying to @⁨Vlyn@lemmy.zip⁩

Teams, Visual Studio, VS Code are trash, they leak memory like no other

WSL2 is hilarious, just run Linux/UNIX?

SQL Server and SSMS are trash

I run Docker quite a bit but if you’re actually writing the containers efficiently it shouldn’t be sucking down ~64GB of RAM. But I’ve also seen how people shovel things like Java, log rotation, etc. into those containers because they act like it’s a 1994 VPS.

Replying to @⁨partofthevoice@lemmy.zip⁩

Why an RDBMS on the local though? Testing shit doesn’t make sense to name it as a regular piece of software.

I always build against a local DB?

For our desktop / LAN software the DB will always be local.

For web, it’s easier since I’m likely to burn the DB down over and over during early development / prototyping. But I’m not using cloud hosted DB even in production, and don’t expose Postgres outside the DB server, so I find it easier to work on this way.

EDIT: I also think that a default installation of VS includes SQL Server. I don’t use it, so always have to adjust the installation and remove all of those bits, but I also have complete control of my environment. I could see an IT department just doing a stock VS installation with the required workloads.

Replying to @⁨hdsrob@lemmy.world⁩

Yeah sorry, that’s what I meant by testing stuff. I suppose if you’re always testing things in the DB, it makes sense. Usually in my case, I would spin up a Postgres instance only for the week or so that I’m developing and testing with it. Eventually I push to cloud though. I don’t keep it running locally unless I’m testing a change. But I’m not testing changes often… I wouldn’t consider it part of my stack for that reason. I might run a local RDBMS a few times a year.

On the other hand, I will use SQLite or DuckDB all the time for local work. Not sure if those count as RDBMS, they are serverless.

I won’t never consider a local RDBMS as having stable data storage, so it falls into a strictly “testing” category for me, I guess “development and testing” is more accurate.

Replying to @⁨partofthevoice@lemmy.zip⁩

I could totally see that for the web stuff where I only make changes a couple of times a year. Usually when working on those I just delete the local DB before I start to keep it clean, but spinning up a new copy would be more efficient.

For our desktop apps / server Postgres is always installed locally on the machine, so keeping it there mirrors “production”.

I spent most of my time working on those apps and services, or working on the Android client (or both at the same time when a feature requires that both change), and often on a copy of actual customer data as we do a lot of custom work for clients.

Replying to @⁨undefined@lemmy.hogru.ch⁩

This is on my work PC, I can’t just switch there (:

For .NET development Visual Studio and Rider are the only decent options, everything else is “trash”. Teams is the company communication tool (besides Outlook).

And we run SQL Servers in Azure, PostgreSQL would cost the same (but I’d love to switch to it myself).

You don’t need 64 GB of RAM, I was happy with 48 GB too, but the headroom is nice. 32 GB would be borderline for my work though, especially as I often have two heavy backend services open (2x Visual Studio) plus a Python project for automated tests (VS Code).

Replying to @⁨undefined@lemmy.hogru.ch⁩

I build windows software, so need Windows and VS. I keep my entire development environment in a virtual machine. I also have a couple of other VMs for client isolation, clean installation testing, etc.

So having that much memory allows me to run more than one virtual machine at a time, and keep enough reserve for my actual desktop.

It was also my first rebuild in over 12 years, and RAM prices hadn’t gone stupid yet, so I figured I’d drop a few more $ and build another decade+ future proof machine.

Replying to @⁨undefined@lemmy.hogru.ch⁩

Java dev in charge of a $100M product here. Can’t actually compile it with less than 32 GB of RAM.

My old job working with a hydraulic analysis firm, needed 256 GB to run the product it in local development mode; to run customer models in production was a mainframe job - typically multi-terabytes. Computational fluid dynamics eats all your memory and asks for more. My work computer would have been pretty shitty as a gaming desktop, but did have every memory slot maxed out.

Yes, you might be working on something more lightweight, and that is fine. That doesn’t mean that your requirements are the be all and end all.

Replying to @⁨undefined@lemmy.hogru.ch⁩

I develop in containers, which means I don’t have to install dependencies on my host.
While it’s overhead, it’s never that massive.
Sure things like Codium and all the tooling takes up a lot of memory… I don’t think I’ve seen over 10gb of “dev related” memory.
I feel like people are significantly desensitized about how much data 1GB actually is.

Replying to @⁨Wispy2891@lemmy.world⁩

Clearly, the focus is on local AI development — a timely move as cloud AI token costs start to rise.

This is called burying the lede.

If Microsoft knows this cloud-based AI thing is a bust and people will be moving to local models that are not controlled by Microsoft or OpenAI or Anthropic, then it’s only a few months before Satya tells his investors buddies and the bubble pops.

Replying to @⁨schipelblorp@sh.itjust.works⁩

I find this unlikely… IMO I think they are hedging in both directions.

Personally I like the idea of local AI. open source models that you an control, decide, and use smartly, sort your things etc… and not pay an absurd cost or link up.

Personally I think MS is actually betting on the opposite. IE they had a prototype windows that was basically just an AI prompt, no start menu etc… and applications just “streamed”.

IMO I think that’s more of the goal, use the data center buildout to drive up hardware prices, until people cannot afford a basic PC. Sell thin clients… then sell us “access” to compute in a form where we own nothing, but pay by the processes used etc…

Replying to @⁨TheFogan@programming.dev⁩

I agree it’s a hedge, but I think it’s a pretty big admission that the writing is on the wall.

Given how much Windows has invested in cloud AI, that they are encouraging developers–the sweetest plum, the people most likely to pay for cloud AI–a local environment is a pretty big admission. This is the sort of thing corporations that have the ability to control markets don’t do unless they think the market is going to leave them behind.

Replying to @⁨Wispy2891@lemmy.world⁩

64GB of RAM to use it.

Does that mean it does not run on my beloved Thinkpad X220 with 4GB?

Looks like I am stuck with running Debian 13 on it.

Fun fact, at $currentwork there are two true believers in AI and somehow they managed to procure me a laptop for home office which weights in roughly 9 kilograms - a bit more than six times as heavy as my 12 year old X220. Must be the battery which is needed to power the NVidia graphics card.

Replying to @⁨Wispy2891@lemmy.world⁩

The goal, really, is to cut the crud out of Windows to create a more Linux-like experience.

LOL. I’ll just keep using Linux, thank you very much. Great article though:

[…] demanding 64GB of RAM in the age of the RAMaggedon seems inexcusable. (Especially because Microsoft’s partnership with OpenAI and its overall AI push is a big reason memory prices have skyrocketed.)