skysight-inc/HackerNews huggingface dataset:
This is a good link. I particularly liked the ending paragraph about motivation - I think it's all network effect. If my friends and people I look upto were working on environmental engineering then maybe I too would jump into it. Unfortunately, none of my peers work in that area hence I spend time thinking about new buzzwords and technologies instead.
Duplicates https://news.ycombinator.com/item?id=14171119 , posted earlier by Denis Roio .
I want to thank @redsummer for posting this fascinating article. Despite its flaws, Hacker News is one of the best things going on the Internet right now, especially for retired folks like me who have the time to wade through the new stuff and find the occasional gem.

My takeaway is that globalization has winners and losers. The winners get to keep the spoils and write the history books. The losers are debased and then ignored.
Mitigation isn't a big technological challenge per se. The big showstopper is the fear of the unknown unknowns; the remote possibility that despite our careful science and engineering, the cure ends up being worse than the disease. Because we only have one shot, and no "undo" button, large scale geoengineering will be put off for as long as possible.
Not an expert on climate either, but I own an aquarium so have a decent experience with artificially high CO2 levels. It's a common trick to inject pressurised CO2 to aquarium to speed up growth in planted freshwater aquariums. It works great for plants, but only if you provide them sufficient levels of other two necessary components: light and nutrients. If either of those is lacking plants will actually suffer, become unhealthy or algae will take over. Nature is all about balance, so you better increase all variables or not touch anything. Increasing just one almost always generates instability which can easily cascade into a disaster for farmers and the whole ecosystem. And it's such a dynamic system with so many variables in play that it's impossible to account for all possible side-effects this can create.
2^64 nanoseconds is ~584 years, though.
> I don't think the `className` argument sticks. `class` is reserved so you can't use it.

But you can use it. JSX nodes get compiled into React.createElement calls with object literals[1], and {class: "foo"} is a perfectly valid object literal in JS, s there's nothing stopping `<div class="foo" />` to get compiled into `React.createElement("div", {class: "foo"})`

In fact, other frameworks that support JSX syntax allow the use of `class` instead of `className`[2], so it's not a limitation of JSX per-se, it's just a design decision on part of React (and an annoying one at that).

[1]: As noted in the first code snippet on the React homepage https://facebook.github.io/react/

[2]: E.g., Mithril https://mithril.js.org/jsx.html#jsx-vs-hyperscript
Ignorance and scepticism are a double edge sword. The problem is absence of curated information. The fact that she believed in how homeopatic medicine worked, or that he believed in aura cleansing, has nothing to do with the capability of the method itself, but with the source of knowledge for the carrier of the method. There are alternative medicine that work wonders, there are concepts of aura. The application of the method is wrong: non physical nature of the aura concept presented via foreign means to the method itself: a device. Or, the context is wrong: general immune system boost with alternative medicine will also cover the fact that her organism could fight off a specific case of infection. While she is ignorant in why that might have worked, I would not equate the method with the application of the method in your post.
Among the other benefits the Internet has provided, we can now watch in real-time the blow-by-blow of weighty matters such as an English language critique gone wrong (coming from a site as utterly devoid of respect, purpose and integrity as LinkedIn).
Silly point. O2 shortages are irrelevant- 210,000ppm to 209,800ppm O2 is far less of concern than 300ppm to 400ppm CO2.
Click baity how?

And that comment is valuable because it shows that it's feasible to do with data center water, which is much less hot than the industrial sources you mentioned.
Shameless plug time!

Someone says "minesweeper", I post my implementation. It's an established ritual.

Here go: http://www.ronilan.com/bugsweeper/

Few notes:

1. This is dated January 2014. It is a job interview homework.

2. The HN community has detected a bug and indicated that it should be fixed. That was done March 2017.

3. There are currently no known bugs.

4. The goal of the game is to find the unknowns.

5. No puns intended.

6. Code: http://www.ronilan.com/bugsweeper/js/bugsweeper.js
I guess I was thinking more literally: the Earth does not have large windows we can use to exchange air with the outside environment. Carbon sequestration doesn't remove CO2 from our "spaceship," though it may help.
You may want to consider always flying the same airline, getting that airlines credit card and using it for everything, and purchasing a lounge membership to that airline.

If you do this and fly enough your experience will be much better. You can arrive to the airport later because you can use the elite/first class line at security. If you need to check bags there will be a priority line and finally if you need to change something you will have access to a priority phone line that is answered in a timely manner and the customer service agents in the lounges will help you quickly and effectively. Also, many change fees will be eliminated and you will occasionally be upgraded to first class.

Edit: they will also put special tags on your luggage that will cause it to come out first and get lost less.

Edit2: They will also treat you better on the plane. They have a list of where everyone with status is sitting and they make an effort to be nice. It helps if you are also nice to them.
Patent lawyers read them and check if your work doesn't infringe. In my company that's standard procedure.
Hawking Biryanis to Helping Bayer Life Sciences
By my math, we're fine for almost 600 years:

