skysight-inc/HackerNews huggingface dataset:
Oh, I see. I thought you meant you didn't see Navdy offering navigation on their hud. Never mind! :-)
I think I trust my compiler to generate clean assembly more than I trust a commercial company like Synology to write secure software
Om and Flux
>And honestly, the inconveniences aren't hard to work around. If you work across timezones, you figure it out pretty quickly.

Spoken like someone who has never dealt with computing time.
Or, sometimes you have to serve 10k pages at once. http://www.kegel.com/c10k.html
> I think the assumption is that the money you save by reducing the complexity of the welfare bureaucracy would be passed into the income itself.

Agreed, but there are currently many more people who aren't currently receiving benefits than those who are. Expecting to save multiples of the current expenditure by decreasing the bureaucracy is obviously unrealistic.

> But I was assuming that the basic income system would give the same amount of total money to people currently receiving welfare benefits.

Fair enough, I was trying to point out that achieving that would require either restricting those who receive the basic income or increasing taxes in order to keep the change revenue neutral.

> My point was that among people currently receiving benefits, some portion of them would receive a lot less on basic income, even though the money received would be the same on average.

Again, I agree, though I don't see that as a problem. Politically, I don't think there would be enough of those people to be a problem. And socially, they probably shouldn't be receiving that much more than the average anyway.

I guess I wasn't so much arguing with you as using your comment to go off on a tangent :)
> I am surprised that focusing on streaming live video games is better in the long term then focusing on live content in general.

> I'm not an expert on the subject, can someone enlighten me?

It probably helps to see live streaming of video games in the context of pro sports.

This was surprising to me as well, until I heard friends, in particular younger ones and children speak about it. Professional videogaming tournaments are big and serious business.

And with that, I can also imagine how watching non-pro/non-top gamers making with funny commentary is in fact a lot more fun than watching amateur sports players do the same :)
Tangential question: reading the transcript, I'm surprised that two of the three parties' lawyers are attending the court session via speakerphone. Is that common?
Because we have multiple app servers, but only one reverse-proxy? I don't want to centralize a task that could be distributed.
> I admire the Japanese honor though..

There's no honor in making a quick exit instead of facing the music.
> I admire the Japanese honor though

huh?
New Relic is a bigger business now* (*speculating). And it used to be integrated into the dashboard before the add-on marketplace existed.
I do not admire a society in which highly regarded scientists are drawn to commit suicide after being cleared of any wrongdoing, according to the original article. The loss of Sansai is truly saddening.
This library is a couple years old already (version 0.1.6 hit PyPi in Nov 2012). A rename at this point seems unlikely.

Unlike datetime.now() and datetime.utcnow(), arrow.now() produces a datetime that includes tzinfo. As long as that's on there and correct, I think the risk you describe is low.
Where does the idea that when getting rid of timezones we'll also get rid of "relative time" reference points stems from?

We'll also know that 12am is noon in England and dawn in New York. We could have handy mappings to look that up too.

We just wont have all the constant need for mental conversion baggage associated with timezones, and the crazy boundary issues.
Can you give some examples of parts of the world that have different standard business hours from 9 to 5?

In your explanation, don't use times as reference points.

...

