skysight-inc/HackerNews huggingface dataset:
> the Pokemon aren't only catchable by one person in a given location.

Oh.. Didn't know that..

> Secondly, if our universe is a simulation, do you really own the land you claim to?

We have to go back to the root of what ownership is.

The way I see it ownership of land evolved somehow like this: During stone ages or somewhere along that time, a group of humans decided that anything that grows or walks around that land was theirs to claim. Hence if another group of people tried to catch or collect something on that land they would start a fight. In essence this means that ownership of the land => ownership of the resources on the land.

Back to the Pokemon, and again I thought that only one person could catch the Pokemon that spawn in a location. A Pokemon is a resource that is only available on a specific
location, even if it needs a smartphone to see it and catch it. Assuming that this resource has some value, how is it different than a buffalo that lives in a specific location. It too needs tools to catch it.

Therefore I cannot see why I cannot claim ownership on a Pokemon that spawned in my land, the same way I claim ownership on a tree that grew in my land.

Edit: BTW, just making very lighthearted discussion.
The power of ynab isn't the tool, but the philosophy. The UI works well because it changes how you think of your budget. I'm a little disappointed the author didn't comment on how ledger compares with the budgeting side, as tracking expenses is only half (or less) of the battle. I'd recommend ynab because it forces you to plan instead of react. I think as far as software goes, that's the fundamental advantage- you think differently. It's kind of like how editing in vim you start to think in terms of verb-object.

