3 ms·
Any sufficiently complicated distributed program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Erlang
by hinkley 3y ago
Any sufficiently complicated distributed program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Erlang
- whalesalad 3y agoI've done this multiple times. I will not make the mistake again. Next big system is being born in Elixir.
- pdimitar 3y agoWell, give me a call if you need help. Just looking for work again lately.
- whalesalad 3y agoFeel free to shoot me your cv/resume to the address in my profile! We just hired two new engineers this week, so the timing is not perfect, but I would like to have your info around for a rainy day which might come sooner than later.
- pdimitar 3y agoJust did. Thank you.
- nesarkvechnep 3y agoSame as @pdimitar. I’m looking for part-time work.
- whalesalad 3y agoplease see comment to @pdimitar and do the same ;)
- mikhailfranco 3y agoVirding's First Rule of Programming: http://rvirding.blogspot.com/2008/01/virdings-first-rule-of-programming.html http://rvirding.blogspot.com/2008/01/virdings-first-rule-of-...
- tombert 3y agoThat has definitely been my experience. There's been a good number of times I end up gluing things together with ZeroMQ and SQS and Redis where I start thinking "you know this would have been easier to get an equivalent (or better) product in Erlang". Sadly, I've only ever had one job at a shady startup that used Erlang; I would love to work for a company that sees its power, but sadly it seems that everyone who has not drunk the Erlang koolade thinks that Go is a suitable replacement.
- lionkor 3y agoBut go only has 3 or 4 ways you can shoot yourself in the foot at every turn with concurrency! Better than C++, I guess.
- tombert 3y agoI don't really mean to crap on Go, I actually think it's a reasonably ok language all things considered; if nothing else (at least on one machine), it gives you nearly the highest performance-to-effort ratios. It just annoys me that people see "Go is good at concurrency", and then see "Erlang is good at concurrency", and then assume Go ~= Erlang, which is not the correct conclusion.