skysight-inc/HackerNews huggingface dataset:
An open specification, sure. But the specification is for all practical purposes controlled by Google: it's not an open standard as a result. (On the plus side, the specification now looks like it may actually be viable to make an independent implementation, which it certainly wasn't before!)

The performance hit is that inherent of having to have multiple GCs given the multiple VMs. This is part of the reason why support for non-JS VMs didn't get into WebKit proper: <https://lists.webkit.org/pipermail/webkit-dev/2011-December/.... Various citations to research around there are listed in that email.
And if you are in a situation with limited access to electricity, that may not be relevant. Some third world countries have electricity but cannot afford to make it available 24/7. You clearly have no idea how spoiled you are that you think a decision like that is purely a matter of personal budgeting. A netbook would have been cheaper. I know that. It would not have served my needs as well. It still wouldn't. Nowhere in there did I list price point as impacting my decision to purchase a tablet.

Sheesh.
I did not put that there because it was the best syntax. :) I put it there because I felt it was most likely to be understood by someone new to the language. I assume you're implying I should have used {}?
..better a read-later than a read not-at-all service.

Seriously, Delicious has been on a slow slide downhill since before Yahoo abandoned it. One would have expected the new owners to try to reinvigorate it, but they seem more intrigued by the possibility of dressing it up in hopes of doing another Instagram, instead of actually improving the service. The Bookmarking action [when it works, currently for me ~70% of the time] takes 4-10 seconds regardless of the quality of connection. It's frustrating.

Google, or someone here, please take up the mantle. We need a fast, reliable service with a data-driven UI on which everyone can get aboard.
We could try using the Fermi estimation technique ("how many piano tuners are there in Chicago?")

I have to agree with suresk people, out of all of the folks I know, the number of guns is either 0 or >1. I don't know anyone with just one gun. I suppose if you divided the number of people in a household by the number of guns you may get a number closer to 1, but that means assigning gun ownerships to babies.
EE? Extended Essay at the IB?

That's only supposed to be 4000 words. A project like this could turn into a book.
I just mark things unread and handle them later.
This is the important part to read:

"While I was in Thailand I got a dotted line tattooed across my wrist as a reminder of all those who didn't get another day, who all would I'm sure do anything to have just a little more time. I got the cut here line tattooed on my wrist to remind myself that if I ever don't fully appreciate the opportunity that I have and the life ahead of me, then I don't deserve it and it can easily be taken away. To me it's a very positive reminder, with a dark but real truth behind it."
If Twitter and Facebook users picked Oscar winners … (infographic)
A large portion of web design is the use of typography, making this largely counterproductive.
Ten years later, this article still resonates on so many levels. I hope we reach a day that we all aspire to like those that refuse to download the next x-behemoth flavor-of-the-day framework for all the reasons stated in this article instead of deriding them.
Presumably?

"An undergraduate computer science student at Oregon State University"[1]

[1] http://ngokevin.com/about/
My god, the ability to use this for tracing code makes me more excited than anything I've seen in a while. The debugging facilities on x86 are, well, limited to the point of being damn near useless. I may spend some time hacking solid trace functionality into this, if it ends up being an open core.
That's roughly what my experience with reddit was like. All of my posts sat on 1 point, all of my threads would get downvoted to zero and disappear.
That was my reaction as well. Maybe it is because I am from New York, but when I see JDateTime I did not think of Iranian time conversions.
When using a filler text, it takes a conscious effort to not read it when glancing through the page and instead try and perceive the filler as a layout filler. So it only makes sense to replace the recognizable glyphs with meaningless scribbles and eliminate that effort.
That's real culture. What seems to pass for "culture fit" at companies is either style / process difference of beliefs (at best) or high school cliques (at worse).
The use of Lorem Ipsum is to have a place holder for your typography. With this you're replacing your typography with unrelated glyphs. This is going to make your mock-ups less relevant and is going to be harder to explain to your clients.

Also the block font looks extremely heavy, would skew the hierarchy of the page and be pretty distracting.
I think EE stands for Electronic Engineering in this context.
Speaking as someone who grew up in the South-East of Norway, where there's very short dark parts of the night during the summer, it is certainly harder to go to bed when it's light outside, but it is still manageable. Heat was a much bigger issue for me in terms of getting sleep. Dark blinds, and a strict bedtime ritual to calm down and prepare for sleep helps. you get used to it. Up North there are substantial parts (though sparsely populated) of Norway where it doesn't get dark during the night in summer and people still manage.
I'm not sure it that's the focus of the project.

If this is his final EE project as said on the page, in my opinion the main focus of the project is to have a working proof of concept of an implementation of a X86 processor on a FPGA.

