skysight-inc/HackerNews huggingface dataset:
I keep it limited to "oh, how nice!" as that does not take live birth as a given.
The problem is that a lot of writing from ancient sources e.g. Bible, Confucius etc. get discounted because of the language used. If you actually think about what they actually meant at the time a lot of the time there is a lot of wisdom in it but because of the language used it is too dense for most modern readers.

Unfortunately a lot of atheists just decided they knew everything once they realised that the Bible wasn't the literal truth. Many Christians wouldn't claim that and Atheists tend to point at the likes of Ken Ham to strawman the rest of the Christianity.

However I do appreciate Christianity in Europe is very different than it is in the USA.
Excellent reply. The GO is very impressive and I don’t think most folks have seen it.
People have a right to be called what they want. You even admit she legally changed her name so why not use it? The motivations around her desired name are of no concern to any of us.

Intentionally refusing to refer to someone by their chosen name is wrong whether that name is Muhammad Ali, Chelsea Manning, or Julia Turing. I have certainly seen comments flagged on HN for inappropriateness when they refuse to refer to Manning by her chosen name.
Defacing US currency isn't legal.
Azure is unlikely to ever be a competitor.

AWS - because they really don't have a choice.
Robot tanks: On patrol but not allowed to shoot
Yeah to be honest one of the things that made me skeptical of the code compression / productivity claim is looking at the implementations of Chez Scheme and Racket (after also looking at 20+ compilers / interpreters, and working on a language for a few years).

I'm pointing to them as very long-lived and valuable codebases written in Lisp dialects. Chez Scheme is a 35 year old codebase and Racket is also decades old.

So I'm not saying there's anything wrong with them, but I am saying that it doesn't appear that they're 10x easier to understand or modify than LLVM or CPython (Chez being a compiler and Racket being an interpreter as far as I remember). Or that you can get a 10x better result.

Basically for the claim to be true, why can't you write something like Racket in Racket 10x faster? Like 3 years instead of 30 years. And why doesn't it do way better things than CPython or Ruby? Those claims might be "slightly" true depending on who you are, but they're not devastatingly true. There's been more than enough time to evaluate the claims empirically.

In other words they would have already proven themselves in the market if that were the case. You would have extraordinarily productive teams using these languages -- along the lines of what PG hypothesized 15+ years ago.

http://www.paulgraham.com/avg.html

In fact the thing I found was interesting is that at the core of Racket is a big pile of C code, just like CPython. A year or 2 ago I watched a talk about them self-hosting more, and moving to Chez scheme's backend, but I don't recall the details now.

https://github.com/cisco/ChezScheme

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

https://github.com/racket/racket/tree/master/racket/src/rack...

(FWIW I also looked at and hacked on femtolisp around the same time, since I was impressed by how Julia uses it.)

correction: it looks like Racket has a JIT too, written in C. Still same point applies: it's not magic and looks a lot like similar codebases in C. Chez is more self hosted AFAIR but it's also hundreds of thousands of lines of code.
ApplicationInspector: A software characterization source code analyzer
Not sure I have the same take as you. For instance....

The most important node on the network happens before you were born - it’s the network between two people that had sex leading to your conception.

So, that’s pretty huge, and it’s very early in life. Finally, it’s the biggest, most important node in your life because everything in your life will flow from that node.

So yes, some decisions have been made. As an American, I’m mostly optimizing early decisions (and mistakes). But to a kid born between two refugees in Syria, his optimizations will look much different from mine due to the initial node in his life.
Fuck Epic and fuck being stuck in healthcare development hell
The delivery company is one actor. They lose money every time this happens.
Exactly. From the perspective of high level decision makers, PaaS is heading toward being a commodity good, so differentiating your platform can be what makes a deal and making regulatory compliance "easy" in heavily regulated industries can be a pretty strong differentiator.

If you have an existing business relationship with a company and already trust them to help you navigate regulatory hoops, there's going to be strong inclination to continue to trust them as you expand your infrastructure to the cloud.

