skysight-inc/HackerNews huggingface dataset:
My thinking is pretty similar to yours. Especially the point on subsidies, although I would modify it slightly: if subsidies are employed (explicitly, or implicitly in the case of 'nuclear insurance'), governments should aim to keep them as technologically neutral as possible. I'm not arguing against subsidies (especially at this point): if it's a choice between climate catastrophe or handing out subsidies I'd definitely go with the subsidies. However, I think it's counter-productive (and more costly in the long-run) for governments to distort alternative energy markets by 'picking winners' (as they always seem to do). In other words, subsidise equally.

Carbon pricing always seemed like the elegant, 'neutral' solution to me, but it doesn't seem very popular. Also people seem to have trouble understanding that it makes perfect sense to cycle the revenue back to individuals (e.g. tax cuts), as the point is to make co2 emission intensive activity relatively more expensive (meaning people efficiently substitute away).

On the solar costs, it sounds like you've made a fair calculation (although I'm by no means an expert either, so not really qualified to make any kind of judgement). Although one other factor (which you might have already built in to your unit price) is the cost of transmission infrastructure: renewables (particularly wind) need to be geographically distributed to ameliorate their intermittancy issues (i.e. the wind only blows in some parts or the country at any given time, the sun is only visible from some perspectives etc.). Either that or, as you pointed out, you need quite a lot of energy storage capacity. Most likely there's some optimal mixture of both.

There's two other bits of fission tech that could be real game-changers: small modular reactors (https://en.wikipedia.org/wiki/Small_modular_reactor) and sub-critical reactors (https://en.wikipedia.org/wiki/Energy_amplifier). Although I get the sense the latter is a bit more speculative (even though we have all the bits of technology to make it work in theory).

And I should probably correct something that I think I (mistakenly) said earlier as well: nuke plants, although they can scale up and down to try and match demand, it apparently is not a fast process (meaning at least some energy storage or 'peaking'/'energy sinking' capacity is required, somewhat mitigated by good predictive models of demand).
Yes, Flocker will remain open-source and my hope is that the community continues to improve it. Fli too, btw, for creating and managing ZFS snapshots https://github.com/ClusterHQ/fli
Yet hydro is only 23% of Ontario generation vs 36% nuclear.
>> they're benchmarking raw scripts

TechEmpower uses gunicorn/nginx [1] for Python frameworks, and has since 2014.

>> all you need to do is try to do a little more processing inside your HTTP handler

Unless you're working with an external service like a relational database, in which case performance between Go/Java and Python will be comparable [2]. If you don't need to leave your process, Go/Java will flatten Python.

[1] https://github.com/TechEmpower/FrameworkBenchmarks/tree/mast...

[2] https://www.techempower.com/benchmarks/#section=data-r13&hw=...
Perhaps. But why did they then chose to have a second child?
A Message to 2600 Readers and Writers
"Though outsiders expected Mr. Ferrucci would use his talents to help find hidden signals in the financial markets, his job has focused more narrowly on analyzing the torrent of data the firm gathers about its employees. The data include ratings employees give each other throughout the work day, called 'dots'"

This -- Isn't -- JEOPARDY!! This is shit.
At that point in space exploration, 13% was way too high a risk, even for professional astronauts.
Ultimate flat-earth debunk
It's been some time but I've read the entire report cover-to-cover. While yes, the general conclusion is that NASA's dysfunctional management structure and institutional optimism driven by moneyed interests is the primary culprit. The report never really tries to perform a root cause analysis on how something like the O-ring "safety factor" problem arose.

Something which, as summarized by Feynman's quote above, should be patently obvious to any engineer as bullshit.

Feynman's appendix is the only part that even tries, but it doesn't go far enough through no fault of Feynman's, he had no resources to pursue this line of inquiry. It was a struggle just to get that appendix into the report.

They should have interviewed every single person in any way remotely involved in that O-ring decision, find out if they objected to it, and if they didn't what money/institutional/social obstacles there were to prevent that.

Did some engineer actually sign off on the aforementioned "safety factor"? We don't know, but somehow I doubt that's language management came up with on their own, and if they did that there was no way for an engineer to spot that and report "wtf? The system doesn't work like that!".

Reading between the lines some engineer actually did come up with that estimate, but likely that engineer was where he was because NASA had a culture of promoting mindless yes-men.
I once proposed a backwards-compatible way out of this: "Safe Arrays for C"[1]. The fundamental problem with arrays in C is that compiler has no idea how big they are. My proposal was to replace

int read(int fd, char buf[n], size_t n);

with a safe form

int read(int n; int fd, char (&buf)[n], size_t n);

This says that the size of "buf" is "n", which comes in as another parameter. There are no array descriptors; the generated code for a call is the same. Thus, this is backwards-compatible, allowing mixing of "regular C" and "safe C" modules.

