skysight-inc/HackerNews huggingface dataset:
> Note that final gem: "YOU SHOULDN'T BE PROTECTING PEOPLE WITH SILLY PASSWORDS". So he's throwing what, more than half his users, under the bus...

On the one hand, with a decent password manager it is pretty easy to avoid silly passwords. For most sites that require a password, I am never going to need to login to those sites except from my home desktop, my work desktop, and my mobile devices. My password manager (1Password) works and syncs with all of those, so I'm fine.

1Password is commercial, but there are free password managers that achieve the same result, I believe.

On the other hand, there are some times when a strong password is annoying. Spotify, for example. I have a strong password there, and when I got a receiver that had Spotify support it was a real pain to enter that password. 1Password (or any other password manager as far as I know) does not have a version for Denon receivers! I had to look up the password, and then enter it via the receiver remote and on-screen keyboard. Every time there was a transition of case or between alphabetic and punctuation, it would take several button presses to switch the keyboard mode. Ugh! It took something like 10 minutes to enter that password.

My receiver also has SiriusXM, Pandora, and Flickr support. I don't use any of those, but someone who did would have 3 more passwords to enter. And then there is my Blu-Ray player, with Amazon Prime support, Netflix support, VuDu support, and a whole bunch of others. (Seriously, there are at least 50 services in the "video" section, and a whole bunch in the "audio" section. Some of those are services that don't require a login, but many do).

It would be extremely annoying to try and enter strong passwords for all those. Until a better way is found to provide these kind of services on receivers, Blu-Ray players, game consoles, and such it will be hard to get people to use strong passwords.

I've seen one service do it a right way. I gave the device my account name. The device talked to the service, and then showed me a 5 digit or so number. I then had to go to the service's web site, and enter that number. The device was then linked to my account. Presumably, the device and the service worked out some kind of credential that the device would use on subsequence accesses to prove its identity.