Yes, of course there are variations in standards; but that makes times all the more valuable as reference points. People in Saudi Arabia, for example, will have similar ideas of "what people do" around 6pm, and if they work with someone in Argentina, they can have an interesting conversation figuring out how Argentinians are different (and how they're the same). But if they lose time as a shorthand, it's suddenly really hard to have that conversation.
I'm upset that in the year 2014 we still think that having the package maintainers patch ancient software instead of providing latest upstream versions is a good idea. I'm a big fan of the *BSD package management model - they give you a stable core, you pick your own (upstream, possibly bleeding-edge) versions of everything else.
For those looking for additional reading: Nemo's series on BitCoin and Cryptography is a very balanced read. https://self-evident.org/?cat=12
This is a very interesting problem to tackle for all runtimes.

In my experience, the main issues are:
[1] How do we store the date / time fields in the database tier
[2] How do we display those fields to users in multiple time zones and cultures and gather validated input from those cultures
[3] How do we do date / time math in a simple manner

Issue [1] has implications for manipulating data directly (i.e. querying or reporting). Should the data be stored in UST or in some "local timeframe"?

Issue [2] always seems to trip some developers: how do we render a time or date in a way that makes sense in a global world (i.e. "8/5/2014" vs. "5/8/2014" vs. "5-8-2014" or 3:26 PM vs 3:26 etc).

Issue [3] is always a pain too, based on whatever decisions were made for [1] and [2].

Test of awesomeness: if your code works in Hebrew or Thai cultures!
See my blog post about a benchmark comparing the performance of heavyweight vs. lightweight Java threads in a web server: http://blog.paralleluniverse.co/2014/05/29/cascading-failure...
In general no, parties have pretty wide latitude to file motions. If the law doesn't permit the request, the remedy is just that the court rejects it. That's the basis of the adversarial system; parties are expected to try to make any argument in their favor they can possibly come up with, and the court's job (or jury's job) is to weigh them. So it's disfavored to punish someone who makes a losing argument beyond just the fact that they lose the argument. In rare cases an attorney can be sanctioned for lawyering way out of line ("Rule 11 sanctions"), but that usually requires a pattern of over-the-top behavior, ignoring the court's instructions, repeated frivolous arguments, etc.
Answer: Because you're not using Erlang/Elixir.

This sounds flippant, but it's not. The erlang BEAM VM is the only system designed to do concurrency correctly. Unfortunately, I think that many people think that concurrency can be done in a library, or on non-concurrent systems like the JVM. I understand fully why Go would like to claim to be concurrent, and all the other languages would like to claim it, because the reality is we're in a multi-core multi-node distributed world. But don't fall for it.

Worse, there are some simple low hanging "concurrent" fruit like go-routines that make it seem like you've solved the problem.

I would have no problem if someone had made a language and VM or compiled-to-binary like go, that was truly concurrent, and that copied the erlang solution (no mutable state, supervision trees, let it fail, etc.)

Seriously, steal from the best if you're making a new language.

So far, nobody has. And since we live in a multi-node, multi-CPU world, you really should learn erlang (or elixir- which adds some features and has an easier syntax).

Seriously, I know it's much easier to go with flavor-of-the-month and pretend that there is no downside. But sooner or later-- hopefully sooner, because it will be much more painful later-- you have to pay the piper for not being concurrent. We've seen massive failures and re-architecting of systems as a result-- twitter survived years of fail whales because of their poor initial engineering. Can you count on enough VC money to do the same?

PS- not to pick on Go. Go has several features that are really bright choices. I am just using it as an example here, but I've heard of everything up to and including node.js being claimed as making erlang unnecessary.
> If your application is largely fetching a bunch of external resources, say from something slow like a database or a web API, mashing them up and returning a response to a client, you need async.

Web request maybe, database definitely not. Async means you put a high load on the resource you connect to. In the context of a database that makes absolutely no sense. In fact, it's much more common that if you have an async app that you have a connection pool that gives out limited number of connections. At that point you might just use threads.
>Yup; it's not impossible; but think of how much more complicated the interface would become. There would have to be a whole lot of little, wordy labels instead of simply showing the time.

Or, you know, it would just be something like "+6" (meaning 6 hours ahead of your time in their daily cycle), etc.

