Last Active
  • Compared: Apple Silicon M1 vs M1 Pro vs M1 Max vs M1 Ultra

    My last major Mac purchase was my 2012 Mac Pro (in 2013 I think). With some help from OpenCore and a Vega 56, it ran Catalina just fine. It now serves as a VMware ESXI host along with a 2009 Mac Pro I got used. Considering the 2012 and 2009 are essentially the same beast and were supported up until 2019, that 7-10 years of official support (plus a handful of tweaks for unofficial support the years following) is phenomenal.

    Likewise, our 2005/2006/2009 iMacs are rocking Linux, Lion, and Mojave, respectively, and the 2015 MBP's easily have a few more years on them. I think the oldest supported Mac we own is my wife's 2014 Mini.

    As for my workstation, it's definitely time to get a new powerhouse.  The fact that my M1 MBP can only run one monitor has been a bit limiting this past year.
  • Apple's M1 Ultra combines two M1 Max into a powerhouse chip

    The keynote also mentioned "the last" M1 chip in the lineup was Ultra.

    My bet is Mac Pro gets M2 (Max/Ultra) with each chip having 2 interconnects instead of one and perhaps 128GB per package, supporting quad/hex/octo configs within insane core counts.
  • Safari Translation uncovers March 8 event hints on international Apple sites

    The Dutch site says "Zo snel. Mis 't niet." (So fast. Don't miss it.)
  • T-Mobile will shut down Sprint's 3G network in March

    davgreg said:
    The only area rough around the edges is the millimeter wave 5G which is still problematic. I was in Nashville near Vanderbilt Thursday and the millimeter wave was up and running but the network not well optimized - crazy fast signals outside and nothing inside a simple brick restaurant. It was like this in Memphis recently as the same tech was rolled out but was much improved within a month or so.
    Physics.  The lower the frequency, the greater the likelihood it will travel far and go through objects.  Converse is true: the higher the frequency, the shorter the distance traveled and the more likely items are to interfere with that frequency's propagation.

    Lower bands = lower bandwidth channels; higher frequency bands = huge bandwidth channels.  Wider channels travel shorter distances; narrower channels can go further, generally speaking.

    The addition of 700MHz for LTE and 600MHz for 5G to T-Mobile's portfolio mean they will benefit tremendously from the lower frequencies, but you won't get crazy fast on those bands at great distance (I would argue that anything over 100Mbps to a cell phone > 1 mile away is pretty cool).

    Millimeter wave bands such as 28-47GHz, their Part 15 counterparts, 24GHz and 60GHz, and the lightly-licensed 70/80GHz E-band are amazing. I have deployed point-to-point links on 24-, 60-, and 70/80GHz, and they range in capacity from 1Gbps to 10Gbps.

    But those frequencies don't propagate through most solids. The antennas have to have line of sight to each other. At anything over 18GHz, rain begins to cause problems. 
    At 58-65GHz, oxygen absorbs the signal. Human bodies certainly have a blocking effect, and building walls most certainly will too.

    The 5G spec has all kinds of redudnancy/resiliency/aggregation built in to allow the phone's radios to switch back and forth between bands, based on what's available.

  • This is why Apple TV 4K Siri Remote scrubbing doesn't work on Disney+, other apps

    Apple's player API is extremely limiting if you want to do custom overlays, play more than one program at a time (2-,3-,4-up), or preview information from other channels or programs, etc. You also have limits on knowing if the content meets the user's content restriction criteria because they don't make that available unless you use their player controller. There's more than one reason there are dozens of custom player API's.  Most of them are lousy.

    I wrote my own that supported swiping to scrub through the stream, among other things. I wouldn't be surprised if Apple announces those API's at WWDC next week and all this hoopla is over nothing, presuming the dev teams adopt the new gesture recognizers.

    rundhvidwilliamlondonMacProforgot usernamefastasleep