skysight-inc/HackerNews huggingface dataset:
> though the Russian government has not historically pursued accused hackers.

between a blogger criticizing Putin's regime and a hacker who stole a bunch of millions from an American bank - who do you think the Russian government would go after? :)
A "9-5 job" would become... what? A "most common workday start time to most common workday end time job"?

It'd become the same as in any country which doesn't have that particular expression, that is, probably most of them.

"I was up coding last night until 3am" would have to be something like "I was up coding last night until 6 hours before the next day's standard workday start".

There's no such standard; different countries have different business hours, so to a foreigner "3am" doesn't tell her that it's "6 hours before the next day's standard workday start", and to a local you can just say the actual time, since she would know the new "standard", whatever it'd be.
It is far more impractical to employ live humans to enforce speed limits and jaywalking ordinances in the name of safety. We don't see the solutions that best improve safety because there are many other considerations in play.

As I mentioned before, the urban planners who are adding resistance to the system are not helping the overall efficiency. Intentionally decreasing the capacity of urban infrastructure is almost criminally stupid. It approaches the level of solving an overpopulation problem by conducting a decimation lottery every time the number of people approaches some upper limit.

Some planners are shutting down some roads to increase throughput, by encouraging greater use of more improved roads. Others are altering roads, or installing traffic circles, or adding stop signs and speed bumps, just to make vehicle traffic gratuitously more difficult. Those people are the assholes.

Congestion results from insufficient infrastructure to meet public demand. If your sidewalk is too narrow for the foot traffic, and people get jammed up and spill out onto the street, you cannot solve the problem by making it narrower and throwing caltrops onto it. And that doesn't work with cars on roads, either.
> One use-case that seem to be missing is time deltas.

I just fired up ipython and tried:

>>> t1 = arrow.now()
>>> t2 = arrow.now()
>>> t2-t1
datetime.timedelta(0, 4, 864716)

It appears the difference operator returns a datetime.timedelta object.
Funny, "labor law disaster tourism" could also explain how an American feels visiting Spain, France or Italy right now.

No system is perfect, but let's not pretend labor laws in the EU don't come with massive downsides (unemployment, difficulty to start or grow a business, purchasing power of discretionary income).

Here's a simple rule of thumb for understanding the situation in the US: if you have to be at work at a specific time and get scheduled breaks, you probably get paid overtime. If you're judged on your output and nobody notices when you go get coffee, eat lunch or start in the morning, you probably get paid a consistent salary regardless of exact hours you were in the office.
I agree that external IO most likely would benefit from async. But, we don't need to turn the entire request-response code flow into async style, just because of one async call. We could break it up into 3 parts: sync code, async code (for external IO), sync code again.
Great post and congrats. 2 questions:

1. You're background is in SEO, how much do you attribute SEO to Examine's success thus far?

2. Why do you think it took 2 years to make decent revenue?
i'd rather have collision avoidance and collision generation aversion than "fast, minimal memory"
Same with an auto insurance radio commercial playing a horn, tires screeching, or even a car collision sound, how can that not be illegal.
For some reason, i can't reply on the comment below, so i'm doing it here.

We don't have crappy internet service when it comes to Telenet in terms of speed. The competition (DLS) is not stable on a lot of places.

All of them have caps on the internet and are very expensive when looking at our neighboured countries.

But then again, everything is expensive and everyone has a monopoly here in some sector...

The governement has financial intrest (stocks) in the telecom companies. So that won't change soon.
Why would medicine be unlike any other science? Imagine if the standard model was someone's intellectual property.

Owning abstractions is mind-bogglingly absurd, akin to thoughtcrime.
This could now be accomplished by providing an offset (say number of characters from the start) to where the information cited can be found.

What I find more of an issue is when trying to track down the source of some “fact” is going three or four papers up the citation chain and finding the paper at the end doesn’t actually say what the starting paper claims.
Obviously you would want to design this in such a way that you do not decrease the average support to the poor, and while you would distribute it amongst the entire population, those of us with comfy incomes would have it recovered via taxes, by design.

I would also expect it's possible to design a system that doesn't substantially reduce the income of existing welfare recipients. Most government programs seem to exclude people from other programs and it's a very complicated game to even know how to sign up for things.

In fact, this is why my mother became a social worker, because she found it so difficult to get things like AFDC (replacement child support for families with deadbeat parents) and food stamps, even though we had a lot of advantages over other people who likely needed those things even more than we did.

And sure, those jobs will disappear but in fact the turnover in a lot of these programs is very high, it's very tough to do this type of work for very long, few people spend an entire life working for a social service program, and those who do are often committing fraud - not to say there aren't certainly _some_ who do who work very hard and are honest.
Discussions exhibiting various degrees of in/civility over "hot button" social issues crop up regularly in my online and local tech communities, including HN.

