skysight-inc/HackerNews huggingface dataset:
Everyone has a threshold regarding the amount of suffering they are willing to endure rather than dying. Yours (and your grandfather's, per your other comment) may be high, but so isn't everyone else's.

Suicide and euthanasia are valid options in some situations, which are up to each individual to evaluate for themselves.

The doctor in the article has been confronted to the selfish side of love too many times. People want their family members to be kept alive because losing them would make them sad. Somehow more sad than seeing them suffer and slowly die anyways.
There’s a difference between an extra layer of abstraction/indirection and going crazy with the a bunch of new hot (unnecessary/inapplicable) technology.
Good stuff. I was just kidding about the grand version update to commemorate the inclusion. Probably about 100% of females that saw the old blurb will welcome the update.
I think its a hard case to sell that there is no benefit to oral health by flossing. I know for myself, food gets stuck in places that not even brushing and using mouth wash can dislodge. I dont want to be one of those 'i am a corner case and you are wrong people', but I find it doubtful this is unique to me
One thing that confused me in this document is how are the traces insulated from the underlying copper sheet ? I definitely don’t have the EE foundations to see how that isn’t a giant short circuit. Could someone eductate me?
was.

nowadays it's pretty polished, fast and stable.
Experiments to do with your baby (2013)
Applying thermal paste "the correct way" needs some person to do very delicated labor. And also is impossible to do a proper QA.

Now imagine doing this in a factory pipeline. I don't think this would scale.
">Nederlandse Spoorwegen (NS), the Dutch state railway company"

So everyone is also paying slightly higher taxes to pay for it. It is not free, the cost is just obfuscated.

Imagine if they just raised taxes and then made every week book week.
What's the name of this condition?
The article makes it seem way more automated than it is. In that sense this is one of a handful of folks doing this and a really exciting time for avant garde music in my opinion. It's increasingly popular in the industrial music genre.

There's a long history of this arguably starting with Kraftwerk and spanning genres including some of the amazing things bjork has made.

On my constant playlist is author and punisher who is an engineer by day and makes his instruments from scratch:

https://youtu.be/Sdx0vvHxrzQ
How much will Bitcoin have to be worth, and for how long, to make it successful in your eyes? Or is the entire idea of a digital asset with intrinsic value impossible to you?
That was kind of my point..

MCAS should turn off as soon as a single sensor fails, and three sensors are therefore unnecessary. Two sensors are sufficient to detect when a single sensor fails. If you only have two sensors and two fail, then MCAS remains active and your plane crashes. But that's not likely to happen. However that's more likely to happen if you have three sensors and try to use two sensors to vote out a third, in order to keep MCAS active when a sensor fails. In that configuration, a double failure (causing a crash) is three times more likely.

My conclusion is turn off MCAS as soon as even one sensor disagrees with the others. And if that's how MCAS is configured, then three sensors is unnecessary overkill. If you want overkill, you may as well double up the sensors on both sides and have four instead of three; all the better right?
I have a mid 2014 MBP, and I wonder if my machine could benefit from this kind of effort...
Tax compliance is high when counterparty (employer or broker) reports income. Tax compliance on cash transactions is lower.

I don't think stealing books from library at any kind of scale approaching the value of tax evasion is so easy to get away with.
It's a real pity that people don't look at the numbers but talk about these issues as if they were categorical decisions between "either meritocracy or socialism". That's a false dichotomy.

There is wealth inequality and then there is wealth inequality. There is a difference between a society in which the average employer earns 30 times more than the average employee, and a society in which the average employer earns 300 times more than the average employee, or one in which the average employer earns 3000 times more than the average employee. Repeat those statements with median.

There is also a huge difference between a society with a Gini index of 0.28 and one with a Gini index of 0.49. And it makes a huge difference if the index is increasing or decreasing or staying stable.

There are dozens of other factors and indicators that can and should be taken into account. For example, the percentage of income spent on rent is a huge factor. If you spend more and more income on rent, your discretionary salary disappears very fast.

You seem to assume that any kind of wealth and resource distribution is fine, as long as society is just meritocratic, but that's clearly not the case.

Moreover, this cannot just about chances for the talented. You also want to live in a society in which untalented people can live a decent life in dignity, a society in which relative poverty does not lead to widespread social unrest or crime.

If the gap between rich and poor wouldn't continually increase and the trend wasn't further aggravated by existing inheritance laws, there would not even be a need for discussion.
That's a good question. As long as you have additive changes, Prisma can do the change automatically for you. As soon as it's a change where anything will be dropped (field, relationship etc), Prisma will prompt you and ask if you want to perform that breaking change. The only command you need to know for data model changes is `prisma deploy`.
Disclaimer: I work at Prisma.
That's an irrational position. After the Ethiopian Airlines initial report was released pilots were discussing refusing to fly them even for ferry flights (i.e. no passengers).

The Ethiopian airlines crew followed Boeing's post-Lion Air safety bulletin and still crashed. There's no safe way to operate a 737 Max in its current state. The hypothetical recovery techniques (e.g. point nose down to release pressure on the horizontal stabilizer) only work at high altitude, which is notable if Ethiopian airline's AOA sensor was damaged by a bird strike right after take-off.

Nobody who understands the current state of this investigation should be saying they'd be comfortable on a 737 Max without changes. The "pilot training" narrative isn't just dead, but dead, buried, with a tomb stone.

Sure, pilots should have received training on MCAS existing, but MCAS was commanding trim changes that aren't easily recoverable under any circumstances and certainly not if you follow procedure and disable electronic trim. Nobody should fly on the 737 Max until an update completed, I'd go so far as to suggest that the US/EU should ban ferry flights.
My day to day value from typescript is that when you’re on a make things happen team that’s burdened by type pendants or grouchy C#/java/r/whatever “devs” who find themselves career “transitioning” to JavaScript/web-apps throw them typescript as a Turing Tarpit & then everyone shuts up and then makes a thing. Dumb arguments get relegated/channeled into PR/issues on the tsconfig.

I say that half in jest but one of the dumbest & most destructive things in software engineering is tribalism or militant belief systems. Having a “neutral” way to deal with them (or something like “data” seeming like it’s neutral) once and for all does wonders for productivity

People who don’t like or trust typescript, what’s your good-faith case against it. Personal productivity or ugly/confusing syntax are valid reasons I think
No. If the wall is stationary and infinitely massive, you’d bounce off at the same velocity; if it was moving at the same speed as you you’d bounce off at three times the original velocity.

Edit: if the other object is a car, then yes, there is no difference in either case from your perspective.
Posted a link to the actual post a few hours ago... https://news.ycombinator.com/item?id=19596590
When Google first arrived, I’d say the improvement was way more than 20%. Did you experience that?
I'm writing a DDD helper library in Typescript (https://www.npmjs.com/package/@node-ts/ddd), but found it more difficult doing something similar in Javascript. The richness and safety that static typings bring to a project compounds as time goes by.

I've also found it easier for new developers to become productive sooner when the language and framework guides them in the direction they want to go. I'm all for anything that supports a positive developer experience, and it's more concise to express my design in terms of static types than it is through mounds of documentation or exploring the code.
> The ACA, for example, is a great law for entrepreneurial software developers, not so for the lower income small businesses, because of the increased costs. Nothing holding back the working class is caused by plutocrats.

The ACA is what happens when you try to appease plutocrats (specifically in the financial services sector) when dealing with deep problems for non-plutocrats.

> Abstractly, wealthier riders are colluding (via Lyft) to drive down margins of unskilled workers.

The idea that the plutocrats (e.g., VCs) have nothing to do with Lyft is amusing, but not exactly factual.
https://medium.freecodecamp.org/the-top-contributors-to-gith...

On these figures, Amazon is behind other giants and has fewer contributions that a number of midsize tech companies like Red Hat or Pivotal (my employer).
It looks like you started with writing an interpreter in C#, then wrote the compiler in the language itself. Which is a cool concept, I must say. I can't fully wrap my head around the practicalities, though. Do you compile the compiler with an older version of itself during development?

This is called bootstrapping [0] and is common in compiler development.

[0] https://en.wikipedia.org/wiki/Bootstrapping_(compilers)
so now you use even more energy to cool down warmth from using too much energy?
I think it was not the FAA's fault but rather the fault of the shrinking budgets and deregulation in parts that offload the safety checks to the manufacturer. blame congress over the past 20 years or so. the greed of boeing to shoehorn the MCAS into the aging airframe is the issue. they didn't want to have to get a new type rating and wanted to prevent needing to retrain pilots.
Mint 19.1 Mate
The pieces glued down are small pieces of circuit board, not just pieces of copper, so the circuit board substrate is always between the copper layers.
For core services like a proxy, http server etc, I’m kind of glad when larger companies adopt/support a solid service. I think it validates that choice for other companies, and brings attention/bug fixes etc among other things.
This doesn't seem like a common occurrence, judging from all the praise of TypeScript sung on this thread and elsewhere, but I've had an overall negative experience working with TypeScript so far.

Here's some thoughts on what has contributed to that so far:

1. TypeScript pushes you towards its own build pipeline (based on tsc) that doesn't play nicely all the time with mainstream JS build pipelines (usually based on babel).

With babel 7 came @babel/preset-typescript, which I hoped would narrow the gap, but so far it's very clearly a second class citizen in the TypeScript ecosystem, with new features built only with tsc-based pipelines in mind (Project References is the one that stands out because we sorely need it for our monorepo codebase, but can't use because we chose to adopt @babel/preset-typescript), and having personally ran into several issues stemming from what seems to be fundamental incompatibilities between tsc and babel that have no real workarounds (here's one that I can remember off the top of my head: https://github.com/babel/babel/issues/8361).

The reason this is so frustrating is TypeScript could have been just a type checker, like Flow. But instead, it had to introduce it's own compilation tooling which is still vastly inferior to babel in terms of overall flexibility and extensibility. All of this seems to be due to what I believe are a few fundamentally poorly thought-out decisions at the beginning of the project to allow TypeScript to specify its own language features that have runtime semantics (things like Enums and class visibility modifiers, neither of which are anywhere close to becoming standardized in JS-proper, by the way, and both of which are completely orthogonal to TypeScript's main responsibility of type checking), and implementing them using a separate build pipeline instead of as extensions to babel & its own type checker.

