Languages and libraries
go email library
SHOW HN2014
69points
29comments
#447of 2,272 in 2014
Top 20%of 2014 by points
How HN took it
CuriousMostly questions and neutral comments
2 positive, 5 neutral or asking, 0 mixed, 1 critical, out of 8 comments about the project. Thread score +0.05.
Privacy: 0 for, 1 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Useful library that will make life easier
From 1 comment
This looks great! It will definitely make my life easier. Thanks for sharing.
mratzloff on HN
Objections
Constructor naming: NewEmail instead of New
From 2 comments
Interesting choice of NewEmail() over the more idiomatic email.New().
tshadwell on HNLooks interesting. A couple suggestions: 1. People have already suggested this, but it would make more sense to make users call email.New() rather than email.NewEmail(). 2.…
dradtke on HN
Sending Gmail passwords in plain text looks risky
From 1 comment
Using plain text Gmail password looks like a red flag. ``` e.Send("smtp.gmail.com:587", smtp.PlainAuth("", "test@gmail.com", "password123", "smtp.gmail.com")) ```
zavi on HN
Required fields only checked at runtime
From 1 comment
I'm a novice at Go, but I've written several email libraries in other languages. Two lessons from that experience that I thought I'd pass on: - I've found it a more flexible…
curveship on HN
Requests
Constructor that takes required fields or a single-pass struct creation
From 2 comments
I'm a novice at Go, but I've written several email libraries in other languages. Two lessons from that experience that I thought I'd pass on: - I've found it a more flexible…
curveship on HNLooks interesting. A couple suggestions: 1. People have already suggested this, but it would make more sense to make users call email.New() rather than email.NewEmail(). 2.…
dradtke on HN
Plain-text email parsing support
From 1 comment
The easiest way and properly the right way to send email is in plain text. I would be happier if the package can add a parser to read all meta data from text, in the way of HTTP…
yixizhang on HN
Questions
Why NewEmail instead of New
From 2 comments
Interesting choice of NewEmail() over the more idiomatic email.New().
tshadwell on HNIn Go isn't `email.NewEmail()` more idiomatic? To be fair, you could write: e = &email.Email{ [fields and values] } The only thing NewEmail does is give you a pointer to an Email.
dkuntz2 on HN
Alternatives named
gochimp Go client for Mandrill
From 2 comments
https://github.com/mattbaird/gochimp
jwcrux on HNBeat me to it. I've been using gochimp to send emails with Mandrill templates (using MergeVars) with much success. I send them async when a user creates their post and log the…
elithrar on HN
go-guerrilla Go SMTP server
From 1 comment
Here's a Go smtpd. https://github.com/flashmob/go-guerrilla
hendler on HN