Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MailCrab

tweedegolf.nl

Post reply on HN
Print view View original

21–30 of 36 posts

Re: MailCrab

#21

Post by Ocha »

brightball wrote: post #10

For shared non-production environments, I’ve always been a big fan of Mailtrap.io in this space. Same idea of faking delivery but puts it in a location where non-devs can access and review it. https://mailtrap.io/

Also, there is https://mailsnag.com that has more generous free plan and error simulations. Helped me uncover couple bugs in my projects

Re: MailCrab

#23

Post by xslvrxslwt »

achairapart wrote: post #11

In this space there is also Mailpit[0], written in GO, runs from a single binary (also has Docker images). [0]: https://github.com/axllent/mailpit

According to Discord, Go was (or at least it used to) cause huge latency spikes because of it's GC - they've rewritten it in Rust and now it's A LOT faster, without any latency spikes.

https://discord.com/blog/why-discord-is-switching-from-go-to...

Re: MailCrab

#25

Post by joaonmatos »

xslvrxslwt wrote: post #23
achairapart wrote: post #11

In this space there is also Mailpit[0], written in GO, runs from a single binary (also has Docker images). [0]: https://github.com/axllent/mailpit

According to Discord, Go was (or at least it used to) cause huge latency spikes because of it's GC - they've rewritten it in Rust and now it's A LOT faster, without any latency spikes. https://discord.com/blog/why-discord-is-switching-from-go-to...

Which is a factor that really does not matter for a test server

Re: MailCrab

#26

Post by Scaevolus »

xslvrxslwt wrote: post #23
achairapart wrote: post #11

In this space there is also Mailpit[0], written in GO, runs from a single binary (also has Docker images). [0]: https://github.com/axllent/mailpit

According to Discord, Go was (or at least it used to) cause huge latency spikes because of it's GC - they've rewritten it in Rust and now it's A LOT faster, without any latency spikes. https://discord.com/blog/why-discord-is-switching-from-go-to...

300ms latency spikes on a particularly pathological production workload are irrelevant for the stated use case of a test email server.

Re: MailCrab

#27

Post by RobertRoberts »

It's finding systems like this that make HN valuable from time to time. I didn't even "think" to look for a system like this, and I could use it right now, and I find there are multiple other ones similar in the same posting from comments.

Re: MailCrab

#28

Post by kodah »

xslvrxslwt wrote: post #23
achairapart wrote: post #11

In this space there is also Mailpit[0], written in GO, runs from a single binary (also has Docker images). [0]: https://github.com/axllent/mailpit

According to Discord, Go was (or at least it used to) cause huge latency spikes because of it's GC - they've rewritten it in Rust and now it's A LOT faster, without any latency spikes. https://discord.com/blog/why-discord-is-switching-from-go-to...

The GC iterations they were talking about were during incredibly high throughout. Most users would not notice this. It's not some general indictment of Go.

Re: MailCrab

#30

Post by ptman »

xslvrxslwt wrote: post #23
achairapart wrote: post #11

In this space there is also Mailpit[0], written in GO, runs from a single binary (also has Docker images). [0]: https://github.com/axllent/mailpit

According to Discord, Go was (or at least it used to) cause huge latency spikes because of it's GC - they've rewritten it in Rust and now it's A LOT faster, without any latency spikes. https://discord.com/blog/why-discord-is-switching-from-go-to...

The go GC has kept evolving since.
Post reply on HN