I'm stuck on ynab4 for as long as possible, but you can try out the nYNAB (the SaaS offering) for free for a little more than a month. If you get it, be sure to watch the instructional videos.
The C Based GRPC (C++, Node.js, Python, Ruby, Objective-C, PHP, C#)
> C++ is hard enough to get right without exceptions

In what manner? If you use exceptions, you must (IMO) use RAII, or yes, it will be painful. Every example of "painful C++" I've seen involved someone ignoring that, and that is fighting the language. I understand that's a bit of a strawman argument, but you didn't elaborate enough in your post to debate it.

If you are using RAII, exceptions shouldn't be terribly hard to "get right"; an exception propagating up the stack will free resources as it goes. (This is the same behavior, again, as numerous other languages; except in C++, I have the benefit of RAII, in others, I generally do not.)

> dealing with failure in bodies of code that you didn't write and maybe don't have control over (or even source code of) is death on wheels.

It's peculiar that I only ever hear this argument against C++, when Python, C#, and to an extent Java¹ work in the same manner. Were you writing a C++ webserver, for example, I expect that you would do exactly what my current job's Python webserver does: if an uncaught exception makes it to the main request handler, it is caught in a catch-all, duly logged, and a 500 served in response. This is appropriate both in Python and C++ IMO. (Whereas in the hypothetical C++ side, I gain the benefits of static typing and RAII that I can never have in Python.)

In my day-to-day Python, we quite often learn about uncaught exceptions — from third-party code that I didn't write and maybe don't have control over — in production; sometimes, we will add a handler for that particular exception where appropriate (it was a bug) or fix the underlying symptom (the exception indicates a larger problem, and allowing it to propagate to a good catch-all point was appropriate, as was 500'ing the request).

But again, "death on wheels" is not really something I can provide worthwhile argument against. Perhaps where third-party code has caused pain (at least, for me) is when a very low level (say, socket error) propagates through the stack; there might not be a good way to catch these beyond "catch everything", but again, that's not unique to C++. The biggest problem I've had with these is that they lack context: what caused this socket error? Or, if some library catches & re-throws its own exception class, too often do they discard the inner error, and I lack the root cause (a different lack of context). But you see this in Python as well. Error codes are perhaps the worst, as they will quite often force you to lose context; do you expose error codes for all of your inner error conditions? (And theirs, transitively?). (I've never seen a non-exception C++ or a C codebase use anything aside from error codes as a substitute.)
If I had a daughter (which I do) who was conceived while using birth control (which she was), I would not refer to her as an "accident". While technically correct, the word carries too much unintended meaning in the ears of the listener.
Ways to prevent sharing economy fraud
Young people in developed nations are the next wave to get hammered by globalization. The capital markets aggressive search for efficiency will leave no developed world worker unscathed until they are all at parity with developing nations. But if it's any consolation they aren't the only ones. The only difference is that most of the baby boomers made it into the asset class before globalization was in full swing.
I remember reading about Flipkart when they turned off their website. At the time I thought that was a potential terrible sign of things to come (moving to walled garden mobile apps instead of URLs and websites).

Thankfully, hardly anyone of consequence followed suit and the move was widely seen as a disaster.
> If you know Asm you'll be far better at C; things like pointers and indirection immediately make sense.

A lot of recent issues with compilers "introducing security issues" has come from this sort of understanding of C (overflows, other undefined behavior, etc). The places where C differs from just writing the assembly yourself are really really hard.
I've worked in offices with dogs and it's incredibly distracting (the barking!). Is that really a good idea for a learning environment?

Oh, and I'm also allergic to them, though I'd never dare mention it.
One person who avoided this was Mark Cuban, who bought a bunch of Yahoo! put options when broadcast.com was acquired, hedging himself against the stock crash.
Google generate revenue through advertising, and more of that by locking up the advertising networks and market than through user data.

They also have exceptionally good technical execution on backbone infrastructure. I'm impressed by how good they are, I really am. As well as at not fucking up upgrades to software that runs on top of that.

But their understanding of, and attitudes toward, end users really, really, really stinks. Perhaps not massively worse than the rest of the industry, but certainly no better.
He was from hollywood, right? No "tech" experience? In some ways he was right. A lot of "tech companies" are media companies now. Was he ahead of his time? A poor exec?
That's a really good point - it's very rare for someone else to need to use my web code.
But calling her a "crash" seems worse.
I teach my daughter that there is no such thing as an accident. The word "accident" is one of those words that we as a family refuse to use. Instead we examine the reasons why certain things happen. There is always a root cause that points to premeditated intent or negligence. Understanding this is crucial to having a good grasp of how the world works. Intentionally denying oneself such understanding is voluntary ignorance on a scale that's difficult to imagine and impossible to justify.
> E.g. the long nose stereotype is there for a reason.

Is there actually any science behind that? I'm under the impression that it's not actually possible to identify any ethnic groups based on the stereotypical jew nose.

>The fact that you think cranial capacity is a "looks different" that would affect people's choice of sexual partners is ... odd.

I don't think that. You're asking me if Jews and Poles were different sub-species. Different sub-species must have different patterns of attributes. It doesn't have to be an attribute that people sexually select for, or that can be observed from the outside. I'm asking whether scientists could find such different patterns of attributes. My guess is that the answer is that there wouldn't be anywhere near sufficient differences to warrant considering them a sub-species, but I don't have near enough information to say.
"The language 'accident' doesn't mean nobody is at fault - it just means that the crash wasn't intentional."

That's a fallacious argument.

If a drunk driver gets behind the wheel, they are not intending to crash, but they probably will, and they chose to get drunk and then drive their car - none of that was an 'accident'.

'Crash' describes the situation better without implying cause or intent.
>Its research found that some of the pay squeeze was due to under-35s entering the job market as the recession hit, but it also concluded that generational pay progress had ground to a halt even before the financial crisis struck in 2007/8.

Interesting. I graduated into the worst of the financial crisis (Lehman brothers went under the month after I finished my studies), and I remember reading a lot about the former -- that those graduating into a recession make less in their lifetimes -- but was unaware of the latter part of this statement.
At on of the first "all hands" meeting, she decided to read a children's book. We know what happened: terrible leadership and terrible judgement.
>> We've largely decided that declarative langues (html, xaml) are better for building user interfaces.

On the other hand, many of us decided the exact opposite.

Check the history ?. Declarative UIs has been around for, what 30-40 years, and they don't seem to be actually gaining any share.

They invariably look super-useful and productive when you build "my first app". Typically it is a "ToDo list".

Then you start using it to build something larger and then you swear a lot, and eventually realize that the whole premise is flawed, and then you decide never to use declarative UIs again, ever. lol.
A few years ago I volunteered to be treasurer of a small non-profit. They had been keeping their books on paper. I looked at QuickBooks, and it frankly baffled me. Being an old hand at command line and plain-text computing, I found ledger and immediately loved it. I used the emacs ledger mode to manage the ledger file. I kept the ledger file version controlled in mercurial, so I could easily see diffs between various points in time which was sometimes helpful.

When I turned the books over to the next treasurer, I helped him import into QuickBooks, which he was already familiar with. That's the one shortcoming of the tool, that you are unlikely to find anyone else (e.g. professional accountants) who's willing to work with it.
I think there's a trade-off, millennials will live a life with more public conveniences. Internet, social networks, free games, etc. Not my cup of tea, but as a millennial I think the generational values are generally geared more to life experiences over money.
Old-School PC Copy Protection Schemes (2006)
Surprised this is new/current; in drivers ed in the 80s, our instructor told us "they're collisions, not accidents." Thought this was a common thing for driving instructors to say.
We can already pinpoint at risk children with high accuracy, just check out any inner city ghetto. We just lack the caring needed to do anything about the root cause (e.g. and mostly poverty) that causes kids to go bad later. It isn't a mystery.
And, keeping more on topic, we say "plane crash" not "plane accident" in common speech, and the same makes sense with cars. With airplane crashes, you'll often have the detail given as "controlled flight into terrain". I suggest for autonomous cars that we say "controlled drive into obstacle".

https://en.wikipedia.org/wiki/Controlled_flight_into_terrain

"Accidents where the aircraft is out of control at the time of impact, because of mechanical failure or pilot error, are not considered CFIT (they are known as uncontrolled flight into terrain), nor are accidents resulting from the deliberate action of the person at the controls, such as acts of terrorism or suicide by pilot."

Note that Wikipedia does use the word "accident" - because they are being technically correct.
I don't think that /s is necessary. I think the years have proved that china's trade barrier has worked wonders for home grown businesses. Look at didi chuxing. Blindly aped uber and worth more than them now. On the other hand look at India's own uber competitor: ola. They're struggling almost as much as flipkart while uber thunders ahead.
Yeah, we should've voted for the other guy! What an awful mistake /s
I call her a gift :)
The best part about this library is that it uses HTTP/2.There is big debate that HTTP/2 is not suited non browser scenarios as the protocol does not offer any improvement in that line.

https://http2.github.io/faq/#what-about-non-browser-users-of...
ledger can do budgeting: http://www.ledger-cli.org/3.0/doc/ledger3.html#Budgeting
You can also scrape it off with a blade. Just don't use one you care about, because the metal dulls blades quickly.
What about meaningless comments such as yours with neither information nor speculation? Do they serve a purpose?

I personally like reading comments even if they are speculative, as I am interested but not an expert.
I was thinking DBaaS as well, which is the part that's usually under-emphasized. NoSQL for specific tasks and (sharded if needed) relational with stored procedures for anything complex. When you think of Postgres as its own (heavily optimized) server, it changes the game. For most apps, at that point you just need a passthrough layer exposing endpoints, which is usually a dead simple nodejs app behind a balancer. The rest of the heavy logic is then offloaded to the client. This is why full-stack makes sense now more than ever. It's getting so easy there's almost no excuse anymore.
We do not have lobbying in India. It's called bribing, and I doubt flipkart is doing it. Entrenched companies like reliance/tata are known for that but smaller ones like flipkart cannot take the risk of getting caught.
I can tell you have actual experience here. These are the same things I've heard people I know who have written books say.
I read a lot. I have never read an ebook unless some of the long form stuff that occasionally gets posted here counts. The only things I have to worry about are fire, water damage, mold, and worms. That's not too difficult to control, especially compared to the electronic versions.

Plus, no one can come along and decide to change the title or any of the words later because of some political fashion trend.
Pay for headphones? What airline is that? I've flown on a lot and I've never had to pay for them.

I've always assumed they used the weird connectors to prevent people from taking the headphones with them (since they can't easily be connected to anything except an airline entertainment system)
Strawmen for days!

Just answer me this: Do you believe that the science is purely limited to the scientific method?

Just riddle me that and I'll be content. Just keep in mind that you'll be outing yourself as scientifically illiterate.
This is a small, hypoallergenic dog that I've never once heard bark. She's also very cute. ;)
Airline accidents are still called accidents, but it doesn't stop investigating each and every one to determine the cause and possible corrective action.

