skysight-inc/HackerNews huggingface dataset:
I try to understand people, and your despair is loud and clear here. Change is inevitable for sure, man or nature (man is nature, BTW). The sun will devour the inner planets in 4 billion years, but it is burning brighter each year, and in 1 billion years, it will boil off the oceans, coral and all. To the stars if we wish to preserve humankind.

There is a lot of complaining that nothing is being done. There should be some basic steps aside from accepting your problem to begin with, and that is to study some solutions:

#1. Propose and study solutions to match your conclusions of climate change - I don't find too much here compared with the amount of continuing studies on the climate.

And very important to get intellect to act -

#2. Who's going to pay for it, and on whose back falls the labor to implement #1?

Financial illiteracy is the big problem nobody talks about when discussing STEM deficiencies. You may need to build a skyscraper, but if you have 2 guys, 100 bucks and 1 day, you are going to be living in a lean-to, or a makeshift tent at the end of the day, no matter how much you complain or dream. I try and do my best to live minimally, because I prefer it, it makes me feel more peaceful and less distracted, and gives me plenty of time to read and think. I don't preach that all should live my way.
On a more cheerful note, I found a Tweet today about Sweet Meteor of Death, but it was in reaction to people's political apathy or neuroses over the coming U.S. elections. An apocolyptic meteor for POTUS 2016! You should buy the tee shirt and smile!
I have to agree, programmers unionizing would seem a bit… "spoiled" to me. I've never had any issues negotiating or getting underpaid. The bulk of the issues described under this post actually seem to have nothing to do with pay, but rather with high-pressure work environments and simply getting fired (which in the field of programming, comparatively, is not the end of the world—if you're competent that is).
It's a device, so it can feed the information to all the programs on your computer. WebUSB is a way to make it useful from day one, but it's not the sole target.
Boeings 787s and "new cabin" 778 retrofits have this feature. It was touted by AA and United a while back. When i actually flew in one, flight attendants made zero use of it and just went from 100% bright to to regular "lights off, good night" as soon as meal service was done.
The implication for me was that it was odd since he worked in Bellevue at Unity's offices. If it's true that he worked in their Bellevue offices, Seattle is literally a 10-minute drive away.

Your points are definitely fair considerations, but even when I was working long hours at Microsoft's Redmond campus, I was very aware of what Seattle had to offer that I was missing out on.

It seems quite a shame that it took 6 years to discover the place next door. I'm glad he's discovered it now, though.
Interact with data without mouse and keyboard – the future or useless gadget?
So we're limiting based on USB device type are we? What about USB keyboards with USB ports in them (which are fairly common). They could be registered as USB hubs. One of the main reasons USB security is so poor is that the barriers between device types are not strictly enforced, which has led to problems in the past (for example, USB device spoofing is trivial to do, you can probably imagine the sort of hijinks you can get up to with that).
Why not just write in a nice notebook/journal and take photos to upload to Onenote or Evernote?
You're halfway there, because React is the V but there's no MVC. That design pattern isn't common in the ecosystem, and instead a functional, unidirectional design pattern called Flux is a better fit.

Searching for MVC trips a lot of developers up.
Enterprise clients (the ones they care about) are likely making requests from multiple machines, meaning you have to track API usage per token in a database somewhere.
Analyzing the names of almost every Chinese restaurant in the U.S.
Equally as meaningless to every average user. People on HN/github/etc generally just don't understand what it means to be a non-technical user.
Why volatile is hard to specify and implement
Yes I have. It works ok most of the time.
> Estimates are that about half of SF's homeless are on drugs. Others are just broke. Some have skills, but the wrong ones. Printers, longshoremen - SF once had many of those. Not any more. There's no easy answer.

Hahahahahahah

"There’s no easy answer!" I guess arresting people breaking federal drug laws is right out the window.

NOTHING WE CAN DO, GUYS. TEE HEE.
Reinvention is vital for evolution, right?

