HNHacker News
TopNewBestAskShowJobs

rntz

2,169 karma · joined May 25, 2009

www.rntz.net email: http://www.google.com/recaptcha/mailhide/d?k=018XOhLYKe9NqLdmoSmt6HsQ==&c=mcxnT-9mQPQEL6wailXqNUHk3aPs4Jv1T3vTJsNNAkg=
submissionscomments
rntz··on AlphaGo Is Not the Solution to AI
That's a case of deflation due to hype, not due to anti-hype. The whole point of the original article is to avoid overpromising and underdelivering.
rntz··on AlphaGo Is Not the Solution to AI
> Anti-hype is perhaps more pernicious in bringing about an "AI Winter" than is drumming up interest in what AI, or more accurately AGI, will be capable of in the not-too-distant future.

AI is massively popular in both industry and academia at the moment. It is at no risk of being deinflated by "anti-hype".

rntz··on Encryption, Privacy Are Larger Issues Than Fighting Terrorism
Wrong article. You probably meant to reply to https://news.ycombinator.com/item?id=11288841
rntz··on React Makes You Sad?
You might wanna rethink that target date (April Fool's Day).
rntz··on Functional Programming Is Not Popular Because It Is Weird
The article could use a better example. "C++ templates are complicated and hard to write compared to straight-line imperative code" is not going to convince any functional programmers that imperative programming is nice, even if you can argue that C++ templates are a "functional" language.
rntz··on Functional Programming Is Not Popular Because It Is Weird
Anecdatally, I'm a very top-down programmer, and also a discrete math & logic nerd, and I tend to prefer FP. I'm not sure why you think "math types" tend to work bottom up. Perhaps we mean different things by top-down/bottom-up? Can you give an example of what you think of as "top down" design versus "bottom up" design, and why it seems "top down" is easier in an imperative language and "bottom up" easier in a functional one?
rntz··on Oden: experimental, statically-typed functional language, built for Go ecosystem
What do you mean by "strict semantics"? As a PL researcher, I associate "strict" with eager (as opposed to lazy) evaluation, but Go is eager, so you can't mean that.
rntz··on What Google Learned from Its Quest to Build the Perfect Team
The linked article doesn't support your claim that brainstorming "emphasizes only communication abilities"; it only claims that brainstorming in groups is a worse way to generate ideas than to have people generate ideas individually & then combine them.
rntz··on What Google Learned from Its Quest to Build the Perfect Team
> This is the classic phenomenon of male friendship.

Why do you single this out as an especially male phenomenon?

rntz··on Map of battles fought since 2500 B.C
Both.

There's a massive bias in our historical records towards Europe. But Europe has also seen a lot of wars.

rntz··on Half the world to be short-sighted by 2050
Presbyopia and myopia are not opposite; in fact, you can have both at once! My mother has to wear bifocals for precisely this reason.
rntz··on Outerra, 3d planetary engine for seamless planet rendering from space to surface
There's some folks called I-Novae trying to do a similar thing, but making a space-fight simulator game on top as well, called Infinity: https://www.inovaestudios.com/Technology. I'd be curious to hear a technical comparison. It looks like Outerra focuses more on the planet-side and I-Novae more on the space-side.
rntz··on What “Worse is Better vs. The Right Thing” is really about (2012)
> The point of the posted link is that worse is better than nothing.

No, that's inaccurate.

For instance, one example the article used to support WiB was that x86 (a CISC architecture) beat out RISC architectures. There were many RISC architectures: MIPS, SPARC, DEC Alpha, PA-RISC. So it's not a case of worse is better than nothing. x86 won against real competition, because it took advantage of evolutionary pressures.

rntz··on What “Worse is Better vs. The Right Thing” is really about (2012)
Taken charitably, it sounds like the official is describing the state-level equivalent of operating inside an enemy's OODA loop (cf https://en.wikipedia.org/wiki/OODA_loop, brought to my attention and reasonably well-explained by http://thefederalist.com/2015/12/16/military-strategist-expl...) - roughly, acting so quickly as to make the enemy's response obsolete by the time they go through with it.

Worse-but-Better solutions make it to market dominance before the Right Thing has a chance to get off the ground; and then the Right Thing is no longer the right thing, because the reality has changed.

Taken uncharitably, of course, it sounds like puffed-up nonsense, which perhaps it is.

rntz··on Why Rust's ownership/borrowing is hard
> All GC'ed languages still have issues of ownership, especially if threaded,

This is not true. Ownership is only relevant in the presence of mutability. In a GC'ed language where most or all data is immutable, one rarely needs to think about ownership. In Rust, one needs to think about it all the time.

Rust is certainly a leg up compared to trying to write multithreaded C or C++ code, but that doesn't mean its approach is free of drawbacks.

Empirically, even in Python - a mutable-by-default language - I find myself rarely having to think about ownership. That could be an artifact of the kind of Python programs I find myself writing, though. I'd be interested to hear other people's experiences on that front.

rntz··on How the Fight Over Transgender Kids Got a Leading Sex Researcher Fired
> All the stuff about the adolescent he may or may not have mocked is a red herring - I've followed this issue, and literally the only place I've heard it mentioned is articles defending Zucker.

The article brings up many more flaws with the external review than the use of that anecdote. For example, the misreporting of statistics (70% vs 30% of patients meeting the criteria for gender dysphoria); the low number of interviews with actual patients of the GIC (9 or 11), of whom even so only 2 had complaints; misreporting the nature of the use of play therapy (for assessment vs treatment); and so forth.

If the GIC is to be condemned (as perhaps it should) for conversion therapy, it should at least be done on the basis of a thorough, fact-checked independent review; the article's thesis is that the external review conducted by Zinck and Pignatiello does not suffice. It's not just one anecdote they take issue with.

> His approach involved telling parents to prevent their kids from playing with toys of the "wrong" gender [...] > His position - what he told parents coming to his clinic for help [...] > I've followed this issue, [...]

Do you have any links you think are particularly informative about the practices of the GIC in this regard?

rntz··on How the Fight Over Transgender Kids Got a Leading Sex Researcher Fired
> where it accepted for young children to be attracted or even in love with other children of the same sex.

That's sexual orientation, not gender identity, no? One of the salient points in the original article is precisely the distinction between gender identity (which the GIC sees as flexible, but their critics see as immutable) and sexual orientation (which both appear to view as immutable):

> GIC clinicians view this as a conceptual error: The critics are conflating sexual orientation — which can’t be changed, which is part of the reason we view attempts to mess with it it as unethical — and gender identity, which they say isn’t some hardwired thing

rntz··on Requiem for GitHub
There is a difference between believing some particular individual is guilty of harassment and accepting that a harassment problem exists in an industry or company. If we want to convict someone, either in the court of public opinion or in a court of justice, we must hold ourselves to a high standard of proof. Better a murderer go free than an innocent be hanged, and so forth.

But if we're interested in whether the industry itself has a problem, in whether a problem exists, then we should take women (or anyone else!) at their word when they say they experience harassment, absent strong evidence that they are lying or mistaken. Otherwise, we are violating the same rule: assuming they are guilty of lying until they prove themselves innocent!

rntz··on Requiem for GitHub
I had not seen that post about the investigation before; it's very enlightening, and I upvoted spangry for linking it.

My default assumption is that when there are claims of harassment, there is some substance to them, even if the specifics are wrong. Bringing forward claims of harassment in the tech world turns your life (and that of the accused, if their name is publicized) into a shitstorm; people don't tend to do that without reason. But this is just a heuristic. It looks like Horvath's claims of harassment might be unsubstantiated in this case.

It's hard to tell, though, because most of the things she complains about (with the exception of the code-review stuff, which appears to be just false, which is worrying) is unverifiable outside of he-said/she-said. Note the noncommittal wording: "The investigation found no information to support misconduct or opportunistic behavior by the engineer against Julie or any other female employees in the workplace." No information to support suggests "neither evidence for or against". Which is natural. Harassment is hard to prove or disprove precisely because it usually doesn't leave evidence.

> there was an apparently thorough investigation by a reputed external investigator who found that the claims were false. [...] And yet this single person's claim was enough to force out the CEO

Specifically regarding the ousting of the CEO, let me quote the investigation you linked:

> The investigation found Tom Preston-Werner in his capacity as GitHub’s CEO acted inappropriately, including confrontational conduct, disregard of workplace complaints, insensitivity to the impact of his spouse's presence in the workplace, and failure to enforce an agreement that his spouse should not work in the office.

rntz··on Requiem for GitHub
> The sexual-harassment stuff is unfortunate, but organizations of primates have things like that happen now and then, it's just rare that the victims decide to go public. This does not excuse it but it doesn't necessary say anything about the culture

Harassment does say something about the culture in which it happens. What you're pointing out, correctly, is that it's not exceptional for this kind of stuff to happen - that Github is probably not much worse than most other tech companies in this respect.

As you say, this is no excuse. Change has to start somewhere; we can't keep saying "oh, it just happens, you know, it's not worse here than anywhere else".

> Maybe Github should split into a corporate division and an open source division. The OSS division could make all of its work and decision making distributed and public, and the corporate division could do business development and attack new market opportunities.

I would like that, but how would it make investors money? If the answer is "it doesn't", then it won't happen.

rntz··on Requiem for GitHub
The author is being sarcastic. They are saying that, from the point of view of the "wolves", Github doesn't look like a $20bn company - so it will be made to look like one, by hiring more employees, changing the power structure, and becoming more enterprise-oriented.
rntz··on COGENT: Certified Compilation for a Functional Systems Language
Indeed, but proving a whole compiler correct is really hard. :P
rntz··on COGENT: Certified Compilation for a Functional Systems Language
No, the proof that the compiled code is "correct" does not depend on the compiler being correct - it can be checked independently.

Of course, if the compiler is incorrect it might generate incorrect code, but then the "proof" that the code is correct would not check.

Mind you, it's very ambiguous to describe what their compiler is doing as producing a proof of "correctness". Any time someone says "correct", you should ask, "correct with respect to what?" In this case, AIUI, their compiler produces: (a) a formal description of what the program does (what they call "a high-level shallow embedding of the program's semantics") (b) a proof that this is in fact what the program does (its "correctness")

The idea being that if you want to show that your program is actually correct with respect to the specification you really care about, you do the proof on the formal description (a), and then (b) automatically guarantees your proof carries over to the actual program.

rntz··on Silicon Valley and Black Coders: Howard University fights to join the tech boom
Sure, but I wasn't talking about what it takes to be the best in your field. I was talking about what it takes to even be given a fair shot. (Original comment: "If you didn't spend a lot of time with computers on your own before college, you're not in the running.")
rntz··on Clojure is for Type B personalities
I think it simply reflects that the distinctions each is making are, to a great degree, subjective and up for debate. See, for example, http://blog.ezyang.com/2012/08/is-haskell-liberal-or-conserv..., which argues that Haskell of all languages is, in a sense, liberal.
rntz··on Clojure is for Type B personalities
Cathedral and Bazaar are about different ways of organizing projects; Liberal/conservative or Type B/Type A are about individual programmer preferences. So they're not the same thing, although there's some amount of sympathy between them - one might expect liberal/type-B personalities to be attracted to bazaar work and conservative/type-A personalities to prefer cathedral work. But I don't know to what extent this is true, or testable.
rntz··on Clojure is for Type B personalities
This is basically reinventing Steve Yegge's analysis in [1] of programmers into "conservative" (risk-averse, prioritize safety) and "liberal" (accepting of risk, prioritize expressivity), except less polarizing (because it doesn't involve political comparisons) and less thorough. Oakes also calls for reconciliation, while Yegge tips his hand as a hardcore "liberal".

