wrhn

Recent submissions

Comment · 6 years ago
I think for the vast majority of cases it is better to use whatever you're most comfortable with. Some people just don't have the endurance to learn gdb or lldb, or they are allergic to Visual Studio on Windows because of how big and slow it is. They just use print statements instead. Some people have learned a few workflows with a debugger of their choice and for them it is easy to fire up a debugger.

However, for some things like debugging Windows kernel trickery it is impossible to use print statements.

Personally I like debuggers.

Comment · 6 years ago
But unless you're investing other people's money, you are a small fish in the sea. Like, if all you have is 200k then none of your decisions being public would affect you in a negative way. Admittedly, I don't know much about the stock market but I can't imagine anyone caring if you want to short some company's stock.
Comment · 6 years ago
I know some people are going to complain as with every redesign. But I really like how clean and uncluttered this feels. Lighter blue color, less bold text, dense side panel, misaligned repository header. Ok, it's not really uncluttered. But I think it's good that contributors are more explicitly credited now.
Comment · 7 years ago
It's funny how carefully you're stepping around financially rewarding people who do the work. It's like you know your status does not allow you to own the money generated, so you're settling for owning the results, the process, the method, the responsibility, the all. You are weak.
Comment · 7 years ago
There is also https://git.sr.ht/~mcf/cproc inspired by several other small C compilers including 8cc, c, lacc, and scc. I did not take a deep look at it yet, but it looks interesting.
Comment · 7 years ago
A debugger inspired and somewhat popularized by the Handmade Hero screencast series. Primarily for C and C++. Some people say good things about it and happy that it is being developed. Since it is a paid tool with no demo, you might want first to see it in action before purchasing. A good introduction to the debugger is simply watching a few videos of it being discussed and used by Casey Muratori. Go to the screencast page [0], scroll down, and and the search field (which accepts regexes by the way) type 'remedy'. Click on everything. You might also watch a 2 hour long episode discussing debuggers in general [1] and why Visual Studio debugger is not ideal [2].

[0]: https://handmadehero.org/watch [1]: https://youtu.be/GfGNPo9Z6mA [2]: https://youtu.be/vohsUKjg9tU?t=33

It is still early days for the debugger, so it has bugs and might crash. Another downside is that it is closed source which might be difficult to reconcile with today's culture of open source. It is really unfortunate because author said it is developed completely from scratch using very few third party libraries. Because of that it would be interesting to take a look at the source and perhaps hack on it. But people are buying it anyway.

I urge everyone who might be interested to support the development of remedy, because I want the project to succeed.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton