skysight-inc/HackerNews huggingface dataset:
Niche FTW definitely. But I think it'd be hard to find something that's "steady". I run my own business and it's always changing -- the market's changing, the technologies are changing.
You can do this with Gmail. Gmail will ignore anything after a '+' character in an email address. So let's say you have fakeperson@gmail.com, you can use:

fakeperson+facebook@gmail.com

to sign up for Facebook, and then create filters starting with "to:faceperson+facebook@gmail.com"
Automation is spreading at an unprecedented rate. Factory jobs are all but gone. More automation has been installed in the last 10 years than in all the years previously.

If somebody cherry-picks data to show 'some job growth' somewhere, and claims that disproves that automation is hurting jobs, then they haven't tried to get a job in manufacturing in the last decade; and forget any chance at promotion because there's no path from 'menial floor box-mover' to anything like engineering or management.
There is a tradeoff that is used to justify the long hours. On the one hand, having a well rested doctor is obviously good for them to be making good decisions. But on the other hand, patient handoffs are dangerous. The more times you change the person responsible for a patient, the longer the game of telephone you are playing with their care. This has been measured as being bad for patient outcomes.

Now, that doesn't seem to justify the fact that long hour shifts are placed so close together. It seems like you could give doctors a longer break in between shifts than they have. Residents have the worst of it. The attending actually do get a fair amount of time on/off. Residents already work a lot less than they did 50 years ago, some think that their training should be extended to cover the loss of density.
I was using Google Wallet for the web. Not a huge number of subscribers, but substantial. Google shut it down with no migration path or notification to Wallet customers. Actually, it still seems to be running, but only for use with Google. (eg. Buying Google Drive storage)

I don't hold too much of a grudge about it, but it has shaped my perception of Google services. Except for the extremely established ones, the possibility of an early shutdown should be factored in before choosing to go with a Google service.
The problem is that if people do this, the authorities will quickly learn to gain physical access to a device first and make a bit exact copy before doing anything else. (Which they probably already do anyway.)

It's as if you've created a computer game for the cops in which they have one "life", before "game over". But they can easily defeat that by "saving the game" before the risky encounter with your data-eating password monster, to give themselves as many lives as they wish.
I don't understand how you can discern any difference between the upright position and the 1-2" recline position. I think you may be kidding yourself.
Async/await is commonly suggested as a lighter-weight syntax.
I've done all three of those things on a reclined seat. Why weren't you able to?
When you can explain to me why you SHOULD be able to make a full living wage putting books on a shelf, or pouring coffee, or putting hamburgers in a bag, you can claim it as a terrible salary.
Who or what is Hastings?
No I'm not sure. Maybe it builds a rudimentary index... but give it a shot yourself and see. 15 seconds after installing, you can search your entire system instantly. It's crazy whatever it is doing.

And yes I do believe it uses the USN Journal to stay up to date.
Does it feel wrong if rent increases to the point that the small coffee shop is priced out of the market?
You don't need AI tor that.
> But why do you trust Alton Brown?

Because I've found the information from his shows has been useful in improving the output of my own cooking. Otherwise, I wouldn't have bought any of his cookbooks.

> If you don't know anything about cooking, you have to trust someone to tell you what to do.

Cookbooks are generally not written for, or primarily marketed to, people who don't know anything about cooking.

> So you need a curator for your curators--a reviewer for your reviewers.

That's what acquaintances you know who have demonstrated proficiency in the kitchen are for.

> Pick a set of recipes for the same dish, make all of them, have an accomplice label each with a letter--so you don't know which is which--and do a blind taste test. Rank the lettered portions according to your own preference, and then your accomplice will let you know which recipe you chose as the best.

This is optimal, but an extreme time and resource hog if you are going to do it with a wide enough range of recipes to be meaningful with no prior filter, and also logistically problematic because many dishes are sensitive to holding time (and because of variability in even skilled execution, you need to execute each recipe multiple times, grade them all, and do statistical aggregation of the results), so you need lots of parallel cooks and parallel kitchens to effectively execute this.

> Trust the objective measurements.

Ranking according to your preference is subjective measurement.

> A little bit of science in your kitchen obviates all need for unearned reputation and trust in trademarks.

If you ignore time and resource constraints, it avoids the need for curation (whether earned or not), in practice, to be usefully used, you need a curated filter in front of the process (but then, it also feeds back into the process of meta-curation by providing information on the reliability of curators.)
Think about it like this: On your list of languages, which of them would you say is most productive?

Define productive.

Are you measuring raw lines of code generated?

Or are we measuring amount of production-ready code?

My bet: with an experienced, diligent developer it's a wash. My gut says what you lose in a slow code-execute cycle of static, compiled languages you gain in lower defect rates from compile-time checks. Conversely, what you gain in a dynamic language, you lose in errors caught at run-time.

