knowitall
About
- Banned
- Username
- knowitall
- Joined
- Visits
- 170
- Last Active
- Roles
- member
- Points
- 825
- Badges
- 1
- Posts
- 1,648
Reactions
-
ARM Mac Pro coming sooner rather than later, says Jean-Louis Gassee
loopless said:Anyone who works in or develops HPC software cringes at this. Sure it's likely you can make an ARM chip with the performance of high-end Xeons, but the world of HPC software is a million years away from XCode app development where you can flip a switch to build for a new architecture. There are so many bespoke libraries (e.g. Intel MKL) and years of optimization that have gone into getting HPC code to run fast on AVX Xeons.Apple is a bit-player in HPC with the Mac Pro because of their 'war' with nVIDIA ( cutting off access to the compute power of their massively parallel GPUs) - it would just sideline them even more if they went ARM.
Works fine with XCode.
-
A8, A8X: How Apple's custom silicon hit Samsung with a one-two punch
polymnia said:lkrupp said:Anilu_777 said:I seriously wish bloggers and mainstream media would tell us facts instead of click bait. “Apple is doomed” is what sells eyeballs. YouTube is just a a bad 90% of the time. “I left Apple for Android” sells. It’s Google so I don’t expect better. But mainstream journalists should report fact. And Apple fact is usually missing.
I still don’t care for the tone of his writing. I read it because there is insight in it. And I do my best to look past the adolescent barbs he peppers throughout. -
UN urges US investigation into Bezos iPhone hacking
So, the .mp4 file triggered a player exploit (buffer overrun) which allowed code to be executed that used another exploit to gain root access to the device running a daemon on it gathering and dumping information to ‘bin evil’.
This gives a bleak picture of Apples coding practices. The ‘player’ is almost certain an Apple framework allowing this exploit, which means it isn’t coded in Swift (which doesn't allow for buffer overruns and similar problems) which is bad, but it also means that legacy code isn’t checked for the most obvious and known security problems.
The root exploit, needed to get out of the sandbox and have sufficient rights to operate cross platform and share information without the user knowing it is also unforgivable. It means that the operating system isn’t screened for such things (or screened in a very bad way).
-
Apple Watch alerts Florida man of A-fib, a condition he didn't know existed
StrangeDays said:knowitall said:It seems fair to report the number of people getting a heart attack because of false ‘positives’.
What? You don't have any numbers? Because there very likely isn't any data to suggest it's happened at all? Sacre bleu!
-
A7: How Apple's custom 64-bit silicon embarrassed the industry
Journalist and bloggers were right, 64 bit per se isn’t an advantage.
They just had the transition to 64 bit of desktops which was promoted by computer companies as ‘huge’ while it turned out to be used largely as marketing to sell more computers with no subsequent speed gain to speak of and lots of incompatible software that had to be bought again.
This time journalist thought they knew there stuff and spotted another marketing campaign promoting 64bit for embedded.
The point is that ARM 32 bit and 64 bit are completely different processors using a different instruction set. So thats the difference.
Apple did this before with Intel processors, when used in 64 bit mode (intel keeps its 32 bit stuf lingering around) the processors can be seen as completely different from 32 bit, exhibiting different register sets and instructions with much more efficient context switching.