I think the points raised are well worth considering, whether one sides with the author or not, and are more than relevant to HN readership. Otherwise, I would not have made the submission.
Why buffer on the app server?
Lainchan programming board
The article specifically pointed out the government wanted to make the change secretly, so that nobody would ever know it was done:

when it was over, the government secretly, and surprisingly sought permission to “remove” classified information from the transcript, and even indicated that it wanted to do so secretly, so the public could never even know that they had done so.

So if this has ever been done in the past, there is of course no record of it.
None of this post really makes much sense...
I think a very good paper solving this problem very clearly with a cool execution is by Katti Group.

http://web.stanford.edu/~skatti/pubs/sigcomm13-fullduplex.pd...

It deals with all the issue and shows the 2x throughput as well.
"In the spirit of keeping this in good taste, i'll try to phrase this nicely" creates the impression that you would really rather say something nasty, because that would be the correct thing, but instead you don't do this to be 'nice'. Basically, your original sentence, to a 'native' speaker, comes across as the opposite: "TIOBE index is really bad and I'd like to chastise you for bringing it up."

If you truly don't mean to be snarky, a better approach might be: "from what I can tell (implying that you are not certain) the TIOBE index is not a good measure. Here's why I think this is the case:"
The select() loop has been a core part of unix since before many people here were born. That's the basis of async, evented IO—it's hard to call that a fad.

Perhaps the callback mechanism of Node is a fad—continuation based techniques can make async code look like non-async code. Perl's Coro and Ruby's new(ish) fibers are examples of how that could look.
Rust supports both native and green threads, but defaults to native threads.
That's been my experience. From what I can tell the only time ORM tools actually make sense is when you have a lot of tables (or fewer tables with a lot of columns) and your interactions are very simple - i.e. you're mostly dealing with one table at a time.

But this is pretty much an edge case. For simple applications I can write all the SQL in less time than it takes to configure Hibernate, and applications that require me to join seven tables in every query, use analytic functions, or share schemas with other applications, ORM tools don't handle the complexity very well.
I guess the original publication which listed the high iron content of spinach was:

Bunge, G.. 'Weitere Untersuchungen über die Aufnahme des Eisens in den Organismus des Säuglings'. Zeitschrift für Physiologische Chemie, 16 (1892)

http://echo.mpiwg-berlin.mpg.de/ECHOdocuView?url=/permanent/...

If that's true, then indeed, it was not a misplaced decimal point. Instead, Bunge listed the iron contents of dried food.
It would make sense to go after the blogger if you care more about your ideology than some bank's money. I would go after neither of them though.
I can't speak for others, but for me the politics, not the technology, of Ripple was always what I had an issue with.
The government's attempt to change this history was unprecedented. We could find no example of where a court had granted such a remedy

Of course, the very nature of such a change renders it undiscoverable. Who knows how many records have been changed and records of that change been expunged.
It's so easy to overlook something and not realize it is causing issues for users for a very long time.
Using doubles in a hash algorithm seems (to me) very dangerous.

For years I have had problems with different optimisation levels providing different results for floating point code, as different registers have different internal sizes, FP registers can have different internal precision, etc.

Can this hash function be trusted to produce repeatable results?
I'd choose "Door No. 3": neither C# nor stored procedures, but declarative db business rules using appropriate data types, constraints, default values, views, access controls, and triggers.
This is a straw man argument. Async doesn't have to look like node.js' callback hell - that's what go, erlang and several other languages achieve with M:N green threading.
Designing an Exponentiation Operator for JavaScript (ECMAScript 7)
Except people themselves don't like to deal with time zones, which is why they usually leave them out.
> It'd be interesting if we could break down academic papers into stand-alone facts, which could be cited more succinctly than the paragraphs of prose that we do now.

Perhaps there could be some kind of semantic syntax that would group together the factual claim and supporting information (data and references). For example,

<"e=mc^2",cite1,cite2,data1,data2>

The claims still could be included in prose, but also easily extracted, analyzed, manipulated, etc.

With a little work the claims could form a semantic web, with all that entails, and the validity of cites could be checked automatically when the document is opened or on a regular basis, updating the claim appropriately. For example, the UI could display the claim differently based on whether the cited source has been withdrawn, partially invalidated, superseded, confirmed, rarely cited, heavily cited, based on impact factor, if the source's own citations have been invalidated (e.g., claimC cites claimB which cites claimA; if claimA is invalidated, there should be some sort of indication in claimC -- consider that the invalidation of a seminal claimA would set off a massive chain reaction, as it should), etc.

But that all seems obvious and I suspect I'm not the first to think of it.
From the webpage:

> Python’s standard library and some other low-level modules have near-complete date, time and time zone functionality but don’t work very well from a usability perspective:

