skysight-inc/HackerNews huggingface dataset:
Thanks for your thoughts.

You're right there's a lot of activity in this space, language learning tools seem to be a common itch that developers like to scratch :)

I think Readlang's unique position is that it provides a very streamlined workflow compared to the alternatives, it tries to remove unnecessary friction and lets you concentrate on either reading or learning. e.g. to do something similar to Readlang with other tools you may need:

- LWT (the user needs to run the server software themselves with XAMPP or similar) + Anki

- LingQ (seems OK, but a bit expensive ($10 / month) and personally I think the UI has too much clutter, and I don't like having all the words I know/don't know highlighted in the text, it distracts me from enjoying the content)

- Manually switching between tabs when reading to translate and build flashcards in Anki or similar

Maybe there are other tools that I'm not aware of. Thanks for your links, I especially like the idea of chineselevel.com and I've been thinking along these lines for Readlang - estimating the users proficiency based on the words they translate and suggesting content of the appropriate difficulty. My big missing link at the moment is built in content on the site, I'll probably look into finding good public domain / creative commons content soon.

I'll send you a personal mail now...

Edit: one of your links may contain a typo: http://duable.com/ - this URL is for a brand advertising company
not when you're working via ssh
This is true of all tempered glass, not just that dropped in cold water. The side windows of your car can do the exact same thing because tempered glass is under stress and, when something comes along to break it and release all that stress, it explodes just like the sample pictured in the article, which is why we have to cut and seam it before tempering it. (Your windshield is laminated. Having it blow up like that sample pictured--a very real possibility--could easily cause an accident.)

Normally you don't see windows explode because the edges are smoothed before tempering and protected inside a frame. But if you happen to have a piece of tempered glass and nick the corner against something, it will probably blow up. Actually, tempered glass occasionally blows up all on its own, usually during winter, but you probably won't see that unless you've worked for a cut & temper operation.
The "bad" about that is that if "to google" became generic for "doing a websearch" is to stop other search enginge to start saying "Google it with Bing!".
>few famous historical scientists and artists

Plenty of artists: Mozart, Chopin, Liszt, Bizet, Bieber (all right, maybe not the last one) http://en.wikipedia.org/wiki/List_of_music_prodigies

Others: http://en.wikipedia.org/wiki/List_of_child_prodigies
"Scala is a pretty terrible language to be learning it though."

Pretty good course though. If you want something like that, maybe because you find it helpful to have exercises with deadlines and things, then I'd reccomend the course. But if you have some alternatives you wanna recommend, that'd be awesome.

For Haskell, the only similar thing I know of is the Channel 9 stuff with Erik Meijer. And that's cool stuff. But you're much more on your own there than in a Coursera course. So if you want that kind of thing it might not be a good match.
Christ, get over the class thing. Yes, if you have parents and good connections you've got an advantage. Yes, these traits are often a result of class historically. But trying to use class as an excuse for your own failure is not valid in this day and age.
Akka is also a viable Erlang alternative.
While I agree with your overall message, the

> (...) death march should be the norm. Meaning, 20-somethings should be working 80 hour weeks on a regular basis and projects should be shipped at the soonest possible moment it's even remotely feasible to do so.

has got me puzzled: in my (limited) experience and from what I've read, a death march is exactly the opposite of shipping early. The usual story goes: a deadline looms, or a milestone slips, a middle manager decides to whip up his team instead of reporting it. Overworked team members can't meet another deadline, the client and/or upper management is kept in the dark about the problem, no extension of deadlines for sake of good metrics, rinse and repeat.

``It is done when it is done'' and shipping early is a panacea, not a cause of the problem.
What, exactly, WiFiSLAM is, and why Apple acquired it
Issues? What issues? Most complaints about Go are really just "it doesn't contain my favorite language feature", "I heard the GC isn't even precise so it must suck", "it's too immature", "I couldn't get this library to work within 10 minutes so Go sucks", etc. pp., but people are simply unable to point to any actual pain points that hinder productive use of Go.
> It's not a rich city, like New York or San Francisco, with cash to dump into sprawling bike lanes ... It's great that New York can install ... high-end bike-sharing programs. But ...

