Microsoft stopped supporting XP in 2006. This meant XP machines stopped getting security updates. The following year the WannaCry trojan infected 200,000 XP computers globally, including 80,000 in Britain's National Health Service (including some MRI machines). This caused a major crisis in hospitals, the cancellation of all non-urgent procedures and the reversion to manual methods of administration. This attack cost the NHS over £80 million. Nobody has ever estimated the impact on patient outcome.
There are many ways could try to "help" Dimitrios find ways to run modern Go code on XP, and help him extend the lifetime of his fleet of XP machines. But this would keep his organisation vulnerable to the next WannaCry attack. So I would suggest the most useful response is "don't do it". On Friday, 6 March 2020 19:11:44 UTC, Jake Montgomery wrote: > > On Friday, March 6, 2020 at 1:20:38 PM UTC-5, Amnon Baron Cohen wrote: >> >> Anyone who is able to put up with a 20 year old OS >> will be able to tolerate a 2 year old Go version... >> > > Dimitrios' question is a perfectly legitimate one. Your response does > nothing to actually answer the question. It also comes across as a bit > snarky. Just a friendly reminder that the Go community strives to be > "friendly and welcoming" to all. https://golang.org/conduct is a > worthwhile read. > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/f8b17c6b-55b4-4782-8b48-77855eea3e1f%40googlegroups.com.
