Re: [go-nuts] Re: Changing source code in order code to be supported from older Golang versions e.g. Go 1.10
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. So I would suggest the most useful response is "don't do > it". > > The key point here is risk assessment. Your points are what should be factored into such a decision. Personally, I would seek to upgrade out of such old software, and I think it is somewhat healthy that we eventually make operating vulnerable systems cost-ineffective. But you also have to factor in a lot of other considerations. Some people are somewhat forced to live with the risk of a software vulnerability because there are other parts of the infrastructure you cannot upgrade. So you do your best to wall off the rest of the world and keep using the old system. It isn't ideologically sound. It isn't a good viable long-term solution. But at times, the survival of a company requires you to gamble with the risk. Another observation is that to upgrade out of old software, you need to create an upgrade path that is viable. Since you are somewhat left behind, there are reasons for building some stepping stones along the way, perhaps not just tossing a hail-mary to the newest versions in the hope it fixes everything. Exploring these options might make it easier to handle the situation and slowly move away from a platform you don't want to be part of anymore. You strike the system and listen for where there is a resonance, you can use to lift yourself out of the misery. -- 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/CAGrdgiXbFOHkoQUQu%3Dp4RJN5afqO%2B_uMKrS6-BbPMGESgUCWNw%40mail.gmail.com.
[go-nuts] Re: Changing source code in order code to be supported from older Golang versions e.g. Go 1.10
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.
[go-nuts] Re: Changing source code in order code to be supported from older Golang versions e.g. Go 1.10
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 library to go 1.10 as well. -- 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/c404a006-caf9-4443-ba48-acb4af2084a3%40googlegroups.com.
[go-nuts] Re: Changing source code in order code to be supported from older Golang versions e.g. Go 1.10
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/a94315d3-933a-49b6-a5b2-de811d1e50ca%40googlegroups.com.
[go-nuts] Re: Changing source code in order code to be supported from older Golang versions e.g. Go 1.10
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 was 1.10. > > Is there anyone who had to write a source converter that could convert > recent Golang code to backwards compatible code (in case there is no > version clash/hell of different libs) ? E.g. number literals, source > modules to Golang 1.10? > > > Thank you in advance. > -- 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/5a2710ac-1782-4e24-8c6c-0a1b31e1671b%40googlegroups.com.
