skysight-inc/HackerNews huggingface dataset:
While I agree with what you're saying re: Relaxation after work vs no work at all, the use of words is perfect to describe what I and probably many other people struggle with in regards to bettering their situations. I understand that I have a degree of self-improvement impulse that would be destructive if I indulged it fully, but I definitely have ideas for products and side businesses that I would really like to get around to but it gets washed away by this "narcotic undertow of cheap entertainment" as the author so eloquently puts it.
California Health and Human Services Agency Data Playbook
In addition to the cheap 2 Xeon socket configuration, I would love to see Oracle offering fault-tolerant, mainframe reliability level, infrastructure. Also, "SPARC big iron as a service"...
Actually, several of them, rather. Though in a Manhattan Project sense (or Apollo Project if you prefer), rather than a WWII sense.
Because SPA and asynch is dope, yo! This ain't the 90s. Gotta keep it new & shiny.
They do. They're also responsible for the Shenandoah low latency GC.
Well, sure, but what's that got to do with actual music instruction and how musicians talk about music? Movies aren't always entirely accurate representations of the world, particularly on highly technical topics.

Knowing solfege because you heard it in a movie and using it on a daily basis in the process of teaching or making music are independent concepts.

Anyway, conversation here has brought it to my attention that it is still pretty common, there are some areas where it is useful (maybe even better than numbers, as in the singing and vocal training area; I personally have recognized the limitation of numbers when singing minor notes, for example), and that my own experience was only partly representative of music pedagogy in the US and elsewhere. That said, when I'm teaching people about music, I still plan to only use numbers...the areas where solfege would be useful are pretty advanced, and require more than watching Sound of Music to understand.
The old definition I learned is that it is a version that you think could be released, unless any major bugs appear that you don't know about yet. It's not something where you would expect major API changes.

But those definitions have become much more fluid, and it's hard to find out which definitions everyone is using.
You can't trust a former CIA operative to be truthful about the operational deficiencies of the CIA! That book is just chaff thrown to confuse foreign intelligence services, luring them into a false sense of security about the CIA's imagined weaknesses...

(The fun thing about conspiracy theories is bending them to account for new facts with increasingly twisted, interally-consistent logic ;) )
It doesn't actually matter much if our usage projections are good. What matters is 1) that the energy store is so massive that it's hard to imagine how we could possibly exhaust it, and 2) the current dominant alternative (i.e. fossil fuel) is known to be terrible for us. If we switched to geothermal and set the world up to end humanity in a thousand years, we'd still be better off than continuing our desperate use of fossil fuels and ending humanity even sooner.
See inside this tiny home that’s only 160 square feet
I heard that the are better for the environment and smell nicer too.
...and here is how that is going to play out. We're a large public sector customer. As part of our last ELA renewal (which was an effing effing nightmare over vmware licensing) we got this crapload of Oracle cloud products that we didn't really want or need, database cloud, process cloud, integration cloud, on and on. I think there must have been a mandate from Mark Hurd to the effect that "There will be cloud products on EVERY deal." So now our rep is trying to get us to do POC's to move apps onto the cloud stuff. I bet other customers can tell similar stories. And so Oracle can show growth in their cloud business...
That's one of the pros often mentioned about React. In practice, I haven't found it to be true so far. Once you start using React, you'll almost certainly have to use one the Flux implementations. So let's say you use Redux. Suddenly you also have Actions, Reducers and Stores that you have to learn. If you want to use Async Actions (which is very likely in a web application), you'll probably need Redux Thunk, so that's another concept to understand.

Then there's routing, which is not present in the React core, so you'll need a routing library as well. Again your API surface increases.

In the end, if you want to write a larger application with React, you'll often have a similar or even larger API surface than Angular. I can understand that some people prefer the conceptual model of React (with its focus on Components) over that of Angular. The claims about a smaller "API surface" have always felt wrong to me, though.
Let me ask you a question:

Take 100 rich people and ask them "how hard did you work to get there?", do you think most of them will say "haha i didn't work hard at all! You don't need to work hard to get rich!"