My conclusion is that ===IF=== we can do passwords right everywhere on the client side, then we could indeed stop worrying about weak passwords on the server, and so maybe just storing a hash would be good enough (it wouldn't even need to be salted). Using scrypt or bcrypt would just be a waste of server resources.

But that's a big if. We aren't there yet. I don't know if we'll ever get there. There's no technical reason we can't get there, but it might require the cooperation of too many interests with too many ego issues and territorial issues.
Check out xnomad. It seems to me the closest imitation to Xmonad, and doesn't need messing with a config to get working (that is, comes with good default keycommands and limited layouts). It's not in Haskell, but the authors experimental ObjC-based-but-many-times-cleaner-and-cooler language.

Install tranquil, and then I recommend using the .app bundle I made on my fork (https://github.com/JasonJAyalaP/xnomad/raw/master/xnomad.app...). I added a nice icon and made it much simpler to quit and launch it.
I'm wondering how many fo these apply to other countries in the Anglosphere. Certainly Americans in general must be better at expressing emotions than the British in general, culturally speaking.
I'd think that JVM JIT and GC count as technical advantages.
This is something of a career retrospective review article on solitary written by a psychiatrist from Harvard Med in J. Law & Policy.

http://law.wustl.edu/journal/22/p325grassian.pdf

I had a longer reply, but somehow I don't think you're listening if the New Yorker is hyperliberal. Obviously solitary is not unusual, the questions are whether it's cruel, and whether it prevents recidivism and enables employment upon release.
Cool -- nice find with that article. Tesla / Elon, are you reading this? ;)
That's a reasonable criticism, but I don't see how it's applicable to the Optimus keyboard. The Optimus only changes the labels to more accurately reflect the function the button already has in a given context- such as replacing "U" with a rectangle symbol in Photoshop, or showing accented characters when you hold down the right modifier key. The Optimus doesn't add any new key re-definitions.
Tumblr CEO interview and thoughts post aquisition
And journalists and political activists.
I think "I just like it" or "it feels right to use it" should be enough explanation.

There's a tendency for people to demand a rational list of reasons for any choice (very academic thinking) but more often than not that results in tacked on reasoning anyways...oh sure I use it because of X,Y,Z while in reality we just picked it because it "seemed cool"

I think people are too scared to regret their choices. Just picking something and "muddling through" tends to be pretty awesome. Sometimes you'll just find out it won't click and then you can pick something else (you should find out pretty quickly because it just won't feel right)

Instead there's often a tendency to read "haha IF ONLY YOU HAD THOUGHT ABOUT THIS BEFORE...FOOL" responses instead of "cool that you jumped into the pool, I hope you learned a lot"

/rambling and ranting
Yeah, this for example is blatantly false in most other anglophone cultures and at least a few others I'm aware of. Or it's the exception rather than the rule:

> Whereas, in almost every other culture approaching women this way is met with a confident smile and a “Thank you.”
As an American, I honestly don't see these as being a problem at all where I live. Maybe its more relegated to the coasts but by and large everyone I know here (obviously there are exceptions every now and again) already knows/has this internalized.

This post largely strikes me as attacking American export culture mostly. Guess I'm in an exceptional bubble then.
I'm curious why CloudFlare includes !EDH as part of their cipher suite options... Guessing they were just following the recommendations from https://community.qualys.com/blogs/securitylabs/2011/10/17/m..., but having a specific reason would be interesting to know. EDH ciphers are generally slower (so I could see why a company that wants connections to be fast wouldn't want to use them), but at the same time, they also allow for forward secrecy. Seems like CloudFlare might want to prioritize forward secrecy over speed, as per http://blog.cloudflare.com/cloudflare-prism-secure-ciphers. Maybe I'm missing something here, though... Perhaps that !EDH should be !ADH?
This month I decided to go on a jQuery diet, as a kind of fun challenge. I'd increase my familiarity with the standard DOM and selector APIs, and reduce my dependency on jQuery.

After a few hours of working without jQuery, it became obvious that the standard DOM & selection APIs are verbose and a little awkward. In about 20 minutes I produced a little wrapper that was compatible with a small - but common - chunk of jQuery's surface, and it made life so much more bearable. It clocked in at about 1kb minified (no GZIP).

Obviously it wasn't battle hardened and didn't deal with cross browser issues, as it was just for hacking with - but it felt like proof that a wrapper of some form, if not jQuery, is pretty much always necessary
A HUGE difference, performance-wise. Delegation is O(1), while using any form of `each()` is going to be O(n).

To elaborate -- jQuery does not set an event-handler for each TR -- it sets one on the parent element (the table), and basically when the table is clicked jQuery gets the event and asks: "are you a TR?", and if so, then the handler is called with the clicked element as the context. So even if your table has 1million rows, only 1 event handler is attached and the DOM is only accessed once.

Of course, accessing the DOM 1 million times within a loop is going to take forever.
Awesome insight, Josh! Thanks for sharing!
One would hope not... With the API they offer it should be the type of service that is reasonable easy to make pretty much indestructible.
When?

Year 1 - 5 figures
Year 2 - 6 figures
Year 4 - 7 figures

Why? We knew the industry and knew the problems before we started. We had someone nearby who was desperate for a solution and confirmed they were willing to pay the high rate we were looking for. Technically, we had an interest in the types of technical problems they had and had spent years playing in those areas on side projects.

While working on an MVP we continued selling the vision to other prospects using nothing but balls and a PowerPoint presentation. We landed a second customer for year one and worked hard to keep them happy. Our MVP was barely that and we iterated based on the feedback we got from the first two customers.

Our fee structure puts us in a position where we only make money when our customers do. That makes it very easy to prioritize features based on how valuable they will be to our customers. This creates a nice tight feedback loop. When combined with our fanatical customer support, we have many die hard fans who do a lot of marketing for us in an industry where many of the prospects are good friends with each other and use trade shows as a chance to get together and drink with old friends and brag about the cool stuff they are using to help them with their business.
I think we have another 10 years or so until 2-3nm chips.
And millions of us foreigners with absolutely no vote on anything.
Even if this is true, this only spells the end of exponential growth in hardware performance and the start of the more efficient software era. Engineering is all about finding the right compromises to get the job done given a set of restraints. When the HW performance becomes the major restraint then you just have to design around that.
The grep test - my personal experience
Is there any reason to expect that it wouldn't run as well in Python? They're both dynamic, interpreted languages, and it's not as though no-one's ever written a large codebase in Python.
>So Moore’s Law might be right after all, but it is right in a way that would require the entire mobile ecosystem to transition to x86. It’s not entirely impossible–it’s been done once before. But it was done at a time when yearly sales were around a million units, and now they are selling 62 million per quarter. It was done with an off-the-shelf virtualization environment that could emulate the old architecture at about 60% speed, meanwhile the performance of today’s hypothetical research virtualization systems for optimized (O3) ARM code are closer to 27%.

Why do you need virtualization if the code is Java bytecode? Sure, this doesn't work for iPhone, but Android should be able to easily change the processor architecture. (If I'm not missing something here). There's already Android-x86 project.
Ok dudes, enough is enough.