Is the "success" of id Software an obvious result of open-source acculteration or is it an anomaly? I'd say the latter...
Is it just me or is Comic Sans such an easy target that it seems silly to be elitist about it? It's like if a bunch of film critics kept bringing up how bad Batman and Robin was.
Hmm - having mucked about with a variety of lighting it's only seems mildly effective for reducing jet lag. The article says they are fitting fancy coloured leds that they hope will help, not as far as I can see that they've actually tried it and found it effective. I find melatonin and ambien reduce the jet lag effects about 50% but that's a fair bit more hard core than some LEDs.
Many people have been using two factor authentication for some web pages through SSL, PKCS11 modules and client side certificates on USB cryptokeys or smartcards for ages.

I always find it funny how each new browser and OS release makes it a little more hidden and a bit more convoluted to set it up. All while more and more web developers complain what a big problem secure authentication on the web is.
I think designers tend to overestimate how much the average end user cares about their font choice. If you can avoid using that old English font or any of the ones that look like cursive handwriting, you're doing well enough for 99% of the audience. The world would get along just fine if all we had were Times New Roman, Consolas, Comic Sans, and maybe a "serious" sans serif one.
That talk (which is in written form at http://martin.kleppmann.com/2015/03/04/turning-the-database-... for those who can't watch video) is one of the best I've seen on the subject, and it can really change your way of thinking. Our company has embraced event sourcing wholeheartedly, and it's been gamechanging for us.

One of the key benefits of always being able to re-derive the queryable form of your models from the raw event data, and one that doesn't always come across in tutorials like the OP, is that you aren't just restricted to events that map nicely to "change this specific property in my domain model" or "add a new specific object with these properties." For instance, say you're ingesting emails in a CRM, and you want to say something like "detect the company address from the email signatures, but always make sure that any manually-inputted address overrides that." But then you later change the address-detection algorithm, but want to maintain the manual-override invariant. If that code had been run at email ingestion time in a non-event-sourced paradigm, you'd need to have three-way conflict resolution between old-extraction-algorithm, new-extraction-algorithm, and manual inputs. But with event sourcing, you update the setOfAllEvents -> domainObject function and just push the code, and your data migrates gradually and naturally. And the sky is the limit with how you can combine different types of events.

Everyone loves to talk about source control and continuous integration, and we'd never dream of making the build from code version Y dependent on the build from code version X. But in data management, it's far too easy to use a non-event-sourced approach, and then you introduce those dependencies. And it doesn't have to be that way at all.
This is a great explanation. I'd add one small clarification:

> Back to four stroke engines: Momentum and the firing of other pistons keeps the whole thing cycling back around

The firing of other pistons helps, but really, momentum alone is sufficient. There are tons of single-cylinder, 4 stroke motorcycle, scooter, and off-highway engines out there.
"The rest of the united states dumps their homeless problem on CA."

Hahaha, so because someone else gave us the problem we don't have to solve it anymore.

SORRY GUYS NOTHING WE CAN DO. EVEN WITH INFINITY TAX DOLLARS NOTHING WILL HELP BECAUSE NEVADA BUSSED IN SOME CRAZY PEOPLE. GUESS WE ALL HAVE TO LIVE WITH FILTH AND SHIT EVERYWHERE.

hahahahahahah
I would disagree. Money is artefact of the culture.

If you miss what I want to day by this, I would recommend you to read this nice essay: http://www.naturalhistorymag.com/picks-from-the-past/12476/s...
Currently in battle with Blue Cross Blue Shield. Complete garbage of the universe. Been through 2 rounds of appeals with people that tell me that I am right, but the guidelines say they can't help me. Guess time to fire up the angry tweets.
I work with a lot of people who have never drunk the functional koolaid, professionally. They have to do an extra mental step with map or filter - "oh map, that's where the first argument is applied to each item in the second - I think - perhaps the second argument is applied to the first, right, Stack Exchange". More explicit is clearer, then. 'Clear' like beauty, is subjective. But productivity isn't. And whatever my personal feelings, the productivity of the team wins.

On the second point. I agree. Python's lambdas are a code-smell, for me. Which I don't say lightly, I'm a Scheme/Lisp guy deep down. But they fundamentally work against the aesthetics of the Python language, imho. A local function declaration is much less fragile.

But I would say that as code complexity increases, in my experience, comprehensions don't last long either. They've a narrow range of applicability before you get a big block of spaghetti code. Then it is much better to define a local function and, essentially, 'map' it (even if that 'map' is done as comprehension). Of course, YMMV.
Do yourself a disservice browse using Google Earth with satellite view turned on to any location and zoom out. See if you can spot what is left between the mono-culture farmlands.

We have already sterilised much of the earths surface.
Should Npm Really Be Used as a Built Tool?
I'm sure this has been discussed somewhere, but is there any reason they chose a brand new API involving a whole another protocol over the already-existing DNSCrypt ?
I don't want to offend you, I've lived differently than I do now, but just brainstorming here: sounds like a big piece of property to be able to plant that much. Go minimal to your comfort level. I am not talking a yurt here on 1/10th of an acre, but minimalism can be very rewarding in today's super-size culture.
obviously not
> There is no reason whatsoever to allow remote access to USB devices

Sorta but that's not what this standard is proposing. It's proposing a way of accessing a USB device from a web browser. There isn't any remote access happening here (at least not directly though with this standard you could theoretically do that).

This is simply so web apps can get closer to native apps in functionality.
Stop eating animal-based food. See http://www.cowspiracy.com/ for details.
It's kind of absurd to blame capitalism, when the vast majority of countries implicated are nothing close. Calling Russia or China capitalist is laughable, they are oligarchies greasing the wheels at every turn with extreme levels of corruption.

The US and others aren't immune, but your entire post is ridiculous. These are nations where the government officials pull all the strings, there's nothing free market about that at all.
>How is it different than installing 3rd party software on your OS?

The whole act of downloading and installing?

For desktop apps, you have to do that.

For webapps, you just have to visit a page (or even not, thanks to XSS).

And while we install 2-5 or maybe 20 apps per year (at most, some don't install anything after they get their PCs), we visit 100s of pages each day, and 1000s each month.

Also, while we can realistically restrict our app downloads to legitimate sources (the App Store, the product's webpage etc), we read stuff from all over the place -- that's what links are there for.
Have you read John Sarno's books? If not, I would highly recommend them.
Also appears to subtly alter our moral judgment:

http://www.theatlantic.com/health/archive/2013/04/whats-tyle...
I'm an obsessive notetaker. It helps me improve comprehension and memory.

Having tried a lot of tools including paper notebooks, mapping, personal wikis (ex. TiddlyWiki), tagged note-taking apps (ex. Evernote, Day One journal), blogging platforms, ... I've come to the conclusion that nothing does everything that I want as well as good old markdown.

My solution is a simple but flexible git repo [0]. So far I've logged notes on 50+ items over about a year, including books, courses, videos, magazines, podcasts, etc.

Some of the best examples are Show Your Work! [1] and Cities and Ambition [2].

P.S. One recent development is GitBook (https://www.gitbook.com/). It's a little more than I need personally, but incredibly cool software nonetheless.

[0]: https://github.com/tedmiston/notes

[1]: https://github.com/tedmiston/notes/blob/master/books/Show%20...

[2]: https://github.com/tedmiston/notes/blob/master/essays/Cities...
That is astonishingly close to my ideal. Android compatibility and a normal clipboard style clip and I think I'd be breaking out Fry-take-my-money.png
Personally, nothing. Collective action is the only thing that's going to save us.
Rich people do not need money. Give them more, they will invest it or hoard it. Give poor people money, they will spend it right away. Which helps an economy more?
Sorry, but I'm at a loss for what you believe you're responding to here. I made a clear, factual statement regarding the handling of bound USB devices for known devices and classes. Specifically, HID and other native device classes that are already bound by the OS should not be exposed to WebUSB -- the reasons for and robustness of that guarantee should be self-evident to anyone moderately familiar with USB in modern OSes.

Now, if you have a specific argument to make against my statement, then please share it. I have direct experience with the subject here, and ideally can provide context to address such arguments or clear up confusion. However, I really don't think it's productive to respond with non sequitur arguments and personal attacks.
Cowspiracy's points on GHG emission and water consumption are simply illiterate. They don't recognize the concept of a net flow. (e.g.: carbon that comes out of a cow first went into a cow - via its food - which got apprx. all its carbon from the air)
The things you want to omit have nothing to do with Servo is the point of my comment. Servo's modularity is irrelevant to removing webcam access. Which incidentally I believe you can already do in both Firefox and Chrome by disabling the MediaSource API altogether.
Here you go: https://www.gatesnotes.com/Books/Why-Inequality-Matters-Capi...
I just use a scratch piece of paper and toss it at the end of the day.

Anything that's useful enough to keep is useful to other people too, so that goes into the team wiki.
There is a silver lining to ransomware and other forms of malware. The more people get bitten by them, the more security-conscious they'll become. This is the social piece of the technology/society security puzzle falling in to place. Pity it comes at the cost of so much misery.
Health care works using a subscription model all over the world. You are simply confused by the word "insurance".
I suppose it depends on how complicated the logic is behind your conditional HTML. If there is an initial JS payload that checks the screen size, I might still try to get an HTML string back from the server after checking the size. But there are certainly diminishing returns to server-side rendering if you're making multiple HTTP calls anyway.
This would all be fine and good (just, even?) if nobody was ever coerced into agreement or agreed under duress. You seem to neglect the role of power in extracting preferable terms (and thus wealth).

There often isn't anything "fair and square" except in this idealized notion of some perfect environment you've painted.
Why? I was just about to post a pic of my rash to imgur and ask HN to give me their thoughts.
bubbling asteroids :)
Why do you say that. The article is pretty informative, despite the title.
Nothing short of participating in movements that seek to change the structure of our economy which inadequately penalizes fucking up the environment on decadal+ time scales.
> trends that ... threaten the comfort and safety of billions of people

Again I don't agree that the threat indicated by these trends is as grave as you claim. I agree there is strong evidence of a grave threat to this coral ecosystem, and Australian coastal tourism.
Why does the Hacker News API not have a comment score?
I've been playing with the API a bit and I fully expected comments to have a score, just like stories do, but that doesn't appear to be the case: https://github.com/HackerNews/API#items

It looks like issues are disabled on the Github repo, so I can't easily ask there. Is there a specific reason this has not been made available?

https://github.com/HackerNews/API#items
Often libraries are far too specialized to share or as you point out, have dependencies/licensing that prevent open-sourcing/sharing.

For example I've written various entity/component allocators, pools, and free-list implementations that run ultra-fast and are reusable across almost any game that needs an entity system, but almost each one is optimized for the performance characteristics of the target game. When it comes to game dev, you generally can get much better performance by writing things for the purpose. Usually reusability and performance are at odds in these cases. That might sound counter-intuitive to some in the web world, but it's a fact.

Even in website, you are better off doing things for example like pooling in garbage collected languages, avoiding extra allocations, and using more primitive data structures. This of course makes the code harder to read, test, maintain, etc. so developers in these cases tend not to do it or even be ignorant of these techniques. In games, you do things all the time for your specific use-cases and this really impacts testing and reusability.

It sounds counter-intuitive, but over the years I've learned in most cases reusing things in games is a fantasy only inexperienced developers get hung-up on. That doesn't mean nothing gets reused, rather what tends to happen is you learn from your mistakes/drawbacks of previous code and rewrite it better. In effect, you are reusing the code but it's not a literal drag and drop/cut and paste into a new project. Over time, if something is really solid and doesn't have too many performance/usability drawbacks, it may finally make its way into some sort of cross-project more drop-in library. An example I've directly used EA STL. Even when you reuse something though, people tend to do the equivalent of fork it per project, again limiting reusability.

I suppose in the age of better hardware with tons more ram, some of these concerns may be going away if your target platform is PC, but with mobile, more resource starved vs pc (ex: Nintendo 3ds) and embedded-like platforms gaining popularity, inevitably things circle back to the direction of optimizing per game and per hardware which hurts reusability. Is it really that valuable for example to dig up some library you used one 1 game in the lifecycle of the ps3 when you've already moved to the ps4 for example? Probably not for most developers unless you have a large window between your game start time and the platform lifecycle. Even on PC this is a problem as everything from graphics APIs to average hardware can obsolete a lot of what you've done or make it relatively inefficient/primitive in a new project.
"There is a whole lot of climate change evidence coming out that is terrifying."

Do you think any of that evidence is terrifying to skeptics? If not, think about why not.
That the quote has a certain context doesn't mean it can't apply in different contexts.
Cows and other animal agriculture contributes as much or more [1], to climate change than all cars and trucks. So eating less meat is one good way.

> Livestock is responsible for 65% of all human-related emissions of nitrous oxide – a greenhouse gas with 296 times the global warming potential of carbon dioxide, and which stays in the atmosphere for 150 years.
-“Livestock’s Long Shadow: Environmental Issues and Options.” Food and Agriculture Organization of the United Nations. 2006

[1] From this excellent documentary: http://www.cowspiracy.com/facts/
The post wasn't about the "futility" of a/b testing. It's about the costs of a/b testing that are rarely considered. There's plenty of "pro" a/b testing advice in the world that leads startups to mistakenly waste resources on it.

A solid a/b testing process doesn't just happen without time & effort. You need someone smart analyzing user behavior and forming hypotheses as well as a talented design team to develop concepts that test them.

We simply acknowledged the costs of doing a/b testing well and decided our resources are better spent elsewhere.
The problem is to get started we need more scientists. And academia and education right now right now is so horribly broken with perverse anti-incentives that no young person in their right mind will want to pursue a career in research - they'll go code Ruby instead because they have loans to pay and want a roof over their head.

We also want more engineers and other specialists in government - but decades of bureaucratic creep and managerialism on the one hand and neoliberal-driven cost cutting and privatisation on the other have made government, like academia, very unattractive to young smart people.

So it's not a question of people already in finance, law or tech startups switching over to fighting climate change - as you said, they aren't in the same skill set. We need to train the next generation to fight climate change across a number of fronts - climate study, geoengineering, energy, transport, flood defense, food production and so on. And right now all the incentives are pushing that generation in entirely the wrong direction.
It's not really limited. You just have to name your lambda before you use it.

def make_adder(n):
def f(a):
return n + a
return f

Using this style, you can make the inner function as complicated as you want. You can have statements, or anything else.
None of the intake, compression, power, or exhaust strokes have anything to do with gravity or atmospheric pressure.

Initially, a secondary motor causes the rotating components to rotate, which causes the pistons to move in the cylinder. Later, either inertia or the power stroke from another cylinder maintains the rotation.

The piston movement itself is caused by the piston arm, which is offset from the axis of the crank shaft.
We have to recognize at that point that the human as a whole is still incapable of dealing with this. Either too busy trying to live (sorry for third world people) or too self centered to not think about short term profits. As for loss of biodiversity, nature doesn't care and if we managed to tilt a planet's climate to the point of wiping half of our own selves from it.. then good for the planet.
> The same logic could be applied to local software, which inevitably is also remote in origin.

One big difference is that one chooses to download the software and install it on a computer. In a browser, everything gets downloaded and executed automatically, including scripts. It's just a matter of opening or being redirected to a URL.
How to Pick the Perfect Code Sample for Your Next Job Application
Used it for years for a child care related newsletter - it is a nice readable informal font. Worked well for the audience.
I think you got it better than me.
The many forgotten benefits of segmented sleep