446 karma · joined November 3, 2018
That is the worst thing to happen to Web browsers that I can remember. When I type an address into that bar, I expect the browser to attempt to contact the server I specify. I do not expect it to decide that what I typed was a search term and send me off to Google.
Firefox had actual quick searches in the address bar years before. That is where you prefix what you type with something that unambiguously says where you want to search (e.g. I've had Wikipedia set up for many years now, I type "wp <search term>"). Having a separate search box, as Firefox always had as far as I can remember, has its virtues too as the box stays around between page loads.
Searching in the address bar does nothing but serve Google by making people forget about urls and having all Web access routed through them.
> Beyond a certain level of codebase complexity, there is simply no way to do the job with a text editor
An absurd claim. How can you interpret my post as a "get off my lawn" type thing?
> I see a similar thing happening with coders who do a lot of tests (test driven development),
I mean, yes, but isn't that obvious why? In my work I can safely say I've written the most code in the shortest amount of time. This has allowed us to meet deadlines. But it's all untested. Writing tests obviously takes more time and effort, but I do think they are a good thing. Getting 100% test coverage for every project and following TDD too strictly is silly, though.
And before the VSCode fanboys downvote me, the other day my colleague's VSCode instance was using more than 200GB of virtual memory. When I typed on his editor it was noticeably laggy. He told me it was normal. He had five files open. My emacs had been running for two weeks at that point and had about 200 files, 5 shells, 2 ssh sessions and 1 IRC client going on.
Seriously, guys. The reason why you like VSCode is the same reason we like emacs. Come and use the real thing.