Slashdot Mirror


Apple Expected To Move Mac Line To Custom ARM-Based Chips Starting Next Year, Says Report (axios.com)

Developers and Intel officials have told Axios that Apple is expected to move its Mac line to custom ARM-based chips as soon as next year. "Bloomberg offered a bit more specificity on things in a report on Wednesday, saying that the first ARM-based Macs could come in 2020, with plans to offer developers a way to write a single app that can run across iPhones, iPads and Macs by 2021," reports Axios. "The first hints of the effort came last year when Apple offered a sneak peek at its plan to make it easier for developers to bring iPad apps to the Mac." From the report: If anything, the Bloomberg timeline suggests that Intel might actually have more Mac business in 2020 than some had been expecting. The key question is not the timeline but just how smoothly Apple is able to make the shift. For developers, it will likely mean an awkward period of time supporting new and classic Macs as well as new and old-style Mac apps. The move could give developers a way to reach a bigger market with a single app, although the transition could be bumpy. For Intel, of course, it would mean the loss of a significant customer, albeit probably not a huge hit to its bottom line.

208 of 356 comments (clear)

  1. Great! by DontBeAMoran · · Score: 4, Insightful

    If they're going to make new laptops, maybe the freaking morans will fix the keyboards at the same time.

    --
    #DeleteFacebook
    1. Re:Great! by Hotelkrakow · · Score: 1

      Should be obvious...

    2. Re: Great! by shmlco · · Score: 3, Insightful

      "arm is such a piece of shit for actual performance. this will KILL mac for anything actually useful."

      Yeah, that's why the A12 chip on the iPad Pro benchmarks 85% faster than all of the laptops on the market today.

      And you've seen, of course, the real-time 4K video editing/rendering apps on the iPad.

      Personally, I can't wait to see what Apple's A-series chips can do when not limited by a phone or tablets power and thermal constraints.

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    3. Re:Great! by thegarbz · · Score: 1

      If they're going to make new laptops, maybe the freaking morans will fix the keyboards at the same time.

      They will do something to get you to stop complaining. Notice how no one mentions the horrible touch bar anymore? Well not to worry, but making the next Mac completely unusable you won't ever worry about sticky keys again!

    4. Re: Great! by WorBlux · · Score: 4, Insightful

      Not necessarily. Windows has an ARM version. Though more than likely they'll ditch POSIX support and go full iOS across the line.

    5. Re: Great! by StikyPad · · Score: 1

      iOS is Posix. Itâ(TM)s the same OS as MacOS, just with mobile frameworks and ARM instead of x86.

    6. Re: Great! by WorBlux · · Score: 1

      Nobody does 4k on the CPU. This was hardware acceleration in the GPU, with a company they worked very closely with to get the acceleration working flawlessly for one specific video codec format and setting. Going outside the presets likely won't end well.

      And there's a pretty long history of companies gaming benchmarks. We know geek-bench hits a lot of paths that are hardware accelerated, and memory/disk sensitive. And this is even before going into the fact iOS is finely tuned to the hardware, and the App store likely recieved the geekbench app in an IR that can be precisely optimized for the hardware.

      It's not doubt a good mobile chip, but a workstation chip? I kind of doublt it.

    7. Re: Great! by WorBlux · · Score: 1

      So where's /bin/sh?

      There isn't full support, and even if there were, it's irrelevant as application developers aren't allowed to get at it. Everything is going through the constrained frameworks.

    8. Re: Great! by sodul · · Score: 1

      Actually i think the touchbar would be better if it had the haptic engine that the trackpad uses, it really works well for the trackpad and I think it could Work for typing. I guess they kept that âinnovationâ(TM) for a future release since releasing innovations over time is good for business.

    9. Re: Great! by 93+Escort+Wagon · · Score: 4, Informative

      While I worry about artificial constraints as well... if you’d ever worked with a jail broken iPhone or iPad, you’d know there’s basically a standard bash shell under there. You can ssh into the things by installing the openssh daemon. Heck, people have even run apache and nginx on them.

      --
      #DeleteChrome
    10. Re: Great! by Anonymous Coward · · Score: 1

      Who gives a rat's ass about how fast the ARM chip is on the iPad? All that power is locked up behind iOS, and I can't do anything to take advantage of it, like actually use a UNIX userland where I can do tasks and have a useful workflow... and no, doing gestures or smacking the home button and swiping between apps isn't workflow compared to having multiple displays and different tasks on each.

    11. Re: Great! by spire3661 · · Score: 1, Flamebait

      OK, im going ot step on you now. The A12 is a Ferrari engine bolted to a Corolla frame. It doesnt matter how fast it is when its running a TOY OS. You have all this power and cant bring it to bear. You fundamentally misunderstand the compromise ARM makes due to its form factor and power envelope. Phones are fucking joke in computing power, stop beating this stupid drum.

      --
      Good-bye
    12. Re: Great! by Anonymous Coward · · Score: 1

      "ARM is utter shit for actual computing. Its a fucking toy."

      "The A12 is a Ferrari engine"

      So, which is it? Seeing as the A12 is the ARM part, I believe you are calling Ferrari engines "toys"...which they might be to rich people, but they're performant toys.

      Your opinion is meaningless.

    13. Re: Great! by kupekhaize · · Score: 1

      iMac:~ haize$ which sh /bin /sh
      iMac:~ haize$

      Please get a clue before you keep running your mouth.

      --
      One of these days i'm going to find this 'peer' guy and reset HIS connection!
    14. Re: Great! by spire3661 · · Score: 1

      Oh please. I'm a full UNIX graybeard, phreak and technomancer. The Deliverator is a personal hero of mine. I have witnessed the birth of Psycho-history.. Try again.

      --
      Good-bye
    15. Re: Great! by Anonymous Coward · · Score: 1

      "/bin/sh" Same place it has always been.

    16. Re: Great! by shmlco · · Score: 1

      Out of curiosity, what other computer platform just puts "CPUs on cards" such that you can install just as many (2, 4, 10) as needed? Even blade servers put basically the entire CPU plus RAM plus IO on a system board.

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    17. Re: Great! by WorBlux · · Score: 1

      Interesting. So it's Unix-ish if your a internal developer or hacker. I haven't played with any sort of "smartphone" out of sheer protest of the walled garden mentality of both Google and Apple, even if one isn't quite as strict as the other.

    18. Re: Great! by exomondo · · Score: 1

      Actually i think the touchbar would be better if it had the haptic engine that the trackpad uses, it really works well for the trackpad and I think it could Work for typing.

      That's likely what they're going for with the crappy typing experience they have now: reduce the key travel and typing experience so it is comparable to the haptic touchpad feel so they can replace the physical keyboard with a touch one. I hope they don't because the typing experience on the current lineup is very poor and a haptic one would be even worse.

    19. Re: Great! by arglebargle_xiv · · Score: 1

      Not necessarily. Windows has an ARM version. Though more than likely they'll ditch POSIX support and go full iOS across the line.

      ITYM:

      Not necessarily. Windows has an ARM version. Though more than likely they'll ditch POSIX support and go full retard across the line.

    20. Re: Great! by spire3661 · · Score: 1

      Would you care to put your money where you mouth is AC? IF ARM desktop/professional computing shipments exceed 5% of all computing shipments by 2022 ill put up a bottle of Glenlivet 18.

      --
      Good-bye
    21. Re: Great! by Anonymous Coward · · Score: 1

      More likely a dildo that you insert rectally to control in the screen.

    22. Re: Great! by cheekyboy · · Score: 1

      he only called IOS a toy, not ARM

      --
      Liberty freedom are no1, not dicks in suits.
    23. Re: Great! by drinkypoo · · Score: 1

      Nobody does 4k on the CPU. This was hardware acceleration in the GPU

      You mean, just like people commonly do on desktops? I use my GPU to do video encoding/decoding whenever possible.

      It's not doubt a good mobile chip, but a workstation chip? I kind of doubt it.

      It's not about the chip, there will be a new chip. It's about the core. If the core is adequate when coupled with a decent GPU, and if that actually happens, there's no reason it can't work.

      To my mind, most Apple users can get away with a lot less CPU power than they've got in their laptops and desktops right now, and the rest aren't especially profitable anyway, so why appease them? Apple seems to have the same attitude, given the history of their "pro" machines.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    24. Re: Great! by drinkypoo · · Score: 1

      Out of curiosity, what other computer platform just puts "CPUs on cards" such that you can install just as many (2, 4, 10) as needed?

      They're not actually used in this way, but passive backplane SBCs could be. And NUMA PCs are essentially that, although it's not cost-effective to build them that way. You can build a variety of multiprocessor topologies with HyperTransport, for example.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    25. Re: Great! by goombah99 · · Score: 1

      If you are a professional and earn the accordant salary then your time has value. In that case the cost of the tools is irrelevant to how productive they make you. People who complain about apple's price tag are not using it professionally. And indeed, I personally buy apples for my job and linux for my home computer precisely because of the price issue. if I wast a single day at work due to my computer I paid for the apple. At home, that's not the case.

      --
      Some drink at the fountain of knowledge. Others just gargle.
    26. Re: Great! by JabrTheHut · · Score: 1

      Anything non-Intel from Oracle and IBM, plus back before they took the poison Intel pill, HP and SGI.

      --
      Work like no one is watching. Dance like you've never been hurt. Make love like you don't need the money.
    27. Re: Great! by drinkypoo · · Score: 1

      Anything non-Intel from Oracle and IBM, plus back before they took the poison Intel pill, HP and SGI.

      They certainly did have processor slots, at least some of them. Pre-Oracle, Sun SparcStation machines did, too. Pre-SparcStation machines didn't, though; VME Suns only had a single processor slot.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    28. Re: Great! by nine-times · · Score: 1

      To my mind, most Apple users can get away with a lot less CPU power than they've got in their laptops and desktops right now

      In general, Apple's approach to the market is not really to put out commodity computers that compete on the metric of raw computing power. The anti-Apple crowd never seems to grasp that. It's more helpful to think of them as producing appliance computers as a whole product, aimed at specific use-cases. Granted, one of the main use-cases is general business and home productivity computing, but that's still a particular use case.

      It may sound like I'm just spouting nonsense, but here's my point: They're selling appliances to let people check their email, browse the Internet, and edit Word documents. None of that requires much processing power, relative to how much power is in a current-generation CPU. Apple doesn't need to push the envelope in high-performance CPUs. Instead, they tend to focus on things like a convenient and attractive form factor, making things lightweight, making the battery last longer, having a pretty built-in screen, etc.

      If they can deliver on those things somehow better with ARM CPUs, I wouldn't be surprised if they did that even if it meant less raw power, and I wouldn't be surprised if their fans were happy with the result.

    29. Re: Great! by nine-times · · Score: 1

      I don't think it's just "Unix-ish". macOS is technically actual Unix, and iOS is just a modified version of macOS. As far as I know, iOS is actual Unix, based off of BSD.

      It's just hobbled by being in a walled garden, unfortunately.

    30. Re: Great! by WorBlux · · Score: 1

      >It's not about the chip, there will be a new chip. It's about the core. If the core is adequate when coupled with a decent GPU, and if that actually happens, there's no reason it can't work.

      We have seen ARM in a more traditional architecture like with the Cavium ThunderX, though the consenses is that the per thread performance is somewhat anemic. I think going traditional on ARM loses the tight integration and manufacturing simplicity that a SOC brings. I don't see the advantage over x86. No I think apple wants to bring the same basic chip across thier whole line. Theyll probably change the chip from a 2.4 Big.little to a 4.4, up the RAM to 8GB and expand the GPU and codecs it covers. They'll carefully curate apps to work well with that, and they'll probably make money for a while.

      >To my mind, most Apple users can get away with a lot less CPU power than they've got in their laptops and desktops right now, and the rest aren't especially profitable anyway, so why appease them? Apple seems to have the same attitude, given the history of their "pro" machines.

      Abandoning the high end and server is a mistake in the long run I think. People who need these machines are driving business acquisition. If the ecosystem doesn't have a in-house big-iron solution it can get passed over. And before you say "cloud", it's just other people's servers and leaves you vulnerable to other people's mistakes and quite lopsided terms of service. Critical business data should stay on servers the business controls, and then think about adding cloud if you need remote access and redundancy. It gets even worse if you can't configure the machines to use local domain controllers and servers, like in iOS. (While there are apps to allow one-off access, it's not integrated into the core of the system)

      Really OS X on a big serious system like the Cavium ThunderX would get a lot of people excited about the Apple again. OS X has BSD heritage and should be able to perform just fine on serious hardware. Combine it with a way to run iCloud service on the local server and bind the device to a locally controlled application repository and you'd have a pretty nice enterprise chain.

      It's like the printer and ink model. If you can break even on the big system, and it lets you sell your high margin product into markets you couldn't before then why not? Sure there's this Steve Jobs vision of flashy well designed devices locked on "easy mode" but everyone forgets Steve Jobs just about ran Apple into bankruptcy the first time around. Good designs and UI are becoming more common and less of an up-sell than yesteryear. Apple sales are dropping as they can't get features people (even many die-hard fans) are willing to pay a premium for, and most of their revenue is from leveraging their position as gatekeeper, rather than providing solutions of fundamental IT problems. A new platform isn't going to solve Apple's business weaknesses.

      Compare to Microsoft, which while its improving it's consumer experience is branching out into services and solutions, embracing standards and open source to do so. Their 20 year outlook is more certain than Apple, even if nobody uses Windows in 20 years.

      I know this is a bit ranty, but in the long run gates come crashing down, while bridges get repaired and rebuilt over and over.

    31. Re: Great! by thereddaikon · · Score: 1

      MacOS is a bunch of BSD userland on top of a custom kernel that was developed by NeXT. Then add some Apple special sauce like the carbon graphics toolkit. iOS is MacOS with some things not needed for mobile stripped out and other things added in. They are closely related. The biggest difference is one is x86 and the other is ARM.

    32. Re: Great! by WorBlux · · Score: 1

      OS X is certified POSIX compliant. But by modifying it you don't neccessarily end up with something inside the standards. Take for instance the guy who modified a shovel and ended up with an AK-47. https://thechive.com/2012/12/0... They do some really weird things with the file-system and Jails, and don't expose the full range of system interfaces to the applications. I don't believe you can take any POSIX compliant code and compile and install it for iOS in the same way you can with OS X. (Version 9 and earlier are not BSD based). If you break the jail, reportedly it's close enough for openssh, but I'm guessing that it's not the case for the intended exposed framework.

      And I thing I noticed in research was that Cydia (jailbroke app store) apps were reported as tendeding to break between iOS releases, leading me to believe they are playing fast and loose with the interfaces that aren't exposed through the framework. If not API, at least with ABI.

    33. Re: Great! by thereddaikon · · Score: 1

      Waaaay back in the days of the S-100 bus everything was on a card including the cpu. While the processors of the time weren't meant for SMP the hobby community has gotten it to work on S-100. Depending on your bus architecture there is nothing really preventing this from happening aside from it just being space inefficient and OEMs like to to sell tiered products. IE: different model motherboards that support a different number of physical processors.

    34. Re:Great! by djinn6 · · Score: 1

      No one mentions it because everyone who's fed up with that and the keyboard has stopped buying Macs.

    35. Re: Great! by fiddley · · Score: 1

      You're forgetting your history. Jobs was long gone by the time Apple was driven in to the ground by the corporate bean counters. He was brought back just in the nick of time to broker a deal with Bill Gates and Microsoft who bought a significant amount of non-voting stock which kept Apple's head above water. From there he developed a succession of innovative products which turned Apple co into the biggest company in the world.

      --
      If medicine were ever perfected, we'd all be the same.
  2. Agreed by AmazingRuss · · Score: 1, Insightful

    ... this keyboard is a bad joke.

  3. REcompile by Anonymous Coward · · Score: 1

    and nothing is going to fucking work. guaranteed

  4. Re:It was nice knowing you by ArchieBunker · · Score: 1

    Haha we're back to thin clients again. I love it.

    --
    Only the State obtains its revenue by coercion. - Murray Rothbard
  5. Re:It was nice knowing you by Durrik · · Score: 1

    I was looking at picking up a new Mac when they do the refresh for video editing, digital artwork and animation. Mac is supposed to be better for that type of work. But if they're switching to ARM, I think I'll pass. I'll just look at something like an i9 and programs that can use multiple cores for the rendering the final output of videos and animations.

    While the Intel chips are crufty with all the stuff built up over the years, ARM is not going to be able to replace it for the work I do and plan on doing. I may pick up a Mac mini in the future to cross platform test my games, but its not going to be for any of the major work I do.

    I need a powerhouse for what I do, not a phone with a keyboard.

    --
    Software Engineer & Writer of Military Science Fiction and Fantasy Blog: petermwright.com Twitter: WrightPeterM
  6. Re:Irrelevant to me by KiloByte · · Score: 4, Insightful

    Gnome 3 is an abomination

    Newsflash: in Debian alone there's 57 different window managers (counting packages that declare Provides: x-window-manager). They vary wildly in functionality, but you get both fully-featured/bloated ones and 1990-era alikes.

    it has killed my productivity because window management is a pain and inconsistent, and features that used to work no longer do (it's now impossible to suspend while in a docking station, and this is apparently by design according to the bug report).

    Aye, Gnome 3 is insane -- even Microsoft has backed out of Metro.

    --
    The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
  7. Re:Irrelevant to me by Anonymous Coward · · Score: 3, Informative

    I'm in the same boat. I used to love Mac hardware from ~2004 (PowerPC) until around ~2010. Then it started to get really bad. MacOS went from a UNIX workstation OS to some sort of media consumer / music player thing (useless to me as I can't stand music) and it's clear Apple wants to make their products fancy televisions.

    So I bought a Thinkpad (meh hardware quality, but better than anything Apple has made recently); filled it with tons of RAM (which a MBP can't do) and I'm running Linux with Xfce on it. It's not ideal and it seems to die coming out of sleep 5% of the time (thanks worthless Nvidia hardware).

    I really wish there was a better professional laptop available these days. I do ASIC design and I run simulations that need ~64GB of RAM to complete in a reasonable amount of time. There aren't lots of options for me to do my job on the go (which I sometimes have to). Sadly, since some stuff I do needs to be done without an Internet connection (ugh) I can't just toss these big jobs on a server somewhere.

  8. RIP Mac then by Anonymous Coward · · Score: 1

    One of the last things people still use Macs for are development machines. And the only reason they can do that is because of the x86-64 chips in them.

    Remove that, and you kill that market. And the Mac along with it. Developers are NOT going to move to ARM on Mac.

    If this change happens, I won't be buying any Macs any more (and, yes, I have one) because I literally won't be able to use them. And I know I'm not alone.

    1. Re:RIP Mac then by wwphx · · Score: 1

      I decided a few years back that I'm not going to buy anything newer than a 2012 MacBook Pro, it's the last year that was assembled with screws. Get 16 gig of ram and a 2 TB SSD and it's really nice laptop. I don't know what I'll do for a desktop, right now I'm on a 2015 iMac which should be good for a few more years,so that decision is down the road a bit. If an employer wants me to have equipment newer than that, they can pay and maintain it - my personal equipment will be a bit more 'vintage'.

      --
      When you sympathize with stupidity, you start thinking like an idiot.
    2. Re:RIP Mac then by squiggleslash · · Score: 1

      When I bought my first Mac OS X Mac, which was long before they switched to Intel, virtually every developer I knew was excited by it, and a fair number bought one.

      I really don't get the "But you can't develop on one CPU if your program will run on another" thing. In practice, unless you're writing in C or something equally low level, the operating system matters far more than the CPU architecture.

      Realistically, if the complaint were true, ix86 mobile phones would have taken off as they would have been the only phones people were willing to write software for.

      --
      You are not alone. This is not normal. None of this is normal.
  9. Here comes the singularity by Proudrooster · · Score: 5, Interesting

    Ladies and Gentlemen, step right up to witness another technology train wreck where they try to achieve the illusive singularity. Apple is going to merge iPhone, iPad, and MacOS into a single platform. Other greats like Microsoft tried to achieve the singularity between mobile and and the desktop, but they failed. Their Windows Phone is just a memory and but the strange tiles on Windows 10 still remain and, Windows 10 tablet mode is still unusable.

    Now, a company which doesn't have a touch screen computer, but only a lousy keyboard that everyone hates, is going to try this amazing feat again. Using a mobile ARM processor with a touch screen UI/UX/OS called IOS, they are going to merge it with another mouse driven UI/UX called MacOS. Can they pull it off without a touch screen? How will users dual boot to Windows 10 to run their CAD software? And will it have a headphone jack? So many questions, so few answers. Without the reality distortion field of Steve Jobs this could be a headless company recycling failed ideas from other companies. Did anyone from Microsoft recently take on a leadership role at Apple?

    Not matter how you slice it, it will be painful drama for users. You won't be able to look away, it will be like watching a car crash in slow motion, you know you should look away, but you just can't.

    The singularity, can it be achieved? Stay tuned..

  10. Not so fast. by Anonymous Coward · · Score: 1

    With Xeon-based iMac Pros and the upcoming Mac Pro, I doubt that Apple will move to ARM entirely at any point in the next 5 years.

    There will be Intel-based Macs for some time, at least at the high end. And support will continue as well.

    I think this news means we will see an ARM-based Mac Mini model and something like a Macbook Air running on ARM. The more expensive Macs will stick around for a while. I doubt we'll see the current iMacs or MacBook Pros switch to ARM any time soon.

    Chances are the software transition will go smoothly. Apple has a lot of expertise in switching CPU families and their Xcode is very advanced.

    I do wonder if these will be full MacOS machines. Will Apple really recompile their entire certified BSD UNIX for ARM? You have to wonder if these ARM machines might be a lot more like iOS than MacOS when you look under the hood.

    But it is Sunday and a fine time to bash away on Macs. And Trump. It would be great if Trump bought a Mac so we could have some one-stop shopping for /. trolls.

  11. Torvalds rant: X86 development vs Arm Development by goombah99 · · Score: 5, Interesting

    Recently Linus ranted about how server class ARM development was a deadend because of the lack of sufficient "home" computers for normal use (he didn't literally mean home, but rather personal-computers). The answers that! On the otherhand for those of us who rely on libraries like say TensorFLow that doesn't look too good since a lot of that is X86.

    It will be interesting to see if Developers will flock to this as the optimum ARM development platform or flee from apple due to lack of x86 in their primary laptop.

    --
    Some drink at the fountain of knowledge. Others just gargle.
  12. Re:It was nice knowing you by KiloByte · · Score: 2

    They're turning Macs into phones with keyboards and bigger screens, because everything is a terminal for the cloud now, right?

    Fortunately some folks are going the other way. 100% free software (modem being isolated) Pinephone is coming, so is some Purism stuff -- no need to use Android nor iOS spyware.

    Or Gemini for that matter -- it has nasty non-free drivers, but is pretty functional. Just this Friday I spent a long bus ride hacking on a work project -- as the problem I'm working on involves something multithreaded not scaling well, a 10-core phone is actually better than the 4*2 dev machine. There are folks who use a phone without basics like compiler or valgrind, but I'm not one of them.

    --
    The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
  13. history repeats by crashumbc · · Score: 2

    I'm pretty sure, this is how Apple killed the Mac the first time... History repeats itself?

    1. Re:history repeats by Pieroxy · · Score: 1

      You must be remembering wrong. Apple Mac switched CPU twice already, and it was after Jobs returned to the company so that was the rebirth of the Mac.

      They (almost) killed the Mac once before, while doing nothing with it.

    2. Re:history repeats by drinkypoo · · Score: 1

      They (almost) killed the Mac once before, while doing nothing with it.

      Yeah, you have it right. Apple almost killed Mac by sticking with 68k. But they had an ARM core that would rival the 68k processors of the day in the last of the Newtons, and they neglected to go ARM then like they should have.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:history repeats by _merlin · · Score: 2

      They were on PowerPC in "the last days of the Newton" and while the DEC StrongARM was definitely amazing in MIPS/Watt, the PowerPC chips had better absolute performance, and definitely better memory bandwidth. (But yes, they completely crippled it with brain-dead designs at times, like the Performa/LC 5000 series with its half-width system buses. They'd done the same thing previously putting 16-bit memory on 32-bit 68k chips. There were a disturbing number of Macs that should've and would've performed a lot better if the system design wasn't brain-dead for cost-reduction or compatibility with old PDS/Comm Slot cards.)

    4. Re:history repeats by LaminatorX · · Score: 1

      Yeah, the problems they had with PowerPC only arose as IBM and Motorola left them in a lurch. Motorola never delivered a 64-bit chip to Apple, and IBM never delivered a 3GHz PPC 970 suitable for mass deployment (they ran so hot at that speed that the cooling would've sounded like a blow-dryer). This made the G5 the dead-end of mass-market desktop/laptop PowerPC parts. (If I were still single and had a room full of oddball computers, I'd get an Amiga-One X-5000 though.)

      PowerPC still had legs as an architecture in other market segments, obviously, but at that time, neither IBM nor Moto/Freescale were both willing and able to give Apple what they needed.

  14. "awkward period" == 10+ years/Look at alternatives by mykepredko · · Score: 2

    I can't see this being a very happy transition, especially for developers and product support.

    Looking back, it took 5+ years to end support for PowerPC Macs, I can't see it being any less and I would expect it to be twice that especially for Mac Servers.

    Maybe this is why Linus made his comments about ARMs a couple of days ago: https://slashdot.org/story/19/...

    If this is all a reason for having apps that work on iPhone, iPad & Macs, I again point to HTML5 and WPA. I can see that their growth could result in a downfall of Apple specific hardware and apps.

  15. Re:Irrelevant to me by gweihir · · Score: 1

    Why are you on Gnome if you do not like it? I use a decades old fvwm config that works exactly as I like. This is not windows where you have no or very little control over how your desktop looks.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  16. Will be interesting to see the performance by gweihir · · Score: 1

    I am not tied to AMD64 if I can get the same or better performance elsewhere at the same or better price. However, I expect that single-core performance will be pretty lacking and that would be a show-stopper.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    1. Re:Will be interesting to see the performance by gweihir · · Score: 1

      I am not talking about buying Apple. But if apple can push performance that high, then other will be able to do that too later.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  17. The plan all along? by Misagon · · Score: 4, Interesting

    Apple's own CPUs are not strictly "ARM-based", as they do not have cores developed by ARM itself.
    They have their own cores that are merely using ARM's ISA.

    Apple's CPU designs are likely to have lineage to P.A. Semi which Apple acquired in 2008.
    Before then, P.A. Semi had made processors running the PowerPC ISA. Apple had previously been interested in using those, but opted not to in favour of x86.

    --
    "We mustn't be caught by surprise by our own advancing technology" -- Aldous Huxley
    1. Re: The plan all along? by StikyPad · · Score: 2

      They *are* strictly ARM based â" they use a strict superset of the ARM specifications. They add on a few of their own SoC features and performance enhancements, but anything written for an ARM processor will run on Appleâ(TM)s Ax processors. Itâ(TM)s not like Apple uses unique instruction sets or anything.

    2. Re:The plan all along? by robi5 · · Score: 1

      I bet they license a lot more than an ISA (which may actually be free to replicate, not sure) - ARM is an IP company and have modular hardware designs which Apple likely uses to a great extent, tweaking it here and there and adding or removing modules.

  18. Re:Irrelevant to me by hazardPPP · · Score: 3, Informative

    I've just been delaying trying to switch to KDE to see if it's better, but I need to suck it up and just do it.

    I've been running KDE Neon for more than a year now and I think it's great.

    Kubuntu which I used before that I found to be crappy because it wasn't a "clean" KDE desktop, there were GNOME/Unity things here and there, two or three places to change the same settings, really confusing. Neon is a 100% KDE experience and in my experience it works very well. They've abandoned experimenting with the desktop, and you have a classic desktop experience on top of which you can place widgets if you like (but you don't have to).

  19. combine this with Linus' recent thoughts about ARM by RhettLivingston · · Score: 4, Interesting

    Linus Torvalds has stated that ARM won't win the server space because developers want to run their apps on the architecture it has been developed on and almost all are developing on x86. Many application bugs are still architecture specific. Application performance optimization is also highly architecture specific, especially for database applications.

    Given the Mac's popularity among developers, this argument should apply to the Macs too when looked at from the opposite angle. The vast majority of servers are x86, and developers want to run their apps on the architecture they are developing for. Running in an emulator is nowhere near the same experience. I would think a switch from x86 to ARM would decimate the number of developers calling the Mac home.

    Separately, I don't see the appeal of running phone apps on my laptop or desktop. Smartphone apps do not have the feature density that I'm looking for with a desktop app and desktop apps are not generally appropriate for smartphones. On my desktop, I don't want simplicity. I want to see everything I can at once and to be able to do almost everything with my keyboard.

  20. Re:It was nice knowing you by fustakrakich · · Score: 1

    They're turning Macs into phones with keyboards and bigger screens

    Yeah well, who didn't see that coming 10 years ago? It's logical for their business model. The Mac is a ball and chain.

    --
    “He’s not deformed, he’s just drunk!”
  21. Hybrids? by MMC+Monster · · Score: 3, Interesting

    If Apple is making their own ARM chips, presumably they can put them in at-cost as a co-processor along with an Intel chip on their home computer line.

    Benefits of the Hybrid:
    * Increase adoption of ARM as you deprecate Intel chips over a few generations
    * Run iOS apps at full speed while the Intel processor handles i86 tasks
    * Not be shackled by poor performance of ARM on desktop for individuals running apps that are processor-dependent and slow an Intel chip to a crawl.
    * (if you choose to make hybrid a long term solution) Have apps that run in multiprocessor mode with some processes running on each chip, making your home computer faster than all other manufacturers who are not selling multi-processor solutions.

    --
    Help! I'm a slashdot refugee.
    1. Re:Hybrids? by presearch · · Score: 1

      Seems reasonable.
      Their ARMs must cost them very little esp. compared to what they pay Intel.
      Less worry about heat would give better potential performance.
      Xcode will make porting a matter of setting a build option or two, if that.
      Apple's GPU future also looks promising.
      It's time we finally say goodbye to everything that is 1981's PC.

    2. Re:Hybrids? by XArtur0 · · Score: 1

      Reverse is also possible.

      Have an x86 'Co-Processor' to handle 'Legacy' Apps.
      Compile the Kernel, User-Space and Shell for the 'Main' ARM Processor.

      Sharing Memory between the two can be problematic though.

  22. Re:It was nice knowing you by tsa · · Score: 1

    If you want to do anything with pictures or video you're better off with a Windows machine. Especially if you need 3D accelleration MacOS is utter crap. It just doesn't work.

    --

    -- Cheers!

  23. Re:Torvalds rant: X86 development vs Arm Developme by Joe_Dragon · · Score: 1

    but apple is moving to app store only so this will not help any other ARM dev's

  24. Re:What about Boot Camp? by Joe_Dragon · · Score: 1

    with ATT 5G only $10/GB after your 15GB cap.

  25. Bloomberg by Major+Blud · · Score: 2

    I'm sorry but I can't take anything they say seriously since they claimed that SuperMicro servers were compromised. It's been months since that claim was made and we still haven't seen any proof.

    --
    If you post as Anonymous Coward, don't expect a reply.
    1. Re:Bloomberg by Durrik · · Score: 1

      And it was a very stupid way to claim that they were compromised.

      A low pin chip connected at the ethernet port. Or where the PHY is. By this point the data should have already been encrypted and secured. Especially if its in a secure facility, even communications inside a rack are usually encrypted. Besides if they were wanting to get any unsecured data off the network then it would be better just to compromise the switch. That way they get what they need from multiple sources, and compromise the thing that would be used to detect the information drain.

      If they wanted to get data that isn't secure, they'd have to tap something on the data bus. I think data buses are around 256 bits in most servers. Add in 40-64 bits for the address lines, and you have over 300 pins on the chip, and then you have to have power, grounds, and the pins to send the data out, which means talking to the PHY. I suppose the chip could send out ethernet direct, requiring only 4 pins, but then it would have to be 12V tolerant, and that you need to use a larger silicon process, and more gap between the pins. Most likely they're would talk to the PHY through SMII (or whatever the gigabit interface is, I'm more familiar with 100 mbit interfaces at the hardware level), which is another 20 pins or so. They probably also need an external oscillator.... So I don't think you're going to find a chip to monitor data in a server with less than 400 pins.

      Even with a BGA package this is not a 'small' chip. And then they have to deal with internal RAM/ROM and the processing power to figure out what information they've found and send. There's no way they're going to send all of it. It would take too much time, and make it too detectable.

      I'm not saying it can't be done, and the supermicro servers can't be compromised. Just I believe that they can be compromised in the way Bloomberg claims they are. Hollywood Magic doesn't work, you can't just add in a 'chip' and compromise stuff. You have to add it to where it can be effective.

      --
      Software Engineer & Writer of Military Science Fiction and Fantasy Blog: petermwright.com Twitter: WrightPeterM
    2. Re:Bloomberg by presearch · · Score: 1

      Because it's Hollywood magic, when it sends the zoomed and enhanced data, it displays at 120 cps and each character will make a little chirp sound.

  26. That's not what is happening by SuperKendall · · Score: 5, Insightful

    Apple has stated repeatedly they want nothing like the singularity, that desktops are inherently different than tablets or mobile devices.

    All that is happening here is a processor switch, because Intel has dropped so many balls they are more balls than company now. Apple wants to be able to control the processor so they can actually realize some gains, and avoid some of the shoddy design issues that have come to light in intel processors recently...

    I for one am fine with the change, these days adding support for another architecture is not THAT bad and Apple pulled it off really well before.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:That's not what is happening by Anonymous Coward · · Score: 2, Interesting

      No less than Google has announced that Spectre vulnerabilities are here to stay and cannot be resolved in hardware or software. Researchers presented a new Spectre attack that cannot be defeated. Existing x86 and high-end ARM designs are all vulnerable and will remain broken for any kind of meaningful security.

      Google: Software is never going to be able to fix Spectre-type bugs, 2/23/19

      If Intel's top CPUs are unfixable, that may be influencing Apple's decision to move to ARM, especially if Apple's chip guys think they can fix those bugs in hardware.

      An A13X CPU with decent cooling and high clock rate with multiple neural engines could make a very compelling MacBook Air. Even more so if it was immune to these speculative execution attacks like the various Spectre exploits.

    2. Re: That's not what is happening by StikyPad · · Score: 1

      Iâ(TM)m fine with it as long as I can use off-the-shelf components to build my own. Right now, Iâ(TM)m not aware of that potential for an ARM based system, but that could change I suppose. I donâ(TM)t really want to be locked into Appleâ(TM)s hardware though.

    3. Re:That's not what is happening by 93+Escort+Wagon · · Score: 1

      Apple has stated repeatedly they want nothing like the singularity, that desktops are inherently different than tablets or mobile devices.

      As a Mac user, I will be curious to see if Apple truly believes that or if it was basically just an anti-Windows 8/10 talking point. Certainly some of the bits like Mission Control *look* like iOS, and at seemed like they spent a bit of time talking it up until it became obvious their users realized it was pretty useless on a laptop.

      And I honestly do wonder if one of the reasons they’ve moved to those extremely low-travel keyboards (which many of us abhor) is to try and make the eventual shift to a non-moving, haptic-only “keyboard” less jarring.

      --
      #DeleteChrome
    4. Re:That's not what is happening by Dutch+Gun · · Score: 1

      I don't see any reason to doubt Apple on this. It's not like they aren't aware of the disasters of Windows 8 and Ubuntu's failed Unity experiment, all done in the name of trying to merge mouse+keyboard and touch-first paradigms.

      As for the keyboards, I think it's probably mostly power users who hate those, and it seems evident that Apple isn't really focusing on power users these days. With their iPhone's success, they're clearly focused on the mass market, and those keyboards are (apparently) fine with most normal users.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    5. Re:That's not what is happening by SuperKendall · · Score: 1

      Yes, exactly - and Apple automatically gains some comparative performance boost with other systems by simply not having to have the system performance impacting workarounds Intel chips have to use today, which as you noted don't even really solve the problem entirely.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    6. Re:That's not what is happening by shmlco · · Score: 1

      I run Mission Control on a Mac laptop and it's anything but useless.

      I've got a dozen virtual windows (spaces) running about 16 apps at the moment, with one of those apps (Safari) running about 18 browser windows. Mail, Messages, Slack, Safari, Xcode, Chrome, Calendars, Simulators, Zeplin, iTunes, Fabric, multiple Terminal windows... all work just fine.

      And this is just a late 2013 15" Retina with quad-core i7, 16GB RAM, and 1TB SSD, albeit one connected to a 34" ultrawide monitor.

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    7. Re:That's not what is happening by Jeremi · · Score: 1

      I for one am fine with the change, these days adding support for another architecture is not THAT bad and Apple pulled it off really well before.

      Hmm, maybe. As someone who enjoys developing on a Mac and running Linux and Windows as VMWare VMs when necessary, it's hard to see how an ARM-based Mac could do the necessary x86 emulation at an acceptable speed. Maybe they have some Rosetta-style tricks up their sleeve, but IIRC Rosetta was able to deliver acceptable performance largely because the x86 CPUs of the day were sufficiently faster than the PPC CPUs they were emulating. I'm not confident that is true of today's ARMs (relative to x86).

      --


      I don't care if it's 90,000 hectares. That lake was not my doing.
    8. Re:That's not what is happening by SuperKendall · · Score: 1

      it's hard to see how an ARM-based Mac could do the necessary x86 emulation at an acceptable speed

      I'm not sure about this either - it could be Apple is banking on enough apps being uploaded to the Mac App Store with Bitcode to be able to be deployed from the App Store without even a new build, though things like Photoshop would drag for years after... maybe they have something up the sleeve to get reasonable performance for most apps they can't do real ARM binaries for.

      Probably just a few of the most portable travel models would be ARM at first, with other systems coming later. Maybe also the Mac Pro is a dual ARM-x86 system where it can offload anything possible to the more efficient and performant ARM chip, and have x86 in there for compatibility.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    9. Re:That's not what is happening by Tough+Love · · Score: 1

      It would be great if they'd do it, I'd love to see Apple fade away some more.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    10. Re:That's not what is happening by nine-times · · Score: 1

      Apple has stated repeatedly they want nothing like the singularity, that desktops are inherently different than tablets or mobile devices.

      Well specifically what they said was, they think an attempt to have a singular mobile + desktop UI is doomed to fail, and they're not going to do it. However, I don't think that necessarily means that they wouldn't consider a unified OS.

      This news is that they're likely to move some of their desktop machines to use the same processor line as their mobile devices. Meanwhile, they recently announced that they're making it easier in Xcode to make a single app that will run on both iOS and macOS with just a change in UI.

      What they may be headed towards is an ecosystem where app developers have the ability to make a single app that presents a mobile UI on a mobile device and a desktop UI on a laptop/desktop. Then, they could make phones and tablets that display an entire mobile UI when operating as a mobile device, but turn into a fully-functioning desktop machine with a desktop UI (and all the apps presenting a desktop UI) when docked.

    11. Re:That's not what is happening by squiggleslash · · Score: 1

      Maybe they have some Rosetta-style tricks up their sleeve, but IIRC Rosetta was able to deliver acceptable performance largely because the x86 CPUs of the day were sufficiently faster than the PPC CPUs they were emulating

      True-ish. If most PPC Macs that were being replaced by Intel Macs had been powered by G5s, then the performance would have been considered sub-optimal.

      The question isn't whether good ISA translation software could make software written for the latest i7 run acceptably on a fast ARM, but whether good ISA translation could make software written for a 2014 i5 run acceptably on a modern fast ARM. I suspect it could.

      The other comment I'd add is that experience showed us that developers were extremely quick to put out native versions of their applications as soon as the Intel switch happened. That'll probably happen again, leaving only very old legacy applications needing emulation, emulation that'd probably be fast enough if using more traditional semi-interpreted techniques. Indeed, I'd be interested to see if they support PPC translation as well as ix86 translation, as that might also result in a lot of software running faster than it did when it was native.

      --
      You are not alone. This is not normal. None of this is normal.
    12. Re: That's not what is happening by david_thornley · · Score: 1

      If Apple doesn't care about security, why the Secure Enclave on the iPhone 5S on? Why argue against the FBI's request? Apple clearly cares about security. You can speculate about their motives, but they do care.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    13. Re:That's not what is happening by david_thornley · · Score: 1

      Apple has stated repeatedly they want nothing like the singularity, that desktops are inherently different than tablets or mobile devices.

      Thing is, I keep hearing that like the idea that the iPhone didn't need native development when you could do so much stuff on the web...right up until they introduced the iOS SDK.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  27. Re:combine this with Linus' recent thoughts about by Anonymous Coward · · Score: 1

    switch from x86 to ARM would decimate the number of developers calling the Mac home.

    On the other hand, moving developers' home/office platforms to ARM might decimate Intel in the data center. Linus' argument was that the availability of the x86 to developers was what pulled Intel into the data center.

  28. Re:"awkward period" == 10+ years/Look at alternati by fustakrakich · · Score: 1

    From that summary:
    Without a development platform, ARM in the server space is never going to make it.

    Maybe Apple is out to provide that platform... Pure speculation, of course, but why not?

    --
    “He’s not deformed, he’s just drunk!”
  29. Re:Irrelevant to me by R3 · · Score: 1

    I have to give props to Google for what they did with ChromeOS in the past couple of years.

    While I still have a "regular" Windows 10 PC mostly for games and odd app or two, everything else is done on Asus CN60 chromebox (Haswell i3, upgraded to 16GB RAM and 128 GB m.2 SATA HD). While this model is too old to support Crostini or virtualization (pushing 5 years now), it satisfies pretty much my every need - and as you said: it runs the OS that not actively working against me.

    If only Pixel Chromebooks were not $1300, I would probably buy one tomorrow.

  30. I doubt they'll be "Macs" as such by Kjella · · Score: 1, Troll

    Basically I expect them to be laptops/desktops with the iPhone/iPad/iWatch business model and an i-name like iBook or iNote or whatever. Runs a version of iOS that's adopted Mac interfaces but is locked down with no dual boot to anything else. All applications come from the store so no backwards compatibility with Mac apps, just windowed iOS apps until developers make a store version. The question is just if Apple can resist the temptation to price it crazy, I mean their latest phones are really getting out of hand.

    --
    Live today, because you never know what tomorrow brings
  31. Re:Torvalds rant: X86 development vs Arm Developme by weilawei · · Score: 4, Interesting

    I personally look forward to this. I like the ARM ISA. I thought Torvalds was being short-sighted. For starters, it's a more popular platform by number of chips in the wild. These Intel and AMD CISC designs are all RISC under the hood now, anyway.

    We're just doing away with the cruft of a legacy architecture that grew off track.

  32. x86 by presearch · · Score: 1

    So everything Apple does, did, or will do is doomed to failure,
    but we loves us some x86 architecture from 1979 and can't imagine an alternative.
    The future has spoken.

    1. Re:x86 by drinkypoo · · Score: 2

      So everything Apple does, did, or will do is doomed to failure, but we loves us some x86 architecture from 1979

      Nonsense. All common x86 processors have been internally RISCy since AMD introduced their Am586 chip, and Intel its Pentium. The only thing they shared with x86 processors from 1979 was an instruction set, with its primitive use of a limited number of registers — literally none of which were "general purpose", as various instructions required operands to be placed in specific registers, and results to be delivered to others. These failings were addressed by the amd64 instruction set, which largely permits use of registers as general-purpose, and which provided for four times as many registers in the bargain. The x86 decoder is a minuscule portion of the silicon in a modern processor.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:x86 by squiggleslash · · Score: 1

      I've heard this claimed multiple times and when I try to pin people down on it they can never come up with specifics. What about the original Pentium made it "interally RISCy"? They didn't reduce the number of instructions, increase the number of registers, or anything like that. The Pentium was more or less an incremental upgrade of the 486, with a better pipeline (that meant it was the first to provide superscalar performance... sometimes) and more caches. It was still microcode controlled and still had few registers, and I don't need to explain why it wasn't a RISC chip in any other way.

      The best argument I've heard is that in the Pentium Pro (note: not the Pentium), Intel replaced a traditional microcode controller with a thing that translated ix86 instructions into VLIW instructions, with everything running on a VLIW core. "That's the same!" you cry, well, if it is then every simple CPU is a RISC design, and every CPU that uses microcode has a "RISC core". What, in practice, is the difference between a core that's controlled directly by microcode being read in real time, and a core that's controlled by data from a buffer that's being filled with instructions from a microcode decoder? Nothing, except the buffer. The buffer's a great idea, it makes optimization much easier, but it's not the same thing as adoption of RISC.

      The thing people forget is that by 1995 RISC vs CISC was thought to be over... with the results largely a stalemate, but leaning towards CISC. RISC had come out of the gate with high performance, but could only be improved with higher clockspeeds, and was already suffering issues with data starvation. The higher transistor budgets that were becoming available were not helping RISC much - it was cheaper, and allowed hardware makers to own their own CPUs, but beyond that RISC wasn't improving.

      CISC, on the other hand, had the benefits that it had plenty that still needed to be optimized, and with smaller instructions, was much more cache friendly. Adding a cache and using it to effectively create a Harvard architecture inside a CPU, together with better pipelining, meant you could get superscalar performance and have the benefit of more advanced instructions.

      Now before you point it out, sure, you could add the same features to a RISC design. The issue though was that RISC didn't benefit as much. You needed a larger instruction cache, for example, and equivalent superscalar RISC performance will never beat superscalar CISC performance, because the former is doing slightly more than one simple instruction every tick, and the later a complex instruction usually worth several RISC instructions every tick.

      Why's RISC suddenly important again? RAM is cheaper and faster than it was, power usage is now an important metric, and transistor budgets have stalled. Removing or simplifying the instruction decoder is now worth doing, it's a big chunk of logic that could be eliminated completely now that RAM is cheap. But in the 1990s none of that mattered.

      --
      You are not alone. This is not normal. None of this is normal.
    3. Re:x86 by drinkypoo · · Score: 1

      I've heard this claimed multiple times and when I try to pin people down on it they can never come up with specifics. What about the original Pentium made it "interally RISCy"?

      The Pentium does not internally "think" in x86 like the 486 did. It's actually a RISC processor internally, and x86 instructions are decomposed by the x86 decoder into "micro-operations" which take a single cycle to execute. This is not how the 486 behaved. The same is also true of the Am586 vs. the Am486, and it is how all x86-compatible processors have been designed since.

      The best argument I've heard is that in the Pentium Pro (note: not the Pentium), Intel replaced a traditional microcode controller with a thing that translated ix86 instructions into VLIW instructions, with everything running on a VLIW core. "That's the same!" you cry, well, if it is then every simple CPU is a RISC design, and every CPU that uses microcode has a "RISC core".

      Now you're getting closer. But you can't reasonably say that they are RISC CPUs if the instruction set that they expose isn't RISC, because the instruction set is part of the definition. That's why they are only described as being RISC internally, and not as RISC processors.

      Removing or simplifying the instruction decoder is now worth doing, it's a big chunk of logic that could be eliminated completely now that RAM is cheap. But in the 1990s none of that mattered.

      Back in the 1990s, the x86 decoder was a big percentage of the chip. Today, it's a tiny one, and the benefit of backwards compatibility far outweighs that tiny little speck of silicon.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  33. Re:Torvalds rant: X86 development vs Arm Developme by Ed+Avis · · Score: 1

    I like the ARM ISA.

    ARM classic or ARM64? (Of course anything is better than x86 family, but that's a low bar to clear.)

    --
    -- Ed Avis ed@membled.com
  34. Re: "awkward period" == 10+ years/Look at alternat by StikyPad · · Score: 1

    They already have it, and have for years. Developing for iOS means code is first compiled for x86/x64 to test on the desktop, and then its recompiled with the ARM toolchain when you deploy to a device. Their development pipeline is relatively platform agnostic. Xcode kind of sucks as an IDE though.

  35. Re:Torvalds rant: X86 development vs Arm Developme by goombah99 · · Score: 1

    No you can override the signed app protections easily, especially if you are a developer.

    --
    Some drink at the fountain of knowledge. Others just gargle.
  36. Painful for developers targeting intel by davecb · · Score: 1

    Numerous of my customers use Mac on Intel as development machines for Linux on Intel servers, to provide mass-market GUI tools and target-specific development tools.

    Apple is about to make that unpopular.

    This will put a push on Linux distros like Fedora and hardware companies offerings like Dell's XPS 13 Developer Edition, to finally deliver the year of the Linux Desktop. Well, for developers, at least (:-))

    --
    davecb@spamcop.net
    1. Re:Painful for developers targeting intel by Pinky's+Brain · · Score: 1

      They could launch new server modules at the same time, they've been in the space before. With the whole Spectre clusterfuck and the diminishing process lead of Intel, an ARM solution from Apple might well be superior. If so with Apple's weight behind it a transition could happen very quickly IMO.

      It would be a scary situation for a vertically integrated company to be responsible for so much of computing though, so let's hope not.

    2. Re:Painful for developers targeting intel by drinkypoo · · Score: 1

      They could launch new server modules at the same time, they've been in the space before.

      Who would trust them? Their first servers were grossly overpriced, so were their second servers, and they dropped their third server line just about the same time people got used to using them.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:Painful for developers targeting intel by Pinky's+Brain · · Score: 1

      Like the IT industry has a memory which spans more than minutes and can learn from mistakes.

  37. No gripes like Apple gripes by presearch · · Score: 1

    Please, enough about bitching about the butterfly keyboard, $1000 phones, and the RDF.
    Tell us again about how Jobs ripped off Xerox PARC. That's always a hoot.

  38. Re:Torvalds rant: X86 development vs Arm Developme by serviscope_minor · · Score: 1

    The "cruft" barely matters any more. On super low end chips, sure the instruction decoder matters. On laptops, it really doesn't. The out of order and wide floating point units and wide, fast memory bus are far far more expensive than three decoder.

    --
    SJW n. One who posts facts.
  39. Re:Irrelevant to me by Anonymous Coward · · Score: 4, Insightful

    Grey-beard here. Over the years I have used *A lot* of window managers / desktop environments. The worst I have used recently is by far Gnome. I updated an Ubuntu machine to 18.04 and said "what the hell", and let it default the window manager to the preferred new one. Gnome was the worst piece of junk I've ever used. All the other desktops I've been able to figure out how to suspend without too much difficulty. Gnome - NOPE. I look at the shutdown menu and can't find anything related to suspend. I see shutdown but no suspend. After a few minutes of googling I discover that someone decided that to suspend you should hit SHIFT or CONTROL or something similar while hitting shutdown. I could live with that, EXCEPT the idiots who designed it didn't change the icon. I TRIED pushing shift and control and alt and other things and there's ZERO feedback. There is PLENTY of space for a suspend icon, but some idiot decided that putting a suspend icon was a bad idea. At that point I seriously questioned the sanity of anyone involved. I couldn't believe they would take away a standard feature like that and hide it.

  40. Re:It was nice knowing you by presearch · · Score: 1

    Everything from Microsoft ends in heartbreak.

  41. Re:combine this with Linus' recent thoughts about by RhettLivingston · · Score: 1

    I think the chicken and egg issue will dominate though. Until a large portion of the datacenter systems are ARM, there would be no compelling reason for a developer to switch their development platform and many compelling reasons not too. And until a large number of developers are on ARM, the datacenters would be fighting the developer's platform if they switch.

    Why would I buy a development system as premiumly-priced as the Macs to target a platform that might be successful in a few years? These things don't happen overnight.

    I CAN play devil's advocate with myself here. I do realize that this will help front end developers, and that is almost certainly in Apple's thoughts. But, in my experience, the back end is where the real tech is. If front end developers jump to ARM-based Macs because it makes their jobs easier, we'll see the already damaging gulf between front and back end development widen. That would be a bad result for the industry. Of course, I say this as more of a full-stack guy that believes it is much harder to develop a quality product when nobody on the team fully understands both worlds.

  42. Re:It was nice knowing you by tsa · · Score: 1

    But at least it started.

    --

    -- Cheers!

  43. Re:Apps development by evil_aaronm · · Score: 3, Insightful

    Not exactly true. Some of us *like* the desktop user experience we get with Mac OS. I could use Linux, but I like Macs better. I also understand that Linux can be mapped to look like Mac, but with an actual Mac, I don't need to bother. And kindly don't confuse "I prefer Macs" with "I am a rabid Mac fanboy." There are degrees of difference between the two.

  44. Re:"awkward period" == 10+ years/Look at alternati by pauljlucas · · Score: 1

    I can't see this being a very happy transition, especially for developers and product support.

    Apple has done transitions before: classic MacOS to MacOS X, Motorola 68000 to PowerPC, and PowerPC to Intel. They survived all three. Given their history, they're obviously capable of handling transitions well enough.

    --
    If you reply, do so only to what I explicitly wrote. If I didn't write it, don't assume or infer it.
  45. Re:Torvalds rant: X86 development vs Arm Developme by robi5 · · Score: 1

    > (he didn't literally mean home, but rather personal-computers)

    Thanks for the clarification!!!

  46. Re:Irrelevant to me by Anonymous Coward · · Score: 1

    If you're still inside warranty, then at least that'll be free but from what I saw from the warranty process on a colleagues Macbook, that's gonna be a pain. And if your hardware is older than a year, you're SOOL?

    Move to Europe, EU law guarantees 2 years of warranty.

  47. Re:Torvalds rant: X86 development vs Arm Developme by spire3661 · · Score: 1

    No way Mac goes app store only. Maybe in 10 years, but not today.

    --
    Good-bye
  48. Re:Torvalds rant: X86 development vs Arm Developme by spire3661 · · Score: 1, Troll

    ARM is utter shit for actual computing. Its a fucking toy. You under appreciate the inertia and gravitas x86 has. ARM is wonderful for the low end, but for development, you can fuck right off with that noise.

    --
    Good-bye
  49. Re:Torvalds rant: X86 development vs Arm Developme by short · · Score: 1

    TensorFlow is free software (Apache License 2.0) and it is not written in assembler, you can build it for (mostly) any arch. Google distributes x86_64 binaries but that is just to save people from building it.

  50. what ARM chip would do that job? by iggymanz · · Score: 1

    What was the ARM's floating point coprocessor again? what chip competes against the intel 8th gen?

    1. Re:what ARM chip would do that job? by TeknoHog · · Score: 4, Funny

      what chip competes against the intel 8th gen?

      None, you need Genuine Intel for a flawless Meltdown experience.

      --
      Escher was the first MC and Giger invented the HR department.
    2. Re:what ARM chip would do that job? by drinkypoo · · Score: 1

      None, you need Genuine Intel for a flawless Meltdown experience.

      Almost. You can also get it with POWER, or ARM Cortex-A75.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:what ARM chip would do that job? by angel'o'sphere · · Score: 1
      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  51. Re:combine this with Linus' recent thoughts about by weilawei · · Score: 1

    I'm leaning toward this future. I've switched to using a Galaxy S9+ as my daily computing device, and the Thinkpad is reserved for longer coding sessions.

    But, more and more, I just use a bluetooth keyboard from Omoton and use Termius to SSH in to my servers and the laptop from my phone. File Manager+ has SFTP support, among many features. I have browsers, VNC, DroidVIM (really an excellent port), etc.. Do I need a monitor? I cast the screen to a ChromeCast.

    I write code primarily. If I need horsepower, I spin up a VM from my phone and use SFTP/Git to load up some code, and SSH in to administer it. The phone fits in my pocket while I'm running around between the machines at work, too. Nice bonus there, not lugging the laptop itself.

  52. I fear it's more about the money for Apple .... by King_TJ · · Score: 4, Insightful

    When Apple did the huge transition over from PowerPC to Intel CPUs, it was near the height of Apple's success selling OS X based computers. Even then, there was a big fear it would hurt certain markets, like native OS X game development, as it would make an excuse to "just write a Windows only version and let the Mac users boot into Windows to play it". And that, in fact, DID happen. But by and large, Mac users accepted it as a "win" because Intel CPU development was so much further ahead and drove more competitive Macs with their Windows counterparts. Plus, it wasn't half bad being able to run Windows in virtual environments - where a bunch of processor instruction conversion between x86 and PPC didn't have to happen in the background to make it work.

    This time around? It's far less clear.... Intel still cranks out great CPUs and nobody I know is complaining that their Mac is under-powered, CPU-wise. The big push seems to be Apple's continual insistence that "most people can just use an iPad and iPhone instead of a computer", and an interest in selling their own CPUs instead of giving all that money to Intel.

    I think we're going to see a lot of "dumbing down" of OS X apps if they all start getting coded to run universally on iOS and OS X with ARM. If features in software don't translate well to a touch-screen UI, they'll rip them out instead of keeping "Mac only" versions with more capabilities.

  53. Re: Torvalds rant: X86 development vs Arm Developm by blackt0wer · · Score: 1

    RISC has been alive longer than the x86. It's nice to see a company going back to its roots. That said, I think the idea here is to synergize all platforms.

  54. Re: Irrelevant to me by blackt0wer · · Score: 1

    It all went to hell after [i]screen[/i]

  55. Re:It was nice knowing you by MikeMo · · Score: 1

    So you're going to stop buying a current machine, which apparently meets your needs, based on a rumor about a future Mac which may or may not happen and may actually meet your needs - since you don't know what the specs of this imaginary machine might will be. Did I get that right?

  56. Re:Irrelevant to me by ignavusinfo · · Score: 1

    I'm in the same boat. I used to love Mac hardware from ~2004 (PowerPC) until around ~2010. Then it started to get really bad. MacOS went from a UNIX workstation OS to some sort of media consumer / music player thing (useless to me as I can't stand music) and it's clear Apple wants to make their products fancy televisions.

    Huh? As a dev my use case primarily involves zsh, Emacs, Erlang, and PostgreSQL and all that's running just fine on MacOS thanks. I'm really curious what your use case is? I mean, you make it sound like you've maximized the iTunes window and don't know how to quit the application.

  57. Nevermind this - where's this famous pro tower? by sandbagger · · Score: 1

    I'm looking a two Mac Pros in front of me with seven drives shoehorned into the nearest one and nearly all of the PCI cards used. I've changed so many parts in it the thing has become the Ship of Theseus. They promised a new pro machine and nary a peep so far other than they've got 'top men' working on it. Well, where is it already?

    --
    ---- The above post was generated by the Turing Institute. Maybe.
  58. Re:Torvalds rant: X86 development vs Arm Developme by caseih · · Score: 5, Insightful

    It may be popular but it doesn't mean it doesn't suck. Torvalds was right. But maybe for different reasons, many of which probably don't apply to Apple.

    The main problem with ARM, at least as I as a Linux user am concerned, is the lack of any standardized, open, boot system like the much-maligned BIOS, or EFI, and the lack of a standardized, minimal device tree. There are literally dozens of of cheap single board computers you can get to run linux on. But how many of them can boot a standard distro off of a hard drive or usb stick you just plugged in? How many can run a standard, generic, Linux kernel and a standard, generic, Linux distro? I don't know of any. And it's very frustrating. Those boards that can run android can run a particular version of android, obtained from the manufacturer, limited to their whims to update it.

    The promise of ARM is awesome. But so far I remain disappointed. I've got a drawer full of ARM devices that I used for short periods of time. Sheeva Plugs, a GuruPlug, several raspberry pis, and various random chinese boards. All powerful machines in their own right, but not as useful as I thought. Mostly due to the proprietary (or at least esoteric) boot systems, custom kernels, special device trees, proprietary graphics cores, etc. I just don't really want to mess with U-Boot and flashing special images to partitions just to get the latest version of Debian up and running, or install a 5.0 kernel.

    If intel produced a board at the price point as these ARM boards, but could boot regular old Debian with a generic x86 kernel, supporting the GPIO that makes Pis so popular, I'd ditch ARM in a heartbeat (SBCs, not phones).

    Again, none of this applies to Apple necessarily, though. They control and access every bit of the hardware to make it sing their song, so I'm sure many users won't know or care, as long as they keep buying from the Apple Store. But it's a definite step towards a completely locked-down appliance. Might take another decade, but that's where Apple seems to be heading.

  59. Not Enough CPU for Content Creation by BrendaEM · · Score: 1

    Their next computers will absolutely stink at designing the ones after. They will also stink at working on the advertising video and renderings.

    --
    https://www.youtube.com/c/BrendaEM
    1. Re:Not Enough CPU for Content Creation by Bill+Hayden · · Score: 1

      They could less about content creators now, so no worries there.

      --
      Protect your browser with the Force Safe Search add-on
  60. Just talked about this today by ReneR · · Score: 1

    TL;DR https://www.youtube.com/watch?... will be horrible for users, as no bootcamp nor virtual machine for Windows and Linux anymore

    1. Re:Just talked about this today by XArtur0 · · Score: 1

      I though many VM Engines supported Platform Emulation?
      If not, somebody will come up with a JIT VM Engine that translates x86 to ARM instructions...
      I'm no expert though.

      Also, Linux will be ported to those ARM chips the next day they are made public.

  61. A grain of salt by Guspaz · · Score: 1

    I'm not saying it's NOT happening, but everybody should remember that we've been seeing similar reports to this every year since at least 2011, when it was reported that Apple had internal prototypes of ARM-based MacBooks running OS X. All of the current talk about a 2020 shift to ARM can be traced back to this single unverified Axios article.

    1. Re:A grain of salt by Guspaz · · Score: 1

      I'm not sure those parents were all that relevant to begin with. Apple introduced their own CPU in 2012, before any patents would have expired, and there hasn't been anything in the development of their subsequent chips that would scream "Patents expired here!"

      Their A12X chip is definitely capable of powering a laptop, since it's more powerful than the vast majority of x86 laptops on the market, but they've arguably been in a position to replace at least their lower-end laptops with ARM chips since the A8X (their first 64-bit "X" chip) in 2014, and that's not to say they couldn't have introduced an "XX" variant with more cores had they felt a need to do so.

      Personally, I think the 2020 date does make sense, because the A12X leaped past most mobile Intel CPUs, and there's no reason to think Apple wouldn't be able to get something fast enough for a MacBook pro by 2020. However people have been saying similar things to this for years now.

  62. Re: What about Boot Camp? by fermion · · Score: 1
    When I had to do AutoCAD sometimes boot camp was great. Faster than most native windows setup. But fir the past few years vbox has bern a better fit.

    What we have to remember is that this is not the first time apple has done this, and each time they have done it well with good results and benefits. Obviously the last time we got boot camp which at the time was a huge gain. We will see what is up thier sleeve this time. Likely integration across all the product lines.

    --
    "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
  63. Re:Torvalds rant: X86 development vs Arm Developme by drinkypoo · · Score: 1

    The promise of ARM is awesome. But so far I remain disappointed. I've got a drawer full of ARM devices that I used for short periods of time.

    Please pry those out of storage, and sell them to some geeks who can use them, for a reasonable price. People could use them. Unless you're keeping them for posterity?

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  64. Re:Irrelevant to me by drinkypoo · · Score: 1

    Agreed. I'm pretty much 100% Linux, and the state of desktop Linux is atrocious. Gnome 3 is an abomination, it has killed my productivity

    What's preventing you from going back to Gnome 2 via MATE?

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  65. Re: "awkward period" == 10+ years/Look at alternat by angel'o'sphere · · Score: 1

    Their development pipeline is relatively platform agnostic. Xcode kind of sucks as an IDE though.
    Then use Eclipse or IDEA Intelli J

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  66. Re:combine this with Linus' recent thoughts about by angel'o'sphere · · Score: 1

    Linus Torvalds has stated that ARM won't win the server space because developers want to run their apps on the architecture it has been developed on and almost all are developing on x86.
    Almost all are developing in Java, so the actual hardware does not matter. (*facepalm*)

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  67. Re:combine this with Linus' recent thoughts about by angel'o'sphere · · Score: 1

    Why would I buy a development system as premiumly-priced as the Macs to target a platform that might be successful in a few years?
    Because Macs run OS X or macOS. It is even preinstalled. A random hardware does not.

    Why Mac haters don't shut up is beyond me. If you have no use/need for macOS, fine. then simply shut up, idiots.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  68. Re: Irrelevant to me by Type44Q · · Score: 1

    I swear by Mate.

  69. Re: Torvalds rant: X86 development vs Arm Developm by ChatHuant · · Score: 2

    RISC has been alive longer than the x86.

    How d'ya reckon that? The 8086's design started in early 1976, and it became available commercially in 1979. The first two major RISC projects (Standford's MIPS and Berkeley RISC, who evolved into the SPARC architecture) both started in the 1980s and became available commercially years later.

    Some people point to the IBM 801 as a forerunner of the RISC concepts, but even this only became available commercially in 1980, and, as a single chip, only in 1981. It wasn't successful, but it was used as a base for the development of the RS/6000 - who, however was launched in 1990, 11 years after the x86

  70. Re:Irrelevant to me by angel'o'sphere · · Score: 1

    You know, usually you just "close" the laptop and it suspends ... unless it is a weird "brand" of linux, though.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  71. Re:"awkward period" == 10+ years/Look at alternati by drinkypoo · · Score: 2

    Looking back, it took 5+ years to end support for PowerPC Macs, I can't see it being any less and I would expect it to be twice that especially for Mac Servers.

    Apple doesn't have servers any more. "macOS Server" is an app in their desktop app store which costs twenty bucks, and provides some of the functionality which comes with NT server. The last time Apple had a server hardware product was 2011.

    If this is all a reason for having apps that work on iPhone, iPad & Macs, I again point to HTML5 and WPA.

    Ugh. What a PITA. If that's the best Apple can do, their best isn't very good.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  72. Re: Irrelevant to me by dskoll · · Score: 1

    You don't have to use GNOME. I use XFCE4 on all my machines; it's just enough of a desktop to be usable without getting in your way.

  73. Re:Irrelevant to me by _merlin · · Score: 2

    What if it's not a laptop, or you don't want to flip it shut? I mean, on a Mac you can tap the power button and there's a Sleep button there, Windows can do it from the keyboard or in the menu that appears when you hit the power/standby icon in the start menu, why did the Gnome people decide to make it so unfriendly?

  74. Apple DEV thrash by ElitistWhiner · · Score: 1

    Move from NeXT Obj-C to Apple MacOS was brutal code thrash. Three rewrites to the API's in a single year was a coup de grås. Best move ever. We shutdown development until Apple stabilized MacOS X revs. Bought AAPL stock at $17 and dumped the remaining funds in @ $12. AAPL surging stock price ended development.

    AAPL have been here before and have the architecture, abstraction and now new silicon under it. What could go wrong? Tim Cook for one. Tim is not a bit twister (little nor big endian) and it all looks like supply pipeline in Tim's eyes.

    Personally, Gung-ho for AAPL abstracting the codebase over ARM (MOTO, INTEL, et. al.). QUALCOMM taught Tim the meaning of ' detrimental reliance' as INTEL did SteveJobs. Some lessons don't slot into institutional memory banks. ARM looks like a pivot for Apple down market.

  75. Re:Irrelevant to me by h33t+l4x0r · · Score: 1

    Newsflash: in Debian alone there's 57 different window managers

    So just take a month off to try them all, and hopefully one of them works for you.

  76. Hackintosh? by samdu · · Score: 1

    So this would be the end of the Hackintosh, no? That sucks. While I spend most of my time on my MacBook Pro, I like having my Hackintosh for really heavy lifting.

  77. Re:Torvalds rant: X86 development vs Arm Developme by epine · · Score: 1

    For starters, it's a more popular platform by number of chips in the wild.

    The blind-census argument is itself extremely popular based on its relentless occurrence in the wild, at least that part of the wild with limited binocular vision.

    ———

    Sage: You can't judge a book by its cover.

    Simpleton: Uh, what else is there?

    Sage: The pages inside.

    Simpleton: You mean all those repetitive black marks, the ones that resemble a box of Fruit Loop alphaghetti filmed in black and white?

    Sage: Their arrangement matters.

    Simpleton: You mean like tea leaves?

    Sage: [Takes a slow sip from his steaming mug.] Exactly right—like tea leaves filtered through a brain worth having.

    Simpleton: [Thinks really hard.] Are you dissing mathematicians?

    Sage: Not at all. Leaves produce more symbols at lower intensity, beans produce fewer symbols at higher intensity. You can't judge a theorem by its cover, because there's never enough pages to bind.

    Simpleton: I see what you mean about not judging a book by its cover: some books don't even have covers. Very subtle, but I'm onto your koan. For example, I can still judge a theorem by it's lack of cover. That would still work out just fine.

    Sage: Sure—suit yourself. Looks good on you. Now if you will please excuse me for five minutes, I need to hit the head.

    ———

    [*] Alfred Renyi to Paul Erdos: "A mathematician is a device for turning coffee into theorems."

    For obvious reasons, this quip probably originated in Hungarian, not German, even thought the Satz pun is pretty good.

  78. Poor Adobe by Mistakill · · Score: 1

    Companies like Adobe will have to support updates for Adobe CC (LR/PS etc) for Intel CPU's for a while, while developing ARM (or whatever Apple is actually doing) versions as well (meanwhile trying to lock out Adobe PS CC etc from being run on some idiots iPhone (not the mobile version, the full version... some smuck is going to try to use the full version on their phone)

    I also think Apples sour grapes with nVidia needs to end, im not an nVidia fanboy but think Apple looses a lot of potential locking out nVidia but thats my 10c

    1. Re:Poor Adobe by drinkypoo · · Score: 1

      Adobe will celebrate this because it means that all those perfectly good and very useful pirated rips of PhotoShop that are i386 binary will finally be rendered useless

      386? What's the last version of PhotoShop that ran on NT4, or Sun386i? 6.0 on NT4?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  79. Just move to a CLR along the lines of .NET by Assmasher · · Score: 1

    ...but take lessons from the warts in the runtime.

    Moving their macs off of Intel is a terrible idea as people will then only be purchasing the cheapest possible mac as a compiler host for iOS (if they need to do so.)

    I have a MacBook Pro right now because I can triple boot it between Linux, macOS, and Windows - they do this and I'd rather just have one of the new minis sitting on the corner of my test for iOS builds...

    Unless that ARM chipset will support x64/x86 instructions (which is technically possible but would be weird.)

    --
    Loading...
    1. Re:Just move to a CLR along the lines of .NET by drinkypoo · · Score: 1

      Unless that ARM chipset will support x64/x86 instructions (which is technically possible but would be weird.)

      I don't know that I think they'll do this, but it's actually an intriguing idea. What if they put in a bunch of well-connected ARM cores, and an x86 decoder? They could use the ARM cores as functional units. The performance might take a hit, but most users would probably never notice so long as they did a good job with the I/O.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Just move to a CLR along the lines of .NET by XArtur0 · · Score: 1

      Gives me an idea, would it be possible to make a Hardware-CLR?
      As in, a CPU that takes IL as Native Instructions?

      I don't know how the GC would work, if any.
      Also, the .NET Framework relies on P/Invokes to the Host OS libs for many things, but that is another story.

      Anyhow, I deviated too much from the OPs point.

    3. Re:Just move to a CLR along the lines of .NET by Assmasher · · Score: 1

      Weren't there some 'Java processors' a while back that did something like this (terribly)? Certainly an interesting idea; however, everything comes down to cost in the end.

      --
      Loading...
  80. Crawling even further into their micro-niche by Chas · · Score: 1

    And sealing the entrance shut with successive layers of concrete and steel plating.

    Eventually, the Apple ecosphere will be COMPLETELY irrelevant.

    --


    Chas - The one, the only.
    THANK GOD!!!
  81. The CPU is hamstrung by the OS by tepples · · Score: 1

    Let me try to restate my understanding of the engine/frame analogy more rigorously:

    Even if ARM cores are powerful engines, the I/O and operating system wrapped around them in virtually all such ARM CPUs and SOCs make them unfriendly to serious productive computing.

    1. Re:The CPU is hamstrung by the OS by dj245 · · Score: 1

      Even if ARM cores are powerful engines, the I/O and operating system wrapped around them in virtually all such ARM CPUs and SOCs make them unfriendly to serious productive computing.

      Fortunately, Apply abandoned the serious productive computing market years ago.

      --
      Even those who arrange and design shrubberies are under considerable economic stress at this period in history.
    2. Re:The CPU is hamstrung by the OS by drinkypoo · · Score: 1

      Even if ARM cores are powerful engines, the I/O and operating system wrapped around them in virtually all such ARM CPUs and SOCs make them unfriendly to serious productive computing.

      Wait, that's two separate things. The poor I/O is real, but if Apple is making a desktop or laptop version, they can just make it with better I/O. The poor OS is not real, though. iOS is OSX, with different libraries for making GUI applications, but with the same underpinnings. Android is Linux, at least for now, and similarly uses the real underpinnings. The poor I/O is real, the poor OS is not... it's all the I/O. The notable recent exception was WinCE, but even Microsoft got over the bad OS thing before giving up on ARM mobile. Too bad for them that they didn't do it dramatically sooner, or they might have been a serious contender.

      At least on Android, you can simply install a typical Linux userland, and then go on to use it. And even when using an Android GUI, you've got the NDK to work with. The OS ain't the problem.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:The CPU is hamstrung by the OS by EETech1 · · Score: 1

      I kinda wish Microsoft would have kept WinMo (ce) going. I'd probably still be using it today.

      It was nice having a phone that was not designed as a surveillance tool.

    4. Re:The CPU is hamstrung by the OS by drinkypoo · · Score: 1

      I kinda wish Microsoft would have kept WinMo (ce) going. I'd probably still be using it today.

      Why? It was crap.

      It was nice having a phone that was not designed as a surveillance tool.

      You don't think Microsoft would have put telemetry in wince as surely as they did in win?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:The CPU is hamstrung by the OS by tepples · · Score: 1

      So if someone were to put the core into an environment that was more like that of a x86-64 core - it would still be limited by the environment it used to be put in?

      It would not be. However, that's a big "if", as I don't expect Apple "to put the core into an environment that was more like that of a x86-64 core". Instead, I expect Apple to make Gatekeeper more strict on ARM than it currently is on x86-64.

  82. History repeats. by Anonymous Coward · · Score: 1

    It will kill more than just boot camp. When Apple went from powerpc to x86, they didn't hesitate to break compatibility with everything that came before (great way to get everyone to buy new hardware). I have no doubt they will use this opportunity to do it again.

  83. Re:Torvalds rant: X86 development vs Arm Developme by caseih · · Score: 2

    I'm helping others declutter by storing them.

    In terms of time (mainly) and money it would be cheaper for someone to buy one new than for me to wrap one up and ship it to a fellow geek.

  84. Welcome back by AHuxley · · Score: 1

    Its back to PPC like code.
    Time to learn to code again.
    Ready for hours of code optimization all over again?

    --
    Domestic spying is now "Benign Information Gathering"
  85. The end is near by bornroot · · Score: 1

    Take that Hackintoshians!

  86. Re: What about Boot Camp? by scdeimos · · Score: 1

    Apple's been preparing for this for several years already. iOS deployment to iTunes has included the IL output from LLVM (although Apple variously calls it Intermediate Representation or Bitcode) that Apple can recompile for new CPU targets at their end as and when they arrive. I wouldn't be surprised if that's been happening for MacOS apps as well.

  87. Re:Torvalds rant: X86 development vs Arm Developme by drinkypoo · · Score: 1

    In terms of time (mainly) and money it would be cheaper for someone to buy one new than for me to wrap one up and ship it to a fellow geek.

    Sell them as a bundle, and/or sell them to a local. If you leave them lying, they're just going to turn into landfill sooner or later. Many people are actively using devices like those today.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  88. Re:Torvalds rant: X86 development vs Arm Developme by goombah99 · · Score: 1

    Yes indeedy --in theory-- but the optimizations are everything that makes tensorflow useful. Like SIMD or the pinning of memory for GPU transfers. So no, in reality. You might as well say that one could just compile Linux or Windows or Mac OSX for any cpu architecture just by flipping a command line arg.

    --
    Some drink at the fountain of knowledge. Others just gargle.
  89. Re:Irrelevant to me by drinkypoo · · Score: 3, Interesting

    What if it's not a laptop, or you don't want to flip it shut? I mean, on a Mac you can tap the power button and there's a Sleep button there

    What you do is open the gnome-power-manager preferences, select the "general" tab, and then select what you'd like to happen when you press the suspend button, and the power button. This is essentially the same as on Windows. If I want to reboot Windows, I pick reboot out from the menu; if I press my power button, the machine goes to sleep. I have a hard reset button if I need it; macs used to, if you snapped the programmer's key into place. When I boot into Linux, the buttons work just the same, even though I am using gnome3. I don't spend much time in Linux these days, or I would probably install MATE.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  90. 30 years for Unix on a handheld, why so long? by perpenso · · Score: 1

    If someone had told you in 1978 that in 30 years you would be able to run your Unix programs on a device that fits in your pocket, would you have dismissed it as a fucking toy?

    No we would have complained that it can't possibly take 30 years.

  91. Dual Boot MacOS and Windows is Critical by perpenso · · Score: 5, Informative

    So this means no more boot camp as well?

    Sure, but who wants that

    Apple's market share literally doubled after switching to Intel and allowing Windows to dual boot. One of the biggest stumbling blocks to get people to switch to Mac was their need to use Windows (and before that MS-DOS) software. Once you could dual boot MacOS or Windows you no longer had to choose PC or Mac, you could have one computer that could run either software family.

    Regarding emulation, it worked but was not practical. It barely works today where it does *not* have to emulate the CPU architecture. A switch to ARM would impose a huge burden on emulators and seriously and negatively impact performance.

    While Microsoft might offer Windows on ARM you would have a lot of PC software that will not be recompiled for ARM. So dual booting ARM MacOS or ARM Windows gets you back to the bad old days of having the choose PC (ie x86) or something-not-PC. Good news for Dell, HP, etc ... bad news for Apple.

    1. Re:Dual Boot MacOS and Windows is Critical by mjwx · · Score: 2, Insightful

      So this means no more boot camp as well?

      Sure, but who wants that

      Apple's market share literally doubled after switching to Intel and allowing Windows to dual boot. One of the biggest stumbling blocks to get people to switch to Mac was their need to use Windows (and before that MS-DOS) software. Once you could dual boot MacOS or Windows you no longer had to choose PC or Mac, you could have one computer that could run either software family.

      Regarding emulation, it worked but was not practical. It barely works today where it does *not* have to emulate the CPU architecture. A switch to ARM would impose a huge burden on emulators and seriously and negatively impact performance.

      While Microsoft might offer Windows on ARM you would have a lot of PC software that will not be recompiled for ARM. So dual booting ARM MacOS or ARM Windows gets you back to the bad old days of having the choose PC (ie x86) or something-not-PC. Good news for Dell, HP, etc ... bad news for Apple.

      Apple's computers are an abbreviation. Their money comes from locking people into the Apple ecosystem. Right now, with computers that can run Windows and act like general purpose operating systems (despite how limiting Mac OS is, you can still run unsigned code on it). No, this cannot stand in the world of Apple. They have a new way forward, a better way where your Apple computer connects to your Apple phone and to your Apple tablet all of which can only install Apple approved apps from an Apple only store whilst listening on Apple approved headphones to Apple approved music all of which Apple collects 30% from.

      Apple doesn't care if Peter Programmer buys an Apple computer, you mean nothing to them. They want to force Helen Homemaker and Steve Salesman onto a 100% Apple platform with no escape. We saw this coming years ago (well I did, and if I saw it I'm sure I'm not the only one). Apple are ruthless at simplifying, reducing options, funnelling you into their way of doing things. They're not going to turn these things into giant IOS devices because they have to, but because they want to. It also won't happen overnight, but it will happen.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    2. Re:Dual Boot MacOS and Windows is Critical by perpenso · · Score: 1

      Regarding emulation, it worked but was not practical. It barely works today where it does *not* have to emulate the CPU architecture. A switch to ARM would impose a huge burden on emulators and seriously and negatively impact performance.

      First off, Boot Camp has NOTHING to do with Emulation.

      Agreed, mostly. I address dual boot and emulation as two separate things. Apologies if I was not clear about that. Although to be overly technical one's Boot Camp partition can be natively booted at startup or run via an emulator after having booted macOS.

      And as for losing x86 Windows Application access, Microsoft has already solved that with Windows 10 for ARM 64. It CALLS it "Emulation", but it actually provides x86 Windows Application Support through the use of a JIT Compiler, much like Apple did when transitioning from 68k to PPC. And that worked well enough that Apple was able to put-off rewriting/recompiling lots of pieces of MacOS (Classic) itself for a long time. That's because the "new host" CPU runs NATIVE CODE.

      I mentioned such binary to binary translation in another post, better than emulation, not quite as good as recompiling but often "good enough". The problem with Windows on ARM and translation of x86 code is that not all users will be able to move to that version of Windows.They may have a legacy version of Windows, they may not want to spend the money to buy a second version of Windows. Genuine emulation will be necessary for some.

      More so for emulation, less so for binary to binary translation, I found such things to largely be practical only for short tasks. Minutes not hours. After about 15 minutes the sluggishness would annoy me. I prefer dual booting to Windows for tasks taking hours. And natively recompiled apps seemed an improvement over running the translations. Generating a binary from source code rather than another binary has many advantages. But unlike emulations, translation is more likely to be "good enough" to be tolerable.

    3. Re:Dual Boot MacOS and Windows is Critical by perpenso · · Score: 1

      It barely works today where it does *not* have to emulate the CPU architecture.

      I'd say it more than barely works, I run quite a few Windows apps with Parallels and it works great! Maybe not perfect, but far better than barely works. But I am concerned about this switch; being able to easily run Windows apps when I need to has been a huge benefit for me...

      Personally I can only tolerate emulation for shorter tasks. Things taking minutes rather than hours. For the latter I will reboot into Windows. I'm often overly annoyed by the sluggishness.

  92. Torvalds is mistaken by perpenso · · Score: 1

    Torvalds is mistaken, price dictated x86 Linux replacing traditional *nix RISC vendors. The argument regarding developers wanting the same hardware in the field as in their desktop PC is erroneous. Most *nix software does not care what the underlying hardware is. They may want the same operating system and software stack but that is something quite different than the underlying hardware. If RedHat and Ubuntu offered their respective Linux distributions on ARM and the ARM servers were less expensive to buy and operate they would be used by many and their server side software would not know or care if its Intel or ARM under the hood.

  93. x86 binary to ARM binary translation, native code by perpenso · · Score: 1

    Similar background :-)

    In theory apps will need to be recompiled by the developers. That is probably the best solution.

    However another solution is to have software translate an x86 binary into an ARM binary. You still get native architecture speed but perhaps there is inefficiency since you started with an x86 binary, Source code would have provided more information and more opportunities to optimize the code. I'd lean towards this binary translation solution. Universal and likely good enough. To be clear I expect macOS, its bundled application and Apple's productivity applications will be recompiled and fully native. This binary translation is more for the 3rd party mac apps.

    Then there is emulation. Doable but there is a big performance hit when you have to emulate the CPU architecture. When Apple switched to Intel and PC emulators no longer had to emulate the x86 architecture emulation the Windows environment became practical for some users.

    The folks suggesting that iOS will replace macOS are almost certainly guessing wrong. macOS and iOS share some core operating system code and various APIs, but where their respective libraries and APIs begin to differ tends to be related to the user experience and the mobile user experience isn't going to work on a laptop or desktop. I think Apple has already made comments along these lines.

    Additionally, until MS Windows on ARM is a common office and household operating system I doubt Apple will completely abandon Intel. Apple's marketshare doubled when users no longer had to choose PC or Mac, when they could run both macOS and MS Windows on the same computer. Boot into either operating system as required by the software they needed to run. Since Windows on ARM is not a common operating system, since Windows on x86 is what people overwhelmingly have and will need to be able to run ... switching to a non-x86 CPU would be a return to the bad old days where people had to chooser Mac or PC. Presumably bringing back that choice would cut Apple's sales in half.

    What people *might* be grossly exaggerating is a chromebook competitor. An ARM based Mac where macOS and its bundled applications and Apple's productivity software (word processor, spreadsheet, slideshow, etc) have all been recompiled for ARM. There are many users who would use nothing beyond these apps and a web browser. For them MS Windows and 3rd party Mac software are irrelevant and an ARM based Mac that has much better battery endurance would be great. Think of something like the MacBook Air moving to the ARM CPU but the MacBook Pro staying Intel.

  94. Apple will loose about half its users by perpenso · · Score: 1

    What about Boot Camp? Presumably it goes away. I wonder how many people will find running Windows in a VM (especially one that has to emulate the CPU) will find have problems with that solution?

    Look to the PowerPC era, emulation worked but it was not really practical to use. When Apple switched to Intel their marketshare doubled. With Boot Camp people no longer had to chooser Mac or PC, they could have both on the same computer. Switch to ARM and we are back having to make that choice.

  95. Re:& "Mr. T." is 100% correct (for me @ least) by EETech1 · · Score: 1

    Dang, I thought maybe you made the Linux version because I asked you to?!

  96. Re:Torvalds rant: X86 development vs Arm Developme by spire3661 · · Score: 1

    Considering ALL of cloud is x86, i am not compelled by your argument.

    --
    Good-bye
  97. Re:Torvalds rant: X86 development vs Arm Developme by spire3661 · · Score: 1

    Bullshit and i7s are DESKTOP SKUS

    --
    Good-bye
  98. Never mind this news by internet-redstar · · Score: 1

    The news that Apple is dumping Intel has been there periodically about every 3-5 years,... Without any doubt every time they are negotiation a new deal with Intel... Sad!

  99. Re: It was nice knowing you by shmlco · · Score: 1

    GeekBench says otherwise.

    --
    Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
  100. Strict W^X policy on iOS by tepples · · Score: 2, Interesting

    The poor OS is not real, though. iOS is OSX, with different libraries for making GUI applications, but with the same underpinnings.

    One critical piece of the underpinnings differs: it's impossible for iOS applications to flip a page from writable to executable. Only the system executable loader can do that. The strict W^X policy on iOS makes it impossible to run a compiler like that included with Xcode or a JIT like PyPy. Any tool for programming on a device must be a full interpreter, like CPython or Swift Playgrounds, and a user ends up wasting most of the performance of a powerful ARM CPU on the overhead of this interpreter. This is what I meant by the usefulness of the iPad product being hamstrung by Apple's policies embodied in the OS.

    1. Re:Strict W^X policy on iOS by tepples · · Score: 1

      Why does everyone always start talking about the constraints of iOS when discussing ARM on the Mac?

      Because makers of computing devices have used architecture transitions as an excuse to ramp up restrictions on developers. Microsoft did so with Windows Vista, which introduced mandatory kernel-mode code signing during the transition from x86 to x86-64. Microsoft also did so with Windows RT, which couldn't run code from outside the Windows Store without an (initially paid) developer account. Following this pattern, Apple might add mandatory Gatekeeper to macOS for ARM, such that turning it off works for only 7 days at a time like a free iOS developer account.

  101. Re:Torvalds rant: X86 development vs Arm Developme by DontBeAMoran · · Score: 1

    The only good bug is a DEAD bug. /Starship Troopers

    --
    #DeleteFacebook
  102. Re:Torvalds rant: X86 development vs Arm Developme by godefroi · · Score: 1

    Wait, so the i7 in this Precision 5520 is a desktop SKU?

    --
    Karma: Poor (Mostly affected by lame karma-joke sigs)
  103. Re: "awkward period" == 10+ years/Look at alternat by middlefeng · · Score: 1

    No, they aren't. They officially claimed OpenGL had been replaced by Metal for more than 5 years, and no Metal-enabled app can run on x86/64 macOS.

  104. Re:Torvalds rant: X86 development vs Arm Developme by thereddaikon · · Score: 1

    Great point. ARM doesn't have a basic system specification like x86 PC's do. While its all kind of adhoc and a mess PC side, it does work. Originally the PC spec was just the IBM 5150 and as time went on it extended incrementally. But at least it has one. IMO the push to mass adopt ARM is not a good thing for the Linux world. Its not an open architecture and as you pointed out, the transition is fraught with technical issues. We would be much better off going to RISCV. Nobody "owns" it and the community can develop and agree upon a basic system platform spec. There is still a risk (heh) of fragmentation, one of FOSS' biggest weaknesses, but is the RISCV foundation can agree on a basic general purpose platform spec in the next few years then we can start making truly open PC's.

  105. Re:ARM doesn't make make/sell CPUs, they sell the by Megane · · Score: 1

    Apple has a very old ARM license which allows them to make their own custom cores, which they do for iPhone/iPad. Most modern licensing requires using official ARM cores, to which custom SoC bits are added.

    --
    #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
  106. Re:Maybe they should look at the nice new Power CP by Megane · · Score: 1

    Stayed with what? Motorola wanted to make low-power embedded CPUs with 32-bit cores and pathetic front-side buses, and IBM wanted to make super-powered server CPUs that required liquid cooling. Nobody was making consumer desktop/laptop CPUs, so all Apple could do was put the toy CPUs into laptops and the monster CPUs into desktops.

    --
    #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
  107. *Not* going to turn Macs into iOS devices by perpenso · · Score: 1

    They are not going to turn computers into giant iOS devices.
    They are not going to lock out 3rd party software distribution for computers.
    They are probably not going to to switch all Macs to ARM.

    What they are probably going to do is launch a MacBook Air that is ARM. macOS, its built-in applications and Apple's optional apps on the Mac App Store will be recompiled for ARM. Some people need nothing more than a mail client, a browser and a productivity suite like Apple's Pages, Numbers and Keynote. Such people will get along quite nicely on such a system. The MacBook Pro will remain Intel based for Windows support and legacy software support with full performance. Apple will encourage 3rd party developers to recompile for ARM but they will also probably offer an x86 binary to ARM binary conversion tool for legacy software that is not recompiled. This converted code will run better than x86 in an emulator but not as well as recompiled, in short it will probably be "good enough". Over time an ARM based Mac will become more capable for people that do not need Windows. However for the huge segment of Mac users that do need Windows some Macs will remain Intel based. Again, when Apple went Intel their marketshare doubled as people no longer had to choose PC or Mac, when people could get both on the same machine. Apple will continue to offer such machines however perhaps not at the entry level, MacBook Air, etc.

    1. Re:*Not* going to turn Macs into iOS devices by JabrTheHut · · Score: 1

      Really? Here I thought they were just going to release a version of the iPad Pro with a built in keyboard, similar to the surface tablet....

      I think you people are overthinking things.

      --
      Work like no one is watching. Dance like you've never been hurt. Make love like you don't need the money.
    2. Re:*Not* going to turn Macs into iOS devices by perpenso · · Score: 1

      That's still an iPad not a Mac. In the comment, by "computer" I was referring to a Mac. As indicated by the subject line.

      If you want to argue about a "computer" in general I'm fine with that. I hate that smart phones are called "phones", I think of them as handheld computers given that phone is a relatively minor feature and they are really a more general purpose device. A computer with lots of built-in sensors. But Macs becoming iOS devices, all Macs only getting software from the Mac App Store, all Macs going ARM, no, these things are highly unlikely.

      Plus Apple doesn't consider an iPad Pro with a keyboard to be a "computer", haven't you seen the TV commercial? :-)

    3. Re:*Not* going to turn Macs into iOS devices by JabrTheHut · · Score: 1

      I can honestly say that I have not seen the commercials. (Who has a TV these days? Why watch commercials? Are you 90 or something?)

      The line between computers and tablets has blurred considerably. There's always been blurriness between different types of computing and software - where did the desktop end and the server begin? Linux was a desktop OS that made it onto the server? MS called Windows an operating system. There's always been blurring, this is just more of the same. Apple can stick a keyboard and a not so power constrained ARM chip in an iPad and call it a new product.

      -

      --
      Work like no one is watching. Dance like you've never been hurt. Make love like you don't need the money.
  108. Re:Torvalds rant: X86 development vs Arm Developme by drinkypoo · · Score: 1

    ARM is wonderful for the low end, but for development, you can fuck right off with that noise.

    Development is generally highly parallelizable, so throwing more cores at it is a viable strategy. The big problem with current ARM computers when it comes to development is (yep it's that time again) not enough RAM. And, of course, not enough I/O. Both are highly solvable problems.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  109. Re:"awkward period" == 10+ years/Look at alternati by thereddaikon · · Score: 1

    Apple hasn't made servers in a very very long time.

  110. Re: combine this with Linus' recent thoughts about by weilawei · · Score: 1

    Nifty board! As a matter of fact, I just bought 2 OrangePi PC2's with the Allwinner H5 onboard (quad-core A53). 43$ shipped for the both of them, though less powerful than this board or my phone by far.

    However, I want to try them out instead of the RK3999 chipset because there's indications of OpenBSD support in addition to Armbian and Lubuntu, and I think it'd be fun to play with some ideas I have at a bare metal level. If someone got the RK3999 running OpenBSD, I'd be much more interested, because there's more powerful boards available--like the one you showed.

  111. Re: "awkward period" == 10+ years/Look at alternat by david_thornley · · Score: 1

    If you're using them to do real, professional, paid work, Apple computers are reasonably cheap. If you're using them at home for things that won't make a profit, they're expensive.

    --
    "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  112. Not quite right by SuperKendall · · Score: 1

    That's actually not quite right - at the time they said that web apps were a "sweet" solution - but they never claimed native apps were a bad idea.

    In contract, has has said a number of times they think combining iOS and macOS is a bad idea. They can and will bring elements from one to the other that make sense, but they've always maintained keeping a difference is a good idea.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  113. Eat you own dog food by middlefeng · · Score: 1

    At least Apple's own engineers will be using Mac for their own work, unlike Microsoft engineers using Dell.

  114. Re:Torvalds rant: X86 development vs Arm Developme by rthille · · Score: 1

    If you're in an area with high geek density, posting to Craigslist and just leaving them on your front porch or equivalent may be a good way to get them in the hands of people who'd make better use of them, if that's a goal of yours.

    --
    Awesome furniture, accessories and cabinetry in Santa Rosa, CA: http://humanity-home.com/
  115. Re:combine this with Linus' recent thoughts about by tepples · · Score: 1

    But, more and more, I just use a bluetooth keyboard from Omoton and use Termius to SSH in to my servers and the laptop from my phone.

    That's fine if you already have a cellular data plan for other reasons or transit in your city has Wi-Fi. It's not so fine if, like me, you would have to upgrade from no data plan to a data plan in order to use the SSH client during the commute to and from the office. That's why I still carry a compact laptop for coding on transit.

  116. Re:combine this with Linus' recent thoughts about by weilawei · · Score: 1

    Sure, that's a valid use case. The big thing I miss about current generation unrooted devices is the lack of ability to compile (to machine code) and execute directly on the hardware. That's the big showstopper, and the reason I still have a laptop and server dedicated to providing "backend" support for the phone's role as primary device/smart terminal.

    The range of coding that can be done with an Android device, unrooted, right now, is in pretty rough shape. I might use QPython and QPython3 to do a few small things directly on the phone, but I run into limits pretty quick. If it's useful, that code is moved into a remote git repo and expanded with usage on a laptop, where I can more easily make use of various libraries and system resources. That's how the latest project got its start: I needed some answers on a project, and all I had handy was my phone. Later, it got a frontend for desktop usage.

    But, it's rare that I don't have connectivity. I'm happy to pay for the "unlimited" data plan. Between my wife and I, we blow through 60+ GB of traffic a month on two phones alone (we both have laptops, but both use a smartphone as a primary device). And frequently, the phone *is* the WiFi for my laptop. A more typical scenario is editing directly in Vim over an SSH connection, or, less commonly, grabbing a copy of the code to to work on locally in DroidVim via SFTP/git.

    As to tooling, I'm not an IDE person. I really like Vim, and that makes it very easy to be happy *and* productive on minimal systems--basically anywhere I can get a halfway decent terminal. (I'm a keyboard person all day long, so anything to avoid the mouse.) My concession to IDEs is NERDTree and a few bits of shell script. That also makes it trivial to dump my usual setup in a brand new machine, VM, headless, or otherwise, and have it be set up to do useful work.

    A little off-topic, but tl;dr: We need low-level hardware access on mobile platforms to make them really viable without having to screw around trying to root phones we should own in the first place. (I've said I like ARM, but I'd also really like to see a halfway decent, $30 RISC-V board.) And... to really make them useful, they still need fast cellular radios. My primary ISP, from a usage standpoint, is my phone provider, not my home ISP.

    This model isn't for everyone, but, I always remember wanting more out of my PDAs and calculators. I wanted a full-blown desktop replacement. We are nearly there, but low-level access is the big killer.

  117. Re:combine this with Linus' recent thoughts about by tepples · · Score: 1

    The range of coding that can be done with an Android device, unrooted, right now, is in pretty rough shape.

    Did rootless GNU environments, such as Termux and GNURoot, stop working in recent versions of Android? Some Slashdot users seem to swear by GNURoot combined with XSDL.

    But, it's rare that I don't have connectivity. I'm happy to pay for the "unlimited" data plan. Between my wife and I, we blow through 60+ GB of traffic a month on two phones alone (we both have laptops, but both use a smartphone as a primary device). And frequently, the phone *is* the WiFi for my laptop.

    Last I checked, carriers limited "unlimited" data plans' hotspot use (what you call "the phone *is* the WiFi for my laptop") to 10 GB per month. This means that for people who cancel home Internet in order to afford a cellular data plan, semiannual feature updates in Ubuntu or Windows might have to happen at a public library.

  118. Re:combine this with Linus' recent thoughts about by weilawei · · Score: 1

    Termux works, and I do use it, but it has weird issues with accessing parts of the filesystem and convincing tools to work right due to Android's limitations. I haven't looked at GNURoot. As to the 10 GB limit--that part is real and frustrating and stupidly artificial. I'm already using the transfer! I tried doing without the home connection, but I caved in after maybe 3 months. It does mean that any heavy duty network traffic for the laptop needs to be at home, work, or somewhere like a library, as you said.

    There are real issues with the setup, but the only way I see them getting addressed is with individual effort. I find the services of many large corporations extremely convenient, and really don't want to void the warranty on the newest device I use (afterwards, who cares? I've got an original T-Mobile G1, rooted, still works just fine, if horribly out of date), but I would also prefer to see computing devices owned by the people holding them.

    ARM is good for consolidating on a low-power many-core platform. Big iron, as mentioned elsewhere, still has real value. It just doesn't need to be in everything. Going forward, I'd really love to see ARM replaced with RISC-V, so that open hardware might actually be a useful thing.

  119. Re:Torvalds rant: X86 development vs Arm Developme by Ed+Avis · · Score: 1

    Yes and there's no such thing as x86-64 either, Intel marketing decided it was to be called "IA32-T" or some other nonsense. It's best to ignore the vendor's PR names in such things, particularly when they're as inane as "AArch64".

    --
    -- Ed Avis ed@membled.com