The programmer has to know how big the array is, after all. There must be some way to compute the array size from other variables or constants, or the program has no hope of working. All C needs is a way to allow the programmer to say that in the language. Then subscript checking is possible. Buffer overflows can be eliminated.

The required changes to C are minor. The big one is adding C++ references. Instead of passing a pointer to the first element of an array, you pass a reference to the array. Same object code, but now arrays are first-class objects.

This was discussed at length on the C standards digest back in 2012. After many revisions, the conclusion was that it was technically feasible, but too difficult politically.

[1] http://www.animats.com/papers/languages/safearraysforc43.pdf
There are plenty of governments that miserably fail to distribute very large amounts of aid in a way that actually helps the target groups [0] is one in the US, and internationally, things can be really, really sketchy.

One advantage about doing it via charity is that if a charity is ineffective, or fraudulent, switching to a new one is easy. Fixing a government full of corruption or inefficiency is quite a bit harder.

Government does have an important role, but it is no panacea.

[0] https://www.washingtonpost.com/opinions/how-newark-schools-p...
Very cool. One thing, when typing "hi, my name is yeshivadan." it correctly asks "what is my name." When i type "hi, my name is joshua dan" it asks "who is my name."
The almost-smallest devices are powered by LoopOS(tm):

while(1){ }
It's unfortunate that there aren't separate widely-used terms for recommendation style reviews and critical breakdown style reviews, because it makes it hard to find the latter when I want it. For an example, Jamahl Epsicokhan has written reviews of all the episodes of Star Trek on his site Jammer's Reviews. They break down both the plot and give criticism of the entire work, including parts that would be spoilers. Sometimes you can find these kind of articles under the term "rewatch" though.
Is this the ARES you mean? http://www.aresnorthamerica.com/

Love that they call it the ‘Sisyphus Railroad’.
I don't imagine the FSF has really spent a lot of resources on this page, so it isn't really troubling in the sense of "so much effort, what a waste," so it's more of an amusing, "not much effort, but what a waste".

Those sorts of language changes happen, and it's just never worth fighting for. Especially hacker vs cracker, that one was lost a long, long time ago.

Several of these fit into the same mental territory as genericized trademarks, i.e. digital audio player instead of mp3 player, or Kleenex-brand facial issues instead of Kleenex, again, not worth fighting for.