Like you said, it's the kind of very smart, long-term marketing I tend to associate with "New"/Nadella Microsoft.
Anyone know what the status of this is or like how close to release 1.0 is? I'd really like to dig in and give a try but it's hard to know just how much time I could waste pre-1.0.

I looked on the status page and it seems like things are moving along to the ~1.0 release, but as an outsider I can't gauge if that's three months or a year.

I'm mostly just really excited for this at there's a great deal of it (Deno) that makes a shitload more sense to me than Node (module loading is one, $HOME/.deno/bin is another); and being so heavily integrated with Rust appeals to me in a big way (I actually understand Rust, but C++ always leaves me just instantly mind-fucked).
There might be some fear of competition. Google is offering healthcare solutions some of which seem to be angled at "owning" the healthcare data. I'm only vaguely familiar with Epic's offerings but a lot of these solutions that Google offers seem to encroach in that territory:

https://cloud.google.com/solutions/healthcare-life-sciences/

https://cloud.google.com/solutions/modernize-legacy-apps/

https://cloud.google.com/healthcare/
Would you consider implementing the first part of the Tiger book as enough expertise to start in the field?
This includes, in my case, generating x86-64 assembly and writing a register allocator.
We Built a Mac App in a Day Using Catalyst
It's fine to "consider" these so as long as they do not impact the performance review process. Because if they do impact it, people are going to game them, and they'll become exceedingly efficient at it. Want more PRs? You'll see dozens of PRs a day. Want more reviews? Get ready for bullshit PRs "reviewed" by the dozen. Want more LOCs? Get ready for massive vertical whitespace and detached curly braces.

But really, as a (former) manager this is trying to solve a problem that does not exist. As a manager I'm intimately aware who my most productive reports are. I know what they do, what they worked on last week (I monitor their PRs), when they work, how much bandwidth they currently have, whether they need to take a bit of a break after a tough string of PRs and work on something fun, whether they're stuck and need to be redirected to something else, etc, etc. I call this "management". Managers should actually try to do their jobs. There's never any ambiguity about who sucks and who doesn't, and you can try to bullshit me, and it might even _appear_ to you that your BS works, but in the end I know who's who.
A femtolisp REPL is available from Julia by running:

julia --lisp
I'm not arguing Medium doesn't have value. That's not what stopped me there. Personally, I love the design of the site and have found some great content there.

It's been quite awhile since I've been to Medium and I was disappointed by the intrusion to access the content I was interested in but more put off with being asked to share data with Google and Facebook on what I read there.

Had Medium asked me to pay for a subscription I would make my choice to pay or not, but being asked to let them tell Google and FB what I'm reading there just feels yucky.

Thinking about my own reaction got me to wondering how others react to it and motivated to let others, and especially authors, know how I reacted and why.

Startup school is big on user feedback. This post generated quite a bit, and most of it was pretty good.
That’s so strange. Does anyone know why they’d want to chat using special hardware?
A vlogger I follow on Youtube (Mark Carriker) was diagnosed just over a year ago. He's recorded everything. From first diagnosis, surgery, radiation, chemo, immunotherapy, trial drugs and now Hospice. It's heart breaking to see someone go through this. Hopefully, a cure will be found soon.

https://www.youtube.com/watch?v=CZ5Sk7x7VwY
I actually doubt that. Lead is a shitty abrasive.
MFA is working fine for me with Firefox on both Ubuntu and Fedora.
The Financial Times article provides a little more depth. It mentioned that Google has already decided to delay the rollout of any general-purpose facial recognition tools, in anticipation of malicious use. The FT article also calls his comments a "call for a moratorium", which is quite different than a call for heavy long-standing regulation.

His comments seem a little more driven by things like the use of cameras to identify and locate Uighur Muslims for the purpose of locking them in concentration camps in Xinjiang, where over 1.8 million Muslims are already detained [0,1], than the more civilian uses of unlocking cell phones and bank accounts.

