skysight-inc/HackerNews huggingface dataset:
Sean, have you tried any of the ergonomic keyboards which you find pointless? Unless you have, your argument seems a lot like my ol' man's arguments against <Internet/Facebook/YouTube> a few years ago.

Atwood specifically addresses the fallacy of "thinking vs typing as the bottleneck for programming" with the statement [1]: "What I'm trying to say is this: speed matters. When you're a fast, efficient typist, you spend less time between thinking that thought and expressing it in code."

It's not about averaging 90wpm in code. No programmer I know does that. It's about not averaging 10wpm once you've finished thinking and want to materialize your thoughts or revert a mistake.

My work is typing, primarily code and email. Every minute I spend typing my thoughts is a minute of thought wasted.

[1]: http://www.codinghorror.com/blog/2008/11/we-are-typists-firs...
Looks like a solid walk through of building an angular app.

OT but the fantasy football twist is great. I only just started playing this year so I've been learning a lot. We're playing the uk version but I guess it's much the same. I've found it interesting how much strategy there is and how much data I can analyse.

We have a startup in the construction industry so wanted to use it as a tool for keeping a sort of weekly offline / banter conversation going on with clients. Turns out that I actually enjoy too!
I have a blackwidow, no build problems.

I even spilled alcohol on it (scotch) and it's still working as expected.
it's a lot like the current logo but without serifs.
Fusion trees
Kind of surprised how in depth the tutorial goes, but only manages to mention the word "test" once and doesn't cover the fantastic testing back end included with the AngularJS seed (https://github.com/angular/angular-seed).

