Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

> It's a matter of if you think about it for a bit it makes no sense, it's logically impossible.

Let's take a look at a dictionary definition of culture: "the way of life, especially the general customs and beliefs, of a particular group of people at a particular time" (http://dictionary.cambridge.org/dictionary/british/culture)

Now, note the "particular group of people" part. A person can be a member of more than one group. Some groups are sub-groups of others; some overlap with others.

For example, I am an American, and as such I have been brought up in American culture, with many of the traditions and ideals that that entails; Thanksgiving, the 4th of July, a strong belief in civil liberties, and a love of strawberry rhubarb pie.

American culture is also a subset of Western European culture, with influences from Catholic and Protestant branches of Christianity, so while I am not myself Christian, I celebrate Christmas and Easter and have many Christian influences on my values and life.

However, I am also a member of other cultures. My most recent ancestors to travel to the US were Scottish; and so Scottish culture is also part of my culture, but not most other people in the US. I wear kilts to weddings, and have an uncle and cousin who play bagpipes at weddings and funerals. That's a part of my culture, but that is not a part of overall American culture.

I'm also a software engineer and computer geek, and involved in free software, advocacy for civil liberties online, advocate for strong encryption and privacy, and the like. This is a particular subculture that tends to promote strong protections for individual privacy and liberty, while openness and transparency on behalf of institutions such as corporations and governments. This is not part of mainstream American culture, but it is part of my culture; and this particular subculture spans multiple countries as well, so in many of these ways, I have more cultural values in common with a Brazilian or German who is also involved in these communities than I do with the average American.

There are many other subcultures I could describe myself as a member of. And the same goes for anyone you ask. "Culture" is not one big, monolithic thing with clear boundaries. Because it is a set of customs and beliefs shared with a group, that set can be larger or smaller, and stronger or weaker, depending on how big of a group you choose.

> And if "multiculturalism" whatever that is, is so great, you'd think someone would have come up with support for that notion by now beyond "Ethnic food!"

Food is a pretty fundamental part of any culture. As something that is necessary for sustaining life, it's something that everyone does. In almost every culture I've seen, meals are a large part of fostering community, of strengthening social bonds. You have meals with family, with friends, with coworkers. "Breaking bread" is a term rich with culture connotations of mutual trust, peace, welcoming, because sharing food with someone is so important; and the same holds in many other cultures, one of the most generous and welcoming things you can do is invite someone to your table and share your food with them.

So don't be so quick to dismiss "ethnic food" as an important part of multiculturalism. Food is in many ways the heart of of a culture, and exploring the food culture of another people can be a strong way to share something with them.

However, multiculturalism can extend far beyond that as well.

The musical heritage of America is quite strongly multicultural. Ragtime, blues, jazz, R&B, and hip-hop all have their roots in black culture in the US, but have had enormous influences in white culture as well. Of course a large amount of American musical traditions comes from Western European classical and pop traditions as well, and then there are a variety of folk traditions, such as Celtic, that have been integrated into the mainstream through bluegrass and country music.

But there's a lot more than just that. A large number of cultures have made substantial impact on film in America. Many of our "Western" genre is actually a product of Italy; but that in turn influence Akira Kurosawa in Japan, with Samurai westerns such as Yojimbo. His work has also influenced Western work, where The Magnificent Seven is a western remake of Kurosawa's Seven Samurai, and his The Hidden Fortress is one of the major influences on Star Wars.

Let's see, getting back to day to day life, Jewish culture has also had a fairly large impact; from Yiddish, we get words like "schmuck", "chutzpa" and "klutz". We also get bagels (oops, back to food again),

On the musical front again, some of the best American music like Gershwin's Rhapsody in Blue had roots in Western classical tradition, jazz, and klezmer, traditional Ashkenazi folk music.

I could go on, but man, detailing all of the positive effects of multiculturalism on American society could fill up hundreds of volumes of books, not just a single comment on HN.

> A murder seems to be ipso facto a hate crime.

That is not what is meant by the term "hate crime." Simply redefining a term that has a particular meaning to mean something else does not really add to the discussion.

I'll quote from Wikipedia:

> In both crime and law, hate crime (also known as bias-motivated crime) is a usually violent, prejudice motivated crime that occurs when a perpetrator targets a victim because of his or her perceived membership in a certain social group. Examples of such groups include but are not limited to: ethnicity, gender identity, disability, language, nationality, physical appearance, religion, or sexual orientation.

A "hate crime" is not simply any violent crime. It is a crime in which the attacker was motivated by their perception of the victim's membership of some other group.

There are several things that can motivate a criminal to commit a crime. Poverty, greed, hatred of a particular group, hatred of a particular person, sheer anti-social tendencies, and I'm sure many other motivating factors. Only one of these falls under the term "hate crime" as it is commonly defined; those crimes in which hatred of a particular group of people is a primary motivator.

