padseeker

this ^^^

I've used turbo/stimulus/hotwire. It's best suited for STATELESS interactions withe the browser/web page. The problem is not all desired user experiences and use cases are stateless. And the ecosystem for hotwire is a minuscule fraction of all the other popular js frameworks.

If you're searching for inventory available its perfect. However if you want to update one thing based on the most recently touched input it becomes more complicated and in all honesty more trouble that it's worth.

Honestly if you're a solo Rails dev, use whatever you want. However the React ecosystem, and really all of the other popular JS ecosystems (vue, ), are very strong and you have so many available options. Stimulus is 2 steps back from jQuery, it inverted the Event delegation pattern. No one else outside of the rails community is using it.

Just added you to Launch Point Zero

https://launchpointzero.com/launchsites/innovativ_es

we are expensive to employ

here's another one where someone is complaining

https://x.com/tibo_maker/status/1840656616032489754

I appreciate your comment, and the honesty.

This post is certainly being critical, but I'm also not here to bring the hammer down. I am saying that it has grown very popular, and that makes it harder to get noticed. I know more than a few people have publicly complained on twitter about how their startup listing has been removed or bumped.

I also know there are a lot of scammers out there that PH has to battle against, trying to game the system. I know the people at G2.com when they started and were giving away free ipads for the top people with the most software reviews in a month, and someone tried to jump ahead by downvoting all the reviews of the people ahead of them in a month.

Clearly though expectations have changed. I'm certainly bummed for the 60% of the staff who were laid off. You can't just share your startup without some serious work beforehand or else you risk blowing your shot at 15 minutes of startup internet fame.

My point is not that PH is dying or not, but the game has changed and it has hurt makers who do this for the hope of making a full time living, and we're being crowded out by VC funded startups and previous PH launchers who have had past success (i.e. Tallyforms) that are "relaunching" and sucking up the little amount of attention available on PH. It's frustrating.

I'm sorry the post I wrote in a pinch and shared within 30 minutes and is free does not meet your standards for journalism.

here's a couple of twitter feeds that center on the drama related to product hunt;

https://x.com/WhoWorksThere/status/1840822087868375085

https://x.com/csallen/status/1840792433447391560

https://x.com/HeyImYossi/status/1840634391040577847

theres a lot more in my feed and the people I follow this could be an all day thing but I hope this supports the headline of my post.

Salesforce bought it and there were too many freeloaders.

Options of "local hosting for development purposes"? Do you mean running "rails s" locally on your machine?

Are you saying that the one letter typo on the one of my many points surrounding the drama at Product Hunt discredit the whole thing? No I do not.

Maybe I should have shared in the article all the twitter posts where indie hackers are upset how they are getting screwed and how hard it is to get ranked on PH. There is a lot more drama surrounding PH than just the CTO not knowing one well known community member.

I made a mistake, it will be corrected asap. Thanks for the heads up.

Heroku is the OG of affordable rails hosting. If the tutorial is older than 3-4 years ago then it was published when Heroku was free, which it no longer is.

There are lots of other affordable, but probably not free, options now;

https://railway.app/ https://fly.io/ https://www.hetzner.com/ https://www.digitalocean.com/ https://render.com/

you can't manage permissions very well or precisely. You can give a user "read only" or "edit" but you cannot manage individual sheets or cells. Spreadsheets are great for lots of things, but sharing them with lots of people is not one of them.

hey I think this is very cool and I plan to try it out

higher altitude means less oxygen, means you need to inhale/exhale more to get the proper amount of oxygen, and also faster heart rate. Is it possible the metabolism of people at higher altitudes burn more calories just trying to get the same amount of oxygen?

I'll refine it. I scraped a lot of sites and some of them were terrible. I just figured it was better to have the data there and let users decide as opposed to not having anything. I can see scraping some numbers related to traffic and using that for ranking.

Spoiler alert - The free speech crowd never actually cared about free speech.

Where are all those fanboys who whenever Elon would make a bone headed move, they would correct you about how no Elon is a genius and here's why. I desperately want to hear what they have to say this time.

thanks for the heads up, just fixed it

Explain to me what exactly that means? Do you mean who manages the domains like GoDaddy?

Your first problem is you're using Angular.

There are ways to keep things simple with the front end, only add js for the things where you want instant visual feedback. It requires a little pushback on the part of the dev team, against UX and Product management.

Notice I said profitable niche. You won't magically become the profitable behemoth that Slack will. But you can build a company just on this one angle.

The best engine for generating a startup idea? Find a successful company that charges per user, then build a competing product, and don't charge per user. That's it.

It would be nearly impossible to this for Salesforce. But for a lot of other applications like Slack and Dropbox, you could carve out a profitable niche.

If you are using that many refs you built it wrong - from the React documentation (https://reactjs.org/docs/refs-and-the-dom.htmlhttps://reactj...

"There are a few good use cases for refs:

  Managing focus, text selection, or media playback.
  Triggering imperative animations.
  Integrating with third-party DOM libraries.
  Avoid using refs for anything that can be done declaratively.

...

Don’t Overuse Refs:

  Your first inclination may be to use refs to “make things happen” in your app. If this is the case, take a moment and think more critically about where state should be owned in the component hierarchy. Often, it becomes clear that the proper place to “own” that state is at a higher level in the hierarchy. See the Lifting State Up guide for examples of this."

If you are using refs to talk to your child inputs you've made a mistake. React talks about RAISING THE STATE - for complex forms you need to make all of your inputs controlled, you need to manage the state at the highest level. You need to push those changes down to child components, none of them should have their own state.

React gives you some nice tools to handle most common use cases but you can still make less than optimal decisions.