http://www.ntsb.gov/investigations/data/pages/aviation_stats...
"Single name domains" as you refer to them usually only work because your DNS search domains are filling the rest in for you. This is why people who work for somecompany.com can simply go to http://intranet , because their DHCP server has somecompany.com in the DNS search domains and the browser/OS will be resolving it to http://intranet.somecompany.com under the hood.
Sure, but you can't just say that in an interview—you have to be more eloquent than that. That's like writing "I want to learn" on college applications. Yeah, that's the main point, but that's not what they want to hear.
As I stated in my original post, these have the same classes of problems as null pointers: you have "constructed" an object whose internal state in invalid; a instance of Foo is either a Foo that init'd successfully or not-a-Foo (that failed to init/isn't initialized; a "zombie object") just as a pointer is either a pointer-to-something or a pointer-to-nothing. This is why you say "it potentially forces some additional complexity around initialized/not-initialized state into the other methods.

At least in C++ (and many other OO languages), I find the downsides of having these Jekyll and Hyde classes outweigh any benefits that may come of ignoring exceptions.
I'm a supporter of a large transportation advocacy group that strongly believes in this shift in terminology. I believe in it personally, too.

Anyone who spends some time observing the news in New York - a city with a fairly low (relative) car ownership rate - would immediately notice how even the most shocking, violent, absurd automobile collisions are not just referred to as "accidents" but referred to as distinct forces of nature apart from their drivers. It's always the machine that did the colliding, the maiming and the killing... there is never any agency or responsibility given to the driver. (It's as if these cars just decided themselves to jump the curb, or race into oncoming traffic!) Flip it to a bicyclist or motorcyclist who caused a collision, and you'll see the language very precisely target the user, not the device.

