Everyone was so busy showing Hey's performance problems that they forgot to show how broken it is. What do you think happens if I press the "enter" key twice?

And don't forget that EVERY KEY PRESS WHEN CREATING AN EVENT IS SENT TO THE SERVER

Watch my full video here

For what it's worth, I really don't like being this negative about the quality of someone's software. If I run into problems with software and I have ANY faith the mantainers might fix it, I get it handled privately. The unique combination of cope, incompetence, and genuinely harmful behavior from a Certain Three Letter Account is why I feel the need to jump on this. This isn't a "difference of opinion", this is one person pretending the majority of modern developers are wrong.

Imagine spending this much time and effort to be negative about something someone has built that you don’t even have to use. All for likes.

The Hey Calendar example only shows that the app needs some extra javascript sprinkles on the client. This is not a rails problem, not even a Hotwire problem, it's an implementation problem. Showing the popover instantly can be done by including it in the html beforehand. Things like optimistic updates are totally doable in a few lines of code with Hotwire (Stimulus.js specifically) Preventing double submit (duplicated events) is also doable in Stimulus. Rails has nothing to do here, you can even use Rails without Hotwire. You can use Rails with Inertia and React, or only React, or htmx or whatever you want. Just like the case you mention about Laravel. Hotwire is a Javascript library, you can even use it in Laravel and the result will be the same. Hotwire is: - Turbo (the navigation library, html over the wire, similar to htmx) - Stimulus (similar to Alpine js) - Strada (bridges between Web and Native ) Probably Hey Calendar just needs to be polished, use more Stimulus instead of just Turbo frames and streams. Remember they don't have the team that Gmail has, and it's a fairly new product (launched early 2024). I bet they will fix many of this things soon.

This has much less to do w/ tech stack than it does 37signals approach to making software. Read their process docs, Shape Up, and you’ll see that they have a very laid back attitude towards edge cases, QA, etc. Unless it’s a huge problem for their customers, they DGAF

All of this clip was literally in my talk next week 🙃

It’s a ‘new’ product - products improve. All this hate on Hey feels more like personal grudge against @dhh and RoR. If it was a startup launching this, you’d all be praising it and not even look at performance. Let it mature and look at the benefits - it’s worth it every cent 👏🏽

Non-debounced buttons/actions are the #1 indicator of a rookie frontend dev

I know the term "unusable" is thrown around a lot, but I would unironically rather throw all my events in a .txt file instead of using this mess with my internet connection. To his point, I may not be the target audience for this product. Fair enough, but to recommend this solution to the web devs in general is just irresponsible.