True for the CPU, but quite unfair to the Wii's ArtX GPU, which was substantially faster and more featureful than the ATI r128 in the PB G3.
787 karma · joined May 13, 2008
True for the CPU, but quite unfair to the Wii's ArtX GPU, which was substantially faster and more featureful than the ATI r128 in the PB G3.
The G400 was generally lackluster at 3d performance, so the feature didn't really get used by games.
I suspect the Anonymous author might have gotten a tip or two from a friendly Transmeta hardware or software engineer.
It was very ambitious, supporting a scripting language for what are now called smart contracts, and very complex payment schemes.
It was also a huge pain in the ass to integrate, and the user payment flow was wonky, with a redirect to multiple amazon branded pages to log in to amazon, then redirect back to finish the transaction.
I've not used stripe, but people who have tell me it is super easy to integrate.
On a smaller scale, all jet airliners have a RAT (Ram Air Turbine), which is just a propeller that drops into the airstream if both engines fail. It provides hydraulic pressure and electrical power during an emergency.
Most thick client update mechanisms make this more difficult (but certainly not impossible) thus greatly increasing the risks of embedded malware being detected.
Signal, for example, is reproducibly built, so you can diff the source of each new update and then verify that you get the same binary. This gives you very good assurance that your audit of those diffs is valid to the binary on your phone.
It is possible that IBM tried to squeeze Apple, but given that IBM's interest in Transitive was for enterprise server migration, I suspect it is more likely that Apple got tired of paying whatever small royalty they'd contracted for with Transitive, and decided enough people had fully migrated to native x86 apps that they wouldn't alienate too many customers.
They licensed Transitive's retargettable binary translator, and renamed it Rosetta; very Apple.
It was originally a startup, but had been bought by IBM by the time Apple was interested.
I'm here for 9 months, normally live in the bay area. So trying to improve my Spanish from bad to decent.
Also wrote a script to help me work on my slow 6 year old laptop here, and stream the changes to my workstation stashed in a friend's crawlspace in San Francisco, so I can run builds/tests/etc there: https://github.com/nolanl/rp
Might be useful for other folks in similar situations.
Some switches can do PFC for untagged packets. They classify based on DSCP, and map that to a PFC priority. I've never used that though.
There are newer editions (2004, 2014) of the McKusick et al book, s/4.4 BSD/FreeBSD/1 for the updated title. If you don't want any taint of knowledge of fast flash drives, maybe go with the 2004 edition.
None of this FUD is true. None of the information you listed is collected or stored by Signal. You can verify this yourself by looking at the various government warrants and subpoenas, and Signal's responses: https://signal.org/bigbrother/
If you have the energy flow view up on the screen, you can see the power going from the motor/generator to the battery when you release the gas.
I don't think that is true. In the simplest case, you could modify the #UD handler to notice when the fault is caused by an AVX512 instruction running on an E-core, and then simply and pin the process to the P-cores, migrate the process, and continue. All existing scheduler functionality.
> The only thing that is really affected is the code that could use AVX512_FP16, but I doubt there's a lot of it outside of Intel.
AVX512 is a lot more than just extending the vector width, and that extended functionality can be very useful for quickly emulating other CPU's vector instruction sets.
Old OS versions continue to work fine, and newer OS versions can opt into the new world and benefit.
But location aside, there is very little of the city that is more than 20 minutes by bike away. I used to commute to Palo Alto, and then later Sunnyvale, both were less than 30 minutes. If I made the mistake of trying to drive to work during rush hour, it took about as long.