skysight-inc/HackerNews huggingface dataset:
Haven't tried it, but I heard great things about it from bradfitz, who uses it on http://camlistore.org/ (and whose opinion definitely deserves respect). Is React an all-or-nothing thing, or can you sprinkle it in certain places on your site without needing to make the whole site in React?
The built-in audio on most PCs these days supports 96kHz or even 192kHz sample rates.
You can ask literally any time, but unless you have a real reason it's a waste of time. A good reason would be an increase in responsibility.

Otherwise wait for your performance review. If you don't get one, ask for it.
This only applies if you actually allow people to assume that "hired" means "staying." If you "hire" people on a tentative basis, and tell them that you're doing so, then this can work. (And you don't tentatively hire people who would have to relocate, etc.)
> I wish extreme performance goals and requirements would become a new trend.

Well, there will always be demoscene (http://www.youtube.com/watch?v=5lbAMLrl3xI ) which I've always found remarkable.
The great thing about it is that you can sprinkle it in just where you need to have some dom manipulation.

TBH, a lot of sites really overdo the client-side rendering thing.
Or better yet, pay for results, not hours - if only results were always easily measurable. If A and B have the same base productivity assuming they work the same amount of hours, B's productivity per hour might be less if he works 70+ hours and A works 30 hours. So it might not be fair that they're then still paid the same per hour.
20:00 Antalyaspor – Galatasaray canlı izle
Antalyaspor - Galatasaray Maçi Canli izle
20:00 Antalyaspor - Galatasaray CANLI IZLE
Antalyaspor - Galatasaray CANLI IZLE
Antalyaspor - Galatasaray ONLINE IZLE
17.02.2014 Antalyaspor - Galatasaray MAÇI CANLI IZLE - SEYRET

17.02.2014 Antalyaspor - Galatasaray Canlı Yayın Maç Linkleri

İzleme Linki(1) ||| http://1tk.us/tCi ||| 20:00 Antalyaspor - Galatasaray maçını canlı izle

İzleme Linki(2) ||| http://1tk.us/tCd ||| 20:00 Antalyaspor - Galatasaray canlı izle

İzleme Linki(3) ||| http://1tk.us/tCf ||| 20:00 Antalyaspor - Galatasaray maçı canlı izle

İzleme Linki(4) ||| http://1tk.us/tCg ||| 20:00 Antalyaspor - Galatasaray HD yayın izle

İzleme Linki(5) ||| http://1tk.us/tCk ||| 20:00 Antalyaspor - Galatasaray şifresiz canlı yayın izle
Show HN: I made an app to help programmers improve their writing skills
If you're interested in offering an alternative to US buyers, holler at me - tommy at thecityswig dot com
This is great dogma for people that control their work environment, but keep in mind that not everyone has that luxury. Hardware upgrade cycles and/or upgrade budgets can prevent people from working on the hardware they'd like, group policy can prevent scoping down AV settings, job role may require frequently hopping between OSX/Windows, etc.
yep.

Honestly half the battle is having a great easy to use plugin style that gets lots of people making plugins, and given the incredibly brief mention of plugins which makes them seem quite complex, I'd be quite wary of broccoli at this point.
Once a week for sure when you small, and with your direct reports. Once you are bigger (say 50-100+ employees) and have more indirect reports -- it's hard to meet with all of them every week in an unscripted fashion, especially when most don't report to you anymore. If you force yourself to do it once a quarter, especially in the functional areas you work less on ... it will make a huge difference.
You missed both of my points:

No matter your intended audience, there is always somebody who will need a dictionary. It's not shameful to look up words, and it's easier than ever to do so. You've shifted to arguing about conversion rates for non-English speakers, which is a fair, but separate point. (I'm also curious if small words and simple sentences really do translate to higher conversion rates.) I am talking about prose in general.

> PS Morose is not "very sad" :-)

Nor is awestruck "very amazed." The smaller your vocabulary is, the less you can communicate (as redblacktree pointed out, this is demonstrated quite dramatically by George Orwell's 1984, wherein the language is dumbed down so much and has so many words removed that the citizenry can't express emotions the state deems negative.)

