skysight-inc/HackerNews huggingface dataset:
1) You realize the Elcomsoft attacks were largely mitigated for iPad 2, iPhone 4S and later, right? If I were drchrono, I'd either require those devices (or later), or at least require informed consent by the administrator of an office to allow earlier devices.

I'd bet on iOS vs. stock Android for security-critical bugs at this point, but it's kind of a wash. You could maybe audit Android better, but that would be a serious engineering effort.

2) drchrono makes EHR. They don't make a secure tablet OS, and they don't (as far as I know) distribute tablets/phones to the doctors. Being a software/services business vs. a full consultancy is a big difference. Being a HW/OS developer is a big jump beyond even consultancy.

I'd love it if someone decided to build a SE Android + HW security Android distribution (maybe with device virtualization like from Bromium built in, too). And centralized management per-organization (i.e. not by Google or Apple or a carrier, but yourself). Essentially a Blackberry that didn't suck. Unfortunately, no one is doing that, and it would essentially require being Samsung or HTC to build the hardware, and someone like Google to build the software. Google's Android team has repeatedly shown themselves to be at best indifferent and more likely hostile to any real enterprise security features; they barely have a sandbox (in contrast to Chrome and the SSL teams at Google, and corp security, who are pretty much world-class for security).

I'm pretty sure if someone were building that, it wouldn't be drchrono, though.

3) No one cares about $500 vs. $300 for a tablet once they've made the decision to buy for a doctor's office, at least from my experience with doctors. Pretty much anything <$1k is the same. This is admittedly mainly in the US, but that's where most healthcare spending happens, and where the "meaningful use" incentive happens ($50k to adopt an EHR/EMR).

iPad 2 would be a legitimate deployment platform, and those are cheap (you'd really want a 10" in a medical environment), if you really care about cheap. I'd also want an IPS display for wide viewing angle.
"Flashcards are actually pretty good for acquiring masses of vocabulary. But it doesn't help you put those words together coherently or even enable you to comprehend what you hear."

In my experience with Japanese, using flashcards for kanji doesn't really help with long-term memory acquisition.

I agree with your latter point about context; it's better to find an unknown word in a sentence and look up its meaning, then you tend to remember the word longer b/c you understand how it's used.
Also missing Marpa: http://jeffreykegler.github.com/Marpa-web-site/
The myths are a mix of those that are correct but often misunderstood and those who just are plain wrong. Those which are plain wrong cannot be responded to with "This is right, but ...".
3. I don't understand the desire to trim seconds off of boot-up time (even assuming that systemd does this; it didn't for me). The goal should be to restart less often, not to restart more quickly.

5. The systemd documentation is indeed very good, and that's probably one of the biggest drivers behind its adoption. However, it is also difficult. A big part of the pushback from people over systemd is that it also replaced syslog, and did so with its own custom binary log format. To quote from a forum thread I started shortly after updating my old system to systemd, "Getting smbd/nmbd to work again was a real adventure. Like other users reported, it would just silently fail when starting it from systemd. No error message when issuing the start command, and only a vague "failed" in status. I ended up having to track down Lennart's blog post on "systemd for administrators" to figure out how in blazes to extract anything useful from that cussed binary log system he invented. My first half-dozen or so attempts to get anything useful out of the log journal got exactly zero results; I finally got lucky on another approach..." (I ended up abandoning that distribution altogether after that and a number of other frustrations, and the response from the forums.)

13. The problem for BSDs isn't so much that systemd is or isn't portable to them; it's that some upstream software is beginning to require systemd, making that software difficult (or impossible) to port to BSD.

14. It seems weird to me to hear someone else decide for other people what is or isn't a "negligible" amount of work.

15. So ... systemd is in fact Linux-only by design. How does that jive with 13 again?

19. systemd may not "force" you to do anything, up until your distribution adopts it, pushes it as an update, and then you find yourself spending hours trying to figure out how to troubleshoot a problem that didn't exist before the update. Then it certainly is forcing you to do something.

