HN user

black-tea

446 karma
Posts0
Comments460
View on HN
No posts found.

address bars with integrated search engines,

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.

If I can't do a "modern development task" with emacs or vim and a smattering of standard Unix tools, then I question the sanity of said task. At the end of the day we're editing text. Plain text has stood the test of time exactly because you can process it with tools that everyone knows and have been around for decades. If you find yourself needing special purpose, proprietary tools to handle your code base then you should really reconsider where you're going.

I see a correlation, but I am an emacs user. One thing that rings true is how people use git. I find that the people who use IDEs to do it just want to do it the IDE way, like always merging with --no-ff, and not actually thinking about what they're doing and coming up with their own solution to the merge.

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.

Yeah, I've done that with pandoc too, but I use org-mode. It's much more pleasurable to write than markdown. I don't use a great deal of org-mode features when writing, I suppose, but just being able to fold up sections and knowing the keys to quickly jump between them and rearrange them is great.

Writing markdown with emacs is a huge step up. Now you get to take another big step up when you use org-mode instead of markdown. I'm actually pretty envious.

I am so glad that I took the time to learn emacs during my uni days more than ten years ago. I would see everyone else using absolutely awful IDEs that they never actually understood while I was learning how everything really worked and setting up emacs to make my life easier. Nowadays I see people struggling with slightly less bad tools like VSCode and they often ask me about emacs but they just don't have the time to learn it like I did. I probably wouldn't have the time now either.

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.