The problem with Windows after Windows 7 isn't really ads, it's the blatant stupid use of web view to do the most mundane things and hog hundreds of MB or even GBs for silly features, that are still present in enterprise versions.
The fact that they considered transmitting only keyframes speaks volumes about how inept they are. It can be a cool baseline test, but celebrating trendy choices, like Rust, and not understanding that keyframes and efficient differentials are key to achieving high video compression makes me go completely numb.
The removable nose is a power move from the engineers who built the thing. You cannot possibly believe that the animatronic contribution here is 100% contingent on a carrot?
"There is no point in research, because I do not see anything useful being mass-produced immediately after". It's like saying Gaussian elimination is wasteful because it is just doing some cool magic with numbers that don't mean anything. That could not possible be used for anything real, right?
Seriously, this is just one (but impressive) step along in a million towards not only better animatronics for entertainment. They make a very real and valuable contribution towards improving any robotic motion.
There's nothing wrong with research that doesn't make it to the public. There is definitely something wrong with making false promises to the public, who buy tickets to your park based on what you advertised could be an attractions there, which never materialized.
The important point here is that data collection and telemetry is worthless and was never about improving the experience for you as a user. The coders behind the update nag had every opportunity to do a hardware check, but as I say, big data is never used to improve anything for end users.
How did you tweak and fix it? I suffer with Windows 11 at work and everything is just so slow. Alt+Tab often gets stuck and clicking icons on the taskbar don't register about a fifth of the time.
Take a screenshot with Shift+Win+S? That's gonna take at least 10 seconds for the snipping app to even load, after which what I wanted to screenshot is probably gone.
Open a tab in Explorer? Five seconds, during which individual parts of the UI update.
Delete 50k files from some image analysis? That's gonna crash explorer.exe and take down the whole shell.
I suppose they rewrote the Windows shell in React, and every basic interaction is a major undertaking.
At home I have a 12 year old PC, with Linux and the Gnome DE. It is absurd how much faster it is, everything is snappy and instantaneous.
To me, there is nothing to fix in Windows 11 - they have failed horribly.
From my experience, a computer running that slowly is out of memory and hitting the swap file constantly. The tweaks I did are in settings. I turned off widgets, OneDrive and Ads. Also there have been comprehensive scripts for cleaning Windows 11 shared here on Hacker News if you look for them.
It is not out of memory, with 32GB it is just slow even on a fresh start.
It all goes to say that Microsoft willingly chose to use UI kits with 100x overhead compared to real functionality and rendering. It needs to die, when FOSS can make 12 year older hardware outshine 8x more expensive hardware in every single aspect, without any tweaking.
It's the very definition of insanity.
You are conflating awkward auto-generated backing fields with plain backing fields. A proper serializer handles these cases.
Yes, serialization should and must depend on names, how else to put things back together? The onus is always on the programmer to not break serialization, or provide migration.
Auto mappers sincerely need to go away. They work kind of fine initially, but at the first custom field mapping or nested field extraction, you have to invest hours into mostly complete failures of unecessary DSLs in order to something that is extremely trivial to do in basic C#, and often it is impossible to shoe horn the necessary mapping into place. Then you have to deal with package upgrades which regularly rewrite custom mapping logic, and to be sure you have to write additional tests just to hand hold.
With multi-caret editors and regex there is no need for automappers. You can write a mapping once and forget about it.
This started long before Oracle and the favouring of verbose, ritualistic boiler code was set back at Sun. James Gosling has been staunchly against overloading operators, properties and value types (almost out of spite from Microsoft's success with providing this in C#), the aftermath of which the language and run-time still struggle today and forever will. It's unfortunate that the original inventor, while a brilliant programmer himself, thought so little of others that such features were not to be included, because other programmers might mess up their use.
That's just asinine. Just because any user would like fast navigation doesn't mean privacy only matters if you know what a violation it is to ping every server in sight on user's device, with absolutely no way to prevent it.
reply