writebetterc

6 ms·

61.
by writebetterc 1y ago
You're wrong :-). I hate that stuff, and I'm technically not even in my 20s anymore!
62.
by writebetterc 2y ago
REPL-ify your command line then? There's nothing that says you have to be stuck on bash for your command line needs. https://www.nushell.sh/
63.
by writebetterc 2y ago
IDEs understand preprocessor macros, so IDE features (jump2def, etc) work with this. IDEs also can expand the macro invocations. So, I prefer the macros when possible :-).
64.
by writebetterc 2y ago
Why isn't the conclusion "There is a far better way of using C, which the stdlib doesn't promote... But could"? The fact of the matter is that any sufficiently large C codebase will do this stuff anyway, it's not a
65.
by writebetterc 2y ago
This way of writing programs is also quite a lot faster than depending on fgetline and the like. The integer and float parsing is probably slow, though. My question is: Does the author actually use Windows XP?
66.
by writebetterc 2y ago
Ain't nothing wrong with Swing or JavaFX :).
67.
by writebetterc 2y ago
Good, but that can also be noted in a subtitle right below the authors (I've seen this in papers myself!)
68.
by writebetterc 2y ago
No reason to be rude, it was really not clear that you knew that as null pointers have nothing to do with memory models.
69.
by writebetterc 2y ago
I believe that the parent is talking about how Java, and in turn the JVM, defines its memory model, which describes formally how memory reads and writes occur in the presence of multiple threads of execution. For example, data races are wel
70.
by writebetterc 2y ago
Don't use Fedora if you have a nvidia gpu, or if you have ample of free time.
71.
by writebetterc 2y ago
>pioneer something when somebody pioneers something, they are one of the first people to do, discover or use something new.
72.
by writebetterc 2y ago
> In fact, it was the United States that pioneered this in the modern age. This was instituted in Sweden in the year 1766. Source: https://sv.wikipedia.org/wiki/Offentlighetsprincipen That's 10 years before th
73.
by writebetterc 2y ago
You sure can write C which makes you less prone to making memory safety mistakes, yes. Knowing how to do that is a skill issue. As you say, sometimes our skills fail us, and that's where tooling comes in. ASan, borrow checker, whatever
74.
by writebetterc 2y ago
Memory will always be the limiting factor here. A strong adversary can ensure that you must know the whole list in order to sort it. You can always mmap the file instead and let the OS page in and out parts of the file, however :-).
75.
by writebetterc 2y ago
This post caused me to create an account. This C code is not good. Writing C is absolutely harder than Python, but you're making it so much harder than it has to be. Your program is buggy as heck, has very finicky cleanup code, and s