499
Almost nine gigabytes in size: Windows update 24H2 creates an undeletable cache file
(www.digitec.ch)
this post was submitted on 12 Oct 2024
499 points (98.4% liked)
Technology
59651 readers
2744 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The only (larger) enterprises that insist "we depend on Windows" are those with shitty corporate IT :)
And several governments from various countries and at various levels (municipal, state, federal)
there's
Even worse: governments using Windows are absolutely giving the US services direct access to all their confidential files & communication.
It's an adoption problem. My company only supports windows because all our customers use windows. All our customers use windows because all their vendors only support windows.
Potential solutions:
I get that there are solutions to the problem, but there's no way a team of 10 can port 35 years of win32 dependence and keep the business solvent. Maybe incrementally, over the course of 10-15 years. We're just now migrating off of .NET 4.8 because we use WCF so much.
Depending on the implementation, WCF can be really easy to adapt to new clients. If you wanted to support Linux, macOS, or web, you just implement the part of your service that make sense for those platforms.
I obviously don't know your app at all, but it sounds like a 10 person dev team could probably build a new app in just a few months since the backend is already there. It wouldn't have all of the features, but generally speaking it's a lot easier to rebuild an app than refactor an existing one. Whether that would bring value is another concern entirely.
That's why I put the (larger) there - if you are a small company maybe you can not keep up a separate office infrastructure from your deployment / test systems in case of SW development. If you are a large enterprise and use Microsoft infrastructure, then either the people making the decisions in IT are getting a lot of bribes, or they are really really stupid :) Or both.
And I mean that absolutely without anger against Microsoft, and purely in terms of security nightmare and waste of office productivity because using a contemporary windows system wastes so much more time of any given user that each desk worker probably loses 20-70% productivity compared to a lean operating system (and that would include something like Windows 2000 / XP).