its manufactured on a smaller node so probably has more leeway for higher freq on all core loads.
I’d also be weary of single core scores,Geekbench is known to be favoring specialized instruction sets like AVX or encryption extensions more and more as the version number progresses. Though I don’t know if GB6 is also like this I wouldn’t be surprised it it was caused by it.
The problem with this is Microsoft foresaw it and pushed (bribed?) OOXML through ISO and now there's no standing on "forcing" an open standard without OOXML being one.
how about requiring the format to actually be specified? Isn't ooxml filled with tons of chunks saying "and then this will behave like word 95 did" and not specify what tat is
It sure did! and because those products aren't sold anymore, it's impossible to legally implement the standardc as even with the "full" spec, you need to reverse engineer stuff from unavailable software
Every version of Office is still easily found online... and even if you did want to go the truly legal route for some reason for 30+ year old software, there are still many physical copies left in the world already owned by existing users and developers, or readily available on ebay etc... so I don't think it's fair at all to say it is "unavailable" or "impossible", unless you mean purely from a "buy this new from Amazon or CDW right now" type thing.
If you want to move the bar to quality for your strawman, then libjpeg-turbo is not even close in image quality to plenty of encoders, such as jpegli crush it. For compression size it also loses to modern libs. There is no metric that libjepg-turbo wins at nowadays, not even speed.
Then, if you care to learn, there are extremely high quality, lkely far beyond old software like libjpeg-turbo, use in DoD projects, satellites, medical imaging systems, commercial cameras systems, and plenty of companies that sell such chips and IP to embed in ones own ASIC. There is zero technical problem taking an opensource project, turning that exact code into an ASIC or VHDL one can put into any ASIC, an so the best ideas are reused in hardware all the time.
Alma Technologies, CAST, intoPIX all sell such cores that are integrated throughout the industry, embedded everywhere, and can be bought with an ever improving host of features.
When it works it's amazing. Files are saved as is with date time stamp appended, so all do is to undo that. Great if you trashed something a while back and always quicker than getting it back via github. Haven't found anything using a similar approach - just copy the change to the mirror. if the file is moved, just make a copy of the changed file, if it is deleted, who cares, just ignore from then on. simple. Everyone else is being way too clever, compression and exact deltas history, etc
One recent issue required cloning the user account to get file history working. Just would not work with that account while any new account worked fine.
Current status is broken - the last two security updates report file history as broken. Git hub handles code ok, but for all the other stuff on windows file history was the way to go. Now cumbersome incremental backups.
Interesting, but isn't Wayland the future? Edit: I see it links to alternatives to that, like ydotool and dotool. But these do not seem to be active, well documented projects. Far away from the usability of AutoHotkey.
It may be 20 less but still hundreds. I'll never understand the LTSC advocacy, it is still the same thing except they mopped up the most disgusting looking liquid seeping out to the floor but didn't touch the huge turd sitting in the middle.
reply