Why be consistent with something that suffers from usability problems?
Show HN: Orbits.js – WebGL simulation of the solar system using Three.js
Sophisticated highly concurrent systems mitigate many of these problems by taking control of the scheduling order to dynamically optimize behavior. This eliminates quite a bit of coordination and agreement that you see in a lot of concurrent software.

There is some interesting research on game theoretic adaptive schedulers for highly concurrent systems. Basically, if a scheduler in one process can model the behavior of schedulers in all other processes it interacts with, it can dynamically choose an operation with very low or zero probability of conflicting with the decisions made by all the other schedulers. In principle, this leads to all the schedulers getting maximum work done with minimum coordination or conflict.

Some algorithms I built for massively parallel systems work this way. At some level of concurrency, agreement and coordination becomes impractical so you have to come up techniques where the individual processes make choices that ensure they do not step on each other by making assumptions about the processes they interact with.
Historically, ARM really, really did not like unlicensed or open-source ARM processors. But times change, so I wouldn't be surprised to see them take some easy PR from openwashing at some point.
There is no problem to modify UI state from any thread; just put up some synchronizations.

The hard part is, if the modifications do not form a single, predictable, serialized chain, how can the programmer reason about them? This problem is independent of async/sync. If you use C# async for a UI action, you still need to worry about it.
In some code I wrote for a major corporation who will not be named, that's pretty much exactly what was done. We would use a thread pool to spin off a bunch of workers given Future instances to chew on, and then we'd just block waiting for all the results to come back before returning to the client. The thread that handled a request was synchronous to the client, but did all its services requests async and in parallel. Where appropriate we'd also chain things, so one batch of async requests would go out, the results would be gathered and then those results would be used to generate a new batch of async requests, which one again would be gathered and the results used to respond to the client. For those keeping track, this is basically the lazy IO pattern. Not async in the sense of nodejs (which I hate by the way), no callbacks, rather we get a collection of thunks which we can block on evaluating.
Sorry. Not a dorky paranoid liberal type here. Me, i don't see any use for cryptocurrencies outside of darknet contraband trade/money laundering. Any politician excited about cryptocurrencies would probably use them to receive untraceable bribes. The idea that a public company (i'm talking about Mt. Gox) can hold an asset that can magically disappear without a trace and still receive bankruptcy protection from the government (without the ceo being arrested for theft) is a joke.

i admit it's nice from an engineering standpoint and maybe if this imaginary liberal (does that word even mean anything concrete anymore?) utopia some people seem to be living in was true, it would actually be useful to people who don't want to wait 45 minutes at the supermarket checkout for their crypto-monopoly-money transaction to confirm.
http://www.theguardian.com/science/2014/apr/01/stem-cell-sci...

I thought it would be a crazy story about mutations or something. Turns out the scientific misconduct is less "freaky" and more "we falsified the data". RIP to a great scientist though, he was involved very lightly in that case as it seems. I admire the Japanese honor though..
It seems a simple key mod bucket_size works to divide a workload based on a numeric key. I imagine this has a different distribution which works better for certain use cases. Anyone have an example of when mod will fail for something like this?

Edit: The paper covers this.
There are definitely inconveniences with timezones (believe me, I know); but this would be worse.

The political nightmare of convincing the non-British part of the world that "sorry, your day of the week is going to switch in the middle of the afternoon", for example, hasn't even been mentioned yet. Some of those places might not be keen on having their clocks running on British time. To put it mildly.

And honestly, the inconveniences aren't hard to work around. If you work across timezones, you figure it out pretty quickly.

I work on London time, but live in Central European time; I just talk normally in London time when I'm at work. If we're scheduling something in a timezone-disparate group, I always say "2pm London time" and optionally add in "6:30pm Bangalore time" or whatever is needed. It's only daylight savings that gets annoying, because it changes the offsets.

If I've done this bit of simple arithmetic wrongly -- hey, it can happen -- the problem is revealed when I send out meeting requests. Everyone using standard calendar software on their computers (Outlook, Google calendar, whatever) sees the meeting in their local timezone (because of course meeting requests include tz offset info!), so before they actually accept the meeting request, they'll know I've done it wrongly.
People are making volumes of Bitcoin ASICs for surprisingly small amounts of money, so it is possible. The question in my mind is who's going to be buying volume quantities of this chip and why.
Why was taking the team lead position foolish? Were there no benefits to accompany the drawbacks?
IIRC, Java's original threads were N:1 green threads, while the lightweight threads in Haskell discussed above are M:N green threads. N:1 is easier to implement, and fine for single core systems, but doesn't give you real parallelism. M:N, like 1:1 native threading, gives you real parallelism, but also, like N:1, cheap concurrency (at the expense of being the hardest to implement well.)

Multicore processors and the fact that single-threaded performance basically hit a wall explains why an N:1 threading models in something with the use cases of Java fell out of favor. M:N, while still "green threads", has a somewhat different set of trade-offs versus 1:1 native threads than N:1 does, though.
My X varied wildly over time, but definitely has grown since I got married, bought a house, had a family, etc.

