hthh

9 ms·

1.
by hthh 9y ago
What is "Nitro"?
2.
by hthh 9y ago
"Copyright infringement" is not "trademark infringement" and shouldn't be in the title.
3.
by hthh 9y ago
Why? I mean you're still sending the referer header, right?
4.
by hthh 10y ago
Making the atomic bomb scores pretty high on the evil-genius scale.
5.
by hthh 10y ago
Wow, in a happy coincidence syntect is exactly what I was looking for all last week! Now I just need to figure out Rust.
6.
by hthh 10y ago
Dynamic resizing fixes this, although hash collisions can still be a problem (albeit a very unlikely one if your hash is secure). https://en.wikipedia.org/wiki/Hash_table#Dynamic_resizing
7.
by hthh 10y ago
Absolutely, by all means look at old code - code that has survived and been useful for a long time. It's either adaptable (Linux) or doesn't need to change or adapt much (TeX). Do you currently use and rely on software which you e
8.
by hthh 10y ago
"High quality" is an strange concept. I would look at code you actually use and rely on - that's the best indication of quality. A lot of critical code deals with inelegant, complex problems correctly and efficiently - I&#x27
9.
by hthh 11y ago
This is an interesting article, but the "Portability" comments could be a lot more useful: strndup and open_memstream are both "POSIX 2008", but strndup can be used on OS X while open_memstream cannot.
10.
by hthh 11y ago
On Windows, sure. On other platforms UTF-8 is generally preferable (in my opinion).
11.
by hthh 11y ago
I think this is the COFF document which they say "is directly applicable". https://github.com/llvm-mirror/lld/blob/master/COFF/README.m... I'm guessing the speed difference comes from
12.
by hthh 11y ago
"It's weird how there are like two alternate realities of data compression. "There's people who actually know WTF they're doing. (eg. encode.ru & the DCC's and so on). In that world you have compressors lik
13.
We don’t need new multimedia formats (2010)(fgiesen.wordpress.com)
3 points by hthh 11y ago|0 comments
14.
by hthh 11y ago
I disagree with it, but the Google C++ Style Guide offers the rationale you're looking for (under "On Unsigned Integers"): https://google-styleguide.googlecode.com/svn/trunk/cppguide....
15.
by hthh 11y ago
My GCC seems to be GCC (don't remember why - I guess I installed it for something). I can also make it build using "--std=c99" (but that makes the undefined behavior mentioned in issue #2 show up, which is why I went with cla
16.
by hthh 11y ago
I too wrote a TIS-100 simulator in C ( https://github.com/hthh/tis100sim ) - it's interesting to compare styles. (I get a bunch of errors on OS X unless I change "CC=gcc" to "CC=clang", btw)