The Primeagen’s take is very fair – “Maybe both sides are correct”.
Someone in his Twitch stream: “Nuance? On the Internet?” – I think that sums it up for me.
In related news, you should be aware that HTTP/2 is not yet supported on Heroku.
(You probably shouldn’t be serving assets from Heroku anyway).
Chicago trip next week 🪁
I managed to pick up a cold whilst in Amsterdam. Long story short, Chicago didn’t happen
$ irb irb(main):001:0> RubyVM::YJIT.enabled? => true
You know how, by default, the
<textarea>field stays the same size when people type sentences into the form field? The CSS Working Group is creating a new CSS property so you can style a form field (
The project is a data pipeline of sorts for a healthcare company and has high requirements for availability, which took them on a path towards an unusual architecture where each patient is modelled as a process within the Erlang VM, and all data is stored with that process. A copy of each process is then replicated, using distributed Elixir, across to to geographically different nodes to stand-by in case the original process dies. No database involved.
Very interesting 🧠
When a word is CamelCased, assume “Cased” is a separate word: every upper-case character in a word that comes after a lower case character indicates the start of a new word.
spelloptions=camel, “LiveBook” would be considered a spelling mistake, but with it, it is not. I’ve added it to my config.
Classic rock, Mario Kart, and why we can’t agree on Tailwind – an interesting take on Tailwind CSS.
From Scott Chacon, one of the very first GitHub employees, on the naming of “Pull Request”.
For those of you too young, the @github naming comes from this Git builtin: https://git-scm.com/docs/git-request-pull
I had no idea.