He wouldn't have the time to build a fully ready to market X86 processor all by himself, I think.
What I believe the OP was saying is that they grant access to the friends list, and that Quora already has many of their e-mail addresses. Thus, they indirectly get access to your friends' e-mail addresses.
Much more likely EE => Electrical Engineering. This is probably a senior project or something like that.
They were fine. They changed.

You can't not upgrade, either, since then you're subject to security holes and other anomalies as the upstream provider decides to leave you behind. My original iPad had this happen to it last year. My Mac will follow soon, I'm sure.
Running a professional bump&compensation fund sounds like a fun project. Would love to see how this works out. At the same time it would be a consumer-protection service as it would de-incentivize airlines from overbooking flights.
Actually only heard of it when Mailbox was coming out - looks like they have GTD nailed because they target businesses. I'll definitely give it a try (although with the free plan and it's 10 message credit limit - hopefully I don't need to snooze too many messages in a month). The sad thing is that the clean new-age UI, the queue-reservation-based hype and the publicity from its investors like MG made this sound like groundbreaking thing which it isn't.
That's no good - it should be written in 10,000 lines of C!

http://www.catb.org/esr/writings/unix-koans/ten-thousand.htm...
Agreed. The states do it this way as well. I worked on updating some statutes after a legislative session and it was a nightmare. Many bills conflict with each other. Often, nobody even knows what the latest version of a statute really is. It's a joke.

In some states, such as Georgia, the public can't even read statutes! They have to buy a copy. Pay to know the law to which you are bound. How does that make any sense at all?
You can be right - but your maturity is determined by your response when the team "comes around" to your idea. A mature developer nods, and immediately begins walking through their pre-developed action plan. That person has the confidence that the team knows there was a mistake, and no need to walk through the past.

An immature developer throws out the "I told you so" and lauds it over their team.

We all make mistakes, it's the foundation for the fail-forward-fast mantra. So acknowledge the mistake, impress others that you have a solution, and move forward.
Timestamps on the source code repo seem to date this to July 2009.
upvote, you rock Sallar :)
Please don't call this travesty of a proprietary mobile app "Mailbox". They don't own the word.
That's how I have been doing it until not too long ago.
That's not practical. Sometimes things need to stick together in a package, and it might be bigger than two pages. As a simple example, if you had a bill that included "Fund this new program" and "Levy this new tax to cover it", those provisions should be passed (or vetoed) together.

And the smallest reasonable package might be a lot bigger than that simple example. If you're going to patch something like, for example, the tax code, it could take you well north of a hundred pages to put together a package that coherently accomplishes what you want to. It might not be practical to break it up. There could be many complex clauses that don't accomplish what they're supposed to without the simultaneous enactment of many other complex clauses.

I'm not saying I like long and complex bills. I hate them. But recognize that law is like software (in fact, from a certain perspective, law is software). It should be kept as simple as possible, but "as simple as possible" might still be very complex.
When will we be in a world when we don't have to deal with assembly language at all? When can we just get the job done without having to understand or know any of the things which go down there? Because that stuff pisses me off. Bits? Bytes? I just want that freaking login box and implement some functionality and never have to deal what's under. Is it really that hard? Sigh.
The first thing they need to do is reduce the pension funding requirement, which was forced by a 2006 law. They have to fully fund the pension for 75 years, and do that in 10 years. That would reduce their operating budget deficit.

Second, they need to push their parcel service, and open the counter all week long. The internet has caused a reduction in regular first class postal mail, but is also increasing the number of packages people send. Rising fuel costs make sending packages locally a good option.

I like Saturday home delivery, but from a business perspective, it's not critical. Parcels, however, I think are critical.
It's a late reply, but sure.

The purpose of pairing in this context is not to see a meaningful contribution; rather, it's to see how the candidate interacts with a codebase he's never seen before, and developers he's never worked with before. Can they spot mistakes? Recognize patterns? Read and write code? Does the candidate know the ecosystem well enough to suggest methods or libraries?

Most importantly, pairing tells us whether or not the candidate can communicate effectively. Are they terrified to offer suggestions, or overly arrogant and controlling? Can they explain clearly? Do they clarify when the other half of the pair doesn't understand?

For example, many moons ago, I did some pairing with a candidate that gave me a suggestion on how I could make a section of my code both smaller and easier to read by combining a couple of iterators in an obvious way that I hadn't noticed. We ended up hiring that guy.

The getting-up-to-speed part happens as they pair, with a lot of explanation happening as they work on the system, and it's another important part of seeing how they work -- can the candidate understand new concepts quickly? Do they stop and ask questions when they don't understand?

This type of interview is a performance hit for that employee for the day, but this is fine, as I consider hiring to be very important, and losing a day or two of engineering time over the course of a month is a price I'm willing to pay -- keep in mind that the phone screens eliminate a lot of people.