I'm not sure what your career is, but that's a real bummer that the 40 hour a week grind is your only choice. Maybe a different career would be a better fit?
China has one time zone [1] and it works.
I don't really see any advantage over timezones though.

[1] http://www.theatlantic.com/china/archive/2013/11/china-only-...
Your mini-Heroku with Dokku and Dokkufy
Not ex-wife. They're only living separately.
lxml's `cssselect` method is nice for this - I found that with `xpath` and `cssselect` I have no need for anything else. I use cssselect for simple queries, like "a.something" - which would be needlessly verbose in XPath - and xpath for more complex ones, for example when I need access to axes or I want to apply some simple transform to the data before processing it in Python. Worked very well for me.
Nothing to see here folks. Let's just keep on with the status quo, I'm sure we can build some epic structures to keep the ocean at bay and protect our coastal cities, keep supply chains moving, etc.

Right?
Which would invalidate most of the reasoning in the article.
Show HN: TrueAccord, an API to recover money people owe you in a friendly way
>Think about doing this check without timezones. 2pm for you is... 2pm for them! How useless to know that. So you'll still need some reference to figure out when they will probably start their workday, when they'll probably break for lunch or go home for dinner, etc.. But how can you refer to those times sensibly without using times? You'll say "oh, so 2pm for YOU is sort of like 2 AM for me, how awful that I called your mobile then". And boom, you've re-invented timezones.

With both schemes you need to know that, say "2am here is like 2pm there".

With the proposed scheme, all the other crap that goes with timezones unnecessarily is removed.

Finding when time X (that you have a meeting or an event happens) is at both places? Instant. Knowing time difference when you are given the time at 2 different places? Instant. Time conversions for commerce etc? Done with. How long a flight will take? Instant. Adjusting your watch after arriving somewhere? Done with.

It's the difference between having to do the conversion only when you need it (e.g to know the relative "phase of the sun" at another place) vs having it to do for trivial stuff that doesn't need it, and complicating things needlessly.

(Not to mention: timezones, because they are irregular, and not equal 24 divisions of earth, do not reflect actual "phase of the sun" at place X. With a constant universal time, we could use equal divisions to find out the difference, which would be even more accurate than knowing 2am Bangalore is X am at some other place).
Very nice, thank you, definitely using this in new code.
If they acquired New Relic and integrated it into the Heroku Dashboard it would give them another edge over normal hosting, but doubt that will happen. New Relic seems to do fine be themself.
I have the idea that AngularJS is requested more and more. I thought it was kind of a "must have" skill.
Awesome job, EFF. You are doing important work.

Curious: we have laws against "attempted murder", are there any laws against "attempted illegal redaction of court proceedings" that can be applied here? My concern is that there is no deterrent to this being attempted again, perhaps in a context that is less visible, and less ably defended, than in this case.
You can do livestreaming on YouTube.
The bad technology is what facilitated the bad politics.

Ripple started out with really nice-sounding politics, but because the tech is centralized, all the nice promises were promptly violated. There is no reason the same won't happen here.
Well, it doesn’t work for me and I am sad.
Now you probably know my falling hair chart and I don’t.
what I meant is whether it's a fad to spread async everywhere inside application code, and call that a good thing. the computer is of course async in nature; but the abstraction on the app layer does not have to be.
a government always goes after the ones who present the most danger to it.
This kind of thing isn't even that rare, if you look historically and even applies to whole days.

The most extreme example was how the Swedish calendar attempted to swap to the Gregorian calendar:

n November 1699, Sweden decided that, rather than adopting the Gregorian calendar outright, it would gradually approach it over a 40-year period. The plan was to skip all leap days in the period 1700 to 1740. Every fourth year, the gap between the Swedish calendar and the Gregorian would reduce by one day, until they finally lined up in 1740. In the meantime, this calendar would not only not be in line with either of the major alternative calendars, but also the differences between them would change every four years.

In accordance with the plan, February 29 was omitted in 1700, but due to the Great Northern War no further reductions were made in the following years.

In January 1711, King Charles XII declared that Sweden would abandon the calendar, which was not in use by any other nation and had not achieved its objective, in favour of a return to the older Julian calendar. An extra day was added to February in the leap year of 1712, thus giving it a unique 30-day length (February 30).

In 1753, one year later than England and its colonies, Sweden introduced the Gregorian calendar, whereby the leap of 11 days was accomplished in one step, with February 17 being followed by March 1.[1]

So February 30 1712(!) is a valid date in Sweden, but February 17 1753 + 1 day = March 1.

Imagine building something like a utility billing system over a time period like that....

[1] http://en.wikipedia.org/wiki/Swedish_calendar#Solar_calendar