If you look at the statistics I cited in a previous comment, while it is true that black on white murder happens more often than white on black, white on white murder far surpasses either (and likewise, black on black). No amount of arguing about the black on white vs. white on black levels of crime will make these intraracial crimes go away, and the levels of intraracial crime is a very strong signal that racial animus is not actually the motivation for the majority of crime that occurs.

The reason it is important to look at the motivation behind a crime, and not just the statistics about whether a crime happened, is that the motivations can help tell you the best way to reduce that type of crime in the future.

Hate crimes, in the sense of any crime committed on behalf of membership in some group, can be particularly dangerous because they can lead to either prolonged violence between those two groups, or ethnic cleansing or genocide. These types of crimes, when allowed to escalate, have escalated into some of the greatest atrocities of a last couple of centuries. Breaking the chain of hate-motivated violence by discouraging the use of rhetoric of hate, by changing laws that institutionalize disparities between these groups, and by applying harsher penalties to those crimes committed for these reasons, are some ways to deal with these types of crimes.

Crimes committed due to a hatred of a particular person, however, are fairly different. They are usually based on some aspect of those people's relationship; perhaps an abusive domestic relationship, a cheating spouse, or the like. Here, there isn't some group-based animus, but a dysfunctional personal relationship. Here, the better way to deal with the problems are to provide better outlets for change than violence; provide shelters for people to escape from abusive relationships, allow divorce, as it it preferable to violence or murder.

Crimes that are committed due to poverty, to people having as sense of hopelessness and no further opportunity but to turn to crime, are another kind of problem. Here providing better social services, better education, better access to affordable housing, and the like can all help take that pressure off that can push people over the edge.

In all of these cases, the actual perpetrators of actual crimes do need to be punished; there needs to be deterrence as well. However, on a societal level, there can be many things done to reduce the temptation and pressure to engage in criminal behavior. And even on the individual level, knowing someone's motivation for a crime can be important in rehabilitating them and reintroducing them back to society.


> they didn't immigrate and expect to receive special treatment because they were a member of group X.

No one is asking for "special treatment". They are asking not to get special treatment that consists of being killed by police officers.

And yes, too many white people are killed by police. The police in the US have both a tendency to shoot too many people, and have a tendency to target too many black people, which both add up to shooting disproportionately many black people.

And yeah, the problem is more complex than simple racism by police. There are problems of too many criminals being armed in the US (both black and white), meaning that the police are more prone to shoot in supposed self defense. There are problems of class and poverty, that lead people into violence. There are a lot of complex, interrelated factors that lead to this.

But all of that said, it is undeniable that there are a disproportionate number of law abiding or peaceful, unarmed black men who are killed by police in this country.

> The real race problem is that when it comes to interracial violence, and black on white vs white on black, the facts are black on white racial violence is off the charts compared to white on black racial violence. It's not even close.

Interracial violence is a pretty small fraction of all violence.

Most violence is intraracial. Source: http://www.bjs.gov/content/pub/pdf/htius.pdf (2010, reporting data up to 2005, see page 67); about 42% of homicides are black on black, about 45% are white on white, about 8.8% are black on white, about 3.2% are white on black. If you're white, I'd be a lot more worried about that 45% than the 8.8%.

You know what's likely to be the most likely way to avoid getting killed or shot? Not having family members who have ready access to firearms. You are a lot more likely to be shot by a family member in anger than you are by a stranger of another race.


> Apple serves its Users not Developers, most of whom appreciate there's only 1 icon they need to click on to access the Internet. Only developers think that having multiple browsers to choose from is a value-add - for most users it just adds unnecessary confusion and complexity.

And Apple's restriction has nothing to do with "only 1 icon"; you can ship competing browsers, and in fact Google ships a "Chrome" on iOS.

The restriction is on the rendering engine.

And note that this restriction does not "serve the users". Users who want a faster, or safer, or more compatible browser with some favorite site of theirs that is pushing the envelope on mobile apps via the web are not able to use a better browsers with a better rendering engine.

Look at how many people run Chrome and Firefox on Windows and OS X, when there is an existing browser available. They are not all "developers"; they are users looking for faster rendering, more compatibility with services that are pushing the envelope of web apps, a safer experience, and the like.


Sadly the Google Chrome on iOS is just a UI over the safari engine. Apple won't let Google port their web engine over to iOS like Google did for OSX. This means that Google Chrome on iOS is stuck with however Apple decides to render the web.


That is exactly what lambda is saying... The choice of browser engine is a facade.


For anyone curious, this section is on SAT solving. It's section 7.2.2.2 of TAOCP, and is over 300 pages long. Pretty thorough for a section of backtrack, within a section on generating all possibilities, within a full chapter on combinatorial searching.


For what it's worth, I went to a presentation by Knuth on this exact section with a SAT expert who frequently commented how (for the presentation at least), significant amounts of relevant material had not been mentioned, and some techniques introduced were not particularly close to the state of the art, or good for educational purposes.

What I'm saying is that there's plenty of literature on SAT Solving already, and some of it is probably better.


