top | item 44885673 (no title) Chiron1991 | 6 months ago But "outdated code" isn't inherently bad, is it? v1 code is still supported by the stdlib and it still does its job, at least until Go 2.x drops. discuss order hn newest ayuhito|6 months ago In fact, v1 code usually uses v2 code under the hood, but with different options to maintain backwards compatibility.You still get performance improvements even if you don’t switch over to the new import! Grokify|6 months ago A good example is io/ioutil. It's useful to migrate to eliminate the deprecation messages, but you don't need to do it right away. load replies (1)
ayuhito|6 months ago In fact, v1 code usually uses v2 code under the hood, but with different options to maintain backwards compatibility.You still get performance improvements even if you don’t switch over to the new import! Grokify|6 months ago A good example is io/ioutil. It's useful to migrate to eliminate the deprecation messages, but you don't need to do it right away. load replies (1)
Grokify|6 months ago A good example is io/ioutil. It's useful to migrate to eliminate the deprecation messages, but you don't need to do it right away. load replies (1)
ayuhito|6 months ago
You still get performance improvements even if you don’t switch over to the new import!
Grokify|6 months ago