What actual proof does this dude have that pocket-sized computers have reached their limits of performance and memory?

All I see are some carefully selected quotes from some "hardware engineers" who are doing nothing more than offering up their opinion.

An "ex-Intel engineer" and a "robotics engineer" have a single paragraph. Really, this is your research? Some anonymous quotes, probably taken out of context?

> I have consulted many such qualified engineers for this article, and they have all declined to take the position on record. This suggests to me that the position is not any good.

Really.

Do I have to go on?
I've had backup restore to a new device not work for google authenticator (I assumed that was by design), which is what has made me wary of it.

But for your app, I assume you use manual re-authentication if someone loses their device?
I'd never heard of workman, I think I'll be trying this out.
“in a memory constrained environment garbage collection performance degrades exponentially.” The obvious solution, then, is to throw memory at the problem, no?

Isn't the obvious solution to avoid garbage collection whenever possible? Just consider 'Date.now()' vs 'new Date().getTime()' - are we even trying? Shouldn't we start considering unnecessary garbage a bug, like a memory leak? That might not change everything, but it surely would help, no?
Apalon Releases ‘Pimp Your Screen’ App for Android
Exactly. Most people forget this. It's not the risk present for you or I that worries me. It's that the powers that be can use this information to subvert justice and/or the political process without anyone(other than those affected) ever knowing about it. It's already happened in the past(recent tea party tax scandals, watergate, etc...)
Former Judge of Intl Startup Festival Wins Top Honours, Raises $500K in 48 Hours
Google’s Schmidt: Hollywood Should Take Content Pirates To Court
One additional point is that even if .js doesn't improve much, mobile browsers can get a lot faster. iPhone's webview is a lot faster than Android's webview, so there's plenty of progress to be made especially with rendering.
Testify brother any one else notice the shoutout in toy story one to BYTE?

Always wished I had the nerve to get our electronics shop at BHRA to build the modems costing $35 for one project instead of paying £300 for a five answer modems and £600 for an answer originate - highly naughty at the time as you could only connect approved devices to the BT network - as it was we had them taken apart and some components changed to tweak the gain.
I'll chime in because theres a lot of mis-information here.

My credentials: I am the founder of Authy, we do two-factor authentication using SMS, Phone Calls, TOTP App and Hardware Tokens - we protect over 80,000 accounts including CloudFlare, Coinbase etc, so I am very familiar.

On 2FA using SMS:

1. Yes it's not as secure as a dedicated TOTP App but:

2. SMS phishing doesn't matter here. SMS phishing would allow the attacker to send message as you but not receive messages. In order to compromise Two-Factor SMS auth he would need to be able to receive them.

On VoiceMail Security:

1. True, voicemail is insecure. But if your Two-Factor Auth provider knows anything about security, he can help you. For instance we just helped Coinbase with Voice verification. In order to protect the verification codes going to VoiceMail, we require the person to input a number before reading the token.

Eg.
Hello, this is Coinbase, if you are expecting this call, please press 1.
[ Only on 1] your code is, “1,2,3,4,5,6,7”. Again “1,2,3,4,6,7”, last time “1234567”.!