And several of these carry political loading of their own (e.g. don't say "theft"), as well as that perpetual lost cause, GLAMP.

Oh well. Happily the FSF does a lot of other good work.
If large numbers of poor people choose to live in silicon valley, that implies silicon valley is actually one of the best places for the poor.
It used to be messy but now it's largely just:

git clone git://github.com/c9/core.git c9sdk
cd c9sdk
scripts/install-sdk.sh

https://github.com/c9/core
> One could claim that in a true dystopia the rich would just make it so insufferable that the poor leave as economic refugees.

that is literally happening right now.
Having a culture where failure is okay is different from having a culture where failure is valued. Like the parent commenter said, if failure means you look back at what happened, learn some lessons, do better next time, then that's fine, you've gotten value out of failure. If you say "Hey, I got a failure out of the way," you're playing slots and falling victim to the gambler's fallacy.

> Make New Mistakes. Make glorious, amazing mistakes. Make mistakes nobody’s ever made before.

> Mistakes aren’t a necessary evil. They aren’t evil at all. They are an inevitable consequence of doing something new (and, as such, should be seen as valuable; without them, we’d have no originality).

So, was this mistake glorious, amazing, or new?
Dynatrace redefines innovation: Named Magic Quadrant leader for 7th year
> Am I reading this wrong or did they launch the thing at a temperature way outside the range where they normally launch shuttles?

No, that's correct, the launch was the coldest yet and reached temperatures at which the O-rings had lost their flexibility and couldn't spring back fast enough to seal. In fact an iconic scene from the Challenger hearings was Feynman showing (on TV!) the loss of ductility after having dunked an O-ring in ice-water.
And yet no one talks about the gross disparity of women to men in nursing, social work, childcare, or cosmetic sales.

Why is that?
> because...

Youtube obeys US law by responding to DCMA
This is a quote by Niklaus Wirth, a Swiss computer scientist who has created many programming languages, most famously Pascal. It's a long quote, but I like it very much:

"Many people tend to look at programming styles and languages like religions: if you belong to one, you cannot belong to others. But this analogy is another fallacy. It is maintained for commercial reasons only. Object-oriented programming (OOP) solidly rests on the principles and concepts of traditional procedural programming (PP). OOP has not added a single novel concept, but it emphasizes two concepts much more strongly that was done with procedural programming.

The first such concept is that of the procedure bound to a composite variable called object. (The binding of the procedure is the justification for it being called a method). The means for this binding is the procedure variable (or record field), available in languages since the mid 1970s. The second concept is that of constructing a new data type (called subclass) by extending a given type (the superclass).

It is worthwhile to note that along with the OOP paradigm came an entirely new terminology with the purpose of mystifying the roots of OOP. Thus, whereas you used to be able to activate a procedure by calling it, one now sends a message to the method. A new type is no longer built by extending a given type, but by defining a subclass which inherits its superclass. An interesting phenomenon is that many people learned for the first time about the important notions of data type, of encapsulation, and (perhaps) of information hiding when introduced to OOP. This alone would have made the introduction to OOP worthwhile, even if one didn't actually make use of its essence later on.

Nevertheless, I consider OOP as an aspect of programming in the large; that is, as an aspect that logically follows programming in the small and requires sound knowledge of procedural programming. Static modularization is the first step towards OOP. It is much easier to understand and master than full OOP, it's sufficient in most cases for writing good software, and is sadly neglected in most common languages (with the exception of Ada).

In a way, OOP falls short of its promises. Our ultimate goal is extensible programming (EP). By this, we mean the construction of hierarchies of modules, each module adding new functionality to the system. EP implies that the addition of a module is possible without any change in the existing modules. They need not even be recompiled. New modules not only add new procedures, but - more importantly - also new (extended) data types. We have demonstrated the practicality and economy of this approach with the design of the Oberon System."

Taken from: http://www.eptacom.net/pubblicazioni/pub_eng/wirth.html
I especially ask you to avoid condescension since it's been a few years since I was in the 18-25 bracket.
Solution is to move the bathrooms into the open plan. No more slacking or being aa wimp in private.

Or even better give everyone nappies so they can clean themselves on their own dime. Once they get home.
It kind of reeks of entitlement to me. You would never see someone who is barely scraping by at a blue-collar job make a post celebrating getting laid off.
How+to+care+of+Golden+retriever's+Health+and+grooming
I should have made it clearer that this is just a sanity check. I find the rough approximation 30 million seconds in a year often comes in handy for back of the envelopers like this. 10 seconds thought was all it took to check that 2 people dying every second is at the very least reasonable.
GitLab 8.15 Released
District Court Undoes Fee Award Against Patent Bully
How Google’s Search business and humanity’s information is disappearing
Right, the fact that arrays aren't pointers is academic when they decay to pointers at the drop of a hat. In fact it's so easy to decay the array to a pointer that it is generally best to always treat it as a pointer lest you get burned later on during a code refactor. This mostly means never using sizeof() to get the size of an array.
I had a good chuckle reading this article:

> At Bridgewater, most meetings are recorded, employees are expected to criticize one another continually, people are subject to frequent probes of their weaknesses, and personal performance is assessed on a host of data points, all under Mr. Dalio’s gaze.

I think this is a testament to the disconnect between people in this space and technology. The idea that some mythical holy grail technology will produce alpha is as illusive as relying on automated trades.

> Bridgewater says about one-fifth of new hires leave within the first year. The pressure is such that those who stay sometimes are seen crying in the bathrooms, said five current and former staff members. This article is based on interviews with them and more than a dozen other past and present Bridgewater employees and others close to the firm.

And it confirms my suspicions. I stopped reading here because it's another PR piece for Bridgewater.

I think we will see a small homage to Bridgewater in Mr. Taleb's upcoming books as an example of "techno-irrational exuberance" along with other hilarious empty suit moments described in the book Fooled By Randomness.
Exactly! Shipping ES6 code to browsers.
This is truly one of the best readings, one of the three books I recommend everyone read (and re-read) every now and then.
Node CLI to query stock info and performance using web scraping
You need to read the whole thread:

http://marc.info/?l=linux-pci&m=148238610022972&w=2

"obviously i am interested to get this upstream with the least amount of effort. I am quite aware though that some patches will need an overhaul to be applicable for upstream. its not really my call if it is enough to make this an enable patch and review the quirks enabled by it or if the code needs to be moved."

Upstreaming patches into the kernel requires that you're willing to spend time to rework them so that the result is maintainable. Saying from the start that you only want to do the least amount of work possible isn't helpful.
They can mostly not worry about starvation, and have internet access, and they have some access to flush toilets and showers.

What are you talking about? Incan kings slept on stone shelves and covered themselves with poorly tanned animal pelts, and were at the mercy of insects and crop fluctuations. They didn't have modern sewage systems or vaccinations.
Maybe "stateful containers" aren't a good idea. The whole point of containers is supposed to be that they can be duplicated and loaded into many machine instances. "Stateful containers" with changing databases inside can't be treated that way.
> spend a few hours dredging up people they worked with from our networks

What if there aren't any?
Shareasale Page 3
I would only blame the startup if they were members of Hamas and co. I'm sure there are decent people in Gaza, but unfortunately they are offset by murderous terrorists.
Don't really need to refute a claim with no evidence to support it written by someone likely not involved in the field.
Would Like to Archive Government Web Services, Not Just Web Sites– Please Help
Being cheap helps however this doesn't matter if you still can't earn a living with the chosen profession
Would it be fair to say that, by and large, it powers the smallest general-purpose computers?
Any YC use nootropics? Tell me
Hey guys, I imagine there are probably thousands of you all that have tried nootropics and smart drugs.

I wrote an article specifically about nootropics for the purpose of programming. I'd be interested in:

1) Feedback. Does this resonate at all and is it helpful?