Here's the problem in a nut shell as I see it: if systemd had been the default in Linux for the last ten years, probably the tool chain around it would be mature enough to meet everyone's needs, we would all be accustomed to the specific commands needed to control and interact with and debug systemd stuff, and if someone came along and proposed replacing everything with a syslog daemon and a pile of init scripts, there'd be rage and outcry. That is to say, I don't see anything inherently bad about systemd.

But, what is enormously frustrating is to have something that works, and be well adapted to it, so that if something breaks I know exactly where to look, and then have all of that be replaced by a foreign system that breaks old things in new ways and requires hours spent trying to figure out what the hell happened.

If the replacement system offers serious benefits over the old system, that offsets the pain slightly. In this case, I've yet to see what the actual benefits are; I have no idea what problems systemd is attempting to solve which are so severe, so immediate, so intractable that they require a jarring change to some of the fundamental parts of the operating system.
I bet that copyright and patent laws make life unfair for a programmer. If he is protected by a large patent portfolio, he can attempt to make a profit, otherwise he must beware.
Simple Mean Reversion Trading Strategy in Python
Do think this might be a viable messaging option instead of paying for Internet minutes or SMS?
There are currently 23946[1] FreeBSD ports. Nothing I ever needed in the last 15 years of using FreeBSD was missing. Yes, dependency on glibc and the Linux kernel is sometimes annoying, but in practice it is not an insurmountable problem. Dependency on the Linux kernel is rare and dependency on glibc can usually be easily fixed and upstream is usually happy to accept patches. Systemd is different because there is a lot of software that might decide to use it and you can't just work around it.

[1] http://www.freebsd.org/ports/
"No one tool is going to do everything."

Why not? Isn't it something they should strive for?
I've read about this scenario before but I didn't realize it was Ken Thompson who proposed it. Very cool.

When I read the title I thought maybe Ken Thompson's compiler hack was Go (golang), which he co-created, and I was going to hear a bunch of Python or Node fans talk about why Go is not a threat :)
Pintxo of Sobrasada, piquillo peppers and quail eggs...
Leonard Cohen wiki page has a link to a whole book about this song's history.
Why would systemd suddenly change this? It is one of the init systems with best backwards compatibility with sysvinit. And writing a systemd init configuration for your daemon is trivial and it is also easy to maintain.
So still, the main claim sort of stands - there are unsolved mysteries in every day's life, which we still don't understand fully, but that we use anyway.

