It's generally not as heavy because the layer is just reinterpreting API calls while the user code still runs natively. On a browser running JavaScript, it's using an interpreter for every line of code. Depending on the specifics, it could be doing string processing for each operation, though it probably only does the string processing once and converts the code into something it can work with faster.
Like if you want to add two variables, a compiled program would do it in about 4 cpu instructions, assuming it needed to be loaded from memory and saved back to memory. Or maybe 7 if everything had a layer of indirection (eg pointers).
A scripting language needs to parse the statement (which alone will take on the order of dozens of cpu instructions, if not hundreds), then look up the variables in a map, which can be fast but not as fast as a memory load or two, then do the add, and store the result with another map lookup. Not to mention all of the type stuff being handled at run time, like figuring out what the variables are and what an add of those types even means, plus any necessary conversions. I understand that JavaScript can be compiled and that TypeScript is a thing, but the compiled code still needs to reproduce all of the same behaviour the scripting language does, so generic functions can still be more complex to handle calling and return conventions and making sure they work on all possible types that can be provided. And if they are using eval statements (or whatever it is to process dynamically generated code), then it's back to string processing.
Plus the UI itself is all html and css, and the JavaScript interacts with it as such, limiting optimizations that would convert it into another format for faster processing. The GPU doesn't render HTML and CSS directly; it all needs to be processed for each update.
For D3D to Vulkan, the GPU handles the repetitive work while any data that needs to be converted only needs to happen once per pass through the API (eg at load time).
That browser render stuff can all be done pretty quickly on today's hardware, so it's generally usable, but native stuff is still orders of magnitude faster and the way proton works is much closer to native than a browser.
Yeah but that chart accounted for deaths per distance driven and the bit about speed enforcement and the autobahn was to challenge your assumption that people in the US drive faster on average because people here speed so much they have to be exceeding the limit by a good amount before the cops even blink at them.
Canada and Australia, the only other countries in the OP, are both below the US.
As for speed, at least where I am in Canada, they don't even bother enforcing the limit until you're at least 20% over it. And Germany, famous for its highway without a speed limit, is still lower than all three countries listed.
Whatever is going on in the US to cause a higher amount of car fatalities isn't just distance driven or speed.
Proton proves that you don't need to run on a web browser for cross platform compatibility. Turing-complete platforms are equivalent in their capabilities, it's just a matter of adding a translation layer that doesn't need to be as heavy as a browser DOM (at least for going between windows and Linux on x64).
I'm never buying another Logitech device again because that problem that happened with my G7 back in the 00s still happened with my G900 in the 20s.
With my G7, I'd open it up when it started happening, and open up the switch to re-bend the metal piece to give it some spring back. Kept doing this until one day the plastic button that presses down on that metal part fell on carpet and was gone forever.
With my G900, I said fuck it and just bought some better mouse button switches and replaced the left mouse button. Was actually kinda glad I needed to because the battery had become a danger pillow so I replaced that, too.
But with the button issue existing for so long and being fixed by a part that cost a trivial amount compared to what I paid in the first place, you can't convince me that Logitech isn't deliberately using switches that fail quickly to drive up demand for mice.
From a programming pov, a definition of AI could be an algorithm or construct that can solve problems or perform tasks without the programmer specifically solving that problem or programming the steps of the task but rather building something that can figure it out on its own.
Though a lot of game AIs don't fit that description.
That's not quite accurate because the two numbers have a relationship with each other. i^2 = - 1, so any time you square a complex number or multiply two complex numbers, some of the value jumps from one dimension to the other.
It's like a vector, where sure, certain operations can be treated as if the dimensions of the vector are distinct, like a translation or scale. But other operations can have one dimension affecting the other, like rotation.
I did some research about it and it sounds like what I need is a dongle that isolates the charger and audio grounds from each other. Though a ferrite bead might help with the charge whine I get on one of my indoor chargers.
Was worried for a sec that you were going to say you got back to your hotel only to realize it wasn't your 4yo. Would have been potentially traumatizing for everyone involved that noticed before you quietly returned the kid hoping no one else did notice and that your own kid didn't drown in the meantime.
My dongle that supports charging and analog audio for my car has a whine that changes pitch with the motor speed (guessing it's very sensitive to the voltage or frequency of the alternator or something). Though at least it's low enough that it's almost unnoticeable when actual audio is playing.
It also requires the phone be unlocked to start sending audio through the USB interface. And maybe about 10% of the time whe I get it all set up and music/podcast playing, the motion of hitting the lock button on my phone to turn the screen off also bumps the usb port enough for it to briefly disconnect, which stops my audio and forces me to unlock my phone again to get it playing through the cable.
The phone needs to have a DAC anyways if it wants to drive its speakers. I could live with a smaller analog jack, but hate having to use a separate device with its own DAC that is probably way cheaper than the one already in my phone plus they probably don't even isolate the audio signal from the charging signal because the main selling point is just the ability to play audio and charge at the same time.
Oh wow, if steam is still 32 bit, forget the offshoots, fedora itself won't be worth using. I'm on fedora but if I can't run steam, then I'm finding a new distro.
On the flip side, what's the reason they want to drop 32-bit support, given steam depends on it, which they should understand means it's integral to the size of their current userbase?
Danish millennials and gen xers who work in retirement or old age support roles should change careers. And zers and alphas getting into it should consider hiatuses.
Monkey's paw curls. Now abortions are legal and forced.