Admittedly, I've never had a day when my guys didn't have work to do, but not all interviews involved the company codebase.

I make it a point to carve space out for my team to do miniature research projects, in a fashion similar to the way HP used to work, or Google's "20% time". These are timeboxed, and at the end, the result needs to be made available to the team; and yes, "this didn't work because of X and Y" is totally acceptable. This always pays off in terms of education, and every now and then you get something useful out of them, but they're also fair game for pairing during programming interviews.

Hopefully I've answered your questions.
Portable computing sucks (my response to Ryan Dube's search for tablet bliss)
I mostly agree with your critiques. I would just add that even if there something I might want to use my tablet for the cost of context switching from the computer to the tablet is just too high.

And if I suddenly needed to do something the tablet didn't do well I would have to go back to the computer in any case.
Have you ever gotten things in the mail? Even junk mail?

If so, you may have noticed that your mail is ultimately delivered by a human. Someone who has to be able to grab a handful of mail out of their bag and perform a quick visual check that yes, everything in this bundle actually goes to this address. Someone who might have a hundred bundles destined for an apartment building, and would like to be able to quickly parse the addresses to put them into the proper mailbox instead of having to type a long, cryptic ID into a smartphone, and hope they continue to have connectivity.

Any proposed new addressing system also needs to deal with the fact that the postal service serves EVERYONE. Even people way out in the middle of nowhere who have no cellular service. The ONLY processing power available to those mail carriers is their own brain, so it pretty much HAS to be human-readable.

All of the things you complain about in the address are USEFUL redundancy. Including all of that stuff makes it more likely that mail will get to its destination in the event of the ink being smeared (or running due to being rained on). It's more data that's useful in error correction.

Also, if you are mailing out many things and hate copying the info manually, let me introduce you to a concept called "printable address labels" and "mail merge". I recently had to mail out about a hundred books after a successful Kickstarter; I manually addressed maybe three of them. I put books in mailing envelopes, put the labels on the envelopes, sealed them shut, and brought them to the post office. They figured out how much it would cost me to mail them. I paid with a credit card. It really wasn't a major hassle at all.
Sure, but it's PHP 5 >= 5.3.0. jDateTime requires 5.2. IntlDateFormatter did not exist at the time of writing this code.
I think there must be something seriously wrong with zmq golang bindings if the performance plummets like that. I mean, it's significantly slower than the python version.
This sarcasm isn't adding much weight to your argument. Though I'll agree the parent's criticisms are unnecessarily rude (asinine?).

For my own needs I feel like I've been following a similar path as you were. I've consolodated more and more of what I do around Mac and Apple. However I don't yet see the problem as you appear to have.

I'm very happy with it as an all around platform and as a connected ecosystem. While far from my ideal vision of a tech enabled future, it still seems to be better than anything else I could cobble together today. As far as being a decent development environment I have few problems, I use Iterm2, zsh, tmux and VIm (not macvim) and rarely leave the shell for anything other than Chrome. Homebrew is great too (sort of reminds me of when I used Gentoo, but with far fewer hiccups).

I also love a few of the well designed apps that I use which are Mac only too. Sparrow is heaven sent for e-mail (too bad about the acquihire though). Fantastical + Google Calendar makes working with appointments better than anything I've ever used.

I know that I'm probably getting a bit locked in and one day I may pay a price for that. For now, I'll gamble on today's convenience amortized against tomorrows pain. When (and if) that day eventually comes, the entire technology ecosystem will have practically turned over, the decision I make will be different for reasons I couldn't even guess at today and I'll be (hopefully) a smarter person. Maybe it will be Linux I pick again, but I'm happy to kick that decision one down the road with Apple for a bit.
Yeah, like I said, it was mostly during 2 years in college (in France in the close-knit network of research institutes and universities where the language was actually born) and OCaml is a wonderful language. It has numerous upsides (type inference, the mixed functional/OO paradigms, non-verbose, relatively fast, the awesomeness of pattern matching).

I was mentioning it in my previous comment to provide perspective on my opinion of Go.

I am a big supporter of the idea that all languages have their advantages anyway :)
I know. It's incredibly annoying when people "design" without regard for the UX.
I've never seen JDate.com, I'm sorry for the confusion.
Why do they need giant, expensive buildings in the center of every town, rather than partnering with convenience stores like in Europe?
What they do is totally different from this, they usually engage in very black hat tactics.
do you see every shout nearby you in real-time or is there some filtering going on?
I am surprised that you even know about Bhopal ! A part of the tragedy is that its the largest industrial disaster and yet hardly anyone knows about it.
OS bringup doesn't seem to be part of the goal. It looks like he's just going to run code directly from memory to test it without worrying about needing to get an OS running on it first.
Websites that Challenge and Sharpen Your Programming Skills with Puzzles
Do you use any of them?
I have been using Logentries addon with Heroku (https://addons.heroku.com/logentries) and it does all the things you mentioned namely,

Real-time or very-near-real-time data discovery.
Wildcard search.
Timespan dragging.

I would still like to explore splunk as an offline analysis tool for syslog drains.
I would have told them that I had no idea what that was, but then told them what the "Liskov Substitution Principle" (named after Barbara Liskov of MIT) was. I mean seriously, if a company can't spell, do you want to work there? :-)
You forgot the blurred version - redacted-quora.ttf
I did this same thing for the exams of my last year only.
Had I known before ....

Here's the pattern :

while exams{

0. Study

1. Go to the exam

2. succeed

3. Come back, get fresh a go to sleep

[... idle ... forget everything ... reboot ...]

4. Wake up, get fresh & back to 0. for next exam

}

Here's some advantages :

- when you wake up you actually have plenty of time till the exam

- you don't have to calculate how much sleep you will get or when to squeeze it

- your going to arrive fresh at the exam and not fall asleep on your sheet-keyboard
You can already do most of this. The bigger issue with the post office is even if you do everything right (delivery confirmation , insurance) they still lose your packages and have customer service a bit south of what's depicted in the movie Brazil. The perception of the USPS as incompetent and surly is not unwarranted.
I like the project, but for tracing code, you could probably do better with Bochs. Bochs lets you set breakpoints at certain addresses and CPU states, for example.

If bochs doesn't do enough, it would probably be easier to hack it up to do what you need.
Firstly, apologies for the ridiculously late reply.

Secondly, so what? The particular structure of our economy is no reason to constrain our abilities as a species. I would argue that we have crippled, half educated college graduates doing pointless work across the WEIRD (google the acronym) world, and that this is bad.

My argument is not that we have educated the "average person" (presumably you're not one) too much, but rather that we have educated them too little. Just enough to believe that they know enough, but not enough that they actually reflect upon their existence.
Until this 2006 law that requires the pension to be fully funded for 75 years, and that this be achieved in three more years, the USPS was self sufficient. Postage paid for everything. No cost to the taxpayer. I remember when this was achieved in the 80s - it was on TV. This link has a lot of detail about the USPS.

http://usgovinfo.about.com/od/consumerawareness/a/uspsabout....
The stories were written by Dave "Fargo" Kosak (he's currently lead quest designer for World of Warcraft, btw).

You aren't wrong in remembering the Penny Arcade connection, though. About half of the stories had accompanying illustrations drawn by PA's Gabe.
Apple Will Discontinue the Mac Pro in Europe From March 1
http://en.wikipedia.org/wiki/MINIX
Exactly. An interview is work, on both sides of the table, and I see no point in distancing that work from what we actually expect the candidate to do once they get hired.

Puzzles, whiteboard coding, and so on don't tell me whether or not somebody can actually build software.

If the goal was to get free work, we wouldn't sacrifice staff time on the interviews. We'd give the applicant a challenging "homework" assignment and ask them to do it on their own time.
That's hilarious but there's something really unethical about that though!
There are already several open x86 cores. You're not likely to find these as useful for modern code though, since most people are finally using x86_64 these days and a lot of the instructions being used (and a lot of the processor characteristics of modern chips, from SMT to the trace cache) are very different in modern Intel chips.

You might try instrumenting bochs, which might both run your code faster, require less hardware and give you more accurate results. In many ways, bochs is much better built for the type of thing you want.
What I learned during 10 years interviewing people
I don't know if that would be impossible, but based on the federal laws around the USPS and who is allowed to handle mail, it would be very difficult.
I love JavaScript, but there's no denying that large aspects of the language are somewhat ill-conceived. Crockford himself says this.

Once you know which pitfalls to avoid it's possible to write some really elegant code, but the mere presence of those pitfalls causes a ton of problems when you bring in engineers from other programming languages.

I find it kind of concerning that when someone criticizes JavaScript, everyone's first response is, "he must not have any experience with the language." That's an unfounded personal attack and ignores the crux of the argument.

Look, we love JavaScript, but it doesn't do us any good to pretend it's perfect. It'd be much easier to ramp up new engineers on the language if we admitted its flaws and made efforts to educate "the right way."
Google refuses to withdraw German injunction requests against Microsoft
Yes you see every shoutt around you. But we sort the shoutts by popularity. In addition to that, when someone shoutts, we find the people who are most likely to respond and send them a push notification.
I meant western United States, I'm sorry for being American centric. Really, the definition of reservation is quite simple: an area reserved for something. It's not a national park (though hanford reach is a monument I believe). Given the lack of people on the reservation, the area is quite natural.