|
|
|
|
|
by StrayM
1427 days ago
|
|
> For Elixir? Well you have to use a 4 year old+ third party dependency Can we please stop using “4 year old+” as a generally applicable rule to reject libraries? I know “4 year old” seems like forever ago in Ruby or Node (I can’t talk about Python or PHP), but other ecosystems such as Go and Elixir take compatibility seriously and “4 year old” libraries most often just mean they are done: they work for their intended purposes and there are no breaking changes in the language or tooling forcing frivolous updates. I have used 8 year old Erlang libraries in the past with no issues whatsoever. |
|