So if you can only use SMS or Phone Call Two-Factor Authy, by all means use it. If you have a Smartphone it's better if you move onto a dedicated TOTP App.

The biggest weaknesses this days on Two-Factor Auth is not SMS or the carriers, it's the implementation. Unfortunately although implementing TOTP is easy, a secure Two-Factor system is not. Most are using recovery codes, e-mail and defective recovery mechanisms, which is how this systems are being by-passed.

http://www.slashgear.com/dropbox-hack-allows-bypass-of-two-f...

Find yourself a good Two-Factor Authentication provider. I would recommend Authy, but I am biased so I'll recommend Duo-Security.
Ahh this looks very promising. I'll be checking it out, thanks!
Computer Shopper was the multi-vendor catalog for computers back when a dial-up BBS was all the networking you could expect at home.

There were also articles, every now and then something interesting like reviews of early PC UNIXen, scattered in with hardware roundups that often took the form of "200 laser printers!" each with a 1 paragraph blurb.

If you were the sort of teenager who was saving up for a computer to take to college - as I was - it provided endless opportunity to re-enter prices on spreadsheets while sighing over the latest unaffordable super-PC sporting a brand-new 80486DX-33 and 2 full megabytes of RAM.
At SEOMoz,no? But that shouldn't matter - I could see a few ways you could gain large market share. It's clear to me that SEOMoz, large SEO firms, major/minor search engines will either build or acquire something like this. Some thoughts on large account acquisition strategies and revenue...

Account acquisition
For SEOMoz - Try a few channels in the door. A) More aggressive/direct - Contact a junior salesman, and sell him. Offer him a referral fee for anybody that uses Angular, etc that he refers. THen try that with each, and approach the head of sales. B) Less aggressive - Follow their blog, and find the key SEO thought leaders in their company or that guest blog. Those are influencers, contact them and offer them initial access. C) Partners - do the same for each of their partners. Investigate their entire client lists (eg: maybe linkedin, etc...offer it for free or reduced - and then leverage that for sales).

For major search engines (Google, Bing, DuckDuckGo) - Offer directly to them, their staff, sales staff to partner to do SEO for angular apps and feed that to the search engines for free (or as a service initially of your time). Have their accounts pull you in. Partner with head SEO influencers, or Google partners. Then use that to approach Google/DuckDuck's staff saying "We already do SEO for 30 of your angular app customers".

For growth hackers - Focus on growth hackers, do cross-promo with them offering special deals. Get them to pull you into the major startups they're at.

For major SEO Firms - similar partnering, sales startegies as above.

Revenue
Offer a few tiers, initally to the larger marketing agencies, do it as a service. THis would give you enough revenue to bootstrap (eg: a couple $k per month for a few clients).

Approach a few well known, high grossing startups you know are using Angular, etc and offer to either do it as a service, or to partner and do it for cheap for marketing.

All of these are worth the price you paid - your mileage may vary.
Yes, Python is more unreadable than Perl to me. :)

Read https://coosoft.wordpress.com/2013/02/24/the-perl-vs-python-...
Sex on Campus: She Can Play That Game, Too
'Problem' and 'attacking' sound a bit defensive. The post is definitely a generalization, but I would say (as a Canadian who visits the US a few weeks out of the year) that these are fairly accurate.

I don't know if these are very popular in the US, but the CBC has a whole series called 'Rick Mercer Talks To Americans' (comme ca http://www.youtube.com/watch?v=BhTZ_tgMUdo) where he gets people in DC, New York, and other major cities to go on national television and petition to 'Save The Parliamentary Igloo', 'Stop the Saskatchewan Whale Hunt', etc. These people really just don't seem to:

a) have any awareness of the rest of the continent they live on, above the 49th

b) care what they say in public. They'll just spout anything to be on the TeeVee

I'm aware it's all edited to be entertaining, but frankly it does seem fairly representative of American exceptionalist and isolationist culture.
Event delegation is entirely different to how you would normally do it. It relies on the events from the inner elements bubbling up through the parent elements. So you put an event listener on some common ancestor (the tbody in this case) to the elements you care about (the tr elements). A click event on some tr will bubble up to the tbody*, the event handler there can check whether the originating element matches the selector "tr", and if it does, it does something like: `yourCallback.call(event.srcElement, event)`.