If I were to use a JS type system for a new project today, I'd personally choose Flow over TypeScript in a heartbeat because of this.

(this is getting a bit long so will continue in a reply)
So I’ve tried vertical monitors and I find them to be very unergonomic. Your head naturally moves from the top of the monitor to the bottom. What I find this results in is too much head movement and half the time your neck is tilted more than it should be (ie more than is ergonomically safe)

Each year my company's HR department brings in ergonomics experts who watch each employee work, and they make suggestions (This employee needs a new chair... this employee's keyboard is at the wrong angle... this employee sits too low and his feet aren't on the floor right... etc...)

The last time they came through, they voiced no objections to my portrait monitors.
The arguments against two monitor setups or focusing on two different things seems to be completely opinion based. Of course if you're checking your emails then you might want those front and center.

But for me, I work in auditing and I'm constantly looking at two documents at once, comparing documentation I have against my workpapers. And when working out at a client site I cannot stand using one screen, having to switch between documents every 5 seconds, constantly trying to fit two documents side by side on my screen.

My opinion is that two monitors are better than one, but any variation of that is simply personal preference. Side note, I also think that working with ultrawide curved screens distort the image on the screen too much.
They do and that is why they are a contender. Not a user of envoy.
undervolting the CPU (with Intel extreme tuning) can also help without opening up the notebook. unfortunately that's Windows only. not sure what is for macos...
Before, it was HOC and RenderProps. This is just an example with Hooks, it's mostly how i approach the problem though.
I wish the author would have done more to explain the medical terms. Presumably, the audience is not people who know what sarcoidosis is.
Even with the different emission standards, you're allowed to own the vehicle. However, if it does not pass inspection (if the state has inspections) then it won't be legal to drive as it didn't pass inspection. However, you're still allowed to own the car.