http://wolframalpha.com/input/?i=2%5E64+nanoseconds+from+now...
But before the internet you had to go out of your way to find a second snakeoil salesman. In the internet age, they can be your whole village.
You are agreeing with me strenuously. Anybody can follow the path, with more success than any of the common approaches to starting a business. No approach will guarantee success for everyone who tries to start a business, needless to say.
Can you explain why? Over the year they would release the same water as the river without the dam would do - just not in a peak flood but reduced to a constant flood rate.
Oh Jesus, please don't fill my professional tool with social gunk. What is this, a highschool?

As a side note, recruiters are not on your side, they're on their own side. Don't rely on them for anything, least of all securing your dream job.
Indeed. Evicting someone justly in San Francisco takes at least 6 months (of no rent).
China plans world’s biggest national park on Tibetan plateau
"I mean who in their right mind would write a 27 line init script when they could write a 7 line systemd unit?"

27 lines is horribly optimistic. Complex services like Apache, MySQL, etc. could have initscripts hundreds of lines long, plus the library of support scripts that most distros ship to make the initscripts shorter and more manageable. Most initscripts are like 50%, or more, boilerplate that's the same across all services, but, it's still a pain in the ass to maintain them.

I will not miss initscripts, even if I might have some occasional complaints about systemd.
...or perhaps let's take care of the patients while we develop a cure? If it is a fact that recruiters look at github presence, ignoring that fact is harmful for people only sharing work on gitlab, which in turn hurts gitlab.
Is there any reason to use APFS on desktop?
There's a few things here.

First, the fact that go's language specification allows for this should be enough to stop you right there. Even if today it doesn't move memory around, an update very well could. This library is supposed to be used for cryptographic secrets; "it works by accident for now, probably" is not even close to the kind of situation you should be designing an API around. At any point, without serious warning, an update to the golang runtime can render these protections useless.

There are situations today where go will move data on the stack. I am unsure if it will move heap allocations, but when the garbage collector adds compaction support this will absolutely be the case.
I agree they are much better than strip mining and I said as much, they just are not beautiful.
But that should be 'from 1.1.1970', i.e. from the unix epoch. Still far out, though.
GPL2 Did you Google?

Google "gpl 2 patent clause"

First result, for me:
Patent clauses in software licences - software patents wiki (en.swpat.org)
en.swpat.org/wiki/Patent_clauses_in_software_licences
Jump to GNU GPL v2 - (See: GPLv2 and patents). See section 6 and section 7. Patent attorney Dan Ravicher argues that GPLv2 includes an implicit ...
Services also fall in price when the supply outstrips demand. You should be rooting for windmills to get cheap but wind prices on the market to stay high.

Wind has an issue where it is most productive during the night the grid doesn't really need power. So it will be priced lower.
En-jinks. Apparently it's actually Engine-ecks.
Carbon Capture and Storage (particularly on biomass) appears to be one of the more realistic solutions. So it was a huge shame when the UK Conservative government cancelled planned investment in CCS (breaking a manifesto promise in the process).

It's not a technical or economic problem. It's a political and social problem.

https://www.theguardian.com/environment/2015/nov/25/uk-cance...

https://www.theguardian.com/environment/2016/jul/20/treasury...
The GP specifically mentioned copying data into an `mmap`'d buffer. My point is that copying presupposes secrets already in managed memory, and at that point you've already lost.
Largely because some people use it, and for those who don't putting this in their .emacs serves as a straightforward tutorial focus and a right of passage:

(tool-bar-mode 0)
(menu-bar-mode 0)
(I think we've reached thread depth limits here, so I'll stop at this.)

Yes, it's a last resort and that does give the incumbent a bit of leverage. However, we've seen this type of thing before in the (F)OSS world: EGCS is an almost model example.

> Software is not static and decisions need to be made by everyone the standard impacts.

Sure, but systemd actually has very good reference documentation which you can hold them to.

> Which is why it is important that control rests in a collective that represents everyone's interests.

That may be the thing we disagree about, actually. I actually do think that the systemd maintainers actually do have everyone's best interests at heart and not just RH. That doesn't mean that they formally represent everyone's best interest, obviously. (I readily acknowledge that I may have this perception because I happen to agree with them on many issues, but I do try to be as impartial as possible when discussing it.)

>I think that's the only way we could call it a 'standard' without taking liberties with the word. Wouldn't you agree?

I don't. Off the top of my head, my best example would be AC vs. DC[1]: They were both 'standards', but were basically pioneered by two individuals. (For -- as it turns out -- absurd reasons.)

The point is that a 'standard' for me means something more along lines of a 'standard of service' or 'standard of care'. It's more about having a formalized set of parameters of X. It's not so much about the process itself.

