@GossiTheDog Reminds me of a call I had today with a real, significant company somewhere in Africa, they are knee-deep in the Microsoft ecosystem, except the latency and bandwidth constraints were making any page load on office365 unbearable, the screenshare was painful to watch.
Maybe they should fix that first instead of spending all their capex on GPUs.
@mathieui @GossiTheDog I'm a firm believer that developers should be forced to use shitty machines on shitty internet connections so they can actually feel the pain they inflict on others.
@datenwolf @mathieui @GossiTheDog I've been slowly cutting down my compute for similar reasons. It makes IDEs and fancy code completion tools almost impossible
@datenwolf @mauve @mathieui @GossiTheDog You are conveniently forgetting that Visual Studio has recommended specs of "64GB RAM" and "16 core CPU" and we often don't just run the client, but an entire backend cluster as well, with a debugger attached. What we definitely shouldn't do though is give the senior devs in charge of architectural decisions overpowered workstations with like 96GB RAM, so they can't say shit like "(this 200-project nightmare solution) builds and runs fine on my end".
@lidsel @datenwolf @mathieui @GossiTheDog That's whack. IMO 32GB is decadent. Consumers are getting by with like 16
@mauve @datenwolf @mathieui @GossiTheDog Note that this is recommended, not required. They list minimum requirements as 4 cores and 4GB (absolute minimum to even run it) or 16GB (reasonable performance) RAM, but that cursed solution I described makes it cry on a laptop with 6 cores and 32GB RAM. I have a lot of strong feelings about the design decisions on that project.
@lidsel @mauve @mathieui @GossiTheDog
Then don't use the latest version of Visual Studio. Actually the "latest" version of VS that I keep using from time to time is VS2012. If you really need the latest MSVC compilers you can install those stand alone.
That said, these days my IDE consists of Vim, a shell, and on Windows the RAD Debugger; plain GDB everywhere else.
@datenwolf @lidsel @mathieui @GossiTheDog I feel you. I'm considering making a replacement for unix ed with some bits added for LSP support and calling it a day.
@datenwolf @mauve @mathieui @GossiTheDog I don't really have a choice. This is for work, the laptop and software licenses are provided. It's a Blazor .NET 10 project - not even supported in VS 2022. VS 2026 is a mixed bag, because some of it runs better, but there are many bugs and unfinished refactors (like options will straight up be missing because they haven't ported portions of the UI yet). Blazor is just particularly bad and unstable (and not helped by this particular monster project).
@datenwolf @mauve @mathieui @GossiTheDog People love saying shit like "just use commandline debian and write in assembly like a real developer", but it's not the job market reality. For what it's worth I never had issues with Visual Studio on personal projects, beyond some missing support for source generators, but it's not like any other IDE supports that either, since they're still very much a beta feature.
@datenwolf @mauve @mathieui @GossiTheDog
To show my age, I recall (pre Internet) there was a company that provided 286 machines to their support staff rather than current 386/486 PCs.
Maybe Borland?
@mauve This is why I've always kept using the oldest machines and phones I can cope with. It's a helpful barometer.
@mauve @mathieui @GossiTheDog
I've been preaching this for years. Developers should be forced to work and test their software on Celeron, 256MiB RAM, 256MiB swap, 5400 RPM spinning rust 120GB HDDs.
I'm okay with compilation to happen on a beefy iron.
But the actual user experience should be the absolute minimum.