This is the truly tragic thing about this incessant anti-intellectualism: people lose some measure of ability to express what they really mean or feel, all in the name of meeting the lowest common denominator.

(For the record, I am not a native speaker, and I love seeing words that I don't understand.)
I simply disagree. Internet commenters in general are on red alert looking for any little thing to complain about. So many of these complaints are not worth clogging the tubes with or necessarily even valid at all.

(depth of this thread and meta-meta-meta acknowledged and ceased)
I'm recommending not just the Preston Blair book (which is a classic in the field), but a specific series of exercises by master animator John K that use it for visual reference.

These lessons are aimed at getting someone up and running with a solid knowledge of constructing a figure in three dimensions as quickly as possible. You can quite easily stack anatomy on top of this foundation and draw in more complicated styles than "1940s cartoon character"; it's useful to learn construction with those kinds of characters because they're basically little but their construction.

I do not by any means discount the value of anatomy lessons and text, life drawing, sitting out in public doing quick observational sketches, frame-by-frame analysis of video, going to the zoo to draw, or any of the other myriad activities that make up part of a serious art education. I did that, and so did everyone else I knew during my time in animation, no matter how stylized most of their final work was.

But I think these lessons are a great hand up over the huge gap between "I can copy what I see onto paper OK" and "I can draw any damn thing I please in any pose I like, with no reference beyond a few design drawings".

(tangential edit: I'm surprised to find another cartoonist here on HN and curious to see your work, but your website doesn't mention that at all, and Google turns up nothing. Any links? My website[1] is full of my stuff.)

[1]:http://egypt.urnash.com
I found this video (long) very interesting and useful
http://www.youtube.com/watch?v=up3Z7LU2pV8

Also, check out all videos and books by Bruce Blitz
For example - http://www.amazon.com/dp/0762402490/
Watch his videos on youtube first, to get an idea of his teaching style

Disclaimer: I'm not an artist, just someone who has interest in this topic.
We're replacing one Backbone view at a time as soon as they need to get more dynamic. So far I'm impressed.
It's a pretty badge, but unfortunately it's a security risk. Putting identifying information on there is an opening for social engineering attacks. The employee name and anything tying it to Microsoft shouldn't be on there. Really, just the photo and badge id (not the employee ID) should be there. If there's a "return to" address, it should be a nondescript PO box that's not in Redmond.

Edit: Also, the employee number shouldn't be on there for the same reason.
Its not HTML5 video. Shame.

Does anyone know enough about I-frame frequency limits in H.264 or WebM to tell us weather Randall could have included the pitch drop experiment?
I couldn't see any information on the linked page - anyone know what the latency and throughput characteristics of this set up are?

Would be very interesting to understand how audio attenuation impacts the TCP/IP connection.
Why Ruby Blocks Exist
Airbnb could probably do better than just "real bed" for bed type. Maybe they should make the host list the different bed sizes/counts. Yours would have been: 1 double, 1 single & 1 couch.
It's cool to see how a piece changed over time, but I don't quite understand how that helps improve writing. Perhaps it would help identify common mistakes, but the app is pretty much passive in terms of suggestions.
Can we quit with the "rock stars", "ninjas" and all that? We're not teenage boys, stop talking to us as though we are.
1) If you want to be able to view Quora posts in general, I'd recommend installing https://chrome.google.com/webstore/detail/quora-unblocker/pc... for Chrome or https://addons.mozilla.org/en-US/firefox/addon/quora-share/ for Firefox (I recently made the latter since it didn't seem like an equivalent to the Chrome plugin existed).