At that point I'd select for languages that are simpler with fewer surprising semantics (crossing Perl and Javascript off the list), with more built-in run-time and/or compiler safety (knocking things like C off the list). I generally also prefer compile-time safety over run-time safety, as I'd rather find problems on my workstation than in the field because I missed testing a codepath.
> I don't know if quantum computers exist, but I'm sure once they do, the people who build them will keep them secret.

They not only do exist but have already successfully factorized low magnitude numbers [0]. The question is if an agency with a high enough budget, secrecy and highly qualified personnel did not already scale up the reliability and capacity of existing technology.

[0]: https://en.wikipedia.org/wiki/Shor's_algorithm
It did, for at least one of the commenters.

However my theory is that the dough itself conducts heat better the denser and wetter it is. The bottom of the dutch oven transfers the heat very quickly, but also right at the beginning, when the dough is densest and wettest. by the middle of the cooking time, when the dough is likely to burn, it is actually the coldest part of the pot.
https://www.microsoft.com/security/portal/threat/encyclopedi...

Click "What to do now", all patches are there.
These are going to be 150W+ for sure, heat be damned when you need performance.
It has to me--I have long femurs and the tight seats are already bad enough. When someone reclines, I am that much worse off. I usually sit in a "V" as much as possible or get an aisle seat so that one leg can stretch into the aisle sometimes.

Honestly, I'm pretty much done with flying until such time as airlines come to grips with their management problems.
AMD was a handy workaround, but better solutions exist now.

For one thing, each and every little module doesn't need to be written with knowledge of AMD or how it's going to be imported at all. If you used AMD with this component example, every single component you write would need to be wrapped in a `define()`. This has no wrapping, just standard JS exports.

Secondly, each module doesn't need to know its own name (to pass to the `define()` call), or even have a static name at all, it can effectively be anonymous & truly dynamic.

