skysight-inc/HackerNews huggingface dataset:
The bad idea is taking a threaded language and retrofitting events, which Python is doing. This results in an even worse mess. Python now has two kinds of blocking, one for threads and one for events. If an async event blocks on a thread lock, the program stalls.

Or taking a event-driven language and retrofitting concurrency, which Javascript is doing. That results in something that looks like intercommunicating processes with message passing. That's fine, but has scaling problems, because there's so much per-process state.

Languages which started with support for both threads and events, such as Go, do this better. If a goroutine, which is mostly an event construct, blocks on a mutex, the underlying thread gets redispatched. There's only one kind of blocking.
Just because the API is bad doesn't mean we should throw money at it. I agree that NumPy might not be the best recipient either. It's hard telling, really.

Personally, I believe the biggest blocker for me is to have good visualization tools. That's ultimately what gets me paid is showing other people my work and getting them to give me money to continue it.

On the core science stack IMO there's numpy, scipy, sympy, matplotlib, pandas and xarray. I probably use it next to least, but I really think sympy is the one that could benefit the most from some funding.
What is that NPV that thay are talking about? When I look at http://www.investopedia.com... (or https://en.wikipedia.org/wiki/Net_present_value ) I see following formula:
NPV = sum { C/(1+r)^t } - C0 - where C is future cash inflow and r is discount rate. If r goes to 0 NPV = sum (C) - C0 - that is far from infinity.
I believe with will need way less people than in the past due to automation and robots.
Regarding weather, places that have clouds due to convection have a chance of clearing up during the eclipse. I experienced this in China in 2009 - completely overcast two hours before totality, clearing up just in time due to lower solar insolation and less convection.

You shouldn't count on this, try positioning for good weather in advance regardless, but just keep it in mind so you don't crash your car heading for better weather if things look poor.
A promise from the government to pay you something in 30 years is inherently a promise to take the resources from your children, because there is nowhere else for it to come from. It doesn't help anything to have the government hold its own bonds; then your children inherit the debt instead of the unfunded program. It's the same number of dollars no matter what you call it.

And you don't want governments holding other investment assets because the government choosing what to invest the money in would be the world's strongest corruption magnet.

> Rather than reducing high borrowing levels, policy makers use financial engineering, such as quantitative easing and ultra-low or negative interest rates, to maintain them, hoping that a return to growth and just the right amount of inflation will lead to a recovery and allow the debt to be reduced.

This is a misapprehension of the relationship between debt and inflation. Inflation is how you reduce the real value of the debt. It's effectively a tax on dollars, and it reduces the debt on both ends: If the government creates new money then it can spend that instead of borrowed money, and if the value of the dollar goes down then the value of each outstanding dollar of debt goes down.

But none of that changes the problem with retirement benefits because, again, the government holding its own bonds is self-canceling. The only thing inflation might "help" there is to allow a reduction in real (inflation-adjusted) retirement payments without a nominal cut.

If you want the same real benefits then you need to collect that number of real tax dollars, and if you won't or can't collect that number of tax dollars then you have to pay lower benefits.
This analysis is incorrect. SQLite must allocate database pages for rows just like the kernel must allocate filesystem blocks for files. Reading a row in SQLite means traversing a B-tree to find the row. Reading a file from the filesystem means traversing a B-tree to find the file metadata. Very similar. The kernel doesn't need to "seek" any more than SQLite does, the article says that all the hard drives are SSDs which don't have heads so they don't seek.

The major differences here are due to the different levels of isolation and authentication that the kernel and SQLite provide. Another difference is the fact that when you find a row in SQLite by primary key, you don't have to do a second lookup to get the data from the metadata. This is a good optimization to use when storing many small pieces of data, but a bad optimization for large pieces of data.
Storing many small files into few (compressed) bundle files is common since at least the 90's for storing game assets, but usually not with SQLite, but some sort of compressed format (simple zip archives are quite common but there are faster alternatives now). The bundling gives you better overall compression, and faster read performance compared to individual files (at least on Windows) as long as you open the file only once, and from then on only seek and read.

SQLite is a big code base, using a simple archive file format instead gives you most of the advantages, but without the bloat.

PS: This is mostly for read-only situations though. Using SQLite probably starts to make sense when the applications needs to write to and create new files in the archive.
Uber Embraces Major Reforms as Travis Kalanick, the C.E.O., Steps Away
All of these are not "nice", and are outdated. Murmur is too big, cityhash was replaced by farmhash, xxhash is good for digests, but not for strings.
How is that possible? Are these images so obvious as 2+2=4? Legitimate question, I am layman in this area.
JavaScript’s Magical Tips Every Developer Should Remember
Data exploration using widgets in Matplotlib
Street wars 2035
We already have mechanisms to control debt accumulation: raise interest rates if we want to borrow more and lower interest rates if we want to borrow less. Interest rates have been rock bottom, negative if inflation is considered, and the US government has been practically paid to borrow via Treasuries.

