✍ Comment below answering these two questions

1. For personal use, I use Firefox & DuckDuckGo. Likewise, for my current work, I use Chrome. I already have a significant number of Google products, so I want to limit the amount of data they are collecting about my searches. I use Chrome for work because my corp is a mix of desktop platforms internally, so there isn't much need for us to have wide support beyond the Big 3: Chrome, Safari, and Firefox.

2. Three years ago, when I was still doing freelance full-stack web development, I used Chrome, Firefox, Safari, Opera, Safari & Chrome for iOS, and Chrome & Firefox for Android. I had this wide spread because I had to account for my client's product being used on a slew of mobile and desktop devices.

I would have to switch between browsers as I was developing, which meant that I could use the best features provided by each. Even though new browsers are coming out all the time, they all have a focus. DuckDuckGo's focus is privacy. Mozilla's focus is accessibility and competing with Chrome. Google's focus is harvesting data and syncing with other Google products.

The kicker is, no matter how good Firefox or DuckDuckGo, or whatever other focused browers you can think of, provide features to developers or hobbyists. They can't possibly surpass the spread of Chrome or Safari. And, those two frequently implement experimental features that aren't remotely close to the W3C's standards. If every big browser did conform to the standards, we as developers would be able to pick our favorite browser and be confident that it would look the same in every other one.

Unless a browser is already in use by consumers, there's no room for developers to use it. That's because our market is consumer focused. Consumers are the product. Developers are an after thought and have to scurry around to support whatever will get the most eyes on a product. It's sad to think about, but the fun part is we get to put our thumbs in a whole lot of pies! 😆

1. I use Google Chrome most of the time. I guess Firefox would be just as good. Of course sometimes i need to test with netscape or ie to cover the edge cases.

2. I think the devtools already give us a lot of tools that are being improved permanently. As a frontend-developer though i am sometimes missing to be on the same page as the product managers. So a possibility of any kind to bring the perspectives of developers and pms together could be a good thing.

For example to mark test cases or tasks in a project (website(s)) and share that. Or something like that..

Brave at home, FF at work.
Brave because it keeps me private at home and FF because it came by default with work laptop.

I'd love to have an inbuilt postman-like tool.

Thanks for mentioning Polypane! (I'm the creator), I'll be keeping an eye out for this discussion :)

Obviously I think most regular browser do a poor job of facilitating developers outside of the devtools. There's so much more a browser could do. I don't think Polypane is perfect but I hope I can keep getting closer to perfect, I have features planned that will last me the coming 5 years to implement.

1. Vivaldi - I am a tab fiend and their handling of multiple tabs and tab stacking is just beautiful. Also they do make dev life pretty easy and as it is Chromium I know if it works there I got Chrome covered pretty much.

2. Would have to be:

   • voice activated stack overflow "hey chrome, what is the bloody syntax for prototype.forEach again, I know I have asked it 20 times this month but one more time please".
   • A sanity check list - "are you really sure you want your font size to be 125rem, did you mean 1.25rem by any chance you dummy?!"
   • something that simply lets me click on an element and then draw a box on the page and say "see this box, this is where I actually want this element, can you tell me which property I botched for the content to end up waaaay over there please?"

A serious answer

I would actually like the items above, but in reality they are a little bit silly 😋

One thing I would actually love to see from a development perspective is a one click button built into the browser that non tech savvy users can use to send performance traces, error information, screenshots etc.

That way when you get that annoying bug report of an issue you cannot replicate they can press a button and send you the information needed.

If this was browser controlled, security and privacy could be easily accounted for I just want to know what "it was slow today" actually means - are you running a 10 year old dual core laptop with a physical HDD on Windows 7 that was running a virus scan for the first time in 3 months and had to wait 3 seconds for a page to load, or do you have a gigabit connection and a monster PC and our application has an actual intermittent issue under certain circumstances?

I am aware we have loads of ways to handle this but building into the browser would be soooo much better.

I love Google Chrome. Just don't like how my data is used, but I can't live without it.

Alright, the first question. I use Vivaldi on mobile (for the cleaness) and sometimes Kiwi (for the extension-support). On desktop I use Opera GX 'cuz it's more RAM-friendly than most Chromium-based apps.

The second question, yeah:

• Something as fast as Opera GX, it works well on my 4GB RAM laptop. And I can now run quite a lot of tabs with it.
• Firefox's devtools and Chrome's devtools combined, somehow. Firefox basically covers a lot of things but it doesn't have Lighthouse.
• If it's a mobile browser it has to have the same experience as desktop browsers. Extensions, themes, and dev tools. Eruda sucks a lot, would prefer use an actual devtool like in desktop instead of that. And for extensions, we already got extesion support in Yandex and Kiwi Browser lol.