remi·3 ปีที่แล้ว·discussWe (Mirego) made the move from Rails to Elixir years ago for three main reasons: productivity, maintainability and performance → https://shift.mirego.com/en/elixir-functional-programming
remi·3 ปีที่แล้ว·discussIt’s not a shell utility, it should work with any shell. $ which networkQuality /usr/bin/networkQuality
remi·4 ปีที่แล้ว·discussReminds me of the classic CSS book (2005?) by Dan Cederholm: https://www.amazon.com/Bulletproof-Web-Design-flexibility-pr...
remi·5 ปีที่แล้ว·discussShamless plug for our Elixir boilerplate we’ve been maintaining for three years :) https://github.com/mirego/elixir-boilerplate
remi·5 ปีที่แล้ว·discussIn 2016, we started to use Elixir as our default backend stack (from Ruby on Rails) for new projects and never looked back! We have since shipped a dozen projects using Phoenix, Ecto, Plug and Absinthe.
remi·6 ปีที่แล้ว·discussThe “new” thing (if you didn’t know it before) is that GitHub applies a collapse/expand behavior to <details> elements.