1,199 karma · joined September 19, 2018
Although on Linux side. As far as i remembered, it's up to how kernel driver developer to map the device input into different class. It would be up to valve to decide what to do in this case.
There is actually a example of such situation. Mozilla removed adobe pdf plugin support a long time ago and replaced it with pdf.js. It's still a slight performance regression for very giant pdf. But it is enough for most use case.
But the bottom line is "it's actually worth to do it because people are using it". They won't actively support a feature that little people use because they don't have the people to support it.
And, no. Although forge does not encourage you to use it. It also supports mixin like direct modification. It's just less polished than mixin(requires more knowledge to java Bytecode)
It's unrealistic to ask mojang to make an abstraction that you can actually change everything in the core without direct modification (let alone how do mojang know what part need to be abstracted?)
In any case, whether it is real person or AI do the task for you. It's the user who submitted the result to be responsible for it. Why do people think it's bad to do this with real human and suddenly be OK to do this with an AI?
I guess Microsoft won't want to deal with the license issue of publishing the loader part.
Besides these, the service worker debugger never work on my iphone device since like two major version ago.(It did not show up in the safari menu) There is no way to use it as a developer even I want to (let alone the devtool crashes and disconnects frequently)
Write a page on chrome, works 90% on Firefox. But will likely works 10% on safari. Supports safari literally means support another browser (by workaround all its bugs).
If it even does.
Like, why would you even buy a album and add it to your collection if you have no idea what it is?
I won't say most react apps performs like this. But it's what you will get if you ship a big react app without optimization at all.
Other framework mostly have a much saner default (for example, component without argument change does not re-render). So it will work well (not best though) even in large scale. But in react they are all opt-in.
Abuse Lodash or Underscore everywhere means the code is not readable unless you know what is every used lodash function intended to do. Combing with weak type and undocumented business logic (and api types), it's a true nightmare experience to work with.
It's probably irrelevant in a personal project. But it's a headache if you are collaborating.
Sometimes it got even worse that original user don't know the exact specification of the utility function either. And the code works just by pure luck. (something like, the method work if all keys are numeric) It will give you a hard time to troubleshoot the problem if it happens.
This is for format only and a lossy conversion.
Line break or whatever finer behaviour isn't preserved perfectly.
Or probably any conversion between different office version is a lossy conversion.
They (microsoft) truly don't know how their format behaves exactly at any time I believe.
Even office for mac or office for web behaves slightly different.
I don't believe they have a true spec (A pixel perfect one) about word document. Or they should use it on their office mac or office web first.
The office relies on behaviour in windows itself "a lot". Even office mac or office web they made themselves isn't a 1:1 replica of the office on windows.
Let alone describe it as a standard.
"this behaviour is as seen in Word 95" sounds sloppy, but it is indeed the closest they can get.
Or what else can you do? You can't just also ship a installation media of word 95 and windows into the ISO standard, right?
Steamdeck with Windows 11 and SteamOS is a whole different experience. When running SteamOS and doing web surfing, the fan don't even really spin at all. But when running windows 11 and do the exact same thing, it just spins all the time and becomes kinda hot.
(Also probably due to it is a tablet, so it have a reasonable fast storage instead of hdds like notebooks in that era)