(I know nothing about electrochamistry or batteries :( )
There are a multitude of natively available browser functions that are immutable and cannot be CRUD'd. This guy really needs to understand more about the browser. His commentary on client storage in the browser also is myopic.
Is there a link anywhere to the full set of totals, so I can lookup my PIN and see how common it is? Surely that would be the most useful takeaway from this article?
"JavaScript does not encourage the use of pure functions."

Neither does Lisp.

"It does not encourage the use of recursion."

Neither does Lisp. (Common Lisp has no tail recursion in the spec.)

"It does not encourage immutability."

Neither does Lisp. (Actually, ES5 does have pretty powerful primitives for immutability, Object.freeze for example.)

"It does not have a robust, sensible type system."

If you mean static typing, neither does Lisp.

"It does not encourage currying."

Neither does Lisp.
It would be wonderful if JoCo makes more money off thissnafu than if Fox had give you him a gratuity or credit in the first place.

It would be beautiful if the above were true and the creative team did it on purpose, for example by intentionally preserving the duck sound after being told to swipe and wipe and the song.
Here we go: http://www.vineroulette.com - it allows you to search for any topic, or 'go random'. It combines all latest Vines in a full-screen visualization.

Edit: Discussion @ http://news.ycombinator.com/item?id=5124795
That's pretty cool. After playing around with this some, I'm glad that I won't just get to use it, but that I'll also get the chance to learn something from the code. I don't believe I've ever seen such nicely routed auto-updating paths before in Javascript.
I absolutely love how the parent comment exemplifies Muphry's law:

http://en.wikipedia.org/wiki/Muphry%27s_law
Building a FreeBSD 9 desktop: A modern guide
> I'd take a reduced salary and reduced position if I was treated like a human being for once.

Right, that's the thrust of my question. A person with a mental illness may not simply be capable of providing the value to their company of say a $150k/yr job, but firing them sort of implies to me that they have no value to the company. If the employee is able to show that they can provide value to the company, just at a lower position I'm thinking that would be a good alternative to outright firing.

Not talking about your case specifically, I can say this, from an employees perspective, having a peer that is not pulling their weight for whatever reason is infuriating as the slack ultimately ends up on the other employees.

From personal experience, I've had several peers who couldn't fulfill their full-time job assignments (for a wide variety of reasons), and I and my other team mates were already pulling 40-50 hour weeks. Having to add another 5-10 hours per week to our loads to make up for one of our peers was really simply unfair to us as well.
Because we all know this, it's just stupid to let people to select PINs. It's much better to pre-assign completely random PIN. As most banks in Finland do.

Based on properly working random number generator, I would say that 1234 is exactly as common PIN as any other PIN number.
Thanks. We still need to clean up the code a bit, and should be publishing more docs on how the thing is structured this week, so keep your eye on our github repo.
A database of of 4 digit passwords is not suitable as a replacement for PINs. Especially not for anything called a fucking analysis.

Banks don't let you choose 4 consecutive numbers or 4 of the same number making his first conclusion completely invalid. A lot of banks assign pin numbers now making the rest of his conclusions invalid.

I get wanting to analyze PINs, it's interesting, but pretending any old data that looks similar will work is misleading, disingenuous, and half ass.
I thought 1337 would be popular enough to be mentioned.
Ada Bryant and Robert Haire
What do you use for database access? It doesn't have a built-in ORM like many of the other frameworks, as far as I can see.
This.

How anyone can 'analyse' PIN numbers with unrelated data is beyond me.
The final image (http://www.banksy.co.uk/QA/camden/Images_Large/photo13-2.jpg) you are referring to is actually a paste-up made from photoshopping together different images.

http://www.flickr.com/photos/pranksy/6564545965/in/photostre...
RAS Syndrome. LCD display is another good one.
"In partnership with the consulting firm Accenture, the researchers randomly assigned a management makeover to a handful of Indian textile firms, while at the same time following a set of control textile factories to benchmark the effects of good management."

It certainly doesn't seem as though there was a potential for this report to have been biased.

A more interesting report would have been for those consultants to have been compared not only against a control but also firms where executives had been taught basic management and business practices themselves. They very likely could have made similar productivity gains and perhaps without spending the normally ludicrous management consulting fees.

Of course I might be wrong - the consultants did such a great job running Mitt Romney's Presidential campaign.
if you have to prepare for enough redundancy for a location to go down, then the cloud works just as well.

I'm really not seeing the distinction here.
I'm not able to replicate that on my machine.

> bpython version 0.10.1 on top of Python 2.7.3
Exactly. Line up with online purchase data and your friends database, and you have even better recognition.

Also: RGPs, as in http://en.wikipedia.org/wiki/GI_glasses

[When I was 10 I had black nylon frames like those, and yes, I was made fun of a lot, so I became a kernel hacker :-) ]
Sure, but it sounds like you're talking about a standard hidden backdoor. This is a pretty straightforward and obvious threat.

What Thompson describes is a whole lot more devious and difficult to detect.
I think it's easy to miss the benefits of HATEOAS. The relative ease with which javascript clients can use so-called level 3 REST to construct resource URLs from IDs is compelling.

We've been using a HATEOAS approach for the interface between our back-end rails app and our front-end javascript rich client.

We've seen significant benefits during development because the hypermedia links allow us to DRY up the coupling between client and server.

The overall result is much less boiler plate duplication and much clearer client code. It's easier to maintain and extend.

We've judiciously identified some exceptions where the client needs to construct URLs explicitly, in our case because the URLs are tied to dates and we think it's silly to have the server construct links for next_day and previous_day let alone an entire calendar view.
Data Driven Disruption is the way to move forward!
You always had to care about the init-system: There are some differences between e.g. debian and redhat (start-stop-daemon only on debian, tools for creating the symlinks to install a service), then there's upstart with a different shell-script-esque syntax.

To support systemd, the number of configs you provide will go from maybe 4 to 5, not from 1 to 2! And, looking at the examples provided by ArchLinux, the systemd services look as if they are a lot less boiler-plate than the typical debian init-script.

https://wiki.archlinux.org/index.php/Systemd/Services (e.g. dropbear is very simple)
> There's also the scope for corruption, when they pick the builders, but that's another story.

I live in Louisiana. Tell me about it!
How recent was this? The reason I ask is that in one of the CES demos they said their old prototype demoed at E3 last year had motion lag due to the color switching lag in the LCD panels they used. Also the nausea may have been experienced because the user was walking around in a game where they don't actually move in real life. Do you think you would experience the same nausea if the simulation was of a desk you sit at with multiple monitors?
Fetching is definitely something I want to do, but it's more of an 'also supports' thing. I want it to be able to get data in all sorts of ways. :)
How I wrote the most upvoted answer on Quora (and you can too)
Nightclub fire kills at least 245 in southern Brazil
I think the concept of redistribution is more interesting than which license. By what method could redistribution be achieved? Transparently accounted voluntary micropayments shared out though the reputation graph of a repo.

Call it, ahem, redis-tribution.
Have you tried using Heisig's "Remembering the Kanji"? I have never tried to learn Japanese, but I have heard very good things about using this book to learn the Kanji.
OH HELLS YEAH. This looks awesome! Thanks!
Great work! A suggestion: to make the text searchable using Ctrl-f, please render the maps using SVG instead of canvas. For a big mind map this is indispensable.
Myrtle Beach app developers create winner in Foursquare contest
Because you suck all the air out of the room.
Yep, you got it. Having a way to auto fetch something is a very soon thing. I also want to be able to have some sort of regex fetcher that can fetch and webpage and regex scrape a value (if not using an api, etc)
“Happiness is a byproduct of function, purpose, and conflict; those who seek happiness for itself seek victory without war.”
-- William S. Burroughs
I just want to emphasize, for anyone hoping to learn writing this way, that you can't effectively learn to write Japanese by typing. It truly isn't for beginners. Some Kanji are so similar that the only real difference is the stroke type and stroke order. Anyone wanting to learn how to write Japanese should, after mastering Hiragana and Katakana (both of which don't take long), pick up an engineer notepad, a brush pen and a modern Kanji learning book like "Let's Learn Kanji", and proceed to practice. Within a few months of daily practice you'll have mastered 250 Kanji, all of the Kanji components and learned a lot of new vocabulary as well.

Just don't attempt to learn Kanji in the order Japanese school-children do. They learn it in the order of conceptual difficulty, not difficulty of writing or frequency of use. Adults should learn Kanji by commonality and difficulty of writing, since our brains have already learned to grasp difficult concepts in our native tongue.
I really don't understand. Knowing the hardware doesn't stop it from failing. There seems to be two approaches here. One, buy really expensive HA hardware. Two, build software that assumes failure and can handle it.

Neither of these guarantee 100% uptime, but you can do the second one on a cloud without knowing the hardware.

Side Note: I've done e-commerce, and e-commerce typically makes all of their money around christmas. It seems crazy to me to buy super expensive HA hardware that can handle your peak xmas throughput, and leave it idle for 11 months of the year.
I think in a lot of cases, effort can be better spent by accepting a combination of tools (e.g. for dealing with screws in my glasses and screws in my kitchen table, having multiple screwdriver heads is probably a lot simpler than designing one that can handle both).
Amazon offers one nine of availability. I'm currently getting three on self-hosted equipment for a high-growth startup, with tens of thousands of concurrent users getting sub-second response times.

The key is having intelligent staff who have a deep understanding of your specific environment. This guy's argument completely discounts the value of that - he's essentially saying that using PHP over writing in C is better because the PHP devs know better than you do how to make stuff work.

My experience with EC2 support staff is that they are mostly concerned with their generic setup and are of no use when anything falls outside of that, and they especially can't provide any help for your specific problems.
I don't know if that means bye bye #4. Those 2 solutions are flash card systems. It might be worth testing fluentu by spending a considerable amount of time on the system and then talking to a native speaker.

Just because it's free, doesn't mean it's free, especially if it doesn't get you closer to the holy grail.

I think innovators should strive to get to the holy grail. The potential upside would be huge.
This was really helpful, thank you for jotting down your thoughts. It is especially interesting that you like the cropped images, I have been debating that design element quite a bit. I can't stand the masonry effect used on Pinterest
It is far more difficult than sequence alignment. Sequence alignment has quadratic complexity, while fragment assembly is NP-hard. Se for example

http://scholar.google.com/scholar?cluster=131745416915434219...
Haskell is so different from JS that is impossible to faithfully translate a monad into JS. It is like trying translate a Haiku from Japanese to English.

Maybe if he called his thing a Jonad, and explained how it was inspired by the monad's "executable semicolon" aspect, it would have been better.
Good thinking - we already planned an svg spike (probably using raphaeljs) :)
Say you release code X under a BSD license. Someone incorporates a neat, but tricky to re-implement, feature and release the code under GPL. Everyone wants that new feature but, if they do, they either have to reimplement it without looking at the GPL source code, or they have to use the GPL license from now on (or, third choice, live without that feature). I used to release my code under a GPL license but found too many restrictions. The worst offenders were tutorials written where the code was GPL. Tutorials that aim to free you by giving you new knowledge should not tie your hands and force you to adopt a license if you want to use that knowledge.
he should have been able to improve the circumstances

Was anyone asking him to? Was anyone paying him to? No? Then it's an uphill battle and also not his responsibility. Leaving is saner.
"holy grail of language learning is the ability to learn a language outside the country that speaks it, to a level of fluency that puts the user within 30 to 45 days of advanced reading, speaking, and vocal comprehension "

As someone who has learned several languages to near native fluency and majored in linguistics at the University, I think the OP is right on in his estimate of the goal. But the biggest problem software in this area is facing is that language learning is not a one way street. You can't memorize thousands of words in all the contexts in which they occur and expect to be able to have any competency, at least for speaking & vocal comprehensione. Even when the software provides dialoges and attempts to simulate conversations (ie. "Pimsleur" and others), it fails because its the same over and over, mostly outside of real world contexts, where background noise, dialects, and other tasks are involved. A new language learner has to be able to respond rapidly and fluidly in spoken conversation over a variety of subjects if he/she wants to be able to function at the level the OP is talking about, and current software simply doesn't provide the degree of realism in these types of situations.

IMHO, in order for any software to be able to achieve the above stated goal, I think it would need to first have a very good humanlike AI. why? So you can have a "human partner" in conversations over a variety of subjects, where the learner is forced to quickly respond and interact with the partner/software. Otherwise, you're left with all the current options which are at best subpar in comparison to actually living and interacting with native speakers in the said country.
I don't disagree with most of your post, though I cannot resist commenting on the whiteboard interview test. Writing anything other than rough pseudo code or algorithm sketches on the whiteboard is a silly exercise. It's not reflective of any sort of reality, probably indicates to candidates that you are not working on any interesting problems, and people won't remember exact syntax or library functions for any language that they don't use fairly regularly.

The whiteboard is only useful as an aid in explaining an algorithm. If a candidate can do that without the whiteboard, even better.