(Also, I wish I hadn't been down voted without a response. If I'm wrong, correct me.)
I'm fully in favor of "dividing" Ray Dalio's "pie" in particular. Dude is worth $14.8 billion. If we're at the stage of divvying things up, I want my "fair share". Unfortunately, as it often happens, that's likely not what Ray has in mind. He'd rather pay for his virtue signaling with other people's money.
Correct in the official sense, and it fits the EEE mantra to a T.

As we all know, transposing each initial by 1 from VMS gets you WNT. Rather like the HAL/IBM Space Odyssey factoid.
The UK is also, sadly, a very low bar to compare against wrt public transport.
2% or less is a lot more common in my experience, irregardless of what inflation is.
Thanks for your upright feedback! You must have caught us in a bad moment, in the transition one year ago from Graphcool to Prisma we indeed needed to do a lot of work in the docs.
Nowadays the Google experience should be much better, while our docs actually represent the product.

Would be great if you can give it another try, as I'm convinced that the docs improved significantly over the last year.
Disclaimer: I work at Prisma.
Scammer rents a place normally with a monthly lease, then they rent to someone else while pretending to be the landlord. Scammer collects rent while not paying the landlord and leaves before/when they're caught. A big win is if the scammer gets full payment upfront, usually by leasing short-term to someone who only needs a few months.

Landlord ends up no rent and new renter lost money and has no place to live. If scammer used a fake/stolen identity then it's practically impossible to do anything.
Divvy is simple and works well for my needs.
Search was not a mature industry at all.
Students accused of jamming school's Wi-Fi network to avoid tests
Something can't be an opinion and a lie by definition.

Lying is consciously uttering something you belive to be untrue. It can't be your opinion at the same time.

So unless you're planning to insult the people you are talking to by calling them dishonest, you should cease this way of discussing the topic.

It's obvious you care greatly about this matter and tempers can understandably get heated, but people calling each other liars rarely have productive discussions that leave all parties wiser.
yes, the IRS concluded that "less than 800 people pay taxes on crypto" using a flawed and simplistic search string. I looked at how I reported various gains filed in 2014 and 2015 and it would not have included me in those 800 people.

