Conversely, cosmos is targeted at me and the lander made good sense. I understand the frustration with “inside” comments like “Don’t settle for localhost:3000”, but I appreciated it and it implied fairly heavily that this tool disrupts a very slow and tedious workflow.
I do agree that some things are buried. The docs didn’t lead me to the information I needed as quickly as I think they could have for example.
Overall I’m excited to give this a shot. It seems like a great tool.
I think I’m also in the target area - I work on localhost:3000 every day building Notion, which is a big React app. But why does changing the port change my workflow? What is the “default” state of the service on port :3000? How am I settling? What workflow are you referring to when you say “this tools disrupts a [...] workflow”
This is my take on it, but I realize now that it’s going to vary a lot from person to person.
The workflow is all the jank that comes with HMR, or worse, reloading entire pages to see changes.
The port number isn’t a specific thing so much as an allusion to the workflow most people use. You’re focused on a single component quite often, but working with it in an entire page served through your entire app server. It’s overkill and slower than necessary, and sometimes comes with all kinds of state frustrations outside of the scope of your component.
Changing the port doesn’t inherently change the workflow, it’s just calling out which port most of us use for that workflow and suggesting to investigate what could be better than that workflow.
They’ve made some changes to the page now, so hopefully this isn’t a source of confusion anymore.
I do agree that some things are buried. The docs didn’t lead me to the information I needed as quickly as I think they could have for example.
Overall I’m excited to give this a shot. It seems like a great tool.