2) In addition to eropple's point about treatment of the new hire, I think it can be disruptive to the existing team to have a bad hire. For one thing, existing staff always have to spend a least a little time teaching a new hire how things work at the company, and that time is essentially lost if they don't work out. It also frequently means you'll have some mediocre/bad code sitting around when the employee leaves, or in the worst case they could inadvertently cause some major security/stability issues for your product. That can be somewhat mitigated by proper process and permissions, but it's still a risk.
For sake of correctness — recent versions of Phantom.js are not dependent on Xvfb or any other variant of X, and there are grandmotherly prepared binary builds on the official website (kinda statically linked, so no dependency on WebKit as well).
Not that it changes the author's arguments that much, but just worth pointing out.
You're probably right -- I can't create a reproducible test case now. Still, given the browser fingerprinting, you're best off blocking the HTTP connection.
The single worst thing you can do in my experience in a fast growing start-up is make a terrible key hire. I wrote about how making a terrible hire as my first VP Sales almost ruined EchoSign ... The Year of Hell: http://saastr.com/2013/11/06/if-your-vp-sales-isnt-going-to-...
Are you 20 % less productive than those that work 40 hours a week?
I can only guess that you just didn't read it, or don't understand it, because you're 100% wrong. Not just wrong, but ironically wrong- you're explicitly proving my point that the only thing you value is logic and reason. Which is ridiculous because our brains do a lot more than just logic and reason.

As for the left/right thing, I know that- strictly speaking, there isn't really that much of a left-right separation of concerns in the brain. It doesn't matter for my point though. It's just a metaphor for the easily demonstrable fact that brains have functions other than logic that are just as useful and important to satisfy.
CSS OS X like selection
Defining growth hacking in one line.
Demo video: http://www.youtube.com/watch?v=LMz21tsberY
I haven't done proper throughput tests with it yet.

I'll see if I can dig out a pcap file I took using it, which should give you an idea of the latencies involved.

[Edit] I've just updated the page with a wireshark screenshot which shows the latencies and also a link to the pcap file.

Something which I'm keen to look at doing is extending it beyond 2-FSK, to improve the throughput.
Microsoft employees get a discount at the apple store for showing their badges. Not so much at the MSFT stores...

Edit: note - this is the retail MSFT stores, not the on campus stores in Redmond or Silicon Valley.
> The Chinese didn't navigate by stars

They do both. THe modern reference: they actually call their latest GPS copycat BeiDou

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

> The BeiDou Navigation System is named after the Big Dipper constellation, which is known in Chinese as Běidǒu. The name literally means "Northern Dipper", the name given by ancient Chinese astronomers to the seven brightest stars of the Ursa Major constellation
Thank you for sharing your experience, and i hope that this post teach people a lesson about context (e.j: in your case you were using the wrong tool for certain context), consider that either serve-side or client-side rendering are not competing to each other to claim which better, it always "depends" on the context that they are implemented and lastly that server-side redering is not something that should be percieve as "old-fashioned", there is a duality between the two techniques that address specifics problems and is our job to choose what is best for the job.
Thanks for your feedback. I find it helpful to revisit how word choice, paragraphs, etc., changed over time, but I agree that more direct suggestions would be useful. I'll brainstorm ways to include tips.
We're using Backbone+React so this may not be applicable.

However...

“You can separate your dev and production build pipelines to improve dev speed, but that’s going to bite you later on.”

In my experience, you must separate dev and prod pipelines. It has never bitten me because I make hundreds dev (local) and dozens kinda-prod (staging server) builds a day.

For dev builds, Grunt just compiles LESS but doesn't touch the scripts so there is literally no delay there. In dev environment, we load scripts via RequireJS so there is no need to maintain a properly sorted list of scripts too.