[1] Oh, how I wish I could do a real proper link on those words, but here you go anyway: https://www.youtube.com/watch?v=v2AC41dglnM
"If I stand on an airplane and jump, do I land where I started, further back, or further forward, relative to the plane?"

I would say, that most people would answer correctly, that you would not land on the same place, but probably be blown away far backwards from air friction (even though they would just call it wind).
2^64 nanoseconds is > 580 years. Even cutting it in half for signed values is still likely 10X the expected lifetime of this particular iteration of APFS.

The granularity is probably useful for establishing an ordering (even somewhat arbitrarily) for highly concurrent file system operations, and thus potentially skipping a bunch of expensive synchronization.
This is true.

Package githubapi uses the GitHub API [1], but that package is not currently used on my site.

[1] https://godoc.org/github.com/shurcooL/issues/githubapi
If someone wants to know like me why Apple came up with a whole new FS - http://www.cultofmac.com/435718/apfs-new-apple-file-system/
The courts disagree and have in fact dinged Apple for abusing market power:
http://macdailynews.com/2013/08/28/u-s-a-v-apple-judge-denis...
Indeed. Thought it would be good to get knowledgeable feedback here about the issue.
I mean who in their right mind would write a 27 line init script when they could write a 7 line systemd unit?

That is a gross and asinine misrepresentation of the impact of systemd.
Let's assume for a moment that this previous design bore many similarities to the google design (which could have happened just because the same people built it not solely because stolen files were used), what if the previous design were only worked on when it was Otto and was discarded when Uber acquired Otto? What would happen then?

Google has specifically stated that their suit is against Uber and not Levandowsky. If this previous design was worked on wholly at Otto pre-acquisition than this lawsuit should be against Levandowsky and in arbitration. This suit is already 1 month old and Uber acquired Otto on September 18th. That's a mere 6 months. If the previous design were scrapped around that date or really only saw significant development before that date, than this lawsuit should be dismissed and focused wholly on Levandowsky and select Otto employees for whom they have evidence to believe were complicit in the alleged acts.

Right now it looks like Google is fishing for an opportunity to hurt and slow down a competitor using a lawsuit instead of being the lawsuit against the person who should have been the defendant in the first place, Levandowsky.

There are hundreds of engineers working on a self driving car effort of their own design for many months even years before Otto was acquired and this lawsuit is wholly unfair to the work those engineers have put in to making that happen. Google is looking a lot like Oracle here using the law to slow down and hurt engineers doing good work.
And drawing water from an aquifer, when we don't even know how fast it's being replenished, seems like a particularly bad idea -- surprisingly so from a company whose headquarters is in California.
You need to flood the place with ozone. It takes a few days and it's pricey, but it gets rid of any smell.
Best way to get delivery I found is Goodneighbor Delivery app for iPhone
Google Patent is a lifesaver for me. But I've noticed increasing number of errors.
The courts have already decided against you here, saying Apple both had market power and abused it re ebooks:
http://macdailynews.com/2013/08/28/u-s-a-v-apple-judge-denis...
> I'm saying that all monopolies are bad.

Including regulated, natural monopolies? (I'm speaking of utilities mainly). Sure they're not great, but I can't think of a better alternative.
see section 30-4-40(A)1

"Trade secrets, which are defined as unpatented, secret, commercially valuable plans, appliances, formulas, or processes, which are used for the making, preparing, compounding, treating, or processing of articles or materials which are trade commodities obtained from a person and which are generally recognized as confidential and work products, in whole or in part collected or produced for sale or resale, and paid subscriber information. Trade secrets also include, for those public bodies who market services or products in competition with others, feasibility, planning, and marketing studies, marine terminal service and nontariff agreements, and evaluations and other materials which contain references to potential customers, competitive information, or evaluation."
Dev-u-an :)
I heard there will be copy-on-write for files. For web devs this would save a lot of space and time when copying files from yarn cache to node_modules.
I kept finding it wanted to clip the right hand edge of the puzzle off the right hand side of the browser window. I tend to use square browsers --- am I weird?

And left-dragging to pan wasn't an entirely happy experience; partly because it kept selecting bits of the HTML on the left, and partly because I felt there was something slightly strange about the way rotation worked. Is it traditional arcball or something else?

...but in general I thought it worked really well. I played sweep mode, and liked it a great deal (I did get an unfair puzzle, but guessed correctly and won it. On, um, easy mode).

Update: has something just changed? I can't delete mines in sweep mode any more --- they just blow up instead.
I would strongly encourage you to just wrap `libsodium`. The authors have thought about this problem a lot, and have done the hard work for you — there is a surprising amount being done behind the scenes to give the kinds of guarantees cryptographic keys warrant.