the best thing about bubbles getting larger is that more people with more personalities and expertise are aware of what these things are. A judge wouldn't rubber stamp a subpoena on such basic and flawed logic, a treasury secretary wouldn't trust their employee with as shoddy an analysis, influential senators wouldn't believe it as their own altcoin trades wouldn't be counted. speculation drives innovation.
Funny to see this as one of the first replies, it's something I've been thinking about lately as well. As long as there is basic collision detection in the model it would be hilarious to see what happens now if you put a couple of them in a proverbial cage. Probably 5-10 years before there's enough fidelity to actually innovate, but there might be enough coming from it to inspire new ideas before then.
I would still do, but you use GPS as a confirmation rather than source of truth.
Aren't VC's subsidizing rides? The fact is, or my guess is, with or without VC's, ride sharing was a technological inevitability.

Edit:
I ignored your point about the ACA, and I think the ACA is the worst of my examples. The health industry is and was previously such a clusterfuck, and there are many "interests" there -- and my impression is (I'd be happy to get slapped down on this), much like education, the industry is full of nonprofits, not plutocrats.
The best thing about US public transit is that it makes UK transit look good by comparison.
The driving force behind this feature do seem to be a couple of Googlers, but at least one person from Mozilla and one from Apple have been involved in the discussion and contributed to the spec changes.
The changes have not been accepted into the spec, however, or even reviewed by W3C-TAG, so it isn't a standard yet.

You can find the full discussion here: https://github.com/whatwg/html/pull/3752
Bandcamp sells good quality FLAC. I've never heard any audible watermarks there.
Well, maybe we're using different terms- as the article notes, there's technically no such thing as a "such-and-such speed impact." I was speaking in terms of how much kinetic energy is liable to go towards damaging the cars involved (or into the fireball of a particle collision); in that case, if you have X energy in two cars, or 2X energy in one and 0 in the other, the sum is the same.

If we consider debris or etc flying away after the collision, then you're right that they're different- the combined velocity of the two cars is 0mph in the both-moving case and 140mph (in some direction) in the one-moving case, and the velocity of all the debris will sum to that velocity. (And the sum of velocities would be weighted appropriately if one of the cars was more massive than the other.)
Maybe because the lifetime of the computer will be shorter, hence, closer to the next sale?
I think it's a great idea. I think you could perhaps reword it to make things a bit less weird sounding though: blocks are created using curly brackets, but correct indentation is enforced by the compiler. Indenting weirdly (e.g. mixing spaces/tabs) will cause a compile error.

Also I can't see how it would affect code sharing at all. I assume it is per-file, so adding entire files won't matter, and if you have a project that wants to steal a bit of code from another in one file, surely you want to convert their indentation to yours - which would be trivial to do given that you enforce correct indentation.

I think it is a good idea. If you ban tabs you'll piss off the sane 50% of programmers, and if you ban spaces you'll piss off the other 50%. Allowing either but with no mixing makes sense.

The only exception I can think of is that some people like to do tabs for indentation and spaces for alignment. Dunno if you could support that easily...
Atypical cystic fibrosis based on the bio
In the US, profit on crypto is straight up capital gains. Held for less than a year = short term capital gains, taxed as regular income. Long term depends state-to-state, but overall taxed less than income (federal has 3 brackets - 0, 15, 20% depending on your income. 500k+ puts you in the 20% bracket)
You say "that's true", and then the rest of your comment has nothing to do with what they said.

The idea that people are advocating for any kind of equalisation that would leave us all poor is a lazy strawman.
Or... stopping at the end of an escalator to figure out where they want to go! This happens way too often at malls, sporting stadiums, airports.
CoffeeScript was born out of frustration with JavaScript’s (then major) shortcomings compared to back-end languages like Ruby and Python.

Try building an app in ES3 JavaScript (i.e. it has to support IE7 with no transpiling) if you haven’t before. It can be rather frustrating if you’re used to modern features.

Prototype.js was the kick that eventually led to the standard library updates in ES5, and (as another post has said) CoffeeScript was the kick that eventually led to language- and syntax-level updates in subsequent versions.
It’s true that every battery has a charge rate curve with temperature. If you go above it dendrites and other chemical junk starts to occur and you lose capacity. But your phone is designed to keep track of this. Fast charging is really about getting as close to that curve as possible. Glass anodes that I mentioned above basically make the chemical damage much less possible/likely. So you could safely charge at 10x current speeds.
I wonder whether you would have such strongly held opinions if you had more experience of medicine, disease, and end of life.
Rust aims for (mostly) memory safely which none of the others do. As a result it is way more complicated and rather different from them.