Is there a smart watch that would connect to two phones at the same time? I’d immediately buy one which showed notifications from my personal and work phones.
Sorry about misuse of “intrinsics”. There is a simdjson library that uses SIMD instructions for speed. Would such an approach be feasible in the ruby json library?
I refuse to live my life as if these things aren't important to me. I refuse to average my entire life style down to my median day. My median day is boring.
Surprised nobody mentioned externalities yet. Carbon tax, and then you can take a more wholistic view when planning your life.
By the way, landscaping as a hobby does not automatically imply trucks, not outside US at least. Unless you actually do it often and need to transport large loads—then yeah, go for it. You’re part of a small minority that might actually need a truck.
We do not test because of a language used but because there are assumptions expressed in code. “Clicking a button validates the email address” is a test you need to have regardless of if it’s implemented as `hx-get` or `onSubmit`. I would argue having good test coverage for the former is more important because the action happens further (another controller+template instead of the same React component).
An important topic I do not see discussed on HTMX and other such tools is testing.
Frontend frameworks all have a way to unit- and integration-test their components without resorting to Cypress or Playwright. How do you integration-test the effect of your hypermedia enhanced applications without a (headless) browser? Using Chrome for a few end-to-end tests is fine. But it is not a replacement for in process RackTest (to give a Rails specific example).
From a quick glance testing is not addressed in this book either.
Nikola is one of Crystal lang largest sponsors[0]. I wonder if this is going to have repercussions. It's no fault of the Crystal community but might cast a shadow nevertheless.
This. The project is considered one of the (if not the) go-to web frameworks in Rust, lives under its own organisation, is promoted and discussed by many other people. It's not a sole property of the maintainer any more. The maintainer does not owe anyone any new code, nor accepting any PRs. But he does have to set correct expectations. If you want to be the sole BDFL and not care about others opinions or contributions then don't promote it as production code, keep it under your own profile, and/or make it clear in the README. Now it's a community project, "fun" is not necessarily the most important quality anymore. State your position early.