Their motivation for building A-series somehow invalidates the fact that it is industry-leading?
We haven't seen a comparison of iOS running on other modern ARM chips, or of Android running on an A-series. We don't actually know that it's industry-leading; in fact, depending on how you define industry-leading (usually performance, which is what we don't have a valid benchmark for, or sales), it's far from industry-leading.
Windows Hello was first, and took longer to crack (if it's even been cracked; last time I checked, well after FaceID had been, it hadn't been).
the Apple pencil
Adonit made active stylii for iOS long before Apple themselves did, and they work with all iOS devices, not just the iPad Pro. In fact, the two I have work better than the Apple Pencil I gave to a friend who bought an iPad Pro recently; that's why I gave it away.
Trumotion
The feature of LG TVs that Apple had nothing to do with? Or did you mean TrueMotion, which is an app not developed by Apple that can also be found on Android? Google turns up nothing relevant.
A-series chips
I'll think about granting that one, though they're just ARM modules assembled in interesting ways. I'm not sure one lego building is really any more interesting than another; certainly not enough so that I's say it "adds something special".
HomePod
The only something special Apple added there was the price and a white ring on your countertop.
I'm not sure that you even can run OpenGL on Windows without installing extra drivers these days.
Okay, so you admit you have no clue what you're talking about, then?
I'd respectfully disagree on backwards compatibility
I'll grant you they're not perfect in that regard, but the actual win32 API has been more or less stable over the years. It was a design goal and they've don a damn good job of sticking to it. Regarding some of the libraries you're referring to (I'm guessing MFC is one of them), that's not really an issue at the OS level, and you actually still can find those libraries, though I'll admit it's a bit of a pain in the ass to do so.
You do realize that OSX 10.7 supports 3.1, and 10.9 supports 4.1?
An oversight on my part. On further review, perhaps I should have scrolled down a few more pages.
But besides OpenGL support, Apple still has the best overall GUI of any *nix I've seen.
Ill grant you that; there's a reason I'm replying on a MacBook Pro right now.
and it's much more consistent in overall experience as compared to Windows
Here's where we disagree. Windows has consistently been shit since 1995, while Mac OS only started its decline about 7 years ago.;)
which last time I looked still had NT 3.1/3.5 and 4.0 based fixed size non-scaleable dialogs for some of its system controls
There's really nothing wrong with that, provided the whole thing fits on the screen. Since you mention both "fixed size" and "non-scaleable", I'm not sure if you're meaning to say the same thing two different ways, or you're referring to the lack of DPI scaling for hi-res displays (as you then go on to talk about that), but you might want to look again. I don't know when they added it, as I was without access to my Windows PC for a couple of months, but there is now an option to force scaling of non-DPI-aware apps, windows, and controls.
That said, if your 4K monitor is small enough that you need scaling, and it's not a laptop display, you're doing it wrong.;)
Considering that FaceID has been successfully fooled with a mask, I'm confident you don't have to go quite that far to get around it. Maybe stand on the corner with the phone and a photo of the owner and offer anyone with similar facial features to your target $5 to try to unlock it and $100 if successful. You get 5 attempts, and we've already seen that siblings and other relatives can, quite often, unlock each other's iPhones.
Of course, that's if it doesn't unlock for the corpse. Have you tried the corpse method? I haven't but I have a hunch it would work quite well, actually.
Another option, and I'm not sure why I didn't think of it earlier, would be to put a pair of UV blocking sunglasses on the target. You should be able to find a pair that fits loosely enough to not disturb their slumber, yet tight enough to stay in place. FaceID does work if your eyes are obscured by sunglasses, and it can't very well check whether they're open under those conditions.
Both of those options are cheaper and faster than sending the phone overseas, or using GrayKey, and you can always fall back to these if the above should fail.
Oh, you mean like Windows has done for DECADES with DirectX?
No, nothing at all like that, actually. Windows has always given you a choice of graphics APIs, for as long as multiple APIs have existed on the platform. If you chose DirectX and vendor lock-in, that was entirely your choice; OpenGL has always been an option for as long as it's existed and, because MS is obsessed with backward compatibility[1], it's all but guaranteed to remain a choice for as long as Windows exists. What Apple is doing is forcing people's hand; they deprecated OpenGL on their platform. To a developer, deprecated means "not suitable for new projects", for a multitude of reasons. First of all, there's the impending lack of vendor support[2], followed by complete removal of the feature.
Unlike Apple, Microsoft recognizes that there are a multitude of older games that people play on their platform, and that there are other platforms[3] people can switch to for their retro gaming needs. Because of this, Microsoft wouldn't do something so stupid as break those older games, some of which people have invested a lot of time and money into. Apple, on the other hand, is going to break games as recent as Sims 4 (2014), which is probably the most popular AAA game on the platform and still has new official expansions being released by EA to this very day. That's going to make a lot of users switch to Windows. That, and WoW, of course.
Lazy Developers, that don't know how to code using a standard Model-View-Controller method, are the ones that will continue to have "porting" problems, you mean...
Really? That's the argument you're going to make with regard to a very performance-oriented segment of the industry? Each layer of abstraction has a performance cost, and wrapping your graphics stack sufficiently enough such that completely ripping it out and replacing it with something else doesn't incur any maintenance cost loses you more than a handful of FPS.
While that might be acceptable for something like a CAD application, you're almost guaranteed to not see it in games; and not due to laziness. Even where it is done -- and there are a number of games that support multiple graphics engines, take Fortnite as an example -- each graphics stack still needs to be maintained as new versions of the API are released.
In case you haven't noticed, graphics APIs are not small simple widgets, they're vastly complex machines, and each version of a graphics API has its own quirks[4], which you have to account for for each version of the API you support. Another thing you may have missed is that not everyone updates at the same time; you may have a number of users on a version of their OS that only supports v2.1 of an API, while everyone else is on a version of their OS that supports v4.4, and your graphics stack needs to handle that, and every version in between. I chose v2.1 and v4.4 for a reason, by the way; can you figure out why?
Let's see what Siemens PLM does with its NX CAD suite for Mac...
Yes. Let's.
[1] Yes, you'll find examples where they've broken things in the past. It's literally impossible for them to not have broken something while making sweeping API changes, but they've historically put in the effort to break as little as possible while still progressing. Now, I praise MS about as often as I praise Apple, they're both fuck-ups after all, but MS has done a damn good job with backward compatibility.
[2] Which really isn't impending when we're talking about Apple, as they're stuck on v2.1, which was
That's all well and good on iDevices, where having a different graphic API for every platform is, and has always been, the norm. On the desktop, we've long been able to support all major platforms with a single graphics stack; Apple is breaking that for Mac OS, and it is not going to end well for them.
it's factually untrue that Apple has no 3D library
It's also factually untrue that anyone here claimed otherwise. What was claimed, which you even quoted, is that Apple has no credible business case for their own 3D library.
Yes, because all of your logic and graphics stack could easily port previously; it was relatively cheap to support those users. Now, supporting Mac users requires maintaining an additional graphics stack and the supporting logic for that. Much more expensive.
Yes, because conducting a thorough investigation through mere observation of public activity is such a violation of your rights. Go ahead, use that line when you're being tried for a crime you actually committed, let me know how it works.
Your honor, by simply investigating me for this crime, the police violated my 4th amendment rights.
See how fast you get laughed out of court. The 4th amendment protects against unreasonable search ans seizure, not against mere observation, investigation, and recordkeeping. As for the 5th and 6th, nobody is being prosecuted here, so they really don't apply.
If Intel were smart, they'd have specified that the on-die VRMs were secondary and required that the motherboard always provide functional VRMs. For several reasons, not the least of which is that VRMs get HOT HOT HOT. On every desktop motherboard I've ever had, the VRMs had more surface area than the CPU die, precisely for this reason.
It's just using the dedicated video decoding/encoding hardware
Okay, well, the GPU essentially captures the stream as it renders it, and encoding is generally considered part of the capture process. In short, your comment distills to "It's not using dedicated hardware, it's using dedicated hardware." This is what happens when you try to be pedantic and fall flat on your face.
I'm not going to get into whether I believe Trump is guilty of this, that, or the other thing, but I really do need to point out your ignorance. The conviction you're asking for is precisely the upholding the AC above you is calling for.
Slashdot Mirror
Their motivation for building A-series somehow invalidates the fact that it is industry-leading?
We haven't seen a comparison of iOS running on other modern ARM chips, or of Android running on an A-series. We don't actually know that it's industry-leading; in fact, depending on how you define industry-leading (usually performance, which is what we don't have a valid benchmark for, or sales), it's far from industry-leading.
Well sure, if you ignore the FaceID IR camera
Windows Hello was first, and took longer to crack (if it's even been cracked; last time I checked, well after FaceID had been, it hadn't been).
the Apple pencil
Adonit made active stylii for iOS long before Apple themselves did, and they work with all iOS devices, not just the iPad Pro. In fact, the two I have work better than the Apple Pencil I gave to a friend who bought an iPad Pro recently; that's why I gave it away.
Trumotion
The feature of LG TVs that Apple had nothing to do with? Or did you mean TrueMotion, which is an app not developed by Apple that can also be found on Android? Google turns up nothing relevant.
A-series chips
I'll think about granting that one, though they're just ARM modules assembled in interesting ways. I'm not sure one lego building is really any more interesting than another; certainly not enough so that I's say it "adds something special".
HomePod
The only something special Apple added there was the price and a white ring on your countertop.
Got any more of those? This is fun.
But still no room for an SD card? Hmm...
I'm not sure that you even can run OpenGL on Windows without installing extra drivers these days.
Okay, so you admit you have no clue what you're talking about, then?
I'd respectfully disagree on backwards compatibility
I'll grant you they're not perfect in that regard, but the actual win32 API has been more or less stable over the years. It was a design goal and they've don a damn good job of sticking to it. Regarding some of the libraries you're referring to (I'm guessing MFC is one of them), that's not really an issue at the OS level, and you actually still can find those libraries, though I'll admit it's a bit of a pain in the ass to do so.
You do realize that OSX 10.7 supports 3.1, and 10.9 supports 4.1?
An oversight on my part. On further review, perhaps I should have scrolled down a few more pages.
But besides OpenGL support, Apple still has the best overall GUI of any *nix I've seen.
Ill grant you that; there's a reason I'm replying on a MacBook Pro right now.
and it's much more consistent in overall experience as compared to Windows
Here's where we disagree. Windows has consistently been shit since 1995, while Mac OS only started its decline about 7 years ago. ;)
which last time I looked still had NT 3.1/3.5 and 4.0 based fixed size non-scaleable dialogs for some of its system controls
There's really nothing wrong with that, provided the whole thing fits on the screen. Since you mention both "fixed size" and "non-scaleable", I'm not sure if you're meaning to say the same thing two different ways, or you're referring to the lack of DPI scaling for hi-res displays (as you then go on to talk about that), but you might want to look again. I don't know when they added it, as I was without access to my Windows PC for a couple of months, but there is now an option to force scaling of non-DPI-aware apps, windows, and controls.
;)
That said, if your 4K monitor is small enough that you need scaling, and it's not a laptop display, you're doing it wrong.
Considering that FaceID has been successfully fooled with a mask, I'm confident you don't have to go quite that far to get around it. Maybe stand on the corner with the phone and a photo of the owner and offer anyone with similar facial features to your target $5 to try to unlock it and $100 if successful. You get 5 attempts, and we've already seen that siblings and other relatives can, quite often, unlock each other's iPhones.
Of course, that's if it doesn't unlock for the corpse. Have you tried the corpse method? I haven't but I have a hunch it would work quite well, actually.
Another option, and I'm not sure why I didn't think of it earlier, would be to put a pair of UV blocking sunglasses on the target. You should be able to find a pair that fits loosely enough to not disturb their slumber, yet tight enough to stay in place. FaceID does work if your eyes are obscured by sunglasses, and it can't very well check whether they're open under those conditions.
Both of those options are cheaper and faster than sending the phone overseas, or using GrayKey, and you can always fall back to these if the above should fail.
Oh, you mean like Windows has done for DECADES with DirectX?
No, nothing at all like that, actually. Windows has always given you a choice of graphics APIs, for as long as multiple APIs have existed on the platform. If you chose DirectX and vendor lock-in, that was entirely your choice; OpenGL has always been an option for as long as it's existed and, because MS is obsessed with backward compatibility[1], it's all but guaranteed to remain a choice for as long as Windows exists. What Apple is doing is forcing people's hand; they deprecated OpenGL on their platform. To a developer, deprecated means "not suitable for new projects", for a multitude of reasons. First of all, there's the impending lack of vendor support[2], followed by complete removal of the feature.
Unlike Apple, Microsoft recognizes that there are a multitude of older games that people play on their platform, and that there are other platforms[3] people can switch to for their retro gaming needs. Because of this, Microsoft wouldn't do something so stupid as break those older games, some of which people have invested a lot of time and money into. Apple, on the other hand, is going to break games as recent as Sims 4 (2014), which is probably the most popular AAA game on the platform and still has new official expansions being released by EA to this very day. That's going to make a lot of users switch to Windows. That, and WoW, of course.
Lazy Developers, that don't know how to code using a standard Model-View-Controller method, are the ones that will continue to have "porting" problems, you mean...
Really? That's the argument you're going to make with regard to a very performance-oriented segment of the industry? Each layer of abstraction has a performance cost, and wrapping your graphics stack sufficiently enough such that completely ripping it out and replacing it with something else doesn't incur any maintenance cost loses you more than a handful of FPS.
While that might be acceptable for something like a CAD application, you're almost guaranteed to not see it in games; and not due to laziness. Even where it is done -- and there are a number of games that support multiple graphics engines, take Fortnite as an example -- each graphics stack still needs to be maintained as new versions of the API are released.
In case you haven't noticed, graphics APIs are not small simple widgets, they're vastly complex machines, and each version of a graphics API has its own quirks[4], which you have to account for for each version of the API you support. Another thing you may have missed is that not everyone updates at the same time; you may have a number of users on a version of their OS that only supports v2.1 of an API, while everyone else is on a version of their OS that supports v4.4, and your graphics stack needs to handle that, and every version in between. I chose v2.1 and v4.4 for a reason, by the way; can you figure out why?
Let's see what Siemens PLM does with its NX CAD suite for Mac...
Yes. Let's.
[1] Yes, you'll find examples where they've broken things in the past. It's literally impossible for them to not have broken something while making sweeping API changes, but they've historically put in the effort to break as little as possible while still progressing. Now, I praise MS about as often as I praise Apple, they're both fuck-ups after all, but MS has done a damn good job with backward compatibility.
[2] Which really isn't impending when we're talking about Apple, as they're stuck on v2.1, which was
Besides which, if you have the PC in question, just pull the drive and crack it elsewhere.
And if you have the iOS device in question?
Considering that masks don't have heartbeats and FaceID has been fooled with a mask...............
Be surprised.
"Knock them unconscious" will most likely end up killing them
Unconscious? Dead? Who cares, so long as the body's still warm enough for the IR scanner and the eyes can be propped open?
That's all well and good on iDevices, where having a different graphic API for every platform is, and has always been, the norm. On the desktop, we've long been able to support all major platforms with a single graphics stack; Apple is breaking that for Mac OS, and it is not going to end well for them.
it's factually untrue that Apple has no 3D library
It's also factually untrue that anyone here claimed otherwise. What was claimed, which you even quoted, is that Apple has no credible business case for their own 3D library.
but Apple isn't in that game
To the detriment and ultimate demise of Metal, along with their viability as a CAD, graphics, and video editing workstation vendor.
Yes, because all of your logic and graphics stack could easily port previously; it was relatively cheap to support those users. Now, supporting Mac users requires maintaining an additional graphics stack and the supporting logic for that. Much more expensive.
only a total moron would think that boning developers in this fashion for no good reason is a good idea
I wouldn't put it past ol' Timmy.
Your honor, by simply investigating me for this crime, the police violated my 4th amendment rights.
See how fast you get laughed out of court. The 4th amendment protects against unreasonable search ans seizure, not against mere observation, investigation, and recordkeeping. As for the 5th and 6th, nobody is being prosecuted here, so they really don't apply.
It was PolygamousRanchKid who said that was long tern; not me. Try again?
Yes, and presidential terms last 4 years, with a limit of 2 terms. That's 8 years, it's been (rounded up) 2.
8 - 2 = ??
If Intel were smart, they'd have specified that the on-die VRMs were secondary and required that the motherboard always provide functional VRMs. For several reasons, not the least of which is that VRMs get HOT HOT HOT. On every desktop motherboard I've ever had, the VRMs had more surface area than the CPU die, precisely for this reason.
The thing is that the hyperthreading doesn't cost much chip area.
The extra cache it needs does, though.
It's not actually dedicated capture hardware.
It's just using the dedicated video decoding/encoding hardware
Okay, well, the GPU essentially captures the stream as it renders it, and encoding is generally considered part of the capture process. In short, your comment distills to "It's not using dedicated hardware, it's using dedicated hardware." This is what happens when you try to be pedantic and fall flat on your face.
Of course, the cells will be larger than 192 bits; I only used that number as it's what they've achieved at this moment.
For reference, parallelization is the same trick used by today's fastest flash-based SSDs. Are those the size of a house?
Just parallel a bunch of 192 bit cells. Access speed issue overcome.
Not sure if trolling or lacking reading comprehension...
Well, it looks like you just have to sit and wait for 30 more months to disprove his point. Good on you for correcting him to no real end, though.
I'm not going to get into whether I believe Trump is guilty of this, that, or the other thing, but I really do need to point out your ignorance. The conviction you're asking for is precisely the upholding the AC above you is calling for.