I mean, it's like a lot of people commenting against this hasn't paid any thought to it at all...
Yeah, my first thought was, "wow, I always thought that about spinach!" But, that wasn't the point of the article at all. This was an engagingly written article that kind of read like a mystery whodoneit?
Hacker Says He Can Break Into Airplane Systems Using In-Flight Wi-Fi
Having used Angular, Ember, Spring and Rails, I'd say that's a bit unfair. Spring and Java are significantly more verbose than Rails. I wouldn't say Angular is more verbose than Ember to the same extent (it is, but not the same order of magnitude as the Spring/Rails comparison).
Analysis of Bitcoin Adoption in a Physical Marketplace
The Bankruptcy Code Is Bankrupt
"Basic Income Guarantee" refers to Basic Income (writing everyone a check) and not Guaranteed Income (writing a check to those bellow the threshold).
Is there any language that got the date & time library right the first time? It seems like people always suggest to use a third party library. JavaScript has Moment.js, Java has Joda-Time, and now Python has Arrow.
yes. they are stored as hashes salted on app end.
That's a matter of terminology. I don't call `go` "async".
One would assume that if the OS is set to English, the keyboard options will be listed in English, and if the OS is set to ㄍㄨㄢ ㄏㄨㄚ, the keyboard options will be listed in ㄍㄨㄢ ㄏㄨㄚ. This isn't a problem at all if you know the name in your own language for the language you are seeking.
ZIL and the Z-Machine
You understood my comment correctly. False consciousness is a good explanation because of the fact that tech workers accept such a meager proportion of the profits generated by their work without complaint. Why would anyone knowingly accept less money than they're worth? They wouldn't, knowingly. It must be unknowingly. They must not know they're being exploited because there is no significant organization. Instead they all act as "temporarily embarrassed millionaires" and try to increase their wealth incrementally, by competing amongst themselves for promotions and raises, working 100 hour weeks at startups for equity, and so on.

You suggest that they look elsewhere for a better deal, as if the free market price for their labor is by definition a fair price, but it is not, because of the power differential between capital and labor. It's not that all business collude consciously against labor(1), it's simply that the exception in the law for tech workers drives the price down, because it's purely good management not to pay any more than necessary for labor.

I'm not suggesting mass strikes, labor unions, and Marxist claptrap as a solution. Removing the loophole would be an entirely reasonable starting point. I've never seen anything approaching a rational justification for the tech worker exemption.

(1) Except when they do, like with the recent wage fixing scandal amongst a subset of well known companies.
Waaaaiit a second! This "async thing" is not a fad created by node.js but rather the effective conclusion of the C10K problem - http://www.kegel.com/c10k.html - that we could scale up our application servers to handle more requests and that threads alone had failed to get us there.

And sorry anyone who wants to claim that Java's green threads are somehow a better programming model than async IO ala node.js + promises is pretending to write code. Yes async IO is not easy, certainly nowhere near as simple to manage as process / fork but with consistent coding style your can still end up with a system that behaves predicably and most importantly can be reasoned about.

Meanwhile I bitterly regret the days and weeks of my life lost to debugging threaded code. Never again!
Been done, since 1998[1]. Had mainstream coverage when it launched. Been totally ignored ever since.

[1] http://www.swatch.com/zz_en/internettime/
You do realise that what is legal tender in a country can change right? He's dreaming about the day the United States, or whatever country patio lives in, changes its legal tender to be bitcoin.

(btw: More logical than changing the tender of dollars to bitcoin would be to tie the value of the dollar to a fixed amount of bitcoin. Which would be the same thing but without losing the word 'dollar'.)
> I admire the Japanese honor though..

Hahah you're that guy at work, huh?
We have 2700 machines using a single Salt master.

You have to tune it or you have the "thundering herd" problem. There are two parameters if I recall:

* a delay between master queries.

* randomization of when to check with the master.

You have to get pretty liberal with these values to scale out, but I assure you, it does work.
Good question! Click here to find out. http://ttly.me/eB3Ca
timestamp 0:07 - s/facilty/faculty/
>and we also quickly figure out why you'd have to be stoned on bud to think that's a deep thought.

That's only because most people are like sheep, capable of only thinking of their immediate practical problems.

Far from being just a "stoner discussion", the perception (of color etc) question has been examined in length, both in philosophy and cognitive science, and is as deep as they go indeed.
I've tried this solution myself, but I find the later copy them to a folder on PC never happens. The receipts build up and when i do remember, i'm not at my pc.