The obvious benefit of this is that if there are 10,000 tr elements, it is quicker to attach your listeners (there's only a single listener on the tbody) and less memory is consumed (again, only a single listener). A more subtle set of benefits come from manipulation of the DOM. Your listener is able to respond to events on elements that have been inserted after the listener was first registered. Also, when removing tr elements from the DOM you don't have to remember to unbind all your event handlers (a common source of memory leaks, as they can be GC'd)
Dropbox DBX Keynote
I can't understand Why Pythonista always interfer in other languages articles and bitching it and propaganda Python.

Get out Python anal fucker.
I don't understand the mechanism here. I thought sucrase, the enzyme that breaks down sucrose (table sugar) into 1 fructose and 1 glucose (same as HFCS), acted almost immediately -- at least on the timescale of nutrient absorption. Is it just short circuiting our sense of satiety? Maybe the raw fructose makes things sweeter and stimulates reward centers better?

I wonder where honey falls in all this since it has higher fructose than the most common 55% fructose HFCS blends.

We seem to know so little about all of this, but I think it's safe to say that both sugar and HFCS are bad in quantities that the common american is accustomed.

I find it's best to just avoid sweet foods all together, but if forced to choose I would take HFCS over artificial sweeteners any day of the week. Our bodies have been dealing with glucose and fructose for a very long time -- even on evolutionary time scales. The same can't be said for Sucralos, aspartame, or Acesulfame potassium.

Everything in the world is either overtly or subtly poisonous; the only question is, at what dose?
I hate to be that guy, but a few things about your writing style throw me off. http://cl.ly/image/3U2k0s2p0b28 is not okay.

But, more importantly, who are you to review a private beta? This stuff isn't released yet.
I made an app that remaps your Mac's power key to forward delete:

https://github.com/pkamb/PowerKey
I personally doubt the problem is mainly maternity leave. 3 months time off for a good employee is not that bad (though if you had an equal male candidate, sure on sheer cost reasons you'd hire them). The problem is they are more likely to leave permanently or the perception they are more likely to put up a stink about discrimination if you say they are not pulling their weight.

Imagine what would happen if a guy came in and said "I like this job, but my real passion may be art. There is a %50 chance in the next 5 years I am going to leave my job to peruse that." You'd try to avoid hiring them.

Of course, this has terrible consequences in that it effectively discriminates against women in hiring, but simply trying to get hiring managers "not to be sexist' isn't going to fix the problem. You are asking employers (men and women) to weigh their personal ideals ( gender equality) against financial incentives(retaining employees, not paying to).
Link between quantum physics and game theory found
Two factor is something you know (but can forget) and something you have (and can loose). The risk is there, regardless of the thing you have being a phone or key fob or smart card.
I remember when this was thick as a brick. An engine for printing money. Those were the days.
Agreed, I"m a Ruby person personally and often end up writing things that later I only shake my head at and rip out and replace with a few lines or a better idiom/algorithm.

To be honest the parent comment to yours first link reminds me of a rather lot of shell/perl created by people that treat things with the procedural mindset and just keep bashing their heads against a problem until it succeeds. There isn't anything wrong with that but that python really is no different stylistically than any of the "horrible perl" stories I've seen. I've seen perl that made most ruby look unreadable at first glance too. I think it really goes to show encrypting human thought into programming languages is not trivial. Also I'm getting sick of these $foo_language is better/worse/a threat(really threat? weird word choice imo) to anything. Every language I learn I learn something new in. Even if its the ones I don't like much like Java/PHP, doesn't mean they're bad languages or they're devoid of being able to teach you new ways to approach problems.

Meh, ranted longer about this than I'd thought I would.
World’s 1st RFID/NFC Enabled Physical Facebook Fangate
Almost every digital guy is familiar with the Facebook fangate, but with the social media RFID/NFC turnkey solution it is finally possible to do the same in the physical world as well.