In all my years of using emacs I have not once been called out on formatting. In my last job the bastion of PEP-8 was a vim user. If you're talking about actual low level text editors like nano or notepad.exe, then sure, but vim and emacs are proper tools.
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.
It really does help to get a reminder from the IDE regarding which methods exist and what their parameter lists are. For C, ctags works well enough I guess and we can complete function names that way. But for Java and C#, I can't imagine that going well.
Well because it is. With a large codebase, things like navigating through a solution, automated code refactorings, intellisense, etc. can be done with IDEs. Do you all so litter your code with print statements to debug?
Are you just playing ignorant for fun? You must know that there are people out there hacking on the most advanced software projects we have such as the linux kernel or C compilers etc. and they don't all use IDEs.
And what percentage of developers is that? That’s about like the same bubble thinking of every developer works on the west coast making $300K a year that you see on HN.
And some people also still write in assembly. I also thought that any high level language was useless. Then I thought anything more high level than C was for beginners.
But I grew up and start being more concerned with making money and implementing solutions than having geek cred...
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.
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 use org-mode for note taking and some task tracking. My main doc writing setup is more like an ide setup.
markdown<->docx with pandoc lets me use a ref-doc.docx file that ensures all the styling I need for legal docs gets into the word doc. So you make a markdown file from the ref-doc.docx then edit the markdown file and convert to docx using the same ref-doc and everything in docx has the correct style, and stuff like line numbers and headers are preserved. Pretty sweet.
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.
For one example that I like to cite, install Org-Babel and play around with a Jupyter-notebook-esque interface within your document. When you’re done, GitHub will render it statically like they do Markdown.
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.
Really? You could easily find comments on here talking about how Steve Jobs wasn't really the genius at Apple, but rather it was Steve Wozniak. We do care who really did it. Always.
Why does it actually matter what Web browser most people use? In absolute terms there are probably more Firefox users now than there ever were. Who cares about the percentages?
In the early 2000s IE6 "dominated". I think we all agree that was awful, with many websites out there only built for and tested with IE. We Firefox users got through that. We'll get through this too.
If developers rely on 'features' added just to Chromium, without any kind of standards involved (i.e. imagine if Chrome said they're going to ship a Dart VM in chromium) then users of every other browser are shit out of luck.
