Weeknotes 120

You might have heard something on the Internet about HTTP/2 and no build JavaScript? (I saw the keynote at Rails World last week). I planned on writing something more substantial but I haven’t got the facts or energy required.

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 🫤

If you want to check whether you’ve enabled YJIT in your Ruby environment, you can check from the console.

$ irb
irb(main):001:0> RubyVM::YJIT.enabled?
=> true

Jose Valim and team are had another Livebook “Launch Week” this week where they unveiled some really nice new features: File Integration and a Remote execution Smart cell were the highlights for me.

Jen Simmons tooted that the CSS Working Group are adding a new CSS rule to allow form input and textarea elements to grow, something normally you’d need JavaScript for.

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 (text-area and input) to grow fit its content —so you don’t have to use JavaScript to do this!

Bryan Hunter spoke at GigCityElixir23 about a project called Waterpark.

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 🧠

A post on the Neovim subreddit drew my attention to set spelloptions=camel.

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.

So without 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.