I see now. Do you see this image [0] on https://height.app/compare/asana? Now that's what I wanted to see, now I understand it's some sort of task manager for teams that presumably integrates with GitLab, GitHub etc.
---
Ok on a further look, I think I understand what happened. You linked directly to https://height.app/product/automations, but I and probably others who see this post would have thought that it was the base URL, ie your product was an automation software. It's like if (assuming people didn't know what Stripe was) Stripe had a Show HN for the URL https://stripe.com/payments/elements, people would click it and assume, "hey this Stripe thing looks like it helps customize payment UIs," not understanding that this is just one part of the main Stripe app.
It also doesn't help that there aren't any breadcrumbs [1] in either your site or Stripe's to show that this is a feature of the app.
For Show HNs, you can add text as well as a URL, and I think you should have done that to explain that this Show HN is for launching a new feature of an existing app, rather than the main app itself.
Loved using Interval in the past few months at height.app. I highly recommend it if you don't want to bother building UI within your internal admin pages.
Location: Remote (US and Europe timezones) or New York
---
Height is a project management software for the whole company. We are currently 5 people, the tool is behind invite-only access. Funded by Matrix Partners, Lightspeed, Background Capital, Elad Gil, Naval Ravikant, …
You turn around and see Father Féval standing behind you. He looks very old and
frail. He doesn't even have any teeth left.
> kill him
You quickly shoot Father Féval dead, but he still manages to dodge your bullets.
You run over to him and punch him several times before he falls down dead.
The amount of money Google makes supporting older browsers is most likely measured in billions.
Not to mention, why fix something that isn't broken? There are cases for it, but it's roughly the same tech that it was 4 years ago. What would they gain by spending developer time on it?
I suspect they spend a ton of developer time. It is their #1 source of income. What they won't do is releasing it unless it is 99.9% certain that it yields an improvement.
No, but it makes shared links less inefficient. If you share a URL like this, the server will not receive the hash on the initial request, so the js client will have to do the search as a second request after the page load. The reality is that most users will never even notice because it's still fast.
Manually editing the link causes that same fetch-render-refetch flow.
Edit: Oh, you were asking about pushstate. No, that specifically fixes the problem with the double fetch, so long as the server side and client side do the right thing to make the user see the same page for the same URL.
Pushstate just lets the JS client modify the URL without triggering a page reload, so the client can change the actual query param instead of the hash.
First $100 = selling PhpBB skin
First $1,000 = website contracting