71–80 of 303 posts
In 2000-2006 I implemented garbage collectors in C on Linux. I used Emacs and GDB, and likely also DDD and GDB from within Emacs. I don't think there was anything better back then. It's been a long time since I used C, but I wonder whether VSCode really gives a better experience than Emacs. Nowadays you can use Emacs with an LSP server, which is likely also what VSCode is doing. And there are Emacs distributions like…
I am curious: how does this guy Friedman make a living?! His full time job seems to be running this podcast interviewing people. Every few days he publishes a 2-hour long interview. He distributes ads, I am not sure how much that brings in.
In 2000-2006 I implemented garbage collectors in C on Linux. I used Emacs and GDB, and likely also DDD and GDB from within Emacs. I don't think there was anything better back then. It's been a long time since I used C, but I wonder whether VSCode really gives a better experience than Emacs. Nowadays you can use Emacs with an LSP server, which is likely also what VSCode is doing. And there are Emacs distributions like…
I don’t understand this sentiment about “modern” (interactive, user friendly) debuggers.
Simply because you have a tool doesn’t mean you have to skip the step of trying to understand the code. Is the suggestion seriously to avoid having tools that are objectively better because there may be a temptation to use them too early, whereas having only more primitive tools would do better?
I have seen the same argument about syntax highlighting. That pretty colors makes for sloppy code reading and monochrome text means you read slower and thus more thoroughly…
Are there no good UI experiences you can bolt onto gdb? Do Emacs/Vim not have nice modes that take some of the pain away? I've no real experience with using gdb - my main debugger usage has been on the JVM or using old Borland debuggers on Win32. Are there no good open source user-friendly debuggers out there? I tend to develop software interactively with a REPL where I can so if a good debugger can give you somethin…
Earlier quoted context omitted.
VSCode is based on Electron, a glorified hack/resource hog of Chromium than even Github largely abandoned. It maybe "great" and mildly "popular" here and there, but it's built on a foundation of mud. Build native apps that work and are performant. With enough effort and care, a frictionless experience can be made with a TUI should some "Jetbrains" come along and try to make a commercial product out of it.
Mildly "popular"? Which editor is more popular than VSCode?
In 2000-2006 I implemented garbage collectors in C on Linux. I used Emacs and GDB, and likely also DDD and GDB from within Emacs. I don't think there was anything better back then. It's been a long time since I used C, but I wonder whether VSCode really gives a better experience than Emacs. Nowadays you can use Emacs with an LSP server, which is likely also what VSCode is doing. And there are Emacs distributions like…
> Regarding the comment about the debugging. For me personally, I always take the time to study the code first before I start debugging. A lot of times I already find the problem by just reading the code and even if that is not the case, I have a much better understanding about how the code is supposed to behave and that makes the debugging session a lot more useful. And I say that because I have the impression that…
On the contrary, I get quite annoyed losing track of indents and scoping. VSCode finally adding colored brackets has been a blessing in navigating legacy code with way too much nesting in the face of developers still unable to keep their code from scrolling horizontally and dividing methods / using different paradigms to prevent overnesting.
Also helps to just not have to spend the limited amount of focus on things that an IDE can cover for you. Programming has become far more complicated (no, not complex) in many ways, and we as a species haven't magically gotten a lot better at understanding it while we seem awfully good at writing things even more complicated.
Are there no good UI experiences you can bolt onto gdb? Do Emacs/Vim not have nice modes that take some of the pain away? I've no real experience with using gdb - my main debugger usage has been on the JVM or using old Borland debuggers on Win32. Are there no good open source user-friendly debuggers out there? I tend to develop software interactively with a REPL where I can so if a good debugger can give you somethin…
Emacs has a couple gdb modes which are fine, and a DAP mode which is very good.
Earlier quoted context omitted.
Linus Torvalds likes the fact Kernel debugging is not user friendly so that it does not detract from good programming practice, making sure you really understand your code and what it should do before having to resort to a debugger. https://lkml.org/lkml/2000/9/6/65
Nokia's Symbian OS was notoriously hard to debug, too. Half-baked emulators and the real device debugging was even worse. I wonder to what degree this contributed to the eventual downfall of the platform. The learning curve was so steep and the IDE and tools placed so many mines under your feet so relentlessly that it must have driven some talent away. (An example: you closed the emulator and it left over some runnin…
We went through several IDEs, Visual Studio, CodeWarrior and finally Carbide.
I’m not saying the OS itself wasn’t complicated though.
I've been trying to listen to the whole thing (it's 5 hours!), and there are some really interesting moments. Albeit, a bit too much talk on old video games that aren't from my generation, but I'm sure this will be interesting to some people to. What I found interesting: * he has insane hours and has never burnt out. He says that if you want to achieve big things in your life, you need to work a lot. He also says tha…
I think Carmack was mostly talking about regular Visual Studio as his IDE of choice, though. Not VSCode.
Most Windows programmers I know (not a lot) use VS for the ease of integration with all things .NET and Microsoft.