On Sun, Mar 8, 2020 at 9:31 AM Amnon Baron Cohen wrote:
>
> 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. S
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 hosp
I think the problem with compiling code written for go 1.14 with the
compiler for go 1.10 is not so much the minor language features like number
literals, but additions to the standard library which those applications
may depend on.
This means you may need to backport parts of the standard libr
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 a
Anyone who is able to put up with a 20 year old OS
will be able to tolerate a 2 year old Go version...
On Thursday, 5 March 2020 11:08:07 UTC, Dimitrios Trechas wrote:
>
> Dear colleagues,
>
> There are even now cases that a Windows XP is needed. The latest Golang
> compiler that could target XP
