My understanding was that Fuscia is a new OS with a different Kernel (Zircon?) that can run android apps targeted at IoT devices and google had stated wont replace android, can you clarify?

We use imx6 industrial parts that are rated -40 to +95 C - that should be enough? Is the problem that you want something off the shelf? (We design our own solutions)

"Except for 13,000 people paying taxes, I'm sure that doesn't bring any money in."

I've a much better bit of sarcasm for you. Do The Maths.

For your 13,000 tax payers (the *original* estimate foxconn gave was 5,200 workers BTW), the investment was $4 Billion. That's an investment of $307,000 ish per worker. The average tax paid for an American over their *entire* working career of 40 years is around $188,000 (Source: Forbes).

At the current expected number of 1,000 workers, that's about $4m per worker.

Still look like a sensible deal?

Interesting article from boing boing yesterday :
https://boingboing.net/2019/01/30/sending-jobs-to-jina.html

Well, for years office for Mac was developed by an independent team and was widely considered to be a better product than office for pc. But donâ(TM)t let that get in the way of having a rant!

Whilst much of what Microsoft does may not be to everyoneâ(TM)s taste, itâ(TM)s a multi faceted company and to generalise would be wrong. Back when windows 95 was a piece of shit and I was starting to run Linux, I still used a Microsoft natural keyboard and intellimouse because they were great.

You know that the companies mentioned are all using un-supported internal APIs to implement their products right? They're called un-supprted for a reason! Feel free to criticise Apple for not realising that these APIs are handy and formalising / supporting them, but really the fault lies squarely with the third party companies.

Er, no. I suspect that you don't actually understand what DisplayLink adapters are or how they work... They're a (admittedly clever) way of creating what is an additional graphics adapter on the far side of a USB connection. Most normal docks are port replicators for interfaces within the machine.

Its not a standard protocol and certainly nowhere close to universal.

So... there are two scenarios :
1) Apple has crafted an update to specifically disable some 3rd party components
2) The third party component designer has failed to make a properly compatible part.

Despite the story sounding like theyâ(TM)re spinning it as (1) Iâ(TM)d be very surprised if it wasnâ(TM)t (2) as thatâ(TM)s the most likely if they can fix it with an update as reported. Whatâ(TM)s the news? Why should a manufacturer go to the effort of testing badly made replacement parts that they never claimed to support in the first place?

So, the data tells us then that most drivers ignore the red light and push it by 0.3 seconds or so to "scrape through". If the priority was safety, as well as issuing tickets, the time between one route going red and the subsequent route going green should also be increased by 0.3 seconds as well to compensate for behaviour. This would have more of an effect of reducing danger than a fine after the fact...

Well worth watching :
https://m.youtube.com/watch?v=Q124C7W0WYA

Sure - but do any of the FTDI interfaces properly support serial break yet? Annoying as ****

I think people have been saying that every year since i can remember on slashdot. Not entirely convinced that this one is any different!

Its an electrical device. Unplugnit before working on it. Its the first thing you get taught. End of.

Absolutely right, but not an issue in this case - it's completely isolated.

Broadly, building an ARM linux target via yocto, some in-house tools (portable C), a couple of GCC variants for other targets. Pretty standard stuff but the main thing is being able to able to address any potentially critical bugs and recompiling in the same environment at any point during the long lifetime of the system.

I think that's a little optimistic - I'm not aware of any long-lived embedded systems where the environment is updated in sync with the outside world. In practice this is nearly impossible (or rather, financially infeasible). Look at embedded systems developed for aerospace / medical devices / safety critical control systems for example. Once the system is tested, you don't do any major changes to the development environment or code!

And yes that does end up with a support nightmare, hence the question :-)