skysight-inc/HackerNews huggingface dataset:
Looking at it right now they seem to have got it right:

Chelsea Elizabeth Manning[4] (born Bradley Edward Manning,
December 17, 1987) is a United States Army soldier who…

Compare it with:

Sir Elton Hercules John CBE (born Reginald Kenneth Dwight
on 25 March 1947) is an English singer-songwriter, …
As far as I'm aware, the use of 'they' for third-person singular of unspecified gender goes back centuries already. I don't see what the problem is.
I would strongly disagree with this. Using a pyramid scheme is hardly a good analogy with the current financing system we have.

Its a pyramid scheme when it doesn't work well & a company when it succeeds if I understand your logic correctly?
Bruce Sterling NEXT13 - Fantasy prototypes and real disruption
Suggestion: add a form around the input and button, and bind on its submit. That makes the application work when pressing [return] from the input field

(you'll have to include a (.preventDefault e) in the (listen) callback though)
The correct word is male or female, for binarily-identifying people at least, trans or not. :/
Ok, mountains are not a "need", but Berlin is way too flat for me.
GCC Looks To Turn Off Java, Replace With Go Or ADA
What are the job opportunities in Andorra like? I am in Barcelona just now, but I miss the mountains.
Bradley Manning changed his name to Chelsea Manning. The preceding sentence is "deeply hurtful" and Wikipedia exploded over such "misnamings".

Edit: I'm fine with calling a person how they want to be called, and showing respect where respect is due. But the retroactive-everywhere-always-and-forever corrections are silly.
Springer's books cost so much that I'm sure even Springer doesn't expect to sell them directly. Their money comes from academic subscriptions that they will get regardless of how their readers get the content. This is why I think they are so fond of the golden model -- they just want tonnes of money for their brand. Elsevier is a nest of sociopaths in comparison.
The easiest way to get a prop trading job is by starting out as a programmer. Most trading systems are built in c++ (Java prob number 2 in popularity), so you'd need to master that. Once you're employed at a firm like that it is very doable to transition to a hybrid programmer/quant role. There are vey few non-programming quant roles left on Wall Street and you chances of getting one without a ph.d. are slim.
That's another part of the problem - anyone who complains about stuff like being called fat is accused of demanding "the right not to be offended" and wanting special treatment even if they're doing nothing of the sort, as a way of pressuring them into shutting up.
Leftover Candy Bars and Cream Pie Dessert Recipes
To bring things back full circle to wikipedia:

http://en.wikipedia.org/wiki/Singular_they

I agree that 'they' works well in English and I continue to use it.
Most societies do try to control gambling because of the social problems it causes.

However this has nothing much to do with misallocating capital (after all, if they're misallocating it in gambling, why do you think they'd be smart enough to do any better if not allowed to gamble?) If you truly want to try allocating that capital better than the former owners of the money, buy shares in gambling companies.
This "static" vs "dynamic" distinction is largely artificial. Every program has parts that make sense to think of as "static" and parts that will be very "dynamic", and the ratio of these two differs from program to program (and even within a program, from day to day).

The same goes for making statements about programs.

Therefore, in Pyret, we recognize that there are lots of different levels at which we make statements about our programs: from tests through types to specifications, spanning both static and dynamic aspects. They not only aren't in conflict, they're even related. Most languages include only a subset of them or make them appear to be disjoint. In contrast, in Pyret, we're already working on linking these to one another, and are going to keep pushing in this direction.

Languages that leave out one or more of these end up forcing users to reinvent these wheels for themselves (because they're each good ideas that people inevitably want). But by forcing people to reinvent a wheel, they end up giving users ad hoc versions of these tools, and also introduce friction between these parts. (E.g., as Robby Findler found several years ago, just about every single bolted-on DBC system had significant limitations or errors.)
How our Server Crashed When HN Traffic Kicked in
Obviously not a "deep v" shape nor something blast resistant, perhaps but some form of deflective geometry might be helpful under the car. It does seem the force ultimately is going ^up^ as opposed to >in< . . .
Ubuntu advanced desktop Linux in terms of ease of installation, drivers and slickness bar a time when Debian seemed to be stagnating.
I was a Debian user for years, but around 2005-6 I decided to change my main system to Ubuntu. At the time, it had been years since stable Debian had been updated and I was finding it laborious to update the software manually. Meanwhile, Debian unstable was more up to date with the latest KDE, gnome, etc but was ... unstable. Ubuntu did a lot of work well in terms of final fit and polish to make Debian more user friendly. While I have long been most at home glunking around in a shell, I appreciated this there's a limit to how much time I can spend compiling KDE and upgrading libc.
It seems like a lot of this comes down to simple confusion of how to identify individuals who have been broadly known more publicly under one self-identification which they no longer identify with. Most people came to know about Manning under the original name, just as I came to know about Prince as "Prince" and not [Unpronounceable Love Symbol]. Confusion, convenience and ignorance does not amount to "virulent hatred" in my book, and it is unfortunate that Manning is not consistently identified with her preferred self-identification, but Wikipedia is an empirical indication of how your average person would identify her, and isn't a claim to "correctness." In time it will reflect the changing awareness of Manning's identity as it is brought to the attention of the public more broadly.
The article seems concerned that it took so long to get there, and that the arbitration committee seems pretty biased against trans people, being more eager to lock trans people and people who know trans people out of transgender-related discussions on Wikipedia than taking action againt blatant transphobia/transphobic editors.
Well as long as you are earning more than you spend, that not a problem.On the other hand if you don't then, you may as well go for one of the cheap countries.....
So you put in cash, but where do the btc go?

Does it make you enter your key?
I don't know, there are a lot of variables. As someone else mentioned, not only was this storm stronger, but it was at the theoretical maximum strength that a storm could be. So, it's possibly among the strongest ever to hit land.

You can't get good info from the news and of course any government will has its own agenda to look good. Getting good data from 3rd world countries is also hard.

We took a direct hit (eye passed over the city) from what was at one time the equivalent of a cat 5 hurricane (Pablo) in the southern part of Negros Oriental in the Philippines last year. I don't know what strength it was by the time it got to us, but the winds were pretty damn scary. Fortunately, this typhoon was mostly wind and not much rain. The typhoon created a mess, but we were largely back to normal in one day.

The year previous to Pablo, we got hit by Sendong which seemed like the opposite of Pablo. There wasn't much wind, but the rain was heavy and steady for something like 10 hours. That rain created much more destruction and lost lives than the winds from Pablo.

So, each typhoon has its own personality. You can't do an apples to apples comparison from one storm to another. It's typical of media to make such a comparison.

The Philippines also has some logistical difficulties that India may not have. It's an archipelago of over 7,000 islands and a very poor country. India has its poor areas also, but the nation as a whole has far more resources.

The Philippines did make an effort to evacuate people and clearly the nation could have better prepared. There is always more that you can do. I don't know how this area in India compares to the Philippines, but we get hit with an average of something like 20 typhoons every year. The Philippines is among the most dangerous places on the planet for natural disasters.

Shelters a great for saving lives, and that's the most important, but it also sucks to lose your house and all your belongings. If someone is looking for a world changing innovation, then figuring out a way to make a cheap structure which could withstand the sorts of natural disasters that the Philippines gets hit with regularly would be huge.

ETA:

http://worldnews.nbcnews.com/_news/2013/11/10/21389125-typho...

> Most of the deaths appear to have been caused by surging seas that resembled a tsunami, flattening buildings and drowning hundreds, according to Reuters.

This supports what I mentioned earlier. The wind is bad, but in a typhoon, it's water which really ratchets up the number of casualties. Comparing winds speeds of two different typhoons isn't necessarily comparing the most destructive components.
The author is very clear that you can scale Java and Scala in the same ways. But doing this in Scala is much more idiomatic and concise.
The servers in this example were configured to be asynchronous. The clients were not. You may still be using asynchronous clients in your code but James's argument is that Java developers don't tend to do this because it requires a lot of boilerplate. Scala developers do this because it's very low syntatic overhead and frameworks+libraries embrace it.
I reserve "it" for unborn babies whose parents don't know the gender.
Oh, race might well affect intelligence, it's just that we're pretty sure the effect is so miniscule in comparison to variation within the races that it's not really that interesting unless you're a racist.
It exists. Check out the rails-api project on GitHub
I am also convinced that parenthetical syntax has real problems that I can't completely ignore.

What brought you to this conclusion? Experience from Bootstrap (in which I found arithmetic and parenthesis counting to be the biggest stumbling blocks) or just personal reflection?
Wikipedia's actions in this case are lamentable, but I do have some sympathy for both sides of the argument Sandifer describes. The language we use is highly confusing and basically invites these arguments - we're trying to use too few words to describe too many things.

I have no problem whatsoever with "trans" people but do not think it is optimal for, eg, Ms Manning to be simply labelled a woman. She is clearly not, at least not 100%, female, not in the same holistic psycho-physical way that other females are. For example, I'd like to see her try to use a female changeroom and see if the other females go along quietly with that.

Of course Manning should have the right to her name of choice and to be treated as the person she identifies as. But asserting that one can change gender just by announcing it - even when it is a completely sincere statement - seems far too simplistic to me. I of course understand the argument that inventing some new gender designator could further marginalise an already vulnerable demographic, but by simply avoiding the question I think we've dug ourselves into a bit of a hole.

As another commenter said, names are important. It is important for Chelsea to be addressed as she wishes. But it's also important for our language to have a reasonable set of tools to unambiguously describe things. Simply declaring "she's a girl now, and if you disagree with that in the slightest you're a transphobic cis majority oppressor patriarchal bigot", as I see far too much on Twitter, is not the solution.

It's a complex question and I'm not sure what we can do to solve it. I am glad, however, that the topic is on the agenda - the fact we're even talking about it is surely a step forward.
I couldn't finish this article but I did look into the move discussions.

Chelsea Manning announced her new identity on August 22d. The original consensus on August 31st was to leave the article at Bradley Manning due to the wikipedia policy that subjects be known by their most common name. This was not final, and it was acknowledged that the common name was likely to change so it was decided that the topic could be revisited in 30 days. http://en.m.wikipedia.org/wiki/Talk:Bradley_Manning/August_2...

By the time the topic was revisited in early October, Manning was commonly known as Chelsea by the public and the article was moved.

I don't see any evidence of "transhate" in this, it's just policy. For another example, Snoop Lion's page is still called Snoop Dogg.

Edit: I'd only read the decision summaries; there is transphobia in the vote justifications.
You could put dates on them.

Github (2012-) github.com/Ogdet
Google Code (2006-2012) code.google.com/u/Odget
"virulent hatred" is, imo, clearly visible in a lot of comments that argue against respecting Manning's gender identity. And beyond that it's concerning that the Wikipedia bureaucracy seems more interested in silencing people who know what they're talking about than in dealing with editors spouting hateful slurs and preaching nonsense that goes against accepted medical consensus on transgender issues.
The fact that they don't now doesn't mean they can't in future!

One of the advantages of having a separate block for tests is we can do things in that block that won't necessarily pervade the whole language where it might not make sense (which we already do: eg, the keywords "is" and "satisfies"). We've all done some sort of "here's a list of tuples, now map the prefix of this as arguments and the suffix as the expected value over this function", so it is something on our mind.

But I've struggled a bit to find a good way of writing it. We've written a few things where it looked truly "naked" to have these tuples without the surrounding function call. So it's as much a matter of syntax design as anything else.

I must say that the code on that page does not look like something I want to copy; it looks like a good compromise, but with emphasis on both words. We don't need to compromise.
Thought-provoking presentation, well done.

When I think about most Android apps I use (and especially my toddler daughter's games), I can't imagine 95% of them need the faster execution speed of optimized Java or NDK code. IOW, they could have been written in Python and enjoy:

1. Faster development
2. Portability across devices
http://eli.thegreenplace.net/2006/11/25/a-taxonomy-of-typing...
Various European Locations (Vienna, Milano, Sofia, Belgrade) - Bank

We're currently looking for a couple of "full stack" developers to join our R&D team.
We mainly work with big data analysis and visualization.

Scala is our "lingua franca" for most things (from Akka to Scalding to Play Framework to Spray) (but we've also used Clojure and Python and are interested in just about anything else). We also use Hadoop (HBase and HDFS), ZeroMQ and Redis.

On the client side we've been using D3 a lot with both Backbone and AngularJS (we tend to use CoffeeScript).

Send over your cv (in English) using "6653437 - {desired location}" as subject line to me michiel.pascolutti@gmx.at (pdf please!)
Ask HN: Is Java still worth learning?
Question seems to start on a bad foot to begin with. I wouldn't say answering questions on SO qualifies someone as 'deliberately practicing' when it comes to programming. I've worked with programmers in their 50s who answer very specific programming questions online but couldn't tell you the last time they even considered trying out a new language.
Where's the best place to brush up on composition vs inheritance?
can someone who is better informed than me compare the typhoon a few weeks back in orissa, India with 12 casualties and this one.

note - this isn't a rhetoric. I genuinely want to understand what is the reason for such a massive difference. I have financial interests in that exact part of India and actually have been thinking that the govt is pretty well prepared (given, well that it is India).
Sorry, lost track of what you were responding to.

Re. your other question, yes, this is a wide-open problem, and we're trying to not get bogged down in research issues like this. We actually have one answer about what to do, presented in a paper we wrote some time ago (http://cs.brown.edu/~sk/Publications/Papers/Published/gmfk-r...), but we don't really want to do that. But because we're working on a (curious) type inference story, we may be able to carve up this problem in a very different way.

Sorry for the non-answer. You're right, and we're working on it.
Wouldn't travelling from Okinawa to Philippines have put those ships in the path of the storm?
> a promises based async implementation is not incredibly helpful when you have a strictly one-after-another ordering of data dependencies

I don't understand what you mean. Of course it's helpful.

memcached.get[String]("someKey") flatMap {
case Some(value) => Future.successful(value)
case None =>
database.query(...).flatMap { value =>
memcached.set("someKey", value, 10.minutes)
}
}

The above fetches a key from memcached and in case it doesn't exist, it fetches it from the database and once that's done, it sets the value in memcached and once that's done the processing is done and thus you can continue with other things. If the clients are non-blocking, than that's totally asynchronous and scalable.

In Clojure you don't see this because in Clojure people don't work with Monads.

> Using promises doesn't make the Scala solution meaningfully or usefully asynchronous unless the handler is yielding its thread while blocking on I/O.

The idea of Futures is not to use blocking I/O, but rather to either:

1) use non-blocking I/O, or

2) delegate the blocking I/O call to some sort of actor, then continue the execution once that's done

Both are possible and quite easy.
> I don't see any evidence of "transhate" in this,

There was plenty of transphobia involved in the discussions, even if it's not plainly visible from the move history.
Great presentation, thanks for sharing it.

Why isn't Kivy or one of the other existing solutions good enough for your needs?
Software development is a pretty safe job these days - I would even dare say more attractive IMO. I would even say that getting a good software engineering job isn't all that difficult - getting a first position in anything is difficult anywhere regardless, and software development doesn't care about your degrees. The only thing employers really care about is whether you can write code with the capacity of improving to the point where you can write good code.

I've been in a somewhat similar situation, although later in my life (left a top 15 math grad program, unsure about what to transition into). If you want to get into software development, just start learning it! It doesn't matter if you're not initially at the top - you should have confidence in your ability to learn quick, and your solid logic/problem solving skills, which are musts in software engineering.

You have a massive advantage over me - I deferred answering this question until I left my PhD program, and took about 1 1/2 years to answer it fully. Less than a year of working in web development, I transitioned from being a junior dev to a senior dev. You can easily set yourself on a faster path since you have time on your side.

Also, keep in mind that there are many companies out there that you likely don't know about. Most companies that recruit from colleges are big. That's not the case most of the time in the real world though - the big companies are just the ones who have the resources to recruit from colleges themselves. The majority are looking locally for talent. Networking is the name of the game, so going to meetup groups (especially meetup.com) for what you're interested in is an easy way to net a payoff in getting interviews, especially if you can sell your credentials to people - if you have to fly to cities & have the $ to do so, it would be well worth the investment.

Just my two cents anyhow.
There is a legal procedure for things like these. Living under a name that reflects your gender identity is usually the first step and a requirement for things like hormone therapy, surgery, birth certificate change, not the other way around.
I wonder if this new ART system shipped with 4.4 changes anything - Google like Python and Go so maybe they'd have them available as languages that target the runtime?

PS. See you at LCAU2014!
The wind was reported at 195 mph with 235 mph gusts

That's insane. I'm sure it would rip out most testing equipment. I've seen the damage from similar micro-bursts (<200mph) in the US and nothing is left standing. And I mean nothing alive. Complete devastation. It would look like thos pictures from when the meteor hit Siberian in the early 20th century. A mess of matchsticks.

_______

edit: updated info

Haiyan attained its peak intensity with ten-minute sustained winds of 235 km/h (145 mph)

one-minute sustained winds of 315 km/h (195 mph) and gusts up to 378 km/h (235 mph)

Still a record, but the sustained winds are more in the mid 100's rather than approaching 200. Immensely strong peak gusts. 10 minutes of that at peak energy must have seemed like a lifetime. There is no natural shelter in these situations. Truly, truly dangerous.

Edit2: like here> http://forums.mammothmountain.com/viewtopic.php?f=15&t=12869...
Yes - if you like money and job security - there is very strong demand for java developers and a lot of code to be maintained. Java is entrenched in the corporate world.

If you want to learn something from learning Java - not so much.
A Day in the Life of a Computer Programmer
The type system hasn't been published yet.

We don't have monkey-patching. We've been burned too much by JavaScript and the like.

Cyclic structures: think about trying to teach graph algorithms. Let's say you believe it's important to write tests. Many graph algorithms aren't inherently mutational. But you need mutation just to create examples of your data. The graph construct gets around this problem entirely, so mutation and graph algorithms become orthogonal topics. In general, I'm a big believer in eliminating unnecessary curricular dependencies. Having taught graph algorithms this way for a few years now, I can't imagine going back.

See the notes on graphs in PAPL (papl.cs.brown.edu/2013/).
You're probably not going to find a temporary programming job where you make appreciably more money than unrelated work so I would suggest finding a job where you're going to meet a lot of people around your age in a similar situation and kick around ideas for projects to do together. Never know what might come of it and the lessons you'll learn from trying to actually build a product will be invaluable.
You're mixing "woman" - gender - and "female" - biological sex - a lot here. The two are not the same.
This is a weird way to put it. The topic has been on the agenda for a long time, gender identity disorder wasn't just discovered yesterday, and there's broad consensus and best practices in the relevant parts of the medical community.

Invoking some "holistic psycho-physical" intuition to dismiss years of research and experience with transgender issues is somewhat presuming.
I agree. If your argument is that doing X in language Y is bad because you have to write a few extra lines of code, and therefore no one (meaning the author) does X, that's an argument that reflects most poorly on the author himself.

You haven't made your Java webapps robust and tolerant of failure because you don't like the extra 3 lines of code you have to write? That makes me question you as a developer and the value you place on things, not the language/ecosystem.