[0]: https://www.nytimes.com/2019/04/14/technology/china-surveill...

[1]: https://www.ft.com/content/fa6bd0b0-1d87-11ea-9186-7348c2f18...
Very funny. Can you please do statistics and share with us? Number of clicks, conversations etc
If a store overcharged you $5, are you allowed to break into the store after it closes to steal your $5 back? Because that seems to be your argument that you are justified in breaking the law as long as it returns you to some natural state of evenness.
> Yet, in an era in which fact-checking has become a national pastime, podcasts have largely evaded serious scrutiny.

I think one of the reasons for this is that there is more friction involved in quoting and disproving a claim in a podcast, versus a blog post or news article. You can’t just copy/past and then link to a source that disproves the claim. You have to rewind, transcribe, include a time stamp, and the new source.

This is certainly not the only reason, but as someone who has listened to podcasts and wanted to correct things via twitter or wherever, this has been an important factor for me.
I wonder if it would make sense for FreeBSD to switch to Linux as the kernel.
They also tend to ask for regulation when they see stirrings that regulation is on the horizon. Better to shape it then have it forced upon you.
The people who have decided they own all the stuff tell you that the things you need to survive "aren't yours" so that you are forced to labor on their behalf. Sounds a lot like forced labor to me.

You've shifted from denying that jobs are coercive and exploitative, to justifying the necessity of such coercion. Pretty revealing.
No, then everyone will use extensions that support their favorite features and the browser wars will start all over again
I went from 0-60 on prostate cancer in a few days last year when my dad was diagnosed at stage 4 (he’s much better now). I was surprised to find that getting into clinical trials is not so difficult and they’re well catalogued; as an example, check out https://www.cancer.gov/about-cancer/treatment/clinical-trial.... Generally, it seems that promising therapies advance pretty quickly, and oncologists seem to stay current. So, I don’t think there’s quite the level of bureaucracy as you may suspect.

That said, with trials there’s a good chance a patient will wind up in the control group (sad trombone), and a lot of new treatments don’t work all that well, or merely extend survival for a few months in exchange for several side effects. A LOT of trials are also simply studying the efficacy of the combination of known treatments; these trials are safer bets, but they’re also unlikely to provide one with a miracle.

With immunotherapies, keep in mind that side effects during treatment can be severe and potentially fatal. Basically, if you have late stage cancer and treatment works, you almost die from the toxic effects of your immune system kicking into overdrive and blowing up all the tumor cells in a few days. There’s a ton of supportive therapy. If a new immunotherapy like the one in TFA showed promise, all the necessary supportive therapy acts as a limiter on rapid scale-up, even with perfect knowledge sharing and patient access.
In partial defense of "It-will-be-different-for-me" syndrome....

Most grad students and postdocs know that academia is competitive and tenure-track jobs are rare, and I bet many of them can quote the 1:9 statistic (or whatever applies to their field). However, that's just the prior. It's really hard to know your individual likelihood because it depends on a ton of factors that you don't--and sometimes can't--know or control. It really might be different this time.

For example, Cell/Nature/Science papers have a huge impact on hiring; a recent study suggested CNS authors are ~5x more likely to find a job. While you need to work hard to develop a good paper, you also need to be lucky in a lot of ways, ranging from the initial choice of topic to how well your write-up comports with 3 reviewers' whims.

It's also unclear how to weight many other factors. Is your advisor well-known? But what about the department's reputation? Is your sub-field trendy? How does your publication record stack up? I don't think anyone can confidently answer those questions and decide they're in the top 11%
I have thought for years that mindmapping could be way more mainstream but I never seen a useful UI. You are absolutely right, a DAG makes most sense.. it could even be multidimensional. Main problem with UI is the > 2D nature of connected data. All of the maps I've seen with wikipedia is insane to transverse.

I was thinking a textual based system would be easier to version control and source, maybe something similar to mermaid [0].