My point was, all other conditions being equal, the people who try hard in their life tend to be more successful that the ones that don't.

Which is why if you take the rich people set and observe how much they work, it is obviously going to be that they work hard.

It sounds classist only if you interpret it that way.
> It has been a long and fun journey.

Using the word "journey" is this context is rather... risky.

https://ourincrediblejourney.tumblr.com
On a related note -- is there a StackOverflow-like site where you can ask questions about basic app architecture so you don't get stuck on a shitty ecosystem?

I'm building a simple front end and I had settled on Angular. But there are too many choices out there. I know there's no simple answer, but there ought to be "rules of thumb" out there to consider. e.g., does your team know Typescript? do you want to use plain old Javascript? etc etc etc.

The choices are staggering.
To me personally, "release candidate" implies "almost ready". After all, it is a candidate for release. In other words, it's released to the public for some final testing and bug fixes with no chance of additional features, API changes, etc. between the RC and the final release.
> mostly for the learning
RC absolutely means non-breaking API changes. Bug fixes yes, but the API will be stable.
They're not regulating the world's space access... they're monitoring to prevent commercial satellites from colliding with debris and other items in orbit. This is a public service.

The US at large does have the power to block access to space, given that they posess the most technologically advanced military on the planet, but I doubt the FAA will be intervening militarily against your bottle rocket any time soon.
Release candidate to me means "We think this software is pretty much done. Does anybody in the community think otherwise?". You don't expect new features or breaking changes. That wasn't what happened during angular2 development.

I started a project at around RC4. It's my own fault to some extent for doing that and not waiting or using angular1.

I found that most of the core functionality like component annotations, ngInit, template syntax didn't change - although I wasnt trying to use the router or forms modules which did experience large changes over the 6 months.

For me most of the pain was in keeping up with changes in the boilerplate stuff in the root of the app like main.ts, modules and and the same keeping up with recent big changes in angular-cli.
Doesn't make sense to repeat it multiple times out, and you definitely could crowd source that kind of info if the mapping wasn't usurped by opaque Google not interested in that.
> And I'm simply saying, if you take 100 rich people and ask how they got there, majority of them would have gotten there because they worked hard.

I'm pretty sure, yes, if you asked 100 rich people, they would say that, the question is whether that attribution is accurate.

I'd suspect that it is true in some respect (specifically, if by "working hard" you mean "spending time in activities directed at getting rich"; there is plenty of hard work people do that isn't directed at getting rich) if you compare them to less-rich people with similar starting conditions. I think, though, that starting conditions and factors outside of the individuals' control are pretty big contributors to becoming rich.
I think this is a profound essay.

Let me just emphasize one point. I think that to find out what you really want, what would be truly rewarding, often you have to sit with your feelings for a good while, and without distraction.
ASRS is NASA ran for a specific reason: To keep a clear line between safety and enforcement. For ASRS to function effectively, pilots have to be able to report incidents without fear of FAA enforcement. In fact, by regulation, a pilot can use the "immunity" rule once every 5 years to avoid a FAA violation.

https://en.wikipedia.org/wiki/Aviation_Safety_Reporting_Syst...
15 F-35 Models Grounded Due to Wiring Issue
Using libraries in Perl and Python, they are generally a lot more finished that JavaScript in my experience.
Drones Make Elephants Go Berserk:

http://www.theatlantic.com/amp/article/481701/
> It's a market Oracle is uniquely qualified to pursue because they already have the sales operation and contacts in place.

Microsoft has a lot of the same kind of sales operation and contacts, and they have a suite of cloud infrastructure that's on par with AWS.
The DOJ is not a part of the judicial branch - it is under the executive branch.
https://www.whitehouse.gov/1600/executive-branch
Oh man, I didn't even realize this changed. But I guess I never expected it to last forever...
This reminds me of the excellent episode of Changelog in which Facebook's head of open source discussed the logistics of managing React so that the public version is exactly the same as the version used by Facebook itself: https://changelog.com/211/

