asdasd

elijahg said:

StrangeDays said:

elijahg said:

I've said this before, but all this closed source incompatibility is chillingly reminiscent of Apple of the mid-90's and Microsoft in the late 90's and into the Ballmer years. Since Sat Nad has taken over, MS have had a much more open approach and they are being lauded for it, with respect for MS steadily increasing. Apple on the other hand is going backwards compared to the huge amount of open-sourcing and increased compatibility after Jobs' return in the early years of OS X, causing respect to decrease. It really is quite concerning.

Jobs as champion of open systems? Interesting way to rewrite history. 

Sorry but no, while Apple has at times leveraged and contributed to open source projects, it has never been about open systems. The very nature of Mac and the ecosystem is a walled garden. That hasn’t changed.

Considering he open sourced pretty much all the APIs on NextStep to become OpenStep, looks like you might need to gen up on your history a bit. Oh and what about Webkit? What about Bonjour? What about CUPS? Swift? IOKit? What about contributions to Apache? To OpenSSL? To Autoconf? To Samba? To X11? LLVM? BSD? Clang? OpenGL? Might as well get your head out of Apple's ass at the same time. Walled garden doesn't mean you have to use incompatible standards and APIs. Look where that got Apple in the 90's.

elijahg said:

Schools in the west seem to try and stifle inquisitive kids; kids who ask questions that aren't in line with the syllabus (but are still related to the subject at hand) are told to stop asking questions and answer the contrived question that they've been set that is usually full of holes. Especially in the UK with the ingrained socialism in schools, teachers try and treat all the kids as having equal intelligence, which they do not. And therefore most of the time it just ends up with the lowest common denominator setting the pace of the class, resulting in a disproportionate fraction of time spent on the kid who's probably going to end up as a builder or rubbish collector anyway (valuable jobs don't get me wrong, but not skilled), so the smart kids get bored, learn much less than their potential and are not stimulated. Ultimately reducing the quality of the students.

dysamoria said:

I find it bizarre how nonchalant people are about this, brushing off how much of a nightmare it will be for people using mission-critical specialist tools.

The past transitions were worked out over a very long time because developers wouldn’t move. Companies wouldn’t move. Many software tools have disappeared forever as a result. The stuff that was updated took effing FOREVER, bringing long-term legacy with them that took even longer to eliminate.

There were benefits, such as ports from WinTel, but this time around, that will be inverted: all the specialty tools that were ported to Mac OS because it didn’t need an entire low-level rewrite and optimization for a different CPU... you can expect to lose A LOT MORE this time around. 

dewme said:

This bug should have been caught at the Unit Test level with automated Fuzz Testing.  

The testing required to catch these kinds of bugs lends itself extremely well to test automation.

Embarrassing, but it still happens. Should never happen again.

lkrupp said:

knowitall said:

MacBook ARM sounds logical.

Maybe, but I’n guessing it will run some modified version of iOS and may only run iOS apps. Unless, of course, Apple comes up with a fast and reliable framework (like Rosetta) to emulate X86 code. Will developers have to create universal binaries again like they did for the PowerPC/Intel move.?