[0] https://mermaidjs.github.io
I kept having wrist pains and switched to the Surface Ergonomic Keyboard. I also got a trackball. My wrist pain disappeared quickly and is much less likely now. I have the same setup anywhere I work and at home.
Not only is it a word, but Google had to delete the word twice.

https://www.zachvorhies.com/covfefe.html
> macOS was based on FreeBSD

Can you share some source of your statement?
If you’ve never encountered a brain-dead compliance process, you’ve had an extraordinarily lucky career.

Even good and thoughtful regulations get interpreted into nonsensical bureaucratic nightmares by some companies’ compliance departments. The implementations that add disproportionate friction usually don’t achieve the intended benefit either. It’s not people choosing a convenience vs. safety tradeoff. It’s just people who don’t understand the subject matter at all.
I noticed this video on Reddit recently which is an interview with a person with Williams syndrome:

https://www.youtube.com/watch?v=pxZ7aZMFHPE
Not sure about recruiters specifically reaching out to individual postdocs, but in my experience quant trading firms seem to send recruiting emails all the time.
That doesn't mean what you think. See https://deno.land/std/manual.md#linking-to-third-party-code

"Note that we did not have to provide the --allow-net flag for this program, and yet it accessed the network. The runtime has special access to download imports and cache them to disk."
Severe cases are the only ones where treatment matters. Anything works for problems that aren't severe. Preferring therapy to acupuncture is just a personal preference.

The way you identify a serious case is where the forming and/or maintenance of normal relationships is seriously impaired. Therapy is a way of providing needed human contact. It's just not addressing the underlying problem.
Replicating Polyfill.io Using Cloudflare Worker
It's not even necessarily anticompetitive motive (though it usually is). It can arise out of NIH syndrome: "well we know this works because we did it, but we don't have as much knowledge about other things and they might be unsafe, so let's encourage standardizing around this." Whether Sundar is pitching it due to anticompete behavior or NIH syndrome is another question.
A singer apologized, closed his eyes, dropped his head and died onstage
I don’t see how this reasoning follows. The business model is pretty clear - shave everything to the bone and make your profit on volume. It’s like Aldi or wal-mart for air travel. If they had high margins they’d just get their lunch eaten by someone offering better service at the same price (with lower margins). It’s certainly not incompatible with greed.

Edit: reread your last pp and obviously this isn’t news to you. I just don’t share the greed = margins expectation.
Agree. Except I would keep in mind that AWS data egress is very expensive, so if there is any heavy media involved, you would also want to put a CDN in front of s3 with proper caching or you could find yourself with a hell of a bill from AWS.

So if you are serving up just a few megabytes and hit a few million page views you may find an AWS bill for a few thousand dollars.
Not at all, reread what I wrote. It's getting the data model wrong for the problem at hand.
This is a head-in-the-sand move by US companies (not just Cerner and Epic, but the hospital system CIOs). If they really think Google is going after healthcare data, they should keep in mind Google is already working with NHS and has a little thing called the Billion Users project focused on India. The British and Indian populations have the same health problems Americans do. Proportions might change, but the content is qualitatively the same.

Also, I wonder if AWS is pushing their heads into the sand. Particularly now that Cerner committed to AWS but DoD gave Jedi to Azure (Defense Health and VA are migrating their medical records to Cerner). AWS may be pressuring a customer (Epic) to squeeze their customers. Which absolutely sounds like something I'd expect from Amazon.
I was part of the GCP startup program starting Sep 2018 and just had a normal hangouts call with the GCP sales guy. Your experience sounds nuts.
My wife and I had one right before we conceived our son. Getting pregnant again right after softened the blow for her considerably, and now she's fine. Medically it wasn't a great idea apparently, we were just not being very careful.
The title would be more accurate with "My...".

Edit: It's not about "life", in any general sense. It's about human lives.
Personally it's a combination of wariness and weariness.

Wary of getting onto the new–new hotness bandwagon just because it’s the new–new thing, and weary of being pushed into a new–new thing because it’s the new–new thing and not necessarily the best solution for the problem at hand.

