👀 Missed our live event? 🗓 Google Open Source Live is a monthly event where open source experts provide discussions around their areas of expertise & answer questions in a Q&A forum! 📜 Check out and register for our upcoming events with this link → goo.gle/GOSLNextEvent. 🔜 See you at the next Google Open Source Live event!
@@kamilziemian995 nil, that is more than enough reason "I call it my billion-dollar mistake. It was the invention of the null reference in 1965." - Tony Hoare
👀 Missed our live event?
🗓 Google Open Source Live is a monthly event where open source experts provide discussions around their areas of expertise & answer questions in a Q&A forum!
📜 Check out and register for our upcoming events with this link → goo.gle/GOSLNextEvent.
🔜 See you at the next Google Open Source Live event!
Every Go programmer should watch this talk.
Thank you Russ and Go team!
Thank you!
thank you
Ah, moving to rust
Can I ask why?
I would assume it is because of so many breaking changes.
The for-loop variable scope is a nasty one, it will break a lot of places when they fix it.
@@guibirow You mean breaking changes in Rust? Since Go is very, very stable in that regard, as this talk explain.
@@kamilziemian995 nil, that is more than enough reason
"I call it my billion-dollar mistake. It was the invention of the null reference in 1965."
- Tony Hoare
good luck 🤞