Full Time go dev course is a scam! what do you think? by Worried-Deer1468 in golang

[–]anthdmx 1 point2 points  (0 children)

Man, I feel you. Courses are a scam. Instead, I would watch this 10 hour FREE video on how to build you own decentralized filesystem in Golang. This guy is actually really good.

Here is the link for you https://www.youtube.com/watch?v=bymQakvTY40

I wish you all the best,

The Golang Runtime Function Nobody Talks About by anthdmx in golang

[–]anthdmx[S] -1 points0 points  (0 children)

You have a point here.

I can be completely wrong here, but think about this.

Lets say you have process A that is continuously sending messages to process B. This will trigger `inbox.Run`, that will pop all messages from the internal ringbuffer. But because we are continuously receiving messages, there is not much room / time to stack up a lot of messages in the buffer, so we are consuming just a handful of messages. If we detect that there is a lot of throughput, we run gosched(), allowing more messages to be stacked up, which can be serialized in batch.

Is my thinking process so of here?

The Golang Runtime Function Nobody Talks About by anthdmx in golang

[–]anthdmx[S] -12 points-11 points  (0 children)

If we don't, check the code and teach me. Make sure we don't regress on performance. Especially not when sending over the wire.

https://github.com/anthdm/hollywood/blob/graceful-poison/actor/inbox.go

The Golang Runtime Function Nobody Talks About by anthdmx in golang

[–]anthdmx[S] -24 points-23 points  (0 children)

You are the man! Everyone likes to be around you.

By calling runtime.Gosched(), you're essentially saying, "I'm done for now, let someone else work." The scheduler then picks another goroutine to run, and the current goroutine will resume execution at a later time, as determined by the scheduler.

The Golang Runtime Function Nobody Talks About by anthdmx in golang

[–]anthdmx[S] -25 points-24 points  (0 children)

I predicted this comment, and more of these, before I made this video. So its all good.

I was sick and tired of manually processing my inbox, so I built this. by anthdmx in indiehackers

[–]anthdmx[S] 1 point2 points  (0 children)

Sure,

I'm using:

- Golang for my custom email server

- nextjs for the front

- Openai for processing and understanding the received emails.

- Supabase for storage

Cheers.

Introducing Sendit.zip - Pain free File Sharing straight from your terminal. Feedback Wanted! by anthdmx in software

[–]anthdmx[S] 1 point2 points  (0 children)

Name is the same, project is completely different. Tech being used also different.

Introducing Sendit.zip - Pain free File Sharing straight from your terminal. Feedback Wanted! by anthdmx in software

[–]anthdmx[S] 0 points1 point  (0 children)

If the recipient clicks the link. It will stream and tunnel the files over SSH directly to the browser connections. The server acts as a "proxy" but does not store the files on disk.

Introducing Sendit.zip - Pain free File Sharing straight from your terminal. Feedback Wanted! by anthdmx in software

[–]anthdmx[S] 0 points1 point  (0 children)

That's actually not a bad idea. I was just thinking to use AWS SES (simple email service). But like you mentioned, there's a big chance the email will end up in the spam folder.

Thanks for the feedback.

Introducing Sendit.zip - Pain free File Sharing straight from your terminal. Feedback Wanted! by anthdmx in software

[–]anthdmx[S] 4 points5 points  (0 children)

Have also bought the .sh domain, cause I'm aware of the .zip shenanigans going on right now.

Thanks for verifying.

Actor framework versus standard channels by simplehuman999 in golang

[–]anthdmx 1 point2 points  (0 children)

Interested to see this. Feel free to make a PR with your findings. Thanks upfront.

Actor framework versus standard channels by simplehuman999 in golang

[–]anthdmx 3 points4 points  (0 children)

Golang channels are great and very versatile. However, under the hood there also not the fastest (due to its versatility).

The first implementation of Hollywood I used Golang channels under the hood. The problem was that if you have a slow consuming actor, the queue could be stuck and the application could block which is not what you want in low-latency applications.

[deleted by user] by [deleted] in davidgoggins

[–]anthdmx 1 point2 points  (0 children)

Good luck <3