Really drove home the concept that open-source requires significant thinking and discipline when a library becomes heavily used.
Shawn from Beep here. It's definitely an interesting area for us. We've created a tracker demo but don't have any information on our site about it yet.

I love the idea of inductively charging the dog tracker when the dog is in bed (though we're unlikely to pull that off anytime soon given the state of wireless charging).

You can do a lot with battery life if you only turn the GPS radio on when the user wants to locate the item. This type of product requires really good network coverage. We could make one last for 4-5 months on a single AAA battery.

If you want it to check in every 10 minutes with GPS data it would only last for 3.5 days. If you get smart with an accelerometer you can push that out to 1-4 weeks or more depending on how much the thing you're tracking moves around.

It's a fun product area with lots of parameters to tweak!
"Release candidate" != "Release" but in my understanding "RC" is "almost finished, but we might have some bugs to fix before"

Anyway my personal attitude is to keep away from alphas, betas, RCs and stable-from-yesterday. Applies to frameworks, operating systems and virtually everything, and each time I don't follow that rule, I regret.
This article is veery well written. I read the book a long time ago and never thought Huxley would get almost everything right. "Technology controls the society", this one wasn't that hard to predict.
> Google tends to release code and promote it without
> really using it much internally first.

Is this actually true? My understanding (from watching many AngularJS presentations) is that Angular was developed with input from many teams at Google.

(edit: Angular was first used on an internal app at Googel: https://www.youtube.com/watch?v=r1A1VR0ibIQ&feature=youtu.be...)
I think it's more compelling, however, to just think about how much bigger the interior of the planet is than our existence at the surface.

We live on maybe ±1km of the surface or so; we don't dig much deeper than that except perhaps when exploring very deep caves or so. The radius of the Earth is approximately 6300 km. One volume is (4 pi/3) R^3 and the other is 4 pi R^2 dR, so the one volume is larger by a factor of 6300/3; we can only hope to visit one two-thousandth of the Earth's total volume with holes 1km deep. Up that to 10km deep and you'll still only get one two-hundredth of the Earth. Oh, and we've only got about a third of that because oceans.
Promise patterns and anti-patterns
Two things.

First emergency services often do use SMS - as it's the last bit of signal to remain usable as they move into marginal areas. Data's first to go, then voice, last texts.

Second SMS never was 140 chars - it's 160 char GSM, or 80 Unicode, and every feature phone, from years before Twitter started, happily handled the GSM multipart SMS standard. I forget the limit, but it's at least 10 parts (I think it's much more - 64 or 128 maybe), so 512 char SMS is already done. In 1990-something.
Wow that's amazing! It seems like this could revolutionize several industries and create several new ones! I guess there's got to be some kind of catch? Too expensive?
I'm assuming Google doesn't need any of the company's business, and that it is being acquired for its talent.

So, my real question: how much, on average, does a founder get as part of one of these acquihires? And does s/he actually, y'know, have to do any work after getting paid?
Another one of those services I wish I'd heard about before its acquisition. But at least this one does not appear to have been shut down on day one?
Google's "Custom Machine Types" can be a big pricing win over Amazon if your workload doesn't match Amazon's pre-built options.
From the article: "Any time a human needs a relationship and a person isn’t there is an opportunity for a chatbot to fill itself in." Hm. Need to think about that one.

Chatbots currently assume a master-slave relationship, where the chatbot controls the dialogue. The human has to adapt to the chatbot, although there's some illusion that the chatbot understands the human.

Right now, a pharmacy is sending me a text telling me I can refill a prescription by replying "REFILL". But I can't reply "Which prescription?" The autoresponder is too dumb to handle that.
I've been using the Freenode-to-Matrix-bridged Freenode IRC rooms for around a month now and am pretty happy, besides the occasional glitch due to Matrix and its bridges still being in beta.
I still firmly believe Angular 1 got the right pieces into the framework (directives and services), but that the community latched onto some of the extraneous pieces (controllers, controllerAs, etc), which don't offer enough cost/benefit and simply make things much harder to grok. You often end up babying references and being bitten by implementation details of JS and somewhat-confusing names for things (e.g. $scope does not behave like the variable scope of any ES version).

Angular 1 still beats the pants off of everything else in my experience, if you know how to trim the fat. I'd very much like to write more about my approach in the near future.
Ask HN: After Hour Meetings
Whats everyone thoughts on after hour meetings?

There is a few different perspectives im keen to know your thoughts on.

- Meetings with employees

- Meetings with customers of your product

- Meetings with investors

- Meetings with customers of your contracting services

Which cases are ok if any to hold/have/attend meetings before 8 and/or after 5?
Continuous Deployment Design - How we design at Round
Essentially, we're all just pond scum!
You can do what consumers of other things do - buy a sample of each, taste which one you like the best and keep buying that one. It's not like we're talking about taking mortgage here, it's a pack of bacon, costing how much, five bucks?
Kiiah registry reimagines dollar-gifting
TBH it has got to the point now where I just assume people writing these posts are in on the joke and doing it on purpose. At least, I hope that's whats happening.
What games are high reward? In terms of getting you a skill that causes "fulfillment" outside of the game, or gets you money?
Is this trade-off worthy? You gain performance but you are sacrificing huge amount of features. And once you add those features performance will always suffer.
Sarah Paulson's Career Advice? Don't Succeed So Early
Wikipedia suggests cooling of 100 degrees C every billion years.

19 million years is 1.9% of the billion year rate. So it suggests the core should lose 1.9C in 19 million years. That's about 0.035% of the total temp, using Wikipedia's 5700C as the temp estimate.

That's a great initial guess, given how much uncertainty is (i've recently heard core temp could be 4x the wiki number, and some people estimate the earth's core only has lost a few degrees since it formed, rather than nearly 500 degrees). Neat stuff, thanks for providing the opportunity to look in to this.
Baopals: Taobao, Tmall Product Search for English-Speaking Expats in China
Author here. If you have any questions I'm on my bus ride home right now and can answer them.
Let's not forget, Combetta didn't have a security clearance.. just immunity.
Oh I wish! I dreamed of that ha ha
> until they break in a spectacular and often terminal way

One bloke had his Citroen die in such a way in Africa... and had to rebuild it into a motorcycle to get out of where he was

http://www.dailymail.co.uk/news/article-2168061/French-elect...

https://m.thevintagenews.com/2016/05/18/emile-leray-built-wo...
I would: I think that it indicates a propensity to exaggerate.

Perhaps you would, but if so you'd be placing yourself at odds with the consensus definition of what constitutes a "broken bone". Not that it specifically includes "stress fractures":

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

Moreover, I know folks who've had far worse than just shin splints (broken legs, in fact)

I'd continue, but you're going in circles. It's already been established Snowden did not merely have "shin splints."
Wow! That’s what I do (both kinds described by the Wiktionary link). My wife is always giving out to me for it – she just doesn’t understand the dependencies :/. I never realised there was a term for it. Looks like I’m one of today’s lucky 10,000[1]!

[1] https://xkcd.com/1053/
> Having seen how hard many poor people above the age of thirty work....

so agree with you!

poor people often work even more than rich because their salary is low and they have to take extra hustle just to make the ends meet.

Getting a decent salary, which allows getting out of poverty, may free up quite a lot of time.

> "rich" that we discuss here have managed to over leverage themselves such that they have to work hard to meet obligations

agree again :) I think they just carry take a lot on their shoulders just because they like to (thus they "have managed to over leverage themselves ")
Yes, so if you have a uniform distribution of nodes and gateways over space, a node's nearest gateway gets closer as network density increases.
He didn't pick up a pre-alpha nightly build of the framework, he used the release candidate for christ's sake. A release candidate is a "release candidate", that is to say "we're pretty sure we could release this whole thing right now, but we want to send it out to the community to make sure there are no catastrophic bugs we haven't noticed". In other words feature-complete, and with most of the kinks ironed out.

It's sheer insanity to make breaking changes or upgrade the dependencies between a release candidate and a final version. The upgrade from a release candidate to a final version should be the easiest upgrade in the world.
That's interesting they just bought apigee which does about the same thing?
It does not "absolutely" mean that.

It certainly means API changes are not anticipated, and that there should be a very significant problem with an API to lead to an API change at that point; certainly one would hope that fundamental flaws in an API that make it unsuitable for release would be identified well before an RC.

But its certainly possible to have reasons to make a breaking change from an RC (e.g. -- not necessarily relevant to a front-end framework, obviously -- a security vulnerability uncovered that reveals a critical flaw in the logical design, rather than implementation, of an API.)
having your client modify the ZK data is not a good idea, you're bound to cause problems.
Everyone is learning that factoring is a very lucrative business. It's beautiful because 1.5% is an egregious rake that doesn't sound like much...until you do the math.

If you normally wait 30 days for your money, but you opt for next day pay for a 1.5% charge on your $100 dollars in receivables, what's the real cost? The provider earns $1.50 for 29 days worth of floating money on your behalf (you'd get in in 30, but you opt for it tomorrow for $1.50).

Now, let's say the company flips the same $98.50 12 times per year. That's earnings of $18 on $98.50, or 18.25% on the company's money...not bad. But wait. What if the company has a strong cash position and can finance the $98.50 at prime, at 90% of receivables (cause that or better is what strong companies can get). Well, then the company needs to borrow $88.65 for the year, at 3.5% per year (prime rate). The company pays $2.66 per year in interest, out of the $18, to earn $15.34 on their initial 10% of the $98.50. So, 1.5% quick pay actually yields the company 15.34 / 9.85 or 156% on their money.

156% isn't a bad ROI.
"Things that may still change" is generally expected to be bug fixes.

"RC" is not an excuse to flush semver down the toilet. If somewhere in the RC process you realize "this is never gonna work", you call off the 2.0 release ASAP and start working on 2.1 or 3.0 as appropriate.
No no and no. Breaking changes are not ok, not even slightly!

It's not acceptable after an alpha release,
It's especially not acceptable after a beta release.
And it is offensive against developers to have breaking changes from the first release candidate and onwards.

Even for major releases, breaking changes is a VERY BAD thing. But sometimes it is unfortunately unavoidable.
Because Go is my go-to language these days (no pun intended). I really enjoy writing in it, you can produce quality software, and - critically for this project - a high-quality implementation of the distributed consensus protocol at the center of rqlite was available in Go.

With Go I feel like I can get stuff done quicker than C, and still produce high-quality, performant, programs.
I remember when cold fusion came out in the late 1980's. A number of people objected to it on the grounds that using all that cold fusion energy would warm up the planet.
> If people really need to optimize this that's fine, but it should be opt-in, not the only way to do it.

Be careful, you're taking goals of other languages and layering them on Rust. It's entirely valid for a language to decide that the default idioms should not be sub optimal where that's easily achievable. In a language meant to compete with C/C++ on performance, defaulting to a slower idiom when security is not in question may not be the correct choice. In a language that is accepting some level of non-negligible performance loss in idiomatic code already (such as Go), the decision may be different.
The difference is that you're spending time learning about concepts that you are unfamiliar with, as opposed to learning Angulars many APIs.

For instance if you've already spent time learning about Redux you'll have a very easy time re-using those in Angular 2 (with ngrx).
Wells Fargo to Announce an Array of Financial Misconduct Products (satire)
Yes - I would assume so since this is a Stripe transfer, which means it is money being moved from your account to another account, so likely you already paid the 2.9% + .30 on the money coming in.
With Firebase expanding to form an entire ecosystem of services, and being kept alive for a long time now, I have renewed hope that being acquihired by Google won't just be the death knell - at least for this type of service.
If you don't trust the package, nobody forces you to buy it.