> Debt shouldn't be larger than a significant portion of the economy.

Are you referring to just public debt? It really depends again on saving needs. It really isn't that simple. Debt in itself isn't bad, default on debt is bad. If you had to choose between debt and a depression, unless you are Hoover, you will choose debt.
Never mind any paradigms or anything, I believe a lot of the popularity of Redux boiled down to two things:

1. It was there at the right time, when people started getting serious with React and were looking for a way to structure their data flow.

2. Tooling. Soon after it was released, the author demonstrated a pretty neat hot-reloading utility.

So no matter whether you're really into functional purity or are reminded of Win32 event loops, it was a practical solution.
Yes, and it was repealed in the 1990s. That's why we had the 2008 crash. The basic idea of Glass-Stegall was that stock market crashes wouldn't affect banks. This worked well for half a century. Then came "deregulation". With the coming repeal of Sarbanes-Oxley, expect a big crash in a few years.
But that would work only for static content, like the game assets. The discussion of BLOBs vs. filesystem comes up mostly in the context of content management and user/app uploaded content.
Rapid Mobile App Development Tools for Mobile App Development
Rapid mobile app development tools have emerged as one of the most specific methods of creating enterprise apps. The development time with these tools decreases exceptionally.
So what's the difference?

Distribution.

Screen readers apply their transform to source content. By becoming that source (regardless of transform) you are distributing it with control of all the benefits involved, such as community, traffic, and ultimately revenue.
In some jurisdictions, pension guarantees have constitutional protections that may not be erasable by simply passing a bill [1]. While an amendment to the constitution (the CA state constitution, in the case cited) at issue would fix this problem, getting such an amendment passed would not be easy — at least not while many pension recipients are still alive and voting. Senior citizens generally turn out to vote more than other groups, and when their pensions are at risk you can bet they'll show up in force.

1: http://reason.com/blog/2016/11/30/california-supreme-court-w...
I understand the GPL, but I personally prefer BSD/MIT and I am disappointed when I come across things I like in the GPL. IMO the GPL is not really 'free'.

On the other hand, the GPL wouldn't make a difference here unless they are actually distributing it and my understanding of LGPL means that they could do whatever they wanted to as long as they use NumPy and don't change it.
I didn't mean propaganda, there are more cases of people being very ill until they get home. I think it allows both parties to save face or can be a cover for something else ($$$)
I think for beginners (in webdesign) there are some very simple rules to start with:

* Only use one font to start with
* Only choose 3 colors max
* Only choose 3 font sizes max
* Only choose 3 margin sizes max
* Align everything
* Make sure text has contrast with the background

Those limits help you to create a connected design.

After that you can start changing colors, changing margins and sizes, until you think it looks very nice. But don't start adding colors and margins and font and sizes because as a beginner that is very hard to handle.
Hence a reason why so many people are sticking to ML despite the lack of social momentum.
Rust still allows imperative programming whereas Haskell doesn't. This makes a big difference.

Rust is closer to Alan Turing than it is to Alonzo Church.
> Note that the article makes a crucial assumption: That all those unfounded future liabilities (most of which are pensions etc. I assume) of governments are fixed and cannot be changed. This isn't true, though: By changing the law, those unfounded liabilities can be erased at the stroke of a pen.

Easier: default on the debt made by previous generations. No law required.

If only one country defaults it's going to be hard for them, because the future lack of trust and the inevitable retaliations. If a large enough number of countries default, it's different.

The problem is that if they default and start borrowing money again then it will be in vain. Some debt is inevitable (think mortgage to buy a house) but debt for everything is too much despite being convenient: get the money now instead of with next year's taxes and possibly get as much money as the larger country next door (a competitive advantage but be wary of interest rates.)
Hi maxmonlt, can you email me at ashermon@caremessage.org please? I'll take a look.
Nobody expected a Windows release to completely trash hardware driver backward compatibility the way Vista did.

The fact that people are trapped on XP is Microsoft's fault. Because some manager in Microsoft decided that getting the upgrade numbers up by breaking hardware drivers was a good idea, you have a security nightmare decades on.
Exactly. For me, Haskell was a gateway to Nim. I wanted something that feels familiar, but with a strong type system and native speed.

I wish I could invest some time in working with Nim. It doesn't get as much attention as it deserves in my opinion, and it would really benefit from growing the community a bit.
I'm on vacation in the middle of Austria with spotty Internet access, so you'll all have to take what you can get. :)
"at some point people will find out that the pensions they have been promised won't be there when they reach retirement."

