Viewing profile — mccoyst
mccoyst
HN member- Joined
- Mon, Apr 16, 2012, 2:57 PM UTC
- HN karma
- 82
- Public activity
- 28 items
- HN profile
- View on Hacker News ↗
About mccoyst
No profile information was provided.
Recent public activity
-
comment
Comment #4687969
How is Github a monopoly? Bitbucket, Google Code, and even junky old SourceForge are far from unpopular.
-
comment
Comment #4659828
Upvoted. They maintain it by introducing an endless stream of bugs and vulnerabilities.
-
comment
Comment #4357214
People are upset because they wanted to be part of the elite club that maybe possibly would have had their DNT header honored, but now that it's likely that a huge percentage of ot…
-
comment
Comment #4312161
Is anyone else disappointed that the best answer (the standard div() function) was passed over in favor of massively inefficient bit-twiddling wankery?
-
comment
Comment #4255470
Maybe things are different on Dalvik, but javac for the Oracle JVM is about as braindead as a java compiler can get; all of the optimizing is done during JIT.
-
comment
Comment #4189832
A rule for multiple output files: output1 output2: deps
-
comment
Comment #4188846
Here's a makefile: http://code.google.com/p/min-game/source/browse/makefile Here's the dependency script: http://code.google.com/p/min-game/source/browse/dep.sh Both inspired by co…
-
comment
Comment #4171540
"low-level rigid type system" You've never written C.
-
comment
Comment #4161726
You still need entities for reserved characters like & and <
-
comment
Comment #4154261
There's no difference between implementing method dispatch with multiple inheritance versus multiple interfaces. What do you think C++'s multiple inheritance problems are? As long …
-
comment
Comment #4094677
The preprocessor, and conditional compilation especially, are not something to love about C. That is probably one of C's most hateful, code-goop enabling capabilities.
-
comment
Comment #4086220
I do mean almost everything; C has many problems: The preprocessor, no modules, annoying to correctly and portably write even seemingly simple things like signed integer calculatio…
-
comment
Comment #4086180
Either you don't know Java or you don't know Go, because the way the two do things almost couldn't be more different. The JVM and the requirement that every non-primitive be a clas…
-
comment
Comment #4086153
Very few people/projects use Forth… But, I can think of one or two way more popular and significant counterexamples (although I don't disagree with his general sentiment): Perl and…
-
comment
Comment #4086094
Go solves almost all of the problems that C introduces, how's that sound?
-
comment
Comment #4079347
I'm really surprised that people think consoles are currently a niche market for games, after an example like Call of Duty selling 8.4 million copies in the US in a month, with alm…
-
comment
Comment #4079028
The console market is fine and most of what Ars claims has been said at the cusp of every new console generation. The original Playstation came out in 1994 and wasn't discontinued …
- comment
-
comment
Comment #3971516
Why did you decide to use autoconf?
-
comment
Comment #3967997
Clang is not gigabytes big. Even the uncompressed source code for it and LLVM (which are very big) aren't in the gigabytes. http://llvm.org/releases/download.html#3.0
-
comment
Comment #3953873
One of his first examples is additionally absurd and is either the flimsiest of strawmen or he simply doesn't understand when exceptions should be used: try { ... int rc = fx (); i…
-
comment
Comment #3931028
Yeah, I miss domo-kun.
-
comment
Comment #3926455
Exactly what? C99 doesn't have any killer features that legacy code would need to "update" to. If a C89 program is working, adding unique-to-C99 features isn't going to magically m…
-
comment
Comment #3926426
I have severals problems with this. 1) The implication that working legacy code needs to be modified to use C99 features lest it be "out of date". 2) The idea that the world is mov…
-
comment
Comment #3926040
You say that like they are removing all C support. Unless that "legacy" code suddenly mutates to use C99 features that aren't in C++, it'll still compile in the future.