Increasing my productivity is irrelevant if it decreases usability or performance of whatever it is I’m building. If it isn’t serviceable, or maintainable, I won’t consider it. If it’s a proprietary solution that depends on the company surviving, I won’t consider it.

For me it’s a tradeoff of risks. Will the benefit of rewriting everything, again in this new language and framework pay off in reduced operational or service costs or improved performance? If it won't, then investing money and time chasing after the new–new thing just seems to be a waste.
Yea, but if Cambridge and Somerville Massachusetts allowed more housing construction, it would be easier for medial research labs to get staff.
> Anything works for problems that aren't severe

That's measurably not true.

The consequences of not working (so long as it's not counterproductive) on an non-severe (so long as not also progressive) case may be less than a severe case, but that doesn't mean that everything works in those cases.
Where is this recommended ? Also SPARQL as a query language is about "how" you want to get to your data (the relationships you traverse changes your final result) as opposed to SQL which is about "what" you want, set algebra. Not to mention the super grotesque format and the performance.
Surely BaaS would be for sheep.
>Innovate or die.

Close cousin to "financially support your competitors and die."
I believe the current goal is by the end of January (and the main blocker right now is v8 inspector support (debugging in Chrome devtools)).

However internally there are quite a few things need to refactor. Since Deno aims for better Web spec compliance, we need an overhaul of the Worker implementation we have right now. So likely existing API interfaces under the Deno namespace is stabilizing soon, but many of the Web-compat APIs still need frequent updates
How is it a right to be called what one chooses?

I don't think I should have to participate in someone else's reality if I don't want to, just like they're not obliged to interact with me in the way I demand. It's always nice when they do, but I don't think people have a special right to dictate these kinds of terms to other people. I think this is especially true when the person being discussed will never see this conversation.
It’s typically visitors on the outside posting on their behalf.
Much gets made of the “elfin” appearance, “cocktail party” personality, and “unusual verbal abilities,” but there’s nothing good about having Williams Syndrome.
You are misunderstanding. That is what I tell people when they ask me if I am excited about my own pregnancy. The first 20 weeks of the latest pregnancy were all hedging and trying to not get our hopes up.
We Should Have Bought the DVDs – An Op-Ed from the Future
The technical term for recognized squatters rights, for instance, is "prescription by adverse possession" or "prescription by good-faith possession". (Obviously varies some by jurisdiction.) The difference is that the law in most places recognizes fault vs no-fault of the possessor, and so the requirements for legal ownership are different, usually about 10 years vs 30 years of possession.

Movable property is much more varied and complicated.
Tax horsepower
I've built apps that used almost every google API available... it is a completely nightmare. Everything changes every few months, and if you don't update your software, it stops working. I swear they do it just to waste everyone's time.
Allocating on the stack doesn't need GC.
I don't think it's insecure to want to understand the motivations of those you're in business with. It's not just about competition either. If you don't know why a business partner is bothering to work with you or your industry, you shouldn't be investing significant resources with that partner, they may not plan to stick around.

Heck, dealing with large scale Enterprise tech, a 10-year roadmap (in terms of updates & support) is the standard. I don't expect Google to have such roadmaps for things they're piloting, but then I also wouldn't build anything critical, anything that might be strategic and core to my business, on someone else's "pilot" project.

Managing a massive business is complex, successfully doing so cannot be reduced to something as simple as "innovate or die".
I've been running Fedora for ~10 years (switching away from {Net,Free}BSD, I was fed-up to re-invent the wheel and the general poor design of the OS / high inertia of the community), and never rebooted once for "performance reason". My average uptime is in the couple of month, always for hardware / maintenance reason. Even my Windows 10 machines is never rebooted because of performance issue.

I don't think I've had much system failure / panics either.
Epic doesn’t “own” any of the EHR data in their customer’s databases. Not sure when “competition “ you refer to can be considered to come from.