Could you convince this SAT expert to review Knuth's fascicle and send his comments to Knuth? or blog about it for everyone's benefit?


I was reading the proceedings of the 2013 SAT competition and was pleasantly surprised to find Knuth listed as a contestant! It also included a few paragraphs he wrote about his submission.


Hacker News does not support markdown. It supports just italics with asterisks, blank lines for paragraphs, code blocks by indenting with two spaces (while markdown uses 4), and auto-linking URLs. https://news.ycombinator.com/formatdoc


Hmm, I figure it's more the the optimizer depends on code not exhibiting undefined behavior, like in C. It's not really the case that it's lazily evaluated, just the the causality gets screwy when you try to observe things in an asynchronous system without any kind of coherent memory model.


> only to have a mode where it refuses to silently make 'optimizations' when it does identify UB.

That's not always possible. It's not that it makes the optimization when it identifies UB. It's that it makes an optimization that is valid to make if UB doesn't occur, but if UB were to occur then that optimization could cause all kinds of unexpected problems. But the compiler can't necessarily identify those cases.

Please read the "what every C programmer should know about undefined behavior" series of articles from LLVM; they describe the reason why they can't, in general, provide warnings or errors for these cases in which optimizations rely on lack of undefined behavior:

http://blog.llvm.org/2011/05/what-every-c-programmer-should-...

http://blog.llvm.org/2011/05/what-every-c-programmer-should-...

http://blog.llvm.org/2011/05/what-every-c-programmer-should-...

The third article describes why the compiler can't, in general, warn about those cases in which it's relying on lack of UB, but you should read the first two as well.

Note that for some of those cases, clang and GCC have recently added undefined behavior sanitizers, invoked via "-fsanitize=undefined", which can help even more than the warnings they can add. However, what they do is add extra instrumentation to the executable, and then either log a warning or crash when you hit undefined behavior. The runtime aspect helps avoid the "getting this right would involve solving the halting problem" aspect of why they can't, in general, provide appropriate warnings, but it does mean that this is generally only appropriate in test builds, and that you will only find the undefined behavior that you can trigger during test, while there may be more hiding that only show up in obscure circumstances.

If you really don't want undefined behavior, it's best to use a language, like Rust, which does not have any undefined behavior (outside of "unsafe" blocks). The problem with any kind of warnings that are tacked on after the design of the language is that you are either going to get lots of false positives, lots of false negatives, or both. With a language that is designed not to allow undefined behavior, you know that if the code compiles, it doesn't invoke UB.


Did you read the article?

Their top two recommendations were invest in a startup, or give to the Gates foundation.


I said start a company. That's different than investing in someone else's company. You can't be much of an investor with $20k, that's about what Y Combinator gives a team for an initial seed. That money is quickly followed by VC money.


Wow.

I... don't even know what to say about that.

I have known many people to not drink beer. Some of them do so because they just don't like the taste. Some don't because they are former alcoholics. Some are alcohol intolerant; others have trouble with the carbonation. Some don't for their own personal moral or health reasons. Some don't for religious reasons.

I have never had one of those people "impose or restrict" my rights or "make me feel very uncomfortable" in the workplace or any other venue I shared with them.

This exact attitude, assuming that someone who doesn't drink beer will be a detriment in the workplace, is the kind of thing this article is refuting; that if you use enough of these "culture fit" markers, then you will simply wind up picking a team with very little real diversity, which could cause real problems in the long run.


I think that this is a good question, but poorly phrased; you assume in the phrasing that it's possible for the existence of one language to "kill" another.

I was somewhat disappointed when Apple shipped Swift; I feel like Rust has considerably more potential as a general purpose language, and it would be nice to have less dilution of effort in fairly similar space.

However, I don't think that the existence of Swift is an existential threat to Rust.

> Swift will be able to do everything Rust can do and is also positioned as a systems programming language

Swift is an interesting language, with some good ideas, and in many ways easier to use for application programming than Rust; but I still, on balance, think that Rust is more interesting and versatile.

Swift is not really a systems programming language. You can't write a kernel in Swift, nor target embedded platforms, nor write a library that could be called from other languages like Ruby or Python (at least, without bringing in the whole runtime as well). It's closer to the space of Go, a more systems-y application language.

Furthermore, open source Swift does not mean you will be able to use the whole ecosystem on other platforms. I highly doubt that Apple will port Cocoa/Cocoa Touch to other platforms; so Swift on other platforms will likely only be viable for back-end code.

Objective-C has been open source for years, and until the introduction of Swift was the dominant language of choice for writing code on one of the most popular smartphone platforms, but Apple canned cross-platform OpenStep when they bought NeXT, and Objective-C has never made serious inroads on other platforms (I know exactly one person who writes production, server-side code in Objective-C on Linux).

So, I could see Swift becoming popular for writing backends for iPhone applications, but I can't imagine that it will make serious inroads in other spaces, unless Apple makes a dramatic change in strategy and starts shipping their UI libraries on other platforms as well.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: