HAR file viewer: Default to waterfall view

[waldyrious]

The waterfall view is quite useful, more visually pleasing (IMHO) and a more usual match for how the data from a HAR file is typically seen in a browser. Besides, the button shows up first in the UI compared to the Table view one.

For these reasons, it seems to me that it would be appropriate for the default rendering of a HAR file to be the Waterfall view, with the Table view remaining as an alternative.

[peckz]

@waldyrious I see your point; as waterfall is purely vibe-coded, I did not want to make it the default choice.

I think we should preserve the last selected option in local storage; then, if you used "waterfall", it will be preselected the next time you drop the .har file.

[waldyrious]

@peckz Thanks again for the fast reaction. I get where you're coming from, but let me add two data points for your consideration:

1. For me, the value of seeing the Waterfall view by default comes from the system making that initial choice for me, because that's the first impression you make on people. For context, I nearly dismissed this tool in favor of another similar one because I didn't immediately notice it had a Waterfall view, and that was my expectation for a HAR file viewer. (Of course, if I later change to the Table view, I agree that preservation of my choice is a nice feature.)
2. Even though it was a vibe-coded feature (perhaps precisely because of that), it might be more useful to expose more people to it so that its quirks are identified more quickly and ironed out so that you will become more confident about having it shown as the first choice.

Either way, I respect your choice — just wanted to make sure you had these points in consideration.

[peckz]

@waldyrious Thank you! I appreciate the effort, and I mostly agree with you!

When I finished building it, I considered setting it as the default view, though the overall experience for checking headers and responses is not ideal. In the next month or two, I'm going to create a better overview for requests and responses, and then I will slowly roll this out to everyone.

Since this utility is the most popular one, I did not want to change the core experience for people who use it every day.