For production, we concat them with grunt-contrib-requirejs with `almond: true` so RequireJS itself is stripped out completely. Production build takes time (10 to 15 seconds; we're also running Closure Compiler), but it's never a problem.

Even adding JSX (Facebook React) compilation didn't cause a slowdown for dev builds because grunt-contrib-watches compiles them on change and puts into a mounted directory.
Scala's Either, Try and the M word
As the type of employee described here, I think companies would do well paying their employees what they're worth. The only reason I've had to consider switching so far is due to significant pay differences.
...can't...resist....."grammar".

In an attempt to add something useful though, why did you terminate your work with your last client? Did you attempt to negotiate a higher rate? Two years is still very junior, and I assume that you worked out your price with them early on. Did you give them a chance to retain you?
Open source Miracast  implementation
Yes, but then Caesar would have to trust Alice to relay Bob (which could be a fine and pragmatic solution for some use-cases, but wouldn't really be "otr-for-workgroups"). It would also suffer from poor network topology which could be a problem for large chats and/or high bandwith (and/or low latency) chats (file transfer, audio/video chat).
the link's working for me? Either someone fixed it or weird things are afoot with different browsers.

Either way, thanks!
This reminds me of a more cynical way of looking at the taste/ability gap. I can't find the source, but it's based on the idea that by the time you finish a creative work you've improved to the point where you can see a lot of flaws in it. You go back and try to fix them, but by the time you're done with _that_ you've improved enough to identify even more flaws. This cycle will repeat forever as you continue to improve, develop your creative voice and refine your tastes.
I don't really get what you are trying to say. Sure, there are cases where you need barriers, both the CPU and the compiler kind, nobody denied that. Still, in low-end stuff, PIO and cache-free in-order execution still are well and alive, and volatile can be perfectly sufficient under such circumstances.
If you're OK to delegate the scraping process to a SaaS then you may be interested by SEO4Ajax [1] which will make it much simpler. Disclaimer: I'm one of the co-founder.

[1] http://www.seo4ajax.com
I have to disagree with most of this article.
1. Bad search ranking and Twitter/Facebook previews
Don't force your public side to strictly angular. Serve normal pages and use angular for your interactive components. Let Google index a well formed dom. Use a full angular stack for your non public facing application(a SaaS application). You don't want to index this anyways.

2. Flaky stats and monitoring
Use event driven metrics from your api and or client side. Track everything in the sense of user, controller, action, params. Blacklist sensitive data. Derive metrics with funnels, user did x actions, returned and subscribed. Conversion! It's all there just understand your events.

3. Slow, complex build tools.
Your not limited to grunt, or node. For example we use rails and use our own buildscripts and generators to build fullstack angular apps. Easy Breezy.

4. Slow, flaky tests
There is room for improvement. But jasmine and phantom can get the job done. But let's not forget were also testing our api. Use your goto testing framework and let jasmine phantomn do the client frontend testing.

5. Slowness is swept under the rug, not addressed
Precompile your angular templates, only wait for api responses. Don't fragment your page load into seperate request. Resolve all the requires data beforehand in the route provider.
I agree, I'd also add that when you let the juniors sit at the same pay for longer than a year and a half they'll start to build a bit of resentment (even if they don't change jobs as they probably should). Even a pay rise at that point might not help because they can think the next one is going to be just as far off and if they feel they deserved it at an annual review a few months ago they might think of it as lost money.

At least that was my experience. Of course being younger and less mercenary I hung around longer than I should and jumped, just after a pay-rise, to a similar position similar pay job. I couldn't hang around knowing my heart wouldn't be in working there.
Once you write a decent amount of Go code, you won't miss generics.
We've transitioned from Angular to ReactJS with great success. Much smaller learning curve. Using Backbone to handle the models and React for the view is a great combination.
Why would an employee who is not desperate for a job give up their current job in exchange for a position that's probationary? Setting up a situation where the employer can bail out with no cost to themselves indicates that they have zero commitment to making the relationship work.
What's really interesting is that "google" didn't see this coming - they made angular, they should in theory be huge advocates of SPA, but in reality their primary product doesn't support it well at all.
http://www.reddit.com/r/lisp/

http://lambda-the-ultimate.org/

http://www.reddit.com/r/ProgrammingLanguages/

http://www.reddit.com/r/coding/
Show HN: Hackathon Rails starter kit
If Invading Switzerland, Please Do So Outside Of "Office Hours"
ls -1 /usr/bin/ | sed '/^.\{1,6\}$/!d' |xargs whatis '{}' 2> /dev/null | less
When a founder group from a foreign country come to YC, do they incorporate in the US? If yes, once returned in their country, do they incorporate another company/subsidiary? How do they work?
Most security cards I've been issued with are laminar - there's a thinner printed front part glued to a thicker RFID back part. So making the card double-sided just means printing two fronts and sticking them on both sides.
Finally someone sticking up for wikipedia around here. Its disgusting the way She is treated.
Yes, we did use separate dev and prod pipelines when we used AngularJS. (We used https://github.com/ngbp/ng-boilerplate.) It took 2-3sec for the dev build (most of which was taken up by recess) and 30-45sec for the prod build (primarily JS uglification). However, probably 5-10 times we deployed a broken site because either 1) the LESS compiler changed the order of our CSS rules or 2) we used AngularJS DI syntax somewhere that ngmin couldn't handle. We fixed the issues and added better linting, but it's still one more thing to think about (and the theme of this article is that it was death by a thousand cuts, not one big show-stopper).
This mayaswell be titled: "Why we're paying for re-discovering client-heavy apps are hard or bad." Angular, or <insert hot new JavaScript framework> doesn't particularly matter.

Twitter learned it[1].

Lots of us learned it when we were experimenting as Web 2.0 was being born. Things were far more obvious, far more quickly then, as bandwidth and resources weren't anywhere near what they are today. Back then, we quickly realized that just a couple of delayed asynchronous calls could cause your app to slow to a halt and feel sluggish.

That's not to say it can't be done[2], it's just to say that, thus far for the most part, folks end up discovering reasons why they didn't "do it right" too late over and over. I could be wrong, but I feel like there's been a few posts to Hacker News within the past couple months with similar sentiment.

When people start suggesting client-side rendering, I usually ask something along these lines:

Why on earth would you leave something as simple as textual document model creation up to the client's 5 year old machine that is busy playing a movie, a song, downloading a torrent, doing a Skype call, and running 15 other tabs, when your server is sitting around twiddling it's thumbs with it's 8 cores, scalable, SSD and memory-heavy architecture?

[1] - https://blog.twitter.com/2012/improving-performance-on-twitt...

[2] - http://www.quora.com/Web-Development/What-are-the-tradeoffs-...
Flat is a terrible organizational structure for employees who take their career seriously.
Serious question: How/where do you check in your binary builds and debug symbols if you use git? I've read it's not great at some not-so-large project size. I'm using SVN on a micro-sized team with binaries from all released builds safely checked in (which means the repository is probably 100GB-ish in size), and it works great. [and to head off the argument - rebuilding from source is not an option when you have to diagnose a customer crash when they are using a 3 year old build of the software - you'd have to archive a build machine to even have a chance...]
I dont think we'll still be on earth, but this is what i think for humanity

1) Identity: What's real for people and things. Is this a real person or a robot impersonating a person.
2) Mortality: When do I want to kill myself? Because we'll have the choice of how long to live / when to die.
3) Security: how do i prevent someone from hacking into my brain
Lessons from Building LinkedIn Mobile – HTML5 and Node.js
What? The lowest potential in a uniform sphere is at the centre not the surface (http://en.wikipedia.org/wiki/File:GravityPotential.jpg). Also graviational time dilation depends on the potential not the force (curvature) so it is irrelevant if the point at the centre is shifted in spacetime
The "war on centrifugal force" is pedagogical. If you sit in an inertial frame, all forces you intend to teach are due to interactions between objects. This lets teachers introduce the interactions one at a time in a way that presents minimal opportunity for the "no, that equation doesn't work here for XYZ reasons which you won't understand until after you've taken vector calculus" problem.

If you allow rotating reference frames then you've got to talk about transformation rules in gory detail. Everyone understands centrifugal force, but what about the coriolis and euler forces? Our intuition doesn't tell us when they apply and when they don't, so we have to be systematic about it, and that means "gory details". And guess what "being systematic about it" involves? Moving to an inertial frame of reference and taking derivatives!

You can't be intuitively correct or systematic about rotating frames without thoroughly understanding inertial frames, so that's what you learn first, along with strongly worded advice to stay away from non-inertial frames (e.g. defining frame-dependent forces as "fictitious").

Anyone doing general relativity is comfortable enough with coordinate transformations that they can understand the caveats that come with frame-dependent forces and even take advantage of them to simplify calculations or definitions (the process of going from a "global" to a "local" coordinate system is highly nontrivial in GR).

That's why the Coriolis, Euler, and Centrifugal forces are called "fictitious" while gravity isn't.
Mono's parallel implementation is really bad, yes. I've had similar problems with it (despite the fact that the Mono SGen GC is usually pretty decent at keeping up)

Maybe you should contribute a better one. ;)