Unless the person learning AngularJS has never done any automated testing before, I can't see any reason why not to be using tests as a tool to further your own learning. I learned Go last year relying heavily on tests, first specifying what I wanted to achieve in a high level test, then learning as I figured out how to make the test pass.
A Bloody Ballmer and Stalled Discussions on the Long Road to a Nokia Deal
Amazon adds support for Redis in Amazon ElastiCache
You could build your own or you can buy them from vendors, it is actually very common practice to hook up a GPS-powered stratum 1 time server to a network. (e.g. http://www.spectracomcorp.com/ProductsServices/TimingSynchro...)
> Anything that threatens that status quo is usually immediately dismissed. For instance, the idea that teachers should be evaluated based on student outcomes is like kryptonite to union leadership.

Its kryptonite to union leadership because student outcomes involve more than just what teachers control, including what administrators control and how administrators interact with the individual students. No one wants to be held accountable for outcomes when someone else -- particularly their counterparty in the relevant contract -- has the ability to interfere with their ability to influence the outcome.
A lot of people seem to be missing the main point here. I don't think the article is actually advocating developing for Android and NOT iOS. I don't think it is even particularly advocating releasing on Android first. However starting your development on Android - as your first way of prototyping and finding your MVP - gives you a tremendous amount of agility and flexibility. You can create as many APKs as you want, send them to whoever you want without any fuss and they can test them out. You can fix bugs or implement features for just one person and send them the APK the same day. You can integrate your app with the OS and other apps in ways that are impossible on iOS to find what really works and matters to your users. And you can do all this for virtually zero cost on commodity hardware with free tools.

In other words, even if you believe iOS is ultimately going to be your primary platform, there's still a strong argument to do your initial prototyping and development on Android.
Completely agree

20% less than the Nintendo DS is a good sales figure considering the DS is #2 in terms of video game console sales, only selling 3 millions units less than the all time leader, the PS3. (http://www.vgchartz.com/analysis/platform_totals/)
Let me also note the contrast of how certain you are about the US motivations (a heterogeneous entity if any!) -- and here you write that you are "not certain of anything"!

I am certain of one thing -- you are either confused or you write simple propaganda from the viewpoint of some dictators.
Sure, but isn't that the key of Lean Startup, which is what OP was hammering on anyway?

Web apps do perform less optimally, but they are also platform independent and can be done quickly. Why not start there, make sure you are hitting the right user needs, then invest in app development?
I didn't say I never looked at them. I said I didn't need to understand how they worked. There is a huge difference.

For example, I've seen logic that looked at roughly 10 user input fields and generated one out of 30 pre-defined values. That was the extent of what it did. It had multiple classes, complex global state management, database and session interactions and thousands lines of code (with no automated tests or comments). That's how real legacy code looks.

When asked to modify something like that, a bad developer would simply add a few more lines of code, do some manual testing and move on.

Another kind of bad developer would start refactoring that code 'by the book', writing unit tests... and would never finish.

A good developer would start by asking what is the point of that final value the code generates and why we really want to modify the logic. Sure, you want another classification of stuff, but why?

In my case I realized that everything and everyone that were relying on that final value could use something else. Instead of spending time messing around with pathological code from above I spent my time switching systems and people to using other values. Then I simply removed that legacy classification mess altogether. The number of tickets we got for the system dropped by at least 50%. I still don't know exactly how all that code worked, because I merely traced out where it interacted with the rest of the world.

Someone will surely comment "But that's refactoring!". I don't care how you call it, because at the time and place I was working on the project it was considered a rewrite, and that's what matters. If everyone followed Joel's advice, no one would question the necessity of that code, no one would look at deleting it altogether it would still be there, except bigger and buggier.
And they would have been right. The Wii only delayed the inevitable. They had a huge hit but didn't capitalize on it.
This has been in the HDMI spec for 7 years already and most high-end TVs support 10-12 bit input. And lower end TVs it doesn't matter anyway. Also TVs often use at least 10 bits between internal processing steps.

Anyway, what you want is happening for 4k - Rec. 2020 mandates at least 10bit for 4k
I like grouping by functionality. All the account-related code in one directory, all the order-related code in another, etc.

Bugs me to have the order logic spread out in the views, models, controllers, hepers, libs, etc folders.
>Granted, this was 3 years ago.

Choked on the water I was drinking. Is this a serious poast?
It'd be ugly and put other burdens on the pricing strategy and support permutations, but perhaps app-makers so trapped could approximate their desired result via:

(1) offer a reduced-functionality "version N" to everyone, but for the desired 'upgrade' price. (Essentially, this might only have the features of the prior N-1 version.)

(2) offer an in-app purchase unlocking full/pro features, priced at the delta between their desired "full Version N price" and what was already paid

(3) give owners of the previous "N-1 Version" a code that gives them the in-app purchase benefits for free

Maybe Apple would still object... but since the entire process happens inside Apple's system, paying Apple's commissions, advancing the use of Apple's in-app purchase mechanisms, maybe they'd be OK with it.
32-bit is 8 bits per colour channel (24-bit) plus an 8-bit alpha (transparency) channel, not 10-and-a-bit bits per channel. The alpha isn't (normally) sent to the display device, it's used to render overlapping elements at the display generation level (video card). Good LCDs can easily render the full colour depth with headroom to spare. Higher-end graphics monitors are often 12-bit (the extra range is used for calibration/display accuracy, not necessarily for greater depth).
If the car is hotter to begin with because of the air temperature around it then the melting point on a component of the car will be reached faster. So if it was in a much hotter place like Las Vegas where the sun shines a majority of the time I could see things like this happening more often.

Instead of mild I should've said rainy or cloudy place like London.
Yeah see the "failed" Pepsi logo redesign[1]

[1] http://blog.logodesignguru.com/wp-content/uploads/2011/12/Pe...
So in a word, yes.
Smart, hardworking people (the same people who might succeed with a startup) can absolutely get rich (in the "don't really need to worry about money" sense, not in the "absurd conspicuous consumption" sense) working for $BIGCORP in their 20s.
I am a great example. I was raised internationally and born dyslexic. I had a very hard time in school socially. I didn't learn to read till I was ten.
Luckily my parents were very dedicated. Homeschooling, international school and a number of different hippie schools (Waldolf & Quaker Friends) saved me. I even went to a hippie college that didn't have grades (The Evergreen State College).
The result: I taught myself design and programming and now work at Intel.
I love learning. I want my kids to always love learning as much as I do. That is why they are not going to public school either.
> [href]

Seen it, and seen the talk[1].

> we don't really "use" X these days

GTK+ and QT do not use a lot of X, as they render all their widgets with (e.g.) libcairo.so and libpango-1.0.so that only treat X as a framebuffer. Unfortunately, projecting your own usage habits onto others is an easy trap to fall into.

For example, one minor data point, from my desktop system - I use the built-in font server:

$ rdb -q | grep 'URxvt.*font'
URxvt*font: -xos4-terminus-medium-r-normal--14-140-72-72-c-80-iso10646-1

Why? Because it's (MUCH) faster to draw, doesn't slow down even remotely, and after is much clearer to read on the screen than the blurry mess[2] that pango/etc gives you.

/// that said ///

As I mention briefly, I was warming up to the idea of wayland. GTK+ and QT are certainly popular, and some things DO need to be fixed. The linked phoronix article (or talk) does bring up some good points. The massive amount of (serialized) round-trips to the x-server (even locally) that are mandated by the protocol is paticularly outrageous.
If backwards compatibility and remoting can be maintained through some sort of extension (or whatever), then it could even be a nearly-seamless drop in.

The clipboard and selection, on the other hand, have nothing to do with any of that. They aren't a performance problem, and there is no reason to remove it. In fact, given this is a big change in general, and an opportunity to fix some of the core protocols, why not /expand/ the idea to include a full kill-ring or similar? Call it a fix for CUT_BUFFER[0-7] that were never really used?

Changing protocols and the display pipeline ("things programmers have to worry about") is one thing. Cutting UI features that have been in place for a long time ("things users care about strongly") is a different world entirely.

> but a single clipboard is probably sufficient

When you've used both for decades, a single buffer is NOT sufficient. They end up serving completely different purposes, and are often needed simultaneously.

[1]: http://www.youtube.com/watch?v=RIctzAQOe44
[2]: http://www.antigrain.com/research/font_rasterization/index.h...
And you reach your pinky all the way up to the escape key? Try ctrl-[. :)
> wayland

See? That's what I mean by the Not Invented Here syndrome - no concern for existing use-cases, but it's important to reinvent everything anyway. "Most desktop users" don't have an any opinion on unix/linux/X at all, as thye use windows or OSX. So why is this group the only set of requirements worth of considering?

> Apple got right what everyone else got wrong?

LOL. Not even going to touch that nonsense.

> Oh, and the presence of a dedicated "Command" key is another Apple-ism we should have adopted.

Sorry, META is not the same thing as Control, and both are necessary. Control has an advantage (if you remap it to where it's supposed to be by swapping it with CapsLock) that you don't have to leave the home row.

> Command-X, Command-C, Command-V

I think you've mean C-k, C-y, M-y, as supported by a very large amount of unix/X software. Of course, you can change that to your M-x/M-c/M-v with ~/.inputrc of course.

> Desktop Unix, except for Mac OS X, is a mess.

Desktop unix works just fine. GNOME and KDE are a mess, of course, and the source of a lot the bloat and slowdowns that are seen.
YouTube employee intervenes after Google Plus deletes a user's YouTube account
No i would not say so. Just like any other profession there are those who are better and worse. I am not saying that these other teachers did a bad job, hell a lot of them were great teachers. What i am saying is that even if they had been bad, it would not have made much of a difference as those few awesome teachers had already instilled in me what it takes to learn.

I am of the opinion that if someone wants to learn, they will. But i also think it can take someone who tells you, shows you, and helps get to that point so you can know that its possible.
Where have you seen these anecdotes?
Believe me, a big testing section is on the way.
> Have any linux distros solved the problem of configuring multiple monitors using a gui yet?

For two monitors on one video card, things are pretty okay on Ubuntu and derivatives. More than that, especially 3+ with non-uniform geometries, and you will have fun. If you have multiple video cards, you will have even more fun.
My point was not so much that the color is bad, so much that the process by which the color was selected -- ignoring customer familiarity in favor of something that made employees happy -- was very characteristic of Yahoo.
>[K]eyboards like this are not cheap and people who buy these kind of keyboards do for the same reason that Geddy Lee doesn’t play a $500 bass.

I think keyboards are like shopping carts. Get one with a sticky wheel, and you'll find it terribly annoying and distracting. Get one that rolls smooth enough and you don't think much about it. The difference in return between "passably good" and "extremely high quality" is incredibly small, so let's just be honest here -- this is a luxury, not a career requirement.

But then to put it in Gladwell terms, it's been my experience that keyboards are pasta sauce. Some like theirs chunky, others like theirs... low profile? Oh well, at least my first metaphor stood up...
Apple Prevents Omni Group From Offering Discounted Mac App Store Upgrades
You mean Google's yearly Deb Ops ball?
I love the point about iteration here, but I think this post is a little bit disingenuous.

The problem with developing for Android as a startup is that baseline reliability is incredibly resource intensive.

If you want your app to work on the most popular few devices, you will still have to spend a considerable amount of time and money testing the different configurations and fixing bugs that have nothing to do with your core functionality.

If you want broad support to address most of the market, you're going to be spending a huge amount of development time tweaking little details of your code. When you fix a bug for the Galaxy S4, it'll start crashing on the HTC One X, and the Galaxy Note will never look quite right.

Iteration is valuable, but iOS lets you build one product and iterate on it, to build for Android, you have to start by building 15.
Note that the panels are very unlikely to be true 10-bit; they're almost certainly 8-bit with temporal dithering. And the cheap panels are 6-bit with temporal dithering to 8-bit.
you can't just move to a mechanical and expect an immediate increase in speed. I use a mechanical keyboard. When I switch to a rubber dome, i notice a DECREASE in speed, because I'm just not used to it. It takes a long time to get the same speed when you switch to a mechanical, but when you do, you may continue to increase and surpass your speed on a rubber dome. Most fast typists (200-250+ wpm on short passages) use a mechanical non-ergonomic keyboard plus qwerty layout.
Memo To The BuzzFeed Team
You might be overestimating the actual observable effects "ergonomic" keyboards have over traditional designs. I wouldn't make a confident ergonomic claim for either type of keyboard, but I'm very skeptical that ergonomic keyboards on average provide observable health benefits. And, anecdotally, I've never had any health problems related to ergonomics (26 years old, 8+ hours a day at a computer desk for at least the last 10 years).
I also remember when they were tyrannical, monopolistic assholes who got busted for price-fixing the NES and even sued to keep the Game Genie out of stores. They've been stubborn and out of touch for as long as I can remember.
I'm not sure Milton Bradley is the right analogy. Milton Bradley, Tonka, Kenner, Parker Brothers, Playskool, Avalon Hill and Wizards of the Coast (among others) were all successful independent companies at one point. They are all owned today by Hasbro.
I'm not even that concerned about getting rich. It's more about doing exactly what I want, when I want, and making a big impact (in terms of helping people) - without giving the billionaires any more power and money.

As Jesus said - It is easier for a camel to go through the eye of a needle than for a rich person to enter the Kingdom of God.

I'm an atheist, but there's a solid truth in that saying. If you can't make a living on your own, it's OK to join that corp, but otherwise, it's the modern version of dealing with the devil.
These brands are still ridiculously recognizable worldwide. And Nintendo owns many of them.

I'd argue that Pokemon alone even today is worth more than Angry Birds.
To be fair, he is clearly not a diplomat nor does he belong in a diplomatic pouch.
> Sean, have you tried any of the ergonomic keyboards which you find pointless? Unless you have, your argument seems a lot like my ol' man's arguments against <Internet/Facebook/YouTube> a few years ago.

If my wrist/hand/arm/etc. comfort level while using my non-ergonomic keyboard is indistinguishable from my ambient comfort level, why would switching provide any useful data?
Most of the issues with the experiment were identified by other scientists, not the ones involved in the study. That's probably why it was never released in any reputable journal - the study design wouldn't pass peer review. Incidentally, releasing your results to the press before you've published academically is also a fairly reliable warning sign of pseudoscience.

When the entire experiment is based around constantly monitoring someone, any time where you can't see them is a pretty serious flaw in the experiment design. Even if he was only out of view for a few seconds (and I wouldn't mind a source for that), that's all it would take to drink some gargling/bathing water or quickly have a snack that some devotee left hidden.

Smart people can certainly be wrong and often have been. Sometimes due to their own preexisting beliefs and prejudices, sometimes because they were limited by the knowledge and technology of their time, and sometimes even because they're being deliberately deceived and their particularly expertise isn't suited to catching it (I cited Project Alpha in a comment below and there are many other examples).

The key thing about science, and remember that organised science is a relatively new idea in the span of human history and one that's made tremendous advances possible in a short time, is that it's about a consensus backed up by the evidence, not any single scientist's opinion. Sure, sometimes one scientist or a small team will come up with a radically new opinion in some field. When their evidence is examined and their experiments repeated by their peers, sometimes they're a Gallileo. More often they're a Pons and Fleischmann (http://en.wikipedia.org/wiki/Cold_fusion#Fleischmann.E2.80.9...). But if, and quite rightly only if, they've got good evidence and a theory that fits the facts better than any other, the consensus will shift.

It's not about cynicism, it's about rationality and skepticism. As the old saying goes, keep an open mind, but not so open that your brain falls out.
Yep, it's a double-edged sword.

The App Store may offer things like the iCloud SDK but will restrict apps from using features that compete with Apples own apps, as well as any cool hacks which apps outside the App Store are free to make use of.

My take is that Apple is herding developers into the App Store, enticing them with SDK features and the promise of riches, and at some point they will change the default gatekeeper setting so that users see great big warning signs and are too scared of running non App Store software.

We're probably still a few years away from this happening, but the writing is on the wall.
A minor point, it's at its peak of 1kWm-2 when the sunlight is perpendicular to the Earth, that is, when the sun is directly overhead, because that's when it has to pass through the least atmosphere. Sunlight reflecting off the building where the sun is not directly overhead will necessarily be less intense.
This is all predicated on the idea that you being able to release apks easily gets users who care enough too give you valuable feedback that you can use to learn and improve your app faster.

There are more apps on the play store than the iOS store, and apks have always been easy to work with and had this same advantage.

If this advantage has always been present, why aren't the apps already better than iOS apps?
Or you (3.) derive utility from the appearance of backlit keyboards.
Agreed. I'm glad I left TripAdvisor when I did, but what I learned there was incredibly valuable. Working with very, very good people and learning from them early on has proven to be a really big long-term benefit.

But I fucked off to a small medical-software company that I could work at while making video games, I have no taste for the work-for-my-social-startup-so-I-can-buy-a-Lotus world.
Its a little sad that repeating the exercise today shows little improvement over 30 years ago. The HST125 is still the fastest diesel train in the world (the actual video was likely taken from a Diesel Multiple Unit which are lighter and more efficient but not faster), those lines are still not electrified little has changed in train signalling with most of the improvements in train control being to centralise it rather than actually improving the rail service.