One might argue this has already happened in the US, just subtly. Inflation (mostly ZIRP driven) has been very high, and is a hidden tax on those with fixed incomes. Perhaps headline inflation indicators are not high, but just look at the largest component of spending (rent) and you realize how difficult it must be to live on fixed pension payments. As a double whammy, seniors who tediously saved money hoping to earn interest income in their later years, find that income yield is near zero. This doesn't even consider the other major component of spending (healthcare)...
I think it was only changed somewhat recently.

Also some apps load their own emoji, like Facebook and Twitter, so iOS users may be used to seeing/using the normal gun emoji in those apps.
I read an interesting comment thread on a Seattle-oriented forum the other day: It was a thread about some landlord something or other--the topic isn't all that important, just that it brought up the classic landlord-versus-tenant debate--and someone made the comment that a sizable contingent of landlords in Seattle are one- or two-unit (usually standalone house or townhouse, but sometimes condominium or duplex) owners renting out places where the landlord previously lived. The point was that tenants should be more predisposed to give "landlords" as a group a break because many landlords aren't corporate real estate trusts.

A person replied to take issue with that statement and made a what I thought was a good point. He or she pointed out that all of those houses that are being owned by a small-time landlord and subsequently leased out are houses that are out of the pool of available properties for people to own and, possibly, redevelop into more dense or different housing styles. Ownership and renting in this way contributes to the upward spiral of housing prices: a person has owned a house in an area for a while and then moves out. Instead of selling, that person rents out the house while, in all probability, having purchased another house in the same area. As the first house's mortgage is paid down by outside rent, the small-time landlord has even less incentive to sell because, hey, "free"[0] money. Lather, rinse, repeat for an entire metro area and it's just as good a contributor to tight owned housing availability as the specter of foreign investors swooping in or people moving from other regions of the United States. And it reduces the pool of houses that could be used for someone to buy[1] into a market.

0 - I know that being a landlord incurs costs and that not all landlords, especially small landlords, make money on the deal but many obviously do because to do otherwise would be financially foolish.

1 - There's a really good argument to be had about whether or not ownership of one's residence is a good thing for society at large. I happen to think that yes, it is, but that the pool of "culturally acceptable residences" must be expanded beyond "detached house with fenced yard, large driveway, and bountiful on-street parking directly in front of the structure." Point being, people want to have stability in where they live and there's a wide gulf between "5,000 square foot minimum lot size" and "downtown condominium high-rise" that is not being served in many metropolitan areas.
I wonder if Idris could some day take Haskell's place. It sports default eager evaluation. Seems like the tooling (package managers etc.) isn't quite there yet, though.
Literally the same version of Firefox as underpins Tor Browser will tend, pretty much at all times, to be safer than Tor Browser. You can use the search bar at the bottom of the page to find out why, or search the Internet for "grugq tor browser" if you want more people explaining the issue.
Object-Oriented Java Primitives, 0.5 released
Yes you are right. I wrote the 'PS' before I saw your comment. Apologies :)
Worm Grows 2 Heads in Space, Surprising Scientists
The problem is intrinsic to what Tor is trying to do; it's not simply a bad engineering decision on the project's part.
Scale API (S16) Is Hiring Front End, and ML Engineers
Put your money into a full reserve bank, there quite a few around. I have an account with one of such. It also makes sense to open a "metal account" in some offshore bank abroad (remember, US was prohibiting its citizens from buying gold less than 50 years ago)
A centralized payment system will never be able to provide the best service for users. With a single entity in control -- as opposed to an open system where newcomers can enter and compete with incumbents -- there are no competitors, and competitors are responsible for pushing down fees and adding innovation, thus forcing incumbents to follow along or fade away. That's why the web is so successful: competition is built in through an open protocol, so competitors can replace incumbents by providing a better service/price.

With the iPod and iTunes, and the iPhone and the App Store, Apple created something that didn't exist before, and captured most of the newly created market. Replicating VISA's business model doesn't do the same, but simply adds a couple of features to an otherwise closed system where users will not benefit from competition.

An actual alternative to VISA needs to be open, allowing for competitors to easily enter and compete with existing actors. Such a system is the Stroem protocol on top of Bitcoin, which is a thin clearing protocol designed for competition, constantly forcing issuers to follow along on price or be left behind. This is what merchants want, and what's needed to revolutionize payments.
Edit (first line); actually maybe it's my definition of 'thread' that is different. I think of a process as a security context that has one or more CPU routines (complete set of state). Goroutines are not threads in that sense, they lack that CPU state and are just segments of code (logic and data-state).

Goroutines are 'soft threads'. The underlying implementation typically defaults to number of CPU cores as max possible REAL thread count. The real threads will check the message queues for possible wakeups when the previous soft thread blocks or terminates.
There is something I don't get about the databases distributed : they are read/write, and their data is not part of what is distributed in p2p, is that right? It seems to be what means "Block payloads are SQLite database files. Except for special metadata tables, their content is not enforced".

