16 comments

[ 0.21 ms ] story [ 54.5 ms ] thread
Looks like it's harder to do a redbean in golang than it should be at the moment.
TBF, implementing Redbean in C required 3000+ lines and several third party dependencies. Of course it's more full-featured than this Go "proof of concept", but still, I assume it would be much easier to implement Redbean in Go than in C - as you would expect from a much younger "batteries-included" language.
Wasn't criticizing Go. It's the most Wirth-like language we have today with a vibrant ecosystem. Looking at their github, they're already on it.
What’s the requirement for having it all concatenated into a single file? What’s wrong with having the webserver binary and the ZIP file be separate?
I think it's just an interesting technical challenge, not for practical purposes (other than sites that never update content maybe).
(comment deleted)
It seems like both problems in the Go standard library should be fixable? They are corner cases that could be made to work without breaking anyone.
i believe you can achieve what you want with embed https://pkg.go.dev/embed
That’s not the same thing - with embed you have to recompile the server every time you change the page contents.
"just because you noticed its misspelled" is either a very clever joke or a marvelous coincidence.