Bike lanes can bestow great economic benefits, from reduced healthcare costs to reduced pollution, fewer fatalities on the roads, less congestion, less stunting of children's intellectual development, etc. It's a shame people are ignorant of these benefits and choose to disparage bike infrastructure as an example of profligate and unnecessary spending (I recently read another article doing the same for London's cycling infrastructure plans over the next decade).

LSE Study: http://www.guardian.co.uk/lifeandstyle/2011/aug/21/cycling-3...

The Lancet: http://www.guardian.co.uk/environment/2007/jan/26/pollution....

USC Study: http://econweb.umd.edu/~ham/test%20scores%20submit.pdf [PDF]

Economic Benefits: http://cyclingresourcecentre.org.au/page/cycling_benefits_ec...

More bike lanes, fewer gimmicky solar-powered trash cans, please.
"When you are in a position of authority, you should hold yourself to a higher standard." Why? Says who? As soon as people make it to a certain level, they should change? What level? If they're no longer who they were, what do you expect them to achieve in the future?

There are 7 billion people on the planet, the vast majority of them do not share your values.
TxtWeb Android app on Google Play (Works with a data plan and offline via SMS)
Why we shut down Achoo
How do you know that Google didn't have a problem when Oxford dictionary made Google a verb?

Also, Oxford tends to capitalise and / or mark as trademarks words such as this.
Cyprus could get the world's first Bitcoin ATM
Definitely looking forward to seeing if Go has made any progress in catching up to Java and Scala in algorithm execution times.
It depends on how you define "retrospective." Reading the thread, people with pre-existing accounts that did not use the domain feature found they could not start using it, and others that did use it found they could not change it.

While some people may feel entitled, I think it's more a lesson on what not to do. People will always complain when you make something they are using worse (even if you have a good excuse like abuse). That's not the issue. The issue is that when you are a platform company, people get really nervous when you're not open about changes you're making to the thing they're building their business on. Of course it's their right to change their service. Of course they're allowed to do it silently. But it damages trust.

Personally, I just make a mental note to keep that in mind when running my own business.
> After thinking this through, however, I realized that one of the largest mistakes an API company can make is to remove previously advertised functionality (why would developers trust you to provide data to them if you're so quick to remove functionality?).

It seems to me that when providing a new feature in your API, you should have a latency period at the beginning where it is not guaranteed to continue to exist. Sort of the dual to the deprecation period at the end-of-life of a feature (would this make it an "imprecation period"?)

After that period passes, that's a signal to your API consumers that the feature will definitely be sticking around and receive long-term support. But until then, it could be removed without warning at any time; all code that relies on it should have alternate branches to handle the case where the feature endpoints pop out of existence.

Pre-1.0, all features are implicitly imprecatory, of course.
Google Brings TV White Space Internet To South African Schools
The 11 phases of a web developers career
I don't speak Swedish and I'm considering using it out of spite.
I can tell you for sure, this story didn't take place in the public library! Because Dave McClure can barely read and write!
I (obviously) agree wholeheartedly. It is worth pointing out that sometimes historical software is used for instruction, like Unix v6, but that doesn't seem to be common.

A gating factor here is that much of the time, old software doesn't run, isn't available in source form, the old hardware is long gone and there aren't emulators, etc. We also probably over-glorify some things from the past. :)

Making the Texas Persistent Store build again is a bit of a chore as it is C++ from 1994 and things have changed a good bit. But even things that last had a release in the last decade don't build any longer (like framerd). Much less something like SHRDLU which was written in MacLisp and ran on ITS!
Bug in NetBSD 6.0 code ruins SSH crypto keys
The end of the article is important: "Language Council could have ignored Google's requests, but decided to remove the word in order to spark a debate."

Sounds like the Language Council is doing a kind of tactical overreaction to keep Google and other companies from bothering them in the future. They also want people to think more about power over language.
The article is based on a radio interview, found at (https://sverigesradio.se/sida/artikel.aspx?programid=406&...).

The reason behind withdrawing the word, and the tone in which it was said was quite illuminating. Basically, Language Council had grown tired and very annoyed by the discussion with the google lawyers and thus opted to skip the whole mess.
They already can if they want to produce packages. This sounds like it may make that easier.

I'd still prefer to use the ones built and maintained by the distro though.
> Besides Vitess, what other high profile usage is there at Google?

The piece of software that runs on dl.google.com, which serves millions of Chrome updates every day, is written in Go. The problem is: you're asking for Go success stories at Google, even though most of Google's internals will never be published. Why don't you just take a closer look at other companies' success stories and acknowledge them?

> Not to mention they offloaded part of the implementation to Memcache because Go wasn't good enough.

Huh, what? Using memcached means the technology you use isn't good enough, or what are you trying to suggest? Don't forget that the author of memcached is a core Go developer at Google, so I'd say they know what they're doing.
Not even slightly. Cranking out widgets is something you can pick up in less than a day. After a few cycles of retooling for another product, you've had all the experience you need.

A better analogy would be tradesmen. Apprentices worked under journeymen or masters for five or seven years before themselves becoming journeymen. A tradesman or craftsman works on projects or repairs, each one different from the last.

The years of experience aren't all about banging a hammer against a chisel, or tightening nuts onto bolts. Those years of experience are about problem solving; functional problems and non-functional. Not only do I have to deliver the product requested with quality and budget and timing, but I have to solve all of the problems that have nothing to do with the product but everything to do with its delivery: What if it's really cold on one day and someone doesn't turn up for an important presentation? What if one of my tools breaks and I have to improvise? what if the product specification changes halfway and I have to figure out how to implement that (or reject the changes) without causing a fight? What if local regulations change mid-project? What if technology changes a year or two after I start, and I have to learn something new to keep up?

These are the things an apprentice learns in seven years (for the last couple of thousand years), whether a plumber or a mason or carpenter. The best person to solve a series of such disconnected problems is someone who's been in the trenches and dug their way out. You don't get that from a book or from your bedroom.
Bingo. I have a profitable, scalable enterprise. We're worthless because we're profitable - if you make money, your value is a multiplier of profit.

Now, if you run a startup that makes no revenue, or even loses huge amounts of money, your value is a multiplier of the profit you could theoretically in a crack dream make.
I'm not sure this is exclusive to the software/engineering industries. My impression in general is that people "back in the day" were much more content to stay with a single employer for their whole life–or at least long periods of time–than they are today. If that's the case, training new employees from the ground up made much more sense a few decades ago from an ROI standpoint.

I haven't got any statistics to back it up, though, it's just a general impression.
Jeremy Ashkenas in the 2nd Manila.js Meetup
While in theory JSON might be just as streamable as XML, in practice I find every XML parser I have ever used supports streaming, and I have never seen a streaming JSON parser.

Actually, having just googled I find a couple, but the only C one I can find (yajl) seems to be mostly abandoned, with a huge number of open issues.
Just in case anyone isn't aware of the video to which you're referring: http://www.youtube.com/watch?v=tYVCk10AzS0
you're right, the gap isn't that big. Hard to put my finger on it, but for me the general look&feel and 'snappines' of the interface still feels not as refined as gmail.

The threaded view is not nearly as good as gmail's where you just scroll to see the next message (once you view a single message). It feels like there's lots more double-clicks going on in roundcube to get to view messages and interact with things...

I suppose these are not huge functionality gaps, more refinements to the UI. Functionality-wise it would be nice to have some intelligent filters in roundcube like google's. That's where gmail is a combination of an email client and server though.
Wait so... command line is bad and when I suggest you don't have to use that, a GUI program is also bad? What answer were you looking for there?
Yes, of course.

It's interesting, though. You can even list who's connected to the server.

netstat -nat | awk '{ print $5}' | cut -d: -f1 | sed -e '/^$/d' | uniq
> I'm surprised this isn't mentioned in the original article.

Don't be, there's a witch-hunt on Google right now. Nothing but the most negative-spin on them will be reported for the next few months until everyone calms down about reader.
It's not about what you can say - you can say whatever you like - but Sweden or whomever can't officially bestow a new meaning on a trademarked name. It's like enshrining in the dictionary that Coca-Cola means "sugary water".
I think you both mean "retroactive" instead of "retrospective". But whatever, that isn't the heart of the issue here.
1. Yes, I use headphones. Currently Sennheisser HD 555.

2. I have Harman Kardon SoundSticks III 2.1 Channel Sound System. I use them when watching a movie or when I'm alone at home.

3. All kind of metal. Mostly progressive, technical death metal, deathcore, etc. Then classical, ambient, trip and a lot of Soundtracks…

4. I do but I rarely use Spotify.
locally, I find the tmux buffer system (just like in vim) to be very useful for pasting text around the place, also, the newer versions have :choose-tree, which is well worth a look, using ^a s gives you a list of open sessions, from which you can choose what you were working on, and if you give your sessions sensible names (based on the starting directory for example) then you can switch between projects/jobs incredibly easily..

also, running tmux locally has the advantage that if you need to leave the office or go somewhere, you can still reattach to your work machine and pick up from where you left off.. so, in a sense, everything is remote
Kiwibank, woo!
It's all those glaciers, the water's clearer...
Clear Contrast is Critical To Reduce Confusion
If you consider ad-tracking cookies set by sites {A,B,C} to be read by ad-provider X all "one cookie"

I'm not really sure what you mean by this. You said "almost all cookies are friendly" and I'm pretty sure you're wrong. Even if the numbers 'balance out' (which I doubt very much) that's still not close to 'almost all cookies are friendly'.

The pro-cookie side of the privacy debate really needs to just admit there's a problem here, then we can work together to try and ensure privacy and functionality, without making reckless assumptions that somehow tracking is sanctioned or providing value to the user without even the courtesy of asking.
6 lessons World of Warcraft taught me about online marketing
How do trademarks apply to dictionaries? I don't think they do.
Google has been taking action against this genericization since 2003.[1] They also got the German dictionary Duden to change their "to google" Definition to refer to Google only.[2]

[1] https://en.wikipedia.org/wiki/Google_%28verb%29
[2] http://www.nzz.ch/aktuell/startseite/newzzEQXM1K6L-12-1.5328... (German language)
Is there any ETA on the release or is it just a case of "when it's finished"?

I'm about to start a largish project in Go and I'm thinking I'd rather start in Go 1.1 rather than worry about upgrading and testing the project mid-development.
Haha, that's a really good name to use for your technology in South Africa. It's like Google fired its PR department a month ago.
They're called 'conservatives'.
Well yes, but they usually rely on traditional storage methods (on disk or via something like NFS shares). Normally they use sharding based on the mailbox name and spread it across multiple storage backends.

The only mailserver before this that stepped away from this methodology as far as I can remember was DBMail, but it suffered from many other issues instead.

Using Blob-store like S3 (with some kind of encryption) combined with a db with metadata makes a lot of sense to me for this application. Alternatively, storing it all in something like MongoDB's ReplicaSet would also be interesting.

Now, if ElasticInbox is the best tool for this is a separate discussion, but this type of architecture sure is compelling.
Ad industry threatens Firefox users with more ads if Mozilla moves on tracking
Assuming this is true ( I tend to doubt popular science articles by default at this stage) it seems that permanent damage is speculation and the response could be analogous to hypertrophy.
Saying weight lifting damages your muscles is also true but its only part of the story.
Just like others say, PHP is probably the winner here:

- You're comparing raw PHP with frameworks from other languages. Try not using frameworks in other languages.

- You're saying that PHP has no dependencies manager - http://www.getcomposer.org

- Using anything more than PHP for such task is an overkill.

To be clear, I'm not saying that PHP is the best language of them all. Like all languages it has its ups and downs and there's a lot of subjectivity on what you like and dislike. I'm just saying that such comparison isn't really fair.
agl (https://news.ycombinator.com/user?id=agl) knows better, as he wrote most crypto in Go, but here's what I know. AES and RC4 in Go standard library are not constant time. AES should be timing safe when used on amd64 CPU with AES instructions. RSA is blinded, but not constant time, and ECC is not constant time (amd64 implementation of curve25519 in go.crypto is constant time, though). The linked hash functions (MD5 and SHA1) shouldn't be used for cryptography, but they and SHA-2 should be safe as there are no loads or branches that depend on secret data.

If you want a timing safe cipher, use (X)Salsa20 from go.crypto repository.
Dies on chrome for me, ouch!
The Marissa Mayer turnaround
Luke's Change: An Inside Job? (clever)
Yes, that's what I meant. Thanks! And indeed, it's closer to a soup. It takes a while getting used to.
If there's no slack for training time, there's no slack for an empty position, which is what we have now.
Django 1.5 is also the first release with Python 3 support
The life of extremophiles: Surviving in hostile habitats
Brand protection actually.

They didn't object to inclusion of "to google" into Merriam-Webster a couple of years ago. But it was an all-encompassing neologism with a positive bias. The ogooglebar on the other hand carries a negative bias, it describes something that you can't do and it's linked to Google. That's what they don't like.

Silly if you ask me.
Capita Centre, Sydney, Harry Seidler & Associates 1989
But there's a circular logic flaw in believing the two aren't related. Producers (not just laborers, think scientists, researchers, editors, engineers, managers, etc, in that they produce services and products) have some cost/value that you might term "capital" (really everything is technically capital in that sense), and investors having more money due to less taxation results in them being able to pay for more producers.

But it doesn't really work that way. Producers are typically the majority of the consumers as well, and that's money that ends up back in companies as capital that ultimately is more valuable than investor capital, since it's renewable and with a profit margin doesn't gain equity and increase in value like investor capital. But in a sense, then consumers are investors, just a different type, but they're being taxed more highly, so they can't afford to consume as much, so they invest less capital in companies.

There's a cost of living, too, that you can't ignore. If producers contribute more of their earnings to taxes and have less to live on, then the margins are smaller and they necessarily need to seek higher income to offset the taxation -- which results in their production capital becoming more expensive, which makes investor capital less potent as well.

I don't see a good argument at all for taxing people who work for their money, because all of those argument circularly apply to the working people as well, and logic would dictate that it impacts the value of capital and ultimately leads to fewer jobs. Lower producer taxation and higher taxation on investor gains may reduce the available capital (but not necessarily the amount invested) but it also reduces the cost of other forms of capital, while increasing the amount available for investment from producers. That means a much larger class of people have more room to live well and spend, versus a few living well and spending. To put it really simply: higher income taxes and lower investment return taxes results in financial segregation while the opposite tends to destroy it. It's clear, given that basic fact, why some argue for or against it. It also changes the types of investments companies need to seek, which may or may not be a bad thing.