If that's so, what is the purpose of distributing blank sqlite databases (with exception of blockchain keys metadata)? Also, how is it p2p distributed if several users may have the sqlite databases in different state (and thus, different sqlite files)?
Why? They're on a track.
The regret I feel having given away all of my 100 bitcoins at that price point will forever haunt me.
While "GHC is faster than CPython" is a fairly accurate generalization, I still think python performance is easier to reason about. Haskell can give you fast code, but sometimes it will be super slow for no obvious reason.
A blockchain is a distributed ledger, not necessarily public, although bitcoin, being the most famous, is public.

In this implementation it seems anyone can read the blockchain, but writing to it is permissioned/controlled.
Inside the Bold Attempt to Reverse a $55M Digital Heist
A cursory glance at that commenter's recent history shows little evidence of politeness or intention to be polite.

You don't have to like this community but surely you have better things to do than making it worse by trashing it like this?

Also, invoking US politics drama to score points in this discussion topic shows quite a lack of sense of proportion. We are talking about a single person's casually-communicated recollections of their past experiences with a computer operating system. It really isn't worth getting wound up about.
Exactly right. Thank you!
GeoPackage is a great geodata format on sqlite. Also check out spatialite.
5 Kinds of UX Tools for Tech Companies
Show HN: Chrome Extension Read IPA Aloud on Wikipedia
The similarities are striking. Both have a problem with undocumented or experimental modules for everyday tasks, both use compiler plugins to make sure that every package is using its own superset of the language (although in Rust this only applies to nightly), both tout lofty goals while rarely producing production grade systems. Rust is the first toe dip into the world of blog posts heralding the"coming of the age of reason" when we all see the error of our ways for writing dangling pointer references and impure functions. To be a complete cynic, I hope Rust runs right away from over generalized abstractions and the Haskell indifference to achieving real success by overcomplicting even the most mundane of problems.
Can the mankind entrust the future to programmers?
You can understand why I'm not eager to wade into this particular discussion on HN --- it has nothing to do with your comments!

But yes: we do strongly recommend iPhones.
Very smart idea. I use RecUp (was DropVox) a ton - mostly to capture nice moments or sounds (not meetings). I record speculatively - I think/hope nice audio is coming, so I press record. Sometimes I'm right, often I'm wrong. When I listen later it often takes a few listens to recall what I was trying to record. Looking forward to trying this.
Its difficult to have conditions that have Millennials both supporting aging Boomers and raising their own children. Not without lowering standards of living and care for one of the three groups.
This is a very overstated concern, in my opinion. Based on my experience, once you learn the common gotchas (lazy folds, WHNF, etc.) it's rarely an issue. Real-world programs (web servers, databases, etc.) typically end up using frameworks that deal with strictness concerns for you anyway. For maybe the first couple weeks I was learning Haskell, this was a source of confusion, but I don't seem to run into it anymore.

If it's really a struggle for some reason, you can always take the nuclear option and enable strict mode on your code.

Haskell is very good for writing extremely fast code that's also extremely composable, which most languages (even Rust, to a substantial degree) really struggle with. Haskell's pure non-strict semantics and support for fusion/rewrite systems means that you can write complex operations on vectors, byte arrays, text, etc. that span multiple modules but get compiled down to extremely tight in-place assembly code. Another way of looking at it is that the economies of scale for Haskell are very different. There's a higher up-front cost because you have to learn about how strictness works, but as a consequence you can write vastly more complicated programs that are, say, 80% as fast as hand-optimized C for only 10% of the effort of hand-optimized C.
Kalanick got screwed
Thanks, this is a good summary.
2016 article:

http://www.oregonlive.com/travel/index.ssf/2016/08/7_things_...

Hotels across Oregon are already booked solid. Court Priday, manager of the Inn at Cross Keys Station in Madras, said rooms have been gone for a long, long time. "We've been getting phone calls like crazy," he said. "We've been sold out for about three years."
Can somebody explain why this is interesting computationally-wise? It looks like standard derivation to me.
Vanilla SPilla “Self MAde Man,” Numerology Facts, WW3
But flying drones is illegal in India.
> and many states exempt huge swaths of goods (such as groceries) and some have no sales tax at all.

Groceries are exempt from GST/PST or HST in Canada as well.
> A promise from the government to pay you something in 30 years is inherently a promise to take the resources from your children, because there is nowhere else for it to come from.

Not a big deal: those people helped their parents, their children will help them. It's fair and it's what happened for tens of thousand of years: people knew they must have children because without children they'll be pretty much without any support when old. However it works when the number of children is substantial. It can't work with 2 or 1 children per couple and that's where most of the western world is now.