Sometimes a collision IS just an accident. But not all collisions are accidents.

It's really important that policy and public perception change to dismiss the exceptions in behavior and risk-taking that we assign to most drivers who aren't drunk. If a driver is caught clearly speeding, turning through occupied crosswalks, or coming out of an assigned lane in an uncontrolled fashion, and if the result is (almost predictably) a collision, it must be stated that the driver chose to violate traffic laws & take harmful risks, which is no accident at all. The converse of this is that a driver who doesn't take these risks may get into accidental collisions, but they won't be of the sort where the car ends upside down very far from the roadway in a 25mph speed limit area.
In the case of a car crash, calling it an accident implies it was unpreventable and blameless.
Central Limit Theorem – Interactive Data Visualization Explanation
Why SoftBank Wants ARM (And ARM Needs SoftBank)
Philae, the probe that landed on a comet, used Forth.

https://en.wikipedia.org/wiki/RTX2010

ChipWits was a programming game written in MacFORTH.

https://en.wikipedia.org/wiki/ChipWits
Yes, path segment parameters are a rather interesting (but mostly historical) curiosity.

Recently I have begun using them in a few of my internal APIs, where it is useful to have a distinction between "parameters used to filter a set of items" and "parameters used to request items in a particular format"... an example:

GET /v1/tickets;status=closed;milestone=100?fields=id,title,reporter&sort=-last_updated

Pro: this nicely addresses the problem of collisions between the names of data fields (such as "title") and the names of response-modifying parameters (such as "sort").

Con: consumers of your API get to discover the joys of RFC 3986, because there is essentially zero support for path segment parameters in modern HTTP libraries.
Might want to consider the increasing drain on the economy that the government takes.

http://www.usgovernmentspending.com/spending_chart_1900_2020...

One way or another, it comes out of our pocketses.
These accounting apps never worked for me.
I think I'm missing something, but how do you actually use them?

Do you really put every cent you spend into it?
How is it possible? How do you remember all that. for example, during a weekend trip?

Next step: ok, assume we put every cent spent into the app. How does it help?

Even more: I already have all my transactions listed in my bank's mobile app. How to use it?
Yes I was also going to say I remember this mantra going around a few years ago. And, from what I hear on most radio traffic reports, "crash" is the term most often used.
I'm very in favor of this effort. The language we use has a way of reinforcing our cultural values, sometimes in ways that aren't immediately obvious.
I don't necessarily disagree with the high end. But looking at the CASK it's worth noting that they're almost exclusively long-distance flights. I'd like to see the graph from [0] split into long-haul and others. Currently they've got Emirates flying 10+ hours on the same graph as EasyJet doing 30min in Europe. Same for Quantas which does domestic 1h flights as well as international Dubai, or west coast US but is in one bar only. I know these are normalised per kilometer in theory, but there's a threshold when you need 2x the crew, can't really go without entertainment system, etc.

Or specifically why I didn't say rich is that it's not like you have a lot of choice flying long-haul over middle east. You're likely to get a stop-over in Dubai and if you're flying One World, you're likely to have an Emirates code share.
Anxiety contributes to heart disease which is the most likely cause of death. Anxiety also causes a great deal of suffering for many people. I think your advice about driving is correct, because car accidents are a common cause of death. But most of the things you can decide to have a neurosis about are not such a big risk.
Had an experience that gels with this. Advance of $1k per chapter (I wrote 3 chapters of an 8-10 chapter book) then without the publisher pushing it aggressively, royalties beyond that were minimal. The content did not date too badly so much as the presentation of it did.

Deadlines were brutal, especially incorporating edits and requests to expand/etc. That was a brain-melting experience. Sourcing and providing screenshots was particularly annoying.

Be prepared for it to be tougher than you expect and (as Patrick said) not to earn anything after the advance. Just when you feel like you're done, they'll come back with edits that double your workload.

Before long in my writing experience, I had "THINK ABOUT THE MONEY" taped to the top of my monitor. It was the only way I got through it. Interesting to do it once, but I'm not sure that I'd do it again for a publisher.
Thanks so much for your very detailed explanation! With interop, do you mean FFI?

For R7RS-large, are there plans for a module standard?
Because you are gluttons for punishment?

https://news.ycombinator.com/item?id=12115982
The reason those are investigated is because the airline business has taken all reasonable precautions to prevent them. In that case it is fine to use the word "accident" to describe an event that occurred despite the monumental efforts of the industry.

In the case of cars it doesn't make sense because nobody is putting any kind of organized effort into reducing the mechanized carnage. If car wrecks ever become so rare that we thoroughly investigate each and every one of them, then we can start assuming they are all accidents.