throwaway999888

> When you choose the clearly better developer over the other, you're often choosing the one who had better resources growing up, not just natural ability.

Ahh, but natural ability is just as much of a privilege as having a fortunate upbringing! Both are essentially unchosen, born-with things; you can't choose your inborn talents, and you can't choose your parent's resources.

Really, what you're scoffing at is learned skill and saying that born-with skill is better, for whatever reason.

But meritocracy[1] just means "only results matter". It doesn't matter if you worked your ass off for 30 years in acquiring skills that bring results, against all odds (whether genetic or externally imposed). Or if you were just born with it and hardly had to put in any effort.

[1] Whether that is a reality or not; doesn't matter for the sake of the argument.

It's a weird language bug. I wish English (and my own tongue) was as consistent with the dots as Turkish is. ;)

The closest to what you want might be ATS.

So uppercase Turkish `ı` is the same as ASCII `I`?.

Go and Haskell also have some special (unconventional) treatment of capital letters, which probably make them biased towards the English language.

All I've seen indicates that hunter gatherer populations were more likely to be taller than most historical peasant populations. As a consequence of a peasant's diet being less nourishing.

It's unacceptable because of the manager-subordinate relation.

And you can't put the burden on women to actively signal that they are not sexually interested in a professional setting. That's at best a large distraction for them, and at worst very draining and emotionally damaging.

Ah, I see things are working as planned. The upper middle class and lower feeling guilt at their salaries, even though it's just a pittance in the larger pool.

But I've been thinking about how much money I really need. I could have indulged in some expensive hobbies, but I can also get by with lesser equipment and practice the same hobbies, as long as I don't obsess over how "bad" that equipment is. And there are a lot of hobbies that either cost little to maintain, or that benefits other people. So there seems to be a lot of potential for reducing spending on oneself ones immediates and funneling some of it elsewhere (either through money, labour or time).

I don't believe that you would need Strong AI to automate away dangerous parts of jobs. Or the monotonous parts.

I agree. We have a come a long way already, and I would personally prefer that we do our best to not screw up what we already have. That includes global warming, unleashing Strong AI, and so on.

It might suck to actually have to work, even as much as 40 hours a week or more in this day and age and with the productivity increases we've seen. But I don't think work itself is that horrible that I would bet my leisure on some AI that consumes the known Universe making and collecting stamps.

There is already built-in support for pull request[1] and patch based workflows in Git itself. Why do we need to wait for, and choose based on, hosted services providing things like that? EDIT: for more clarity; using pull requests and patches with Git itself means that it simple to rebase or whatever, since you're just working with branches and patches directly.

Or am I missing something? Other than something like usability, perhaps...

[1] I'm not actually quite sure if there is a specific command for that format. Though it should be easy enough to have a third party solution that uses a format through email.

I for one am just waiting for the cispiler.

Finally a use for the GitHub heatmap.

> Why (almost) everything you know about food is wrong

They tell me every other year.

It's how humans rationalize their view of their own "development" and "progression":

1. I liked to do an activity before.

2. I don't do that activity any more, nor like it.

3. I am older, so I must be wiser (or else I wasted my time)

4. Therefore the old activity was bullshit all along. All hail my personal development.

So it is 1. built on top of heavy heavy Web technology 2. very much tied to the OS. The worst of both worlds...

Tech is pretty insular, isn't it. Like how your site uses "gov", a top level domain for the whole WWW restricted to be used by government-specific entities in the UNITED STATES (of America)[1]. Moreover, "The U.S. is the only country that has a government-specific top-level domain in addition to its country-code top-level domain." (Wikipedia)

[1] The point isn't that other governmental entities should be able to use "gov", though. Since English is not a universal language.

I'm not great at naming.

I would find such a bot REALLY annoying. And I have a hard time imagining how others would not, unless they had already tried to put themselves on a guy-less diet.

Since this is a post about "how we work", I would imagine that I would initially get really annoyed, and then be reminded by how it is just a front for social pressure from colleagues/higher-ups. Then when someone asks about how such a reminder has been working for me, I'd just say Great! Really kept me on my toes, such an effective reminder. ...

Not that I even use "guys" that much in any case (or English in daily life!).

Well, for one he doesn't like GitHub pull requests. ;)

https://github.com/torvalds/linux/pull/17#issuecomment-56546...

So host on multiple sites?

"Regulating content" just meaning having some standards for what is hosted on their sites.

GitHub is (or should be) just another Git hosting site/Web frontend/misc. integration with other software project's concern. It should be relatively simple to just choose another website. If we've gotten to the point of saying that they are 'regulating the content of open source projects', we've already failed by making GitHub too important.

Then it's truly a win-win! ;)

What other approach do expect from a place/culture like that.

1. Move code and related (issues etc.) to GitLab/Bitbucket

2. Mark GitHub repo as "Mirror Only"

3. Unsubscribe from all GitHub Issues and notifications (see 2.)

4. No more low-effort spam, only the occassional medium-high effort questions and issue reports. Sweet relief!

If the choice was between piece of mind and stars on GitHub, I think I'd take the first.

Why distributed version control? You need a central place to pull from and push to, to ensure that forks and patches are not duplicated everywhere... ;)

Sorry.

> And if you do it you would probably see yourself as less of a judgemental prick

But what if I already don't see myself as a judgemental prick? :)

> Hmm. I wonder what kind of person I'd be if I had the

> privelege

> and luxury

You would probably see yourself as less of a victim of unfair external circumstances.

It's OK. You may display that book prominently and proudly on your cubicle's bookshelf. You've earned it! ;)

> I thought that rustc was boostrapped from the old c based compiler(allowing you to build clean from source)

What's with all the baseless assumptions of the initial Rust compiler being written in either C or C++ in this thread?

Contrary to apparently popular belief, C and C++ aren't some primordial lifeform compiler language which all language implementations have to be initially written in. Believe it or not, you can write a compiler in any (general purpose) programming language! Amazing, I know.