► Join my Discord community for free education 👉 discord.com/invite/bDy8t4b3Rz ► Pre order (get 30% off) my Golang course 👉 fulltimegodev.com ► Become a Patreon for exclusive tutorials 👉 www.patreon.com/anthonygg_ Thanks for watching
Althought you've done a great job for the framework, I was hoping to see the underlying concepts that the framework is based on ("the actor paradigm" and what it is) Thank you for the video anyway
Am working on a payment gateway and am consdering golang only if I'll get a good actor model implementation. How can I tie any actor to reference which I can use to access it later in a diffrent context.
In my neovim v0.10, scrolloff doesn't seem to work anymore for this purpose. But you can also use ctrl+e/ctrl+y to scroll line by line. You can also use zz to center vertically the line the cursor is on, zb to move the line the cursor is on to the [b]ottom of the screen, and zt for the [t]op. The z* command also respect scrolloff
I really wish you take on more TDD design so I know how to test it. I love to start with testing because tests are needed no matter what, and they are harder to write if you never had tests in mind and realize a lot of refactoring has to happen to just make it testable
instead of using switch cases why not take advantage of state pattern and turn all those cases into objects? You can just send an object with a run method and when it's dequeued from the inbox we call the run method?
@@anthonygg_ In C/C++ you would use ABIs (Application Binary Interfaces). Not sure about Go, doesn't't Go have compiled binaries designed to interop? Your destination could simply have this binary as some form of contract. Another method is to have a TCP actor do all that. But you make a good point either way. Sometimes a simple solution is best.
In terms of usage, this solution is a bit closer to an async queue system like rabbitmq, but the nice trick is that holywood just spawns a new process instead of communicating over the network, and on the other hand, there is no way to send to the consumer of another team, for example. Am I right? Thanks for the video
what is the difference between using (traditional locks , channels) and this actor? from my perspective its only handling race conditions, please correct my understanding here
It would be better if you showed the native implementation and not some wrapper around it. Although I really like this pattern, I found out that some less experienced developers find it confusing. Another point, instead of sending objects, you can pass down behavior (functions) following the "Don't communicate by sharing memory, share memory by communicating." proverb. Also, being a blazingly fast is an outright lie. It is 10x times faster comparing to just having a struct with a receiver that does use a mutex in order to ensure thread safety
► Join my Discord community for free education 👉 discord.com/invite/bDy8t4b3Rz
► Pre order (get 30% off) my Golang course 👉 fulltimegodev.com
► Become a Patreon for exclusive tutorials 👉 www.patreon.com/anthonygg_
Thanks for watching
You are doing a great job Anthony ! Thank you for your time and availability of sharing this information !
Kudos for 10k Anthony 🎉
Althought you've done a great job for the framework, I was hoping to see the underlying concepts that the framework is based on ("the actor paradigm" and what it is)
Thank you for the video anyway
Will go more technical
Am working on a payment gateway and am consdering golang only if I'll get a good actor model implementation. How can I tie any actor to reference which I can use to access it later in a diffrent context.
You have the PID when spawning one. Use that PID.
in vim, you can keep some lines space at top and bottom by setting the option "scroll offset" to a value like 5.
example: ":set scrolloff=5"
also type zz for centering the line in the screen
@@peterszarvas94 every time i learn a new trick in vim i get a little burst of joy
In my neovim v0.10, scrolloff doesn't seem to work anymore for this purpose.
But you can also use ctrl+e/ctrl+y to scroll line by line. You can also use zz to center vertically the line the cursor is on, zb to move the line the cursor is on to the [b]ottom of the screen, and zt for the [t]op. The z* command also respect scrolloff
I really wish you take on more TDD design so I know how to test it. I love to start with testing because tests are needed no matter what, and they are harder to write if you never had tests in mind and realize a lot of refactoring has to happen to just make it testable
What's difference between using framework and using native channels?
you are best actor
This man is a beast
15:28 Instead of adding newlines at the end of the file to center things in VIM. Just hit “z” twice.
Oof, thanks my man! Life saving info. ❤️
非常棒的视频，我很喜欢这种教学风格！
Anthony you’re a homie
instead of using switch cases why not take advantage of state pattern and turn all those cases into objects? You can just send an object with a run method and when it's dequeued from the inbox we call the run method?
Well, hows that going to work over the wire?
Locally that would work great
@@anthonygg_ In C/C++ you would use ABIs (Application Binary Interfaces). Not sure about Go, doesn't't Go have compiled binaries designed to interop?
Your destination could simply have this binary as some form of contract.
Another method is to have a TCP actor do all that.
But you make a good point either way. Sometimes a simple solution is best.
finaly, VIM!!!
Sorry I let you down. Im back.
If possible can you publish your Vim setup video or if a doc which we can follow?
Thanks for the video! What plugins do you use for autocomplete and errors colored?
lsp-zero
In terms of usage, this solution is a bit closer to an async queue system like rabbitmq, but the nice trick is that holywood just spawns a new process instead of communicating over the network, and on the other hand, there is no way to send to the consumer of another team, for example. Am I right? Thanks for the video
You mean over the network?
@@anthonygg_ I mean communication is between golang and OS instead of AMQP or other network protocol
Does it even make sense to call `e.Send` in a goroutine? Since it's only sending a message and not actually handling it, right?
Correct doesnt make sense, but just want to show the safeness of it in case you find a usecase to actually do it in a goroutine
So, is it a PUB-SUB system like redis or kafka?
Awesome
i purchase the course but why there is no content
The content is gradually coming over the month of april. By the end of april all will be available for your lifetime
Join the discord I will add you to the course channel
what colour scheme is that please?
Gruvbox
@@anthonygg_ sorry to ask again, but do you have a link to it, as the normal gruvbox looks a lot different :(
what is the difference between using (traditional locks , channels) and this actor? from my perspective its only handling race conditions, please correct my understanding here
Thankx for your videos, they are amazig! +1 sub from me
You should make a 2d game with this use case! If you have time**
dope
helloworld example with send worked - trying the code-along version again.
So basically, we're doing a an IPC (spawning a process and communicate) + a reducer based on type :p
Pretty nice
yay vim diesel
LMAO! This is it. That quote is mine now. Thanks buddy
At this point the SetState message is not working for me at all with exactly your code.
Will erase the whole project and try again.
It would be better if you showed the native implementation and not some wrapper around it.
Although I really like this pattern, I found out that some less experienced developers find it confusing.
Another point, instead of sending objects, you can pass down behavior (functions) following the "Don't communicate by sharing memory, share memory by communicating." proverb.
Also, being a blazingly fast is an outright lie. It is 10x times faster comparing to just having a struct with a receiver that does use a mutex in order to ensure thread safety
it is still faster though, right? go is blazingly fast itself, i dont see that as a lie
routines leak when testing the example tcpserver....
Doesnt matter, its an example not a copy paste thing. Its an example to give you an idea. And if you want, make a pr and fix
The next episode make go work on beam 😂
Golang basically is a python who scales better 😅😊
Thats actually true.
And has types!
Now try Emacs
anthony I would be tempted to sign up to fulltimegodev is it were a reasonable monthly fee.
Elixir - erlang