When i am at my pc, i forget to copy them from my phone.

I wanted something more instant
How come people with papers on machine learning are doing internships? Is this absolutely necessary before landing a job?
I agree--I am very impressed by your splash page (both design and copy) but I feel like it wasn't consistent with what you get once you sign up. For me, I was expecting something similar to Brian Eno's "Oblique Strategies" from the description (i.e. more vague, abstract suggestions), but it turned out to be more like Random Wikipedia.
Two things I'd like to see from youtube:

1. Frame-rate awareness. Displays that can operate at different native refresh rates matching sources such as film and video are becoming more common. Providing support enabling displays to use the appropriate refresh rate has the potential to eliminate stuttering (that some people are very sensitive to) in properly authored content.

2. Reign in the annotations! Youtube's annotation system is being horrifically abused and is directly responsible for the "spammy" feel many clips have. Turning off annotations in your youtube settings is one of the single most impactful ways of improving your experience. This is unfortunate, since small, non-intrusive, tasteful annotations can enhance the experience for users. Just as ad providers are struggling against ad-blocking software because they didn't exercise taste and restraint in the past, so too are annotations in danger of being turned off and ignored by most.
germany is still unmetered and the last attempt of Deutsche Telekom to introduce a cap resulted in a huge backslash. For now we are save, but i have the feeling it won't last forever.
A company like Silent Circle/Blackphone could buy a million or two in the future. Maybe some Raspberry Pi competitors, too.
Main author of Quasar here. The big question is what do "the majority of applications" tell us? A lot of applications run on virtualized hardware, which basically runs a few Pentiums on a single i7 box. So "the majority of applications" don't really need more than a Pentium. But is that really by choice? Or is that simply because modern hardware is so much harder to fully exploit, so we just don't bother and lower expectations? I think it is the latter. If we make it easier to fully take advantage of modern hardware (its processor and memory architecture, its IO/processing latency ratio etc.) then all of a sudden you'll see how most applications actually need every inch of performance they can get their hands on.
If you didn't see it last week, the "A Buddhist monk confronts Japan’s suicide culture" post from last week is a really great read. [1] There's a portion in the article where it speaks to different cultural norms around suicide.

"By [Japanese] tradition, suicide can absolve guilt and cancel debt, can restore honor and prove loyalty. 'The heirs of Cain can never escape the eyes of God, even less in the next world than in this,' Maurice Pinguet wrote in his study 'Voluntary Death in Japan.' 'But in Japan you can hide in death, disappear into it entirely and mend the fault as you go' In Japan, suicide can be a gesture of moral integrity and freedom, or an act of beauty."

[1]: http://www.newyorker.com/magazine/2013/06/24/last-call-3
I don't find this response convincing...

First, in the intro, it sets up a straw man argument -- that a ORM won't fix your remarkably crappy db or object design. No one expects magic, and I don't see how it's relevant. However, sometimes people are given remarkably crappy designs that they have to support, and ORMs make it much more difficult. ORMs are much better when you can start your db from scratch, but not so good when you have an inconsistent or legacy system.

I agree with him about the dual schema dangers, though (ie, Objects -> tables or tables -> Objects doesn't really matter once you have a good abstract entity model worked out. It's sometimes tough to work one out, though, and I tend to do it in the DB first)

Transactions in an ORM have been a huge problem, so I pretty much do as much as possible in the db through stored procedures, combined with whatever application code necessary to verify everything is moving along as it should.

It seems to me that most developers should learn SQL and databases fairly well. They are just so common, and it's not all that much trouble. Once you know how to normalize data and some basic SQL you're well along the way.

ORMs have their place in relatively simple projects, but once code passes a certain level of complexity then ORMs cause much more pain than they are worth. It's a classic leaky abstraction -- you end up spending too much time fighting with the ORM. Debugging SQL through an ORM can be a nightmare, too.
>Interesting article, but a bit far fetched. You can sync your clocks to GMT, nothing stopping you do that. But I doubt you will convince anyone else to.

