Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mccoyst
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
mccoyst
14y ago
How is Github a monopoly? Bitbucket, Google Code, and even junky old SourceForge are far from unpopular.
2.
▲
by
mccoyst
14y ago
Upvoted. They maintain it by introducing an endless stream of bugs and vulnerabilities.
3.
▲
by
mccoyst
14y ago
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 other people on the web will have the header enabled, suddenly
4.
▲
by
mccoyst
14y ago
Is anyone else disappointed that the best answer (the standard div() function) was passed over in favor of massively inefficient bit-twiddling wankery?
5.
▲
by
mccoyst
14y ago
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.
6.
▲
by
mccoyst
14y ago
A rule for multiple output files: output1 output2: deps
7.
▲
by
mccoyst
14y ago
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 code in "Recursive Make Considered Harmful", always worth
8.
▲
by
mccoyst
14y ago
"low-level rigid type system" You've never written C.
9.
▲
by
mccoyst
14y ago
You still need entities for reserved characters like & and <
10.
▲
by
mccoyst
14y ago
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 as Oracle doesn't add data members to interfaces, Java won't
11.
▲
by
mccoyst
14y ago
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.
12.
▲
by
mccoyst
14y ago
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 calculations, error handling, resource management, almost anything inv
13.
▲
by
mccoyst
14y ago
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 class that inherits from Object are not small differences.
14.
▲
by
mccoyst
14y ago
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 Ruby.
15.
▲
by
mccoyst
14y ago
Go solves almost all of the problems that C introduces, how's that sound?
16.
▲
by
mccoyst
14y ago
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 almost all of the copies on consoles, not PC. And if ever there
17.
▲
by
mccoyst
14y ago
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 until 2009. The PS2 is still being manufactured. PS3 still h
18.
▲
by
mccoyst
14y ago
Why did you decide to use autoconf?
19.
▲
by
mccoyst
14y ago
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
20.
▲
by
mccoyst
14y ago
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 (); if (rc != 0) throw
21.
▲
by
mccoyst
14y ago
Yeah, I miss domo-kun.
22.
▲
by
mccoyst
14y ago
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 make it better.
23.
▲
by
mccoyst
14y ago
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 moving on to newer C standards. 3) The idea that legacy code
24.
▲
by
mccoyst
14y ago
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.
25.
▲
by
mccoyst
14y ago
What rule did he break? What advice did he give?
26.
▲
by
mccoyst
14y ago
"The validity of a logical argument has NOTHING to do with the actual veracity (rightness or wrongness) of the propositions." This is on the poster.
27.
▲
by
mccoyst
14y ago
I don't think that most people understand the GPL. Everybody understands the basic spirit of it, but there are lots of details spread throughout that huge document. The preamble is longer than many permissive licenses. .That there is a prea