Isn't the point of this article to highlight specific tools? A lot of technical PR blog posts do well on HN. Not as many as technical PR blog people wish they would, but still - if the post contains interesting information, that's what matters. Here's a past explanation about this, in case it's helpful: https://news.ycombinator.com/item?id=20186280, which was an answer to https://news.ycombinator.com/item?id=20186246 ("Is it acceptable to have unmarked advertisements on HN?").
There's also this guideline:
"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."
In general I do enjoy technical PR blog posts and also in this one I found interesting bits.
What disturbed me was, that the title said "web developer tools secrets", while in the text it is specifically microsoft edges web developer tools.
This style of language I do not like so much. There is too much agenda in it, in my taste. As this seem to imply, there are only one web dev tools - the ones that comes bundled with your windows OS. (Microsoft does have a history)
Now it seems, the edge dev tools are allmost identical to chrome dev tools, so I might have assumed more ill intent, than what was actually there, as most web devs use one or the other.
But it is still not clear to me, what of the posts information apply only to edge for example. What to chrome. And what would also work in firefox. All of them have web dev tools.
As far as my understanding goes (which may not be very far at all), the common base seems to be Chromium. When I want to debug an HTML source (like the one in the article), VSCodium offers me Chrome or Edge as the base browser (none of which I have installed). I wonder why Brave isn't in there, since it's also Chromium-based.
Oh, I think I understand now. You mean when you use the debugger in Visual Studio Code the target browser dropdown only shows Edge or Chrome and not Brave?
That is weird and I wonder if it has something to do that brave hasn't got the CDP methods turned on that allows other software to remotely control it.
In essence, the debugger spawns a new instance of the browser and controls it remotely from VS Code, much like automated test tools do. It would be interesting to hear from Brave if there is interest in showing up there, too.
Oops, seems my last sentence was badly worded. With “in there” I meant the set of browsers offered by VSCodium, not your article. Your article is fine and informative, except that the title makes it seem more general than it actually is.
What disturbed me was, that the title said "web developer tools secrets", while in the text it is specifically microsoft edges web developer tools.
This style of language I do not like so much. There is too much agenda in it, in my taste. As this seem to imply, there are only one web dev tools - the ones that comes bundled with your windows OS. (Microsoft does have a history)
Now it seems, the edge dev tools are allmost identical to chrome dev tools, so I might have assumed more ill intent, than what was actually there, as most web devs use one or the other.
But it is still not clear to me, what of the posts information apply only to edge for example. What to chrome. And what would also work in firefox. All of them have web dev tools.