Oh please no no NO, do not give them the idea to install more mobile towers. Do it right, run the fibre to the premises. Mobile network towers are not a substitute for fibre network that'll be useful for 50yrs+, where's we'd be constantly having to change the towers every ~15 years if they want to keep up with the latest and as the frequency increases we have to typically install more towers per given area.

The throughput from towers also falls off at a more rapid rate due to contention compared to fibre.

No matter how good mobile/radio towers get, the limitations of bandwidth of the carrier frequency from the Shannon limit mean that fibre/light will always be multiple magnitudes superior.

NBN is a clusterf**k, thank you Tony Abbott, Malcolm Turnbull, and even Stephen Conroy for taking a crowbar across the knees of Australia's networking future for the sake of appeasing Foxtel and Telstra (who pocketed a lot of our money for their crumbling copper ).

I repair these devices, I write software that's used by a significant portion of people repairing these devices.

While it's definitely popular to kick Apple when we talk about repairability, I do have to say that iPhones are typically a hell of a lot more serviceable than other brands. There's very little glue in them other than some small amounts for the screen/chassis seal and some gasket/bonds with small components such as microphones.

Macbooks are also typically easier to work on than PC laptops, though the batteries I do agree on most Macbooks (excluding A12xx and A14xx) are a pain, having to shuck them out like oysters.

Even on the information side,with schematics and boardviews, while not legally made available they are still more frequently available than other brands.

All that said, most techs would simply like the following;

    * Boardviews and schematics
    * Ability to buy custom parts ( such as ISL9240 / 9242 and SMCs )

A nice-to-have would be the ability to create new part bindings on the security/software side, though I see this as notably less likely.

Footage from the other night, timestamp is where the Microscope camera is being used with the HDMI-USB adaptor.

https://youtu.be/pt6pj7el00U?t...

I bought a pair of the very cheap HDMI-USB dongle adaptors from Banggood ( $12 ) for my live-streaming repairs, have to say, I'm impressed. They do have some small artefacts sometimes but overall for the price you can't complain. Worked immediately with linux + OBS.

Indeed. Software seems to now be interpreted as abandoned when it isn't constantly churning. As one asymptomatically approaches zero bugs and no further feature requirements for what ever reason it becomes a violation of natural software development laws and must be outcast as dead.

Yes, there's a lot of possible things to clean up with X.org but at the same time it's damned nice to not have the constant churn of updates.

^--- this definitely. So long as ssh -X is supported, I'll be content; without that, I'm not going anywhere.

Curious as to the methodology used for the JDPower surveys;

First thing to mind is; Do all defects carry the same weight ( paint chip, leaky oil seal, faulty transmission ) ?
Second to mind is; Is the level of defect inspection the same ( "It's a Tesla, I better check the whole car twice over", vs "I'll see how I go" ) ?

No chance of cut-pasting the context/constraints/limits of how that was computed (save the rest of us having to go to the paper directly) ?

Regardless of the quality of the OP's analogy/parallel, the reality is still that the "nm" numbers from the fabs are primarily branding of the process as opposed to explicitly adhering to some standard between the fabs.

I remember when they (Moz) put all the effort in to the XUL UI system, and maybe it was coincidental but I recall performance going to the dogs after that. Above and beyond everything else, the lacklustre performance keeps pushing me back to Chrome over Firefox, which is sad, as I've been using Firefox from back in the days when it was first spawned from the Netscape code and Phoenix ( still prefer the name :( ).

1.2.13 was a great kernel. Held on to that a long time, then 2.0.39 became my next stable hop, but never was a fan of 2.2 or 2.4.

Perhaps closer to 30 years old for those panels or they're some new emerging PV tech still being developed ( often they have lower % but also lower production cost or environmental cost). So far as crystalline PV, they've never been below about 12%, even back in the 1980's. Some real BS being poured in to that movie for sure.

While it could be a lot better, this is definitely a welcome improvement all around. Going to be 12~24 months though before we get access to boardviews and schematics, if we're lucky, and who knows what annoying new "unique" chips Apple has thrown on the board ( like the ISL9240, just to mess with us ).

Looking forward to seeing the whole A17xx/19xx range just go away, it's an annoying set to repair, hopefully the A1466/A1398/A1502 series can live long enough to get people through to this new series happily.

Because it stays with the item under repair. Repairs often require multiple sessions on the workbench and moved between several staff. The idea is that this eInk device stays with the specific job as it's moved around between staff, workbenches and holding slots.

Have just bought the dev unit, will see if it provides any real gains and solves the perceived itch. A bit of programming will be required, and maybe another NFC unit to make it work direct from PC (rather than their pc->bmp->sd->NFC), but it'll be a nice project, or a waste of $100 USD.