📝Get your *FREE Golang Cheat Sheet* - golangdojo.com/cheatsheet

Writing a byecode VM in go and that made me discover a lot of hard things lol

@GolangDojo

Жыл бұрын

Yup, building things is key

@myriaxont

Жыл бұрын

Me too. But i wrote 3 bytecode stack virtual machines. I think to try also some simple register VM. XD

@blade2663

Жыл бұрын

@@myriaxont I cant seem to understand register based VM. I know they are faster by quite a lot Can u give me any resources on implementing one?

@linkernick5379

Жыл бұрын

Isn't Rust more suitable for this task? (Deno and Wasmtime come to mind)

@myriaxont

Жыл бұрын

​@@linkernick5379 In this case Go is as blazingly fast as Rust. In most cases you need one allocation only, so GC isn't a problem. For strange cases you can use the pool. If you want to build a really complex but fast VM - you probably should use C.

After learning rust, these things in the video are very easy🌚

Lmaooo… I want that meme in the intro 😂😂😂

All very valid points.

I've seen your short appearance on Bogdans' Rusty channel, great job, and very nice humour! :) LOL, hahaha. And you also created chatseet? :) You guys have a lot in common!

Very interesting video!

I also bet that in go there are few quirks and bells and whistles according channels. What about them? What about 0-size data, etc. ? If will be nice to watch...

I don't know Go. I barely can read few paragraphs of Go Spec.

I don't no anything about Go(currently only taking a glance at...) but I find this video really interesting. I am a darned TypeScript programmer and it's fun to compare the type system btw TS and Go!

@cat47

Жыл бұрын

I feel like typescript is more oop than go. Also, "btw" stands for by the way, not "between".

@sungjuyea4627

Жыл бұрын

@@cat47 www.google.com/search?q=between+abbreviation&sxsrf=AJOqlzVhVBjwe5RqOcxURjfjJqxtQb3tag%3A1673107581239&ei=fZi5Y8SYDtfh2roPoJiq0A0&oq=between+a&gs_lcp=Cgxnd3Mtd2l6LXNlcnAQAxgAMgUIABCRAjIFCC4QgAQyBQgAEIAEMgUILhCABDIFCAAQgAQyBQgAEIAEMgUIABCABDILCAAQgAQQsQMQgwEyBQgAEIAEMggILhCABBDUAjoKCAAQRxDWBBCwAzoHCAAQsAMQQzoHCCMQ6gIQJzoMCAAQ6gIQtAIQQxgBOgQIIxAnOgQIABBDOgoILhDHARDRAxBDOg4ILhCABBCxAxDHARDRAzoICAAQsQMQgwE6EAguELEDEMcBENEDENQCEEM6CwguEIAEELEDEIMBOhEILhCABBCxAxCDARDHARDRAzoHCC4QsQMQQzoTCC4QsQMQgwEQxwEQ0QMQ1AIQQzoKCAAQsQMQgwEQQzoOCC4QgAQQsQMQgwEQ1AI6CAgAEIAEELEDSgQIQRgASgQIRhgBUNwJWP4fYPAnaAJwAXgAgAGmAYgBjwqSAQMwLjmYAQCgAQGwARTIAQrAAQHaAQYIARABGAE&sclient=gws-wiz-serp

@cat47

Жыл бұрын

@@sungjuyea4627 but it could also be seen as an acronym for "by the way," adding confusion. if you wanted to make it clear that you are using btw as an abbreviation and not an acronym, you could add a dot after the abbreviation like this: "compare the type system btw. ts and go"

@sungjuyea4627

Жыл бұрын

@@cat47 👍

Does go 1.20 address this?

You should make a video about why are more methods when accessing a pointer, than when accessing a variable, due to all go's syntactic sugar. I still don't get it.

IMO, Mistery 1: it does harm readability Didn't know much about the others.. thanks!

What are must-have extensions for go ? Oh & this is someone using FFMPEG with Go ( automated editing FTW) kzread.info/dash/bejne/goCNkrVxpLrIaLA.html

I'm trying to work on an MVP and learning Go Lang because I find it suitable for my project. But since I was unfamiliar I knew what I needed to do was to learn its syntaxes and constructs-Go lang's basics. In the end, I realized that was a waste of time (not 100% tho as some knowledge still remain vital). And why was that anyway? Upon getting started with its packages, I realized those knowledge I had garnered from learning Go lang basics didn't pan out to be that useful for implementing packages. The way the packages are exemplified for use are quite technical and a little challenging. Go lang is fun but as one gets started, it's a little hard to wrap the head around the so-called statically-typed language. For me, if the future or present me could advice my self who was getting started with go lang, then it would be to learn its packages... I discovered the basics were not much of a problem. I am doing some research on Go lang packages to discover how easy it would be for me to implement them and I landed on your channel. Hope I get the help I need!

I stopped watching after you prevent the “naked return” as you did not explain why it was introduced. Have you done summer research and find summering else beyond “it can harm readability”.

Another unknown use for Go: education! docs.google.com/document/d/1dpKjHGzzmpGe2-34x6fb3fhtEBW25OCwL9UvVEOwrPc/edit?usp=sharing