21 thoughts on “Go isn’t secure?!? ft. Low Level Learning | Backend Banter 053

  • I understand not having time to learn vim motions but configuring neovim then keeping the config with git or something else
    is not difficult i am noob when it comes programming compared to these guys but neovim configuration is not that hard.

  • 20 wpm on qwerty with the moonlander? I feel like that's impossible if you know how to touch type, when I first got mine, I basically was instantly at ~40 wpm only because I had bad touch typing habits. Now I'm comfortably within ~80-90 wpm which is identical to my speed on a normal keyboard, it took 3-4 days maybe.

  • could someone explain at 17:50 in detail how harnessing of specific function works?

  • I'm just glad to know there's another Sublime user out there.

  • Learning the low level stuff, even if its just learning the theory, helped me a lot as an engineer. Sometimes you dont need to know how its done, but understanding whats going on opens your mind to new opportunities

  • Man! I'm a java developer with 2 years of fullstack experience with react. And i also tought Spring did so much stuff magically. The day I learned Golang I created from the ground a http server to serve html files and I felt like I really did understand how the internet works. Listeningg to a port, parsing the header, finding a file in you directory based on the input you received. It was amazing

  • Can you interview Anthony gg , the Golang content creator

  • Guys you forgot to start your YouTube Chapters at 00.00 — that means you won’t get chapters parsed out of your description!!

    Just add to the beginning of timestamp list:
    00:00 introduction

  • What he said at 42:13 is exactly what I am going through. I bought a Moonlander too but I can only do average of 50 wpm, which is much slower than my 80-100 wpm. Because of this I cannot use it to do my work, but then I need to use it enough so I get to 80 wpm at least. The paradox is very apparent.

  • C is more low-level than Rust. Rust only allows its memory model, and it compiles down to LLVM, which is a great tool but since its a abstraction above machine code that c doenst have.

    The second point is the memory model of rust is predefined by rust, and it's the reason why it's in it current state won't become part of the kernel(yes there already drivers but in userland)

    The points you raised about hidden allocations are compiler-specific and can be controlled by using flags.

    C started as a programming language to build an OS. As such, it's possible to build anything with it.

    Regarding questions about security, safety, and memory issues, Rust would score higher, but not on being more low-level.

  • Total wasn't waiting for this 6 months ago…doing great everything is great and fine haha…hahaha…hahahaha

  • You should consider changing the name of this podcast to Go Banter. I know Go is your language of choice but sheesh.

  • Oh this will be golden! thank you so much for this!

Comments are closed.