And finally, AMD modules make assumptions about the environment – for example, that you have control over `window.define`. If you're a third-party script trying to load things on someone else's website, good luck – you either just told someone else's module handler that you loaded, and have no visibility into it, or you clobbered the existing `window.define` and broke other people's scripts. (My former company's product was a third-party JS widget, and co-existing with dozens of other scripts and module loaders was a huge problem.)
So, I just did "npm install next react react-dom" which isn't bringing in next's development dependencies. Is there something that I'm missing?
This is one of those occasions where evidence and material facts are irrelevant, what actually matters is how people feel about using Google products. Is the average developer going to feel confident about recommending a Google service to their manager?
I'm under 5'7", I'll trade you your genetic shortcomings with mine, especially with the ladies;)
It's not that humans are largely evil but about asking people to be less comfortable based on your own preference. Don't recline. Move to a non-preferred seat so I can sit next to my girlfriend. Etc. In some cases this may be reasonable but they're the sort of negotiation I prefer not to get into on a Plane where you're implicitly the bad guy if you say no.
$8B Valuation and no product in the market. It sounds crazy for me. Can somebody put some sense here for me?
I don't know their reasons for WinFS, but I do know that Everything's authors figured out a long time ago how to get great search with Windows' current FS.
Do notation makes this stuff a whole lot more readable (See Haskell). Or Async-await (See C#)
> Another difference is that documentation is essentially annotated today. If the documentation is confusing or misleading, it's usually clarified in a stack overflow or some other forum. Before Google, if documentation was confusing, you were stuck guessing or hacking. That was very time consuming.

I would say that one of the reasons why php (the language) took off in the early 2000s was because of its excellent docs pages: each doc page for a specific function had a comment section where you could find the actual examples of said function being used, by actual people. Pretty similar to what one can now find on SO.
As far as I can tell, the standard library functions don't generally handle numbers that large. Try it yourself in the browser, e.g. `Math.sin(Math.pow(10, 15))`. Floating point rounding errors make computing the sine pointless.
Edge IoT and Analytics: What Is It?
Naively, I feel like the same could be said about appliances, or kitchen items, or software, or food, or vehicles, or ...

"Significant safety issue" seems both poorly defined, and doesn't address the rate of incidence or the conditions necessary to create that issue. Many drugs have safety concerns when not used correctly, for example. Or in small populations.
You just broke your site for 40% of the web. http://caniuse.com/#feat=brotli
>No, the idea that aggregate performance...

You're saying no, but our statements mean essentially the same thing. Aggregate performance rebounds to the benefit of capital holders because they are outperforming. For example, it is better to save and lend than it is to borrow, which is why interest rates exist.

I'm not disagreeing that r > g can lead to greater inequality under capitalism. The reason you can have inequality under capitalism is because you have the opportunity for outperformance. I don't want to live somewhere that opportunity doesn't exist. You can if you'd like.

How can you say that it's a problem fundamental to capitalism when I can look through history and say these things without a doubt:

Socialism is the problem that turns aggregate prosperity into greater relative deprivation and narrow concentration of wealth.

Autocracy is the problem that turns aggregate prosperity into greater relative deprivation and narrow concentration of wealth.

Communism is the problem that turns aggregate prosperity into greater relative deprivation and narrow concentration of wealth.

Dictatorships are the problem that turns aggregate prosperity into greater relative deprivation and narrow concentration of wealth.

It's not a fundamental problem of capitalism, it's a fundamental problem of society.

By doing something to alleviate their immediate problems do you mean help them get clothes for a job interview? Point out a way for them to learn a skill to get a job? Locate a homeless shelter for them to spend the night? The longer you take to reform the system, the guiltier you should feel for not simply helping the person with a comparatively more immediate solution: micro actions. All of a sudden micro actions are meaningful.

Your suggestion for an action on how to deal with the inequality of capitalism is to adopt... not capitalism? I think you're lacking important details on how to turn that into an action.
I didn't say it was a deal breaker?

Your post came off as implying REPLs don't have serious benefits for anyone, which felt a bit presumptuous to me.
I don't think anyone needs to defend the idea that working 2,000 hours per year "should" earn someone a living wage.

How about this: If your business can't afford to pay a "full living wage" for a full time job you "shouldn't" be in business.
What is the shutdown rate of AWS & Azure that you've calculated, and what is Google Cloud's? If no one actually has these numbers, let's assume the perception didn't come from nowhere.
I wonder what exactly they're showing to these investors. We as the public know nothing, but people keep poring in money.
If I were focused so unapologetically on purity over pragmatism at the expense of playing nice with the wider web ecosystem, I would perhaps think twice before holding my site up as a positive example of the state of web development with Rust. You may end up doing more harm than good in the PR department. :)
Arduino IDE in Visual Studio – Visual Micro
Freenome is the company, they're doing interesting work but it's still early days. This isn't actually a very new idea, it's been floating around for years in academia (I've personally been hearing it about it for at least 5 years). The hard part isn't really the AI per se, it's getting enough DNA from the circulating copies (i.e. sample prep) and being lucky enough that the cancer you're trying to diagnose actually puts out enough DNA for you to measure at an early enough stage to be clinically relevant. In other words, if you can only get DNA when it's at stage 4 and metastatic, your DNA test isn't actually very useful. If you can get stage 1 cancers, now you're talking, but in those cases tumors tend to shed a lot less DNA (among other reasons because they're smaller).

A very good friend of mine is their CSO, I think they've got a really cool idea and could indeed go far, but it's a fiendishly hard problem.
Yeah, a good portion of those pins will be wired directly to the power regulator components that are next to the socket, and a good chunk more break out neatly into channels for memory and PCI-e.

Seems like it's almost boring these days since everything's encapsulated in a layer of abstraction. A lot of the more complicated wiring is in breaking out PCI-e channels into things like ethernet, audio, and other miscellaneous ports that involve good chunks of analog circuitry.
> There's nothing you can buy that will actually make you happier.

Nothing? Lots of things I buy make me happier.

The stuff I buy that doesn't make me happy is often stuff that I need anyway (like dog food and toilet paper).
I agree; and didn't say it was dubious. That said; the title was phrased with a slight negative connotation; before it was changed it was like:

Newmark was an idealist; now he's a billionaire

He is likely a paper billionaire but the article didn't really prove to me he's less of an idealist not that he would sell; making that figure hypothetical.

Sure he's rich; but he could be much more so and the reason is ethics and idealism. So too me; I think saying the company is worth x; and he owns most of it fails to consider he likely wouldn't sell and has built a profitable business users love while remaining humble and ignoring greed

Edit: I know of one large anonymous donation he has made personally and I an nowhere near connected or know anyone that knows him personally
After working in healthcare IT, I can atleast attest to the general UI clunkiness and terrible software quality that is prevalent in the industry.

Innovation in Health IT happens usually because CMS (Agency that administers Medicare, Medicaid etc) looks at the landscape and comes up with a carrot / stick rewards system to force Hospitals and practices to update their software. They generally do things like:

* Hey you need to store records electronically. If you do this by X, you will get Y$. If not, you will be penalized Z$ every year after X.

* Hey the system you built - It needs to actually be able to talk to other systems. If you do this by X.. you get the point.

* The data you're collecting in your system is stupid. We need X, Y and Z reports to ensure you're actually using the system as we meant for you to use the system. Do this by X.

Several other misc things I noticed:

The industry by itself is extremely complex with business requirements that vary between hospitals, practices, labs and so on. This makes connecting systems together a nightmare. Even when you manage to integrate systems, each hospital and practice has a set of business practices (forms they collect, the way they organize information etc) that make rolling software out very hard. Configurability is king. Making everything configurable and having configuration engineers set things up makes automated testing very hard at a UI level. This leads to some sharp corners and contributes to bugs and general UX clunkiness.

UX design isn't generally valued and suits / "business requirements" / timelines are prioritised over usable, stable, secure software. This is a typical UI: http://uxpajournal.org/wp-content/uploads/2014/07/smelcer3.g...

Standards are out of date and the only thing pushing innovation here is CMS doing its best. The problem with this is that they're a govt agency, so they're generally slow and they're an insurance company, so their primary motivation is to cut cost of care.

Doctors are generally smart, and you can sometimes get good feedback from them, but they're already overworked and can't really vocalize what they find frustrating about software.

I hate to generalize, but in my experience atleast, all other people (middle management, front-desk staff) are useless. By that I mean they just don't understand how software works.

There are some smart CIOs, but they care about their position and the hospital bottom-line, so trying to sell them something that doesn't exactly line up with the CMS carrot / stick model is basically impossible.
... sounds like the medical equivalent of Jira ...
penis land
I suspect a key difference is that the old Bell Labs wasn't beholden to excessive Professional Project Management running the show and making sure everyone has their nose to the grindstone at all times.

I think that's true, and was also true to a greater or lesser extent in many of the other hotbeds of 20th century research -- perhaps including those embedded in more conventional companies (IBM Research and Xerox PARC both come to mind).

Short of being wealth enough to self-fund, are there any truly low-managerialism research places left today?
>Why should the cloud be different?

Because you're not running the stack. Relying on any PASS that you can't lock down to a version and deploy on commodity infrastructure means you've accepted the reality of being vulnerable to platform changes - and in a lot of cases this makes sense because the benefits outweigh the cost of staying up to date - but scenarios you describe are not one of them.
> Is the Rust community claiming that the entire history of computing has lead up to this point, where Rust exists, and now nobody needs to write anything in not-Rust? Are people 200 years from now going to write Rust and nothing else?

Let's be clear - the person who said there'd be no reason to write in anything else is an enthusiastic Rust user, but they don't work on Rust & don't represent "the Rust community." They were speaking from their own experience, based on their own balancing of the trade offs as a user. Presumably a REPL doesn't rate very highly for them.

However, the reasons we don't have a REPL are mainly two: the compiler isn't architected for it and code doesn't compile fast. The solutions are:

* Re-architect the compiler to support incremental code input. This is pretty similar to what we need to support IDEs (which we're working on), so possibly this will solve the problem.

* Get a reimplementation of the backend which is a JIT interpreter instead of LLVM, which takes up most of our compiletime. Work is underway on a project called miri, though it isn't officially supported right now.

* Make the typechecking part of the compiler faster. This is underway through a project called chalk.

In other words, a REPL is not impossible, it just isn't a top priority right now. There are other lacking tools that we're working on - IDE integration and auto-formatting for example - maybe after those are done it will be the top of the docket.
What's "hilarious" about a site being down?
Maybe OT, but pilots have a lot of time off between shifts and it's starting to come to light that their depression rates are much higher than anyone is comfortable admitting. This may from a different source though, since flying is very much about precise repetition and less about complex decision making (ADM is hard, but not the same level of mental stress that doctors endure), you eventually realize that you're a very highly trained bus driver.
That's just the thing "pay the extra money"--okay, fine, but we are doing this all time just to get back to where we were a few years ago minus the "pay the extra money" part of the equation. It's not just airlines that are screwing us, but grocery chains come quickly to mind, and basically any place where the runaway inflation is being passed on to us all the while everyone thinks this is "normal" and "fine" and all the while I think I'm going crazy because I'm the only one who noticed that 14.2oz. is the new 16oz. and ice cream that used to be sold by the half gallon is now 1.5qt. and NOBODY raises a stink about this?

It is NOT OKAY.

It is the kind of thing previous generations would start fights over when a merchant was so blatantly screwing them over.
That was meant to be sarcastic because essentially that is what they did. The "sponsorships" are more like a VIP membership with lots of extra services. These services have a high margin (unlike books where they compete with Amazon) and now they are more profitable.
Yeah, the Morris worm had some major mistakes too. Later worm authors with seriously malicious intent managed to learn from it, and from one another's mistakes.
Absolutely it's about the administrative end and not patient care. We've got a situation in our regional health authority (Vancouver Island, BC, Canada) where they're trying to roll out a significant update/expansion to their EMR (Cerner-based) in the hospital in Nanaimo. Despite immense pressure, some docs have been now suspended for refusing to use it and switching back to paper, despite the massive increase in time it takes to provide the same patient care, and also because of notable examples where the EMR has endangered patient safety. (Google 'ihealth nanaimo' if you're curious for details, then rinse and repeat for the same story in so many other places)