If CGo isn't acceptable, at least use their implementation to guide the design your go-native version.
There is a nice essay about that, by Bret Victor: http://worrydream.com/ClimateChange/
Cool type of Grocery list is the communal one on Goodneighbor Delivery
I think the biggest question here is how can a public municipality sign an NDA written by a private corporation?
I've said it before here, but the best web app I've built was basically Django, with bare minimum js to handle in-page effects.

I've been working on a project which is being ported to React for no reason, just because it's shiny, and it's been worst than expected.

Bundling the entire website into a huge js file doesn't make any sense. In practice, every time you make the slightest change, like adding a div, or changing a class name, your users have to re-download the entire thing.

Webpack takes 1GB of memory and 90 seconds to build it. Firefox Dev Tools eats all my ram if I try to reload the page with it open. And Redux is just bad. So much boilerplate for a dynamic language, with constants and if clauses to decide which action to dispatch. Apparently, it's ok to have presentation logic in a component, but god forbid internal state!

I do believe the reason front-end devs praise it so much is because it allows them to work solely in js, despite the end product being slow and heavy.

I always compare reddit's mobile site, written in react, with Hacker News. The first takes around 7 seconds to load on my cel phone, while the latter loads instantly.

No one but frontend devs care about js. The web hasn't become js centric and I bet it never will. It has become mobile first and all you need for 90% of that is css.

I don't know why fb and google spend money building these frameworks, but maybe because of this:

https://www.joelonsoftware.com/2002/01/06/fire-and-motion/

"But the end result is just cover fire. The competition has no choice but to spend all their time porting and keeping up, time that they can’t spend writing new features.

Look closely at the software landscape. The companies that do well are the ones who rely least on big companies and don’t have to spend all their cycles catching up and reimplementing and fixing bugs that crop up only on Windows XP.

The companies who stumble are the ones who spend too much time reading tea leaves to figure out the future direction of Microsoft. People get worried about .NET and decide to rewrite their whole architecture for .NET because they think they have to. Microsoft is shooting at you, and it’s just cover fire so that they can move forward and you can’t..."

Replace Microsoft with Google or Facebook...
Much like the value of the US dollar, what you're saying is only real if enough people choose to believe it.

Buying into and supporting this behavior is just digging an increasingly deep hole. If you don't want github commits (and an agreement to the github terms of use) to be a mandatory part of all developers lives and CVs, then simply continue being an excellent developer without making github commits that you don't want to make.

We're in an important stage of github adoption at the moment. Some recruiters think it's a critical signaling mechanism. If we buy into that, they will seem to be correct, and the companies they recruit for will allow them to continue with their methodology. Soon, they will become correct because all career-oriented developers will feel compelled to work on github based open source projects to the exclusion of other open source projects, even if they don't actually give a shit about the projects they are working on.

However, if the companies they recruit for see high quality developers going to the competition because their recruiters are dismissing people out of hand for not being on github, those companies will eventually tell their recruiters to pull their fingers out and do some proper legwork.

The correct approach is to starve out this behavior while the cost of doing so is relatively low, not buy into it.
I guess it depends on what you're trying to accomplish. If you are trying to edit on the remote machine, just open the files directly in emacs is the best bet:

http://stackoverflow.com/a/20624538

(side note, this is one of the best parts of org-mode, it supports remote links to files. When you open the link, it will open it in a buffer and depending on your config, even switch to the correct mode).

On the same page there's a tip to set up dired (an emacs file browser) to browse the remote machine and open files within emacs.

You can also run eshell or ansi-term from within emacs, if that's what you need to do.

So I guess I don't find much need to run a client system, but I'm not 100% sure what your needs are.
Those structural engineers benefit from the millions of repeatable experiments in engineering over the past few centuries. It is an extremely well understood subject. Climate science, by comparison, has no repeatable experiments on the scale of a planetary atmosphere and is in its infancy. No-one knows with certainty the impact of 400ppm vs 410ppm so they have to rely on speculative models, so it's right to treat climate science as less reliable than structural engineering.
Between Louisville, Lexington, and Cincinnati there is a large community of developers, tech startups, meetup groups, and a job market that is wide open for good talent. Meetups and classes in Louisville are definitely a google search away. Also there's awesomeinc.org in Lexington. If you want to learn to code, try some online courses first. If you dont hate it, get out and meet other developers, look into courses available. Expose yourself to enough concepts so you can make an informed decision about what you would prefer to actually do as a developer.
Ranking systems help solve this. For example in games. Even in 5v5 games better players will eventually get to the top, because they will cause more games to be won in aggregate over their career. Similarly, systems of apprenticeship, and rankings found in things like martial arts and sports.

The problem is that we need 100,000 doctors, some of them will be more informed than others. The less informed ones will cause the other's to look worse. A doctor is still more informed, but when there are disagreements, it would be useful to know the relative standing of them. It would help with these sorts of problems.