I don't think it was about "convincing". It was about it happening by decree. You know, just like how the timezones we use were enforced in the first place, or Gregorian calendar, or any other regular time keeping...
There was also some concern that the "automatic liquidity provider" feature of Ripple was dangerous, but it sounds like Stellar may disable that.
This is my daily driver: http://www.amazon.com/Casio-Mens-CA53W-Calculator-Watch/dp/B...
no OCR. It's a feature i considered but then wasn't sure how useful it'd be.
Most of the time i just need to recall my receipts and hand them to my accountant.
And there are apps that do OCR better. Didn't want to get stuck into the OCR sucks problem.
I've used this in the past. Good, well-written library. The stdlib datetime/time modules are such a PITA sometimes.
I noticed they are A/B testing their website, when I switched IP addresses, so you might not see clipart:

https://i.imgur.com/aghESl7.png

https://imgur.com/nDO0STG.png
Salt's REAT protocol uses the CurveCP crypto library, so yes, this is being addressed.
It's a slow system with a lot of flaws, but ultimately if Congress were to pass a law saying who the FBI could or could not use a 0-day against, they'd be legally bound to comply. Ditto for presidential directives. If you're arrested as a result evidence acquired through use of a 0-day, you can make an argument in court if you really think you have a compelling case.

There's a whole lot of little details that make these easier or harder under certain circumstances, but none of these are impossible, especially if you have popular support for your cause.

If you don't like the way something works, you can talk to your congressmen, vote, support organizations that promote your cause, etc. Just complaining on the internet won't change much.
Web components in ~20 lines of code
Do you have any savings? Are you married or otherwise unable to move? There are many countries in the world where you can live comfortably for $1000/month (or even less).

That will give you a few years of time to do anything, web apps or something. Maybe one will turn out to be profitable. Or you could just try to do part-time remote work to cover living expenses.
They should not break into systems within country B. That's an act of war.
That seems highly unlikely - unless we're talking about 3rd generation behind the latest tech chips. I could see them open source say the ARMv6 architecture in 3+ years, when ARMv8 has already taken off, and ARMv7 is in legacy mode. But meh.
Google Glass Healthcare Startup Completes Successful Equity Crowdfunding
Timezones in computing are an annoyance to solve properly, once, and then always use that code.

Use a library of timezones maintained by someone else (in the OS, the VM, or similar), because these need to include the history of timezone changes to be complete, and countries continue to change their timezones, daylight savings rules, etc.. I'd dearly appreciate it if everyone got rid of daylight savings time, but it's abstracted away for almost all applications now.

For most purposes, you can store all times in UTC in the database, and let people choose the timezone they want to use for data entry and display. Sometimes you also need to store the "local time" -- e.g., imagine you'll need to generate reports on some stat between 9am and 10am local time, for locations in many timezones -- but always store UTC first.

Building the dropdown list people will use to choose their timezone is probably the most annoying part of it. It's hard to come with something that's complete without having terrible usability.
The async-everywhere trend might be a fad (though I think it was emerging before Node and that Node is a response to rather than the source of the trend), but async itself clearly is not.
The trick is to shop around for the most loathsome defendants you can find until you get a precedent established, then you can expand the technique's use more broadly.
I don't think you need to consider how the loans were offered at all, the legal system should just not enforce debt collection of basic income.
It is interesting that the paper does not actually cite the original paper. I guess it is not critical to the paper, but it does complete the story.

This does bring up a important point in that is old scientific publications in languages other than english. I have many times run into references in German, French or Russian that are only available as low quality scanned pdfs. As a monolingual English speaker these are completely inaccessible to me. I would be great to have all of them OCRed so at least we can run them through Google Translate.
How many nodes do you manage? I've heard of Chef scaling horror stories.
I get that email pretty much every month now, nice thing about Cox is they don't do anything if they have to send it out. It's really just a notification.