[1]: https://plus.google.com/110981030061712822816/posts/KaSKeg4v...

They're both vaguely accurate but break down if you try to credit them with too much explanatory power (as Yegge does, IMO, but Oakes doesn't seem quite as reductionist).

rntz··on Silicon Valley and Black Coders: Howard University fights to join the tech boom
Are teachers, accountants, mathematicians, scientists, doctors, or lawyers known for practicing to get into their respective fields in elementary & middle school? Not so much. Even for the most demanding fields, we expect them to begin to specialize only in their high school years.

To my mind, the fields which are known for requiring training from childhood are sports and the performing arts (music, theatre).

And if I had to guess, I'd speculate this is less because it's intensely difficult to play sports or learn to play music, but because so few people can become professionally successful in these fields (there's only room for so many sports/music/film stars). CS doesn't have this problem (the demand for programmers is skyrocketing), so we shouldn't expect folks who learned to program in childhood to have any more than a mild-to-modest advantage.

rntz··on Silicon Valley and Black Coders: Howard University fights to join the tech boom
Do you have anything more than anecdata for the idea that "If you didn't spend a lot of time with computers on your own before college, you're not in the running."?

I've heard that idea in a lot of places, but it's never matched up with my personal experiences. I did my undergraduate at CMU, and plenty of the better programmers there I knew hadn't done any programming before they came to CMU.

But of course, this too is anecdata.

rntz··on Silicon Valley and Black Coders: Howard University fights to join the tech boom
This is a misrepresentation of the article's position. The article's actual, more ambiguous, position is better summarized in another paragraph:

> People tend to discuss Silicon Valley’s diversity problem in binary terms. One camp says companies are biased against underrepresented minorities, or at least aren’t trying hard enough to attract them. The other says there aren’t enough people from these backgrounds who are qualified for positions—or at least who are good enough to beat those Stanford grads with all the programming trophies and internship experience and Mozart-like childhoods. The reality is, both are true.

← PreviousPage 8 of 15Next →