2) What do you use or feel works particularly well?

https://www.nootropedia.com/best-nootropics-for-programming/
They vast majority of poor in SF grew up there or in nearby areas, they didn't migrate there like the economic elite have.
First, when it comes to stories like this, libertarianism is basically irrelevant in the real world. To a first approximation, even in Silicon Valley, there aren't any. The Valley is far better known for its progressivism than its libertarianism now.

Second, I am unaware of any tenant of libertarianism that says it is somehow bad for people to band together into charity organizations, potentially the very same ones mentioned in the article, and for other people to give money to those organizations. Nothing about libertarianism requires altruistically-minded individuals to literally go out into the streets and start handing out dollar bills to individuals or something. Libertarianism is about not being coerced to join organizations, not about organizations existing.
Modern medicine, access to all the world's knowledge on a handheld device in your pocket, cheap clean/safe water and food from every corner of the world, entertainment (music/films/tv/youtube) cheap/safe transport over thousands of miles in a matter of hours.

There's not a chance in hell I'd want to swap places with a king of 1000 years ago.
All legal and political discourse is a struggle for control of linguistic territory.
spoiler: "Python is still the leader, but C++ is now second, then Java, and C at fourth place. R is only at the fifth rank."
curious to know what you are doing right now ? I'm planning to deploy a redis cluster on a private cloud and am wondering what to use.

do you use hostpath right now ?
Also see Mark Twain's "Fenimore Cooper's Literary Offences"[1], reviewing some of the works of James Fenimore Cooper (of "The Last of the Mohicans" fame).

A sample:

In his little box of stage properties he kept six or eight cunning
devices, tricks, artifices for his savages and woodsmen to deceive
and circumvent each other with, and he was never so happy as when he
was working these innocent things and seeing them go. A favorite one
was to make a moccasined person tread in the tracks of the
moccasined enemy, and thus hide his own trail. Cooper wore out
barrels and barrels of moccasins in working that trick. Another
stage-property that he pulled out of his box pretty frequently was
his broken twig. He prized his broken twig above all the rest of his
effects, and worked it the hardest. It is a restful chapter in any
book of his when somebody doesn’t step on a dry twig and alarm all
the reds and whites for two hundred yards around. Every time a
Cooper person is in peril, and absolute silence is worth four
dollars a minute, he is sure to step on a dry twig. There may be a
hundred handier things to step on, but that wouldn’t satisfy
Cooper. Cooper requires him to turn out and find a dry twig; and if
he can’t do it, go and borrow one. In fact, the Leather Stocking
Series ought to have been called the Broken Twig Series.

[1] - http://www.gutenberg.org/files/3172/3172-h/3172-h.htm
An Introduction to Geometric Algebra
Arguably, part of the problem is that people do. The ones who do come into conflict with the people who have no desire to use their freedom of movement.
I'm currently reading Red Rising and would totally recommend it.
The real problem is that people can say things I don't agree with on the Internet.

I'm sure you know this already, but Google's search rankings !== "the internet".

Not only that, but they've been downranking all kinds of content -- including spam of all sorts; and most assiduously (and famously), virtually all forms of pornography -- for nearly as longs as they've been in existence. Which no one calls "censorship", or "blocking stuff I disagree with"† -- because of course it isn't. It's simply a matter of editorial discretion -- of the kind that all mass media companies have always engaged in, since mass media became a thing.

Got a problem with that? Start your own search engine.

† As if holocaust denialism were a simple matter of "stuff I disagree with". But it isn't of course -- which again, I'm sure you knew already.
We are using DC/OS (Mesos) and found it to be much more feature rich for what our needs were.
My point was not to snark about granular synthesis; my point was to demonstrate the amount of freedom that exists in synthesis methods that have been around for a long time. I understand the criticism that a lot of music is stuck in 12-tone equal temperament, I don't understand the idea that electronic music as a whole is stuck there.