skysight-inc/HackerNews huggingface dataset:
> Do you have any example of code that uses await more than synchronous functions ?

But that was not what I was arguing. Rather, I was arguing that await is more common than capturing the raw future. Case in point: The article, where all of the "real code" snippets rely purely on await.

What I proposed was that async functions would always be automatically awaited unless invoked with "defer", because most code is expressed as a series of invocations that use the return value of the function call.

There are times you want to store the raw future as some kind of state (for example, in a GraphQL server you might "resolve" the GraphQL tree as futures), or wait for multiple futures, or similar, but those are, in my experience, the exceptions, not the norm. Most code is:

let v1 = do1().await;
let v2 = do2(v1).await;
// etc.

In other words, serial.
You might want to add TAHOE-lafs to the comparison.
( URL https://www.tahoe-lafs.org/trac/tahoe-lafs )
A usecase / commercial example of it's use would be LeastAuthority
( URL https://leastauthority.com/ )
If that's not enough already, CEPH could also be added.
( URL https://ceph.io/ceph-storage/ )
Good thread for this here https://news.ycombinator.com/item?id=20679387
Oh, and it's raining again

Light on your car light, bullets on tin.
> The dysfunction seems to be at a higher level.

There was a recent thread, about a paid talk at blackhat, by a scam company, and the audience's pushback. It included a thought, something like, that there are communities of professionalism, and communities of "bs", and they are intertwined interestingly in companies and society.

I fuzzily recall reading years ago, a comparison of subway construction management and cost in various countries. One city that worked well, had the professional expertise to manage the project within the government, able and willing to discipline contractors, and a city culture that this was an area for professionalism, not a playpen for political graft and grandstanding.

Cultures have norms of "this you just don't do". A recurring example is espionage during the cold war. You might kill someone. You can certainly seduce their wife. But you don't otherwise mess with their kids.

I've seen some pretty intense loathing of political subculture, from people in scientific subculture, based on conflicts in such norms (around climate change, and "this is useless research" stories).

Boeing's root failure is said to have been an engineering-centered culture being displaced by another.

So I'd like to see work on how subcultures negotiate and accept boundaries of influence. We frequently discuss examples: the sales team that sells software that doesn't exist, and looks to engineering to magically manifest it. And we name local phenomena, like moral hazard. But I've not seen a vocabulary and theory for discussing such at a larger scale, as instances of larger patterns. Which makes it harder to explore what boundaries might enable less dysfunctional execution of large projects.

Perhaps that's one way to explore "dysfunction [...] at a higher level"?
I rather think that it did work. Or, at least, if he continues being successful having tickets for "NULL" dropped. Because any tickets he actually gets will be to "NULL".
Static typing means that types are figured out statically by looking at the source code, and type errors are detected then when it notices a mismatch. Dynamic typing means that types are worked out at runtime by looking at live objects when code operating on them executes.

Strong typing means that types cannot be substituted for other types. In C, you can write `int x = "one"` and the char * (address of) "one" is automatically converted to an int, or in Javascript you can write 1 + "2" and a string "1" is automatically created; depending who you're talking to, either or both of these qualify as weak typing.

They're both spectrums, and commonly confused with each other.
Could you link me to one of those? I don't seem to be able to find them.
Near collisions of logos (i.e. off by a few pixels) would register as different. You don't want to rely on trademark suits to kill those logos, as it takes a lot less effort to create a logo than it does to sue it out of existence.
> Not automatically coercing values is all that strong typing means.

It's at best a colloquial term and it's misleading to non-technical management.
And what's wrong with porn and blogging about genders?
Why must understanding be conflated with utility?
Not sure I agree. There are plenty of curated resources and institutional frameworks but the last time I took an online university-affiliated class I would have learned more and saved time by simply reading a book. I think being broadly educated is partly having the capacity to delve fruitfully in to unknown domains and grapple with unknown semantics. Perhaps I am biased: my mother was a librarian.
Use a different domain then?
Agree. I have an ebike and commute 8 miles each way. It's been fantastic and I arrive home in the afternoon feeling fresh despite it being 95F out.
What about the shiny metal throttle?

http://propsummit.com/upload/408/tt4.jpg
Yeah I don't disagree. But even there you would have similar other considerations besides the language. Like most still end up with C/C++ there even though there are others like Crystal, Nim, but you just don't find developers who know them easily, nor do you have any ecosystem support.
We have a few ways to ensure you don't send us PII. Sending identifiers like user name or email exist as an option in the SDK, but it is an opt-in integration step and not done automatically. We also have an option to capture screenshots, but again this is something that customers have full control over so that sensitive parts of the app are not captured. And we built a remote kill-switch for screenshots if a customer didn't get their integration quite right or something unforeseen happened. If you have sensitive data in URLs we allow specific URL patterns to not be captured. Was there any specific type of PII you were primarily interested in seeing masked?
We use teams at work. Most people i know cant stand it. Its chatoix UI. 10 tabs on each «teams». Ive deleted the app. Whenever someone tags me i just open their browser app, reply and close. Even having the tab open sometimes causes cpu and memory spike and my laptop fans starts wirring. If they kill skype/lync for teams, MS is making a huge mistake. Lync and Outlook are the most distraction free softwares we use.
Yes, but after sitting down 20 minutes or a day and learning how async/await works, for the rest of your life reading async/await code is clearer than seeing nested callbacks upon callbacks.

The same way code using functions is easier to read than looking at the exact same code expanded in 20 places in your program, even if a function call also has "magic" (passing the arguments on the stack, replicating the behavior inside the function as it was written in the place of invocation, sometimes inlining, returning, moving the stack pointer again at the end, recursion, and so on).

You learn once how function works and that's it. More compiler behind the scenes work ("magic") than writing the same lines again and again, but easier to read.
So they bought it, murdered it then sold it for scrap. How is this not considered gross financial incompetence?
The same concern definitely crossed my mind as a reader, but I think the coloring of the critique should be less #000000 and more #888888. A lot depends on the technical goals of the "P++" variant - and on the culture among the language maintainers.

* If everyone generally views both language frontends as equal and shared responsibilities with valid technical rationales and only some specific/reasoned differences, then it's probably sustainable.

* If the team becomes polarized, or if one subteam wants to substantially reinvent their language ("Let's make it purely functional too! Bring on the monads!"), then yes... they'll feel hamstrung.

It might be interesting for them to consider comparisons with other systems that support multiple language frontends, e.g.

* GCC supports C and C++ (not to mention C++11, C++14, ad nauseum).

* HHVM support(ed) PHP and Hack

* JVM and CLR both support a range of language frontends.

My guess is that GCC is a more favorable analog (it feels normal+realistic to support C99 alongside C++11 and C++14). JVM/CLR seems like an unfavorable analog (they've supported many very different languages... but involve many large teams and diverse technical specs).

HHVM is probably the most pointed analog. It's just... mixed. On one hand, HHVM succeeded in supporting two similar languages for a long time (in spite of significant idiosyncrasies of PHP). On the other hand, HHVM eventually gave up on PHP and went pure-Hack. But (as an outsider) I'm not really sure the reason. It could be that they got boxed-in on a technical issue of language-interop, or it could be they got boxed-in organizationally (being a separate team maintaining a secondary implementation amid a continuous drip-drip of external changes - not a great position).

I interpret the original link above as basically an assertion (crude paraphrase): "The HHVM folks were broadly right about PHP and Hack and technology and all that; but their implementation hasn't succeeded on organizational grounds, and we-here can do those organizational things better."
The docs don't say anything about it, the integration works the same way as for native android?
seems like you are completely missing the use case, if you think EV certificates are for frequently visited website.

I, for one, always make sure my bank has EV before I enter the password. the fact that most people don't doesn't change the fact that it does provide additional trust for those who are aware. security isn't all or nothing.

the second use case is when you first visit a website, which potentially asks for credit card number or anything sensitive, it does improve your trust and reduces the friction with lesser known websites. of course PayPal, as a well known and trusted website doesn't need it - nobody is asking themselves if they should trust PayPal. again, it's probably not a security boundary, and it's probably not impossible to generate bogus ev certs, it's better than nothing.
You should probably be angry at the CAFE regs too. It's what (supposedly) had prevented all the manufacturers from selling a small pickup, which is why Ford stopped selling the Ranger. They basically switched to making the F150, then making it larger (actually, I have suspected without proof that what they did was move models downline - sometime post 1990s, the F150 became really larger - the size of that era's F250, and the F250 became the size of the F350 - Ford's re-introduction of the Ranger? About the size of the 1990s F150...again, I have no proof of this).

Lots of people want a small pickup like the Ranger (Toyota also followed along - compare sizes of the Tacoma of the 90s vs today - I suspect they all changed in size), but they can't buy one. It has something to do with CAFE rules, plus some weird calculation of area - so the larger the vehicles footprint, the more it'll pass or offset or something; I'm not sure how it works.

But something changed in the 1990s - and now we have this.
I was thinking about singular they and its derivatives: their, theirs, them. Plural they is also gender-neutral, but its usage is not new nor controversial.

Defending the use of gender-neutral pronouns was not my point, but since you ask what purpose they would serve, here are some reasons I can think of (and this answer is not limited to English):

- to avoid having to specify or think about the gender(s) of the referred person(s), which may be unknown or irrelevant to the subject (to illustrate what I am saying: for instance, if a scientist found something, I don't really care whether they have blue eyes, or breasts, or testicles, or red hair, right, and if I cared, it would still be irrelevant to the discovery in most cases - not always, though: https://www.nature.com/news/male-researchers-stress-out-rode...).

- some people who prefer to be referred to using they (I know some personally, and there was a submission on HN whose author wants that we use they to refer to… them). We therefore should use "they" for them.

- some people do not see themselves as neither male nor female, so a gender-neutral pronoun is convenient for them, and for other people to speak about them.
The assumption that Tumblr's loss of users is entirely or even mostly due to suppressing adult content is probably unwarranted, but I'd be interested in data either way.
Thanks for the insight, this makes a lot of sense.

What about when depth adds complexity and over serves some of your users. Is it worth it at the early stages of development to spend the time keeping the software simple for those users who don't need the additional functionality but available to those who do? Or do you just leave all functionality in there that's required by all of your known users, train the early adopters who don't need the additional complexity to sift through it and then once your customer base is more representative of your market you worry about simplifying workflow?
Then it’s a corpse.
As I've always said, you can use CSP in Rust. Just use threads and channels. They work great, and they even scale well on Linux to all but the absolute most demanding workloads. If you want a Go-like M:N scheduler, we've got that too: use mioco.

CSP as implemented in languages like Go is just threads, but with an idiosyncratic implementation.
unwanted dilutions, share issuance dilution scams, controlling share dilution schemes, clawbacks... there's a lot of unpleasant things that can happen to minority stakeholders
Plus one for tutanota. I've been using tutanota for years and love it. And the recent calendar feature is great.
EV had one advantage: It allowed browser vendors to push for improved standards (like Certificate Transparency adoption) with minimal push-back. It's easy to complain about expensive security measures for run-of-the-mill certificates, it's much harder to argue about such measures for special extra-secure ones.

And since CAs wanted the EV cash cow, they implemented CT and other improvements, and once they had the code, they had little reason to object against applying the same requirement to regular certificates.

Another advantage is that when my bank requires me to enter a verified-by-visa password on lookslikephishingbutreallyismybank.com, I can actually verify (with a reasonable degree of certainty) who the site belongs to - even if they could, attackers generally won't go through the effort of getting a similar name. But that's a power user feature.
I wouldn't be so sure - at the more desirable schools, tuition is mostly a function of what people are willing to pay. That is why it increased so quickly.
Creative... I've not done it, but it seems if I get a really good scan of a ticket, put my info on it, and use it as needed, they don't have a record of it. So I'd never get a fine.
Full Stack or Back Engineer w/ METEOR in SF,CA
Qualia is HIRING to grow our talented team of
Full Stack and Back End Engineers in SF,CA!

Founded by Stanford Alumni,
Qualia is a real estate tech platform company
revolutionizing the home buying experience.

Collaborate with an all-star team of brilliant and fun engineers,
Opportunities for leadership, ownership and growth,
$40M raised by top SV investors, including Menlo Ventures,
$20+ million in annual revenue,
Growing fast by 100-200% annually,
Cool tech stack: Meteor, Javascript, Semantic UI, Mongo DB, Docker, AWS, GitHub, and Python, Ruby or Go.

If interested, then please send me your resume
to deeann@qualia.com.

Feel free to also forward this to an engineering friend
that you’d love to work with & qualify for a $5k employee referral bonus!

Let's connect @ https://www.linkedin.com/in/dlmahoney/
If I'm reading this right, the 29% and 6% are the same drug. It has a 6% mortality rate when administered very early in the illness.

> The monoclonal antibody cocktail produced by a company called Regeneron Pharmaceuticals had the biggest impact on lowering death rates, down to 29 percent, while NIAID’s monoclonal antibody, called mAb114, had a mortality rate of 34 percent. The results were most striking for patients who received treatments soon after becoming sick, when their viral loads were still low—death rates dropped to 11 percent with mAb114 and just 6 percent with Regeneron’s drug, compared with 24 percent with ZMapp and 33 percent with Remdesivir.
Volvo's selection of engines in the UK has always been lacking. Tbf it could be due to an actual technical issue with adopting the drivetrain to right-hand-drive car, but in general I see that many manufacturers just pick a few engines that they think the British customer will like and that's all you can get, while people in France or Germany get the full choice of all drivetrains. UK vs US is even more funny because it's extremely common to see cars which are only available with a diesel in the UK, but only available with a big petrol engine in the US. Again, it's based on what the customer supposedly wants.
Much-needed Outline.com of the article: https://outline.com/MJaPqX

Wired.com is almost literally unreadable. It's a caricature of all that's wrong with modern web design. Is everyone else seeing what I'm seeing? http://u.cubeupload.com/temp9871/wired.png
I don't know. A lot of these issues (and I must admit I totally lost interest at the point I got to the complaints about message threading, although I did skim to the end[1]) are really personal preference. Take message threading as an example: we use it all the time and it works well. I actually prefer it to Slack threads.

My main beefs with Teams are:

- Performance: it's just far too damn slow to switch views.

- Awkward to switch back to a channel or another chat whilst on a Teams call.

- Connectivity: it's better than it was at handling disconnection and reconnection but, overall, it's still a ####ing moron and a timesink - you're still forced to restart on occasion (which takes too damn long).

One thing I do like: when our company switched from Slack to Teams[2] what I very quickly noticed, and what has persisted over the last year(ish) that we've been using it, is the much higher SNR. Maybe it's that Teams isn't so fun to use but, whatever the reason, there's just way less distracting guff being posted and, perhaps to my surprise, it turns out I'm quite happy with that.

Slack gives the appearance of productivity and collaboration without any of its substance. Teams, well, it's still an IM system and therefore always going to be subject to some level of wrath from me, but for the most part it feels like it does what it does well enough and doesn't try to be the centre of attention quite as much.

[1] Where I was mildly irked to read, "Microsoft Teams is the solution that nobody asked for the problem that nobody had," in the conclusion. I mean, really, if you're going to say that you ought to be honest enough to acknowledge that you could say the same about any current gen IM app. I certainly never asked for software that would make it even easier for people to keep disturbing me when I'm in the middle of something else, and I know more than a few people who feel similarly.

[2] Teams came with O365 and losing history with Slack was becoming a problem, but not one that felt like it was worth paying what Slack charge to solve: we felt like there were better ways to use that money, and overall - and after initial reticence - I'm happy with that decision.
Lots and lots of legacy systems do this, very low limit, case insensitive, numbers and letters only. I know of a major retailer with 10 character, case insensitive, alpha numeric for All their systems. Why? Because that’s the lowest common denominator (as400).
How can you help? It sounds like this is something that needs Google’s direct attention.
Permabanned by an admin and founder after 11 years as a user? That's actually quite impressive, unless you did something obviously outrageous.
So when you get to that edge edge case they drive a mini-van. No one is saying ban cars, just use them less.
That, or received a second ticket. It all went to the plan that time, at least.
The day robots beat self-replicating devices is the day we all get retired.
The incoherence of EV as a response to phishing is part of why it's failed. But I'm not talking about EV; I could care less about EV. I'm addressing your (false, increasingly so as thread deepens) claim that HTTPS doesn't require any form of PKI and that users might as well rely on self-signed certificates. Obviously: no.
Small claims is pretty accessible. This isn't exactly lawsuit of the century stuff - their actions defamed and harmed you monetarily which is exactly the sort of issue our tort system was setup to deal with.

Note that if it was your own bank that defamed you, then you may have signed an arbitration agreement.
How you would know that? You only could know after it happened. Evolution is random.
I prefer Teams to slack. I haven't used slack in a couple of years, so it may have improved since. For Teams, I like the built in screen sharing and the fact that you can share a window rather than a screen. I use 43" monitors so sharing full screen is impractical for someone viewing on a laptop. The voice / video "Teams meetings" are also pretty handy; we would do remote standup using that. I am also able to turn off audible notifications. I'm probably biased because I've been in Microsoft shops for years.
I don’t know how Google evaluates link aggregators. My comment was based on how Google evaluates content sites right now. I’m not saying it’s fair to Examine.com’s researchers and writers, as most of the replies to my comment appear to assume. I should have made that more clear.
Now that I think of it, I'm not actually sure whether I knew before that it was official or not. I've definitely been using it for a long time now though, so I'm happy to hear it's in good hands!
> I'd honestly be surprised if any of them do HSTS properly.

Maybe I'm missing something, but what would an MITM proxy have to do here as long as it passes the HSTS headers on to the browser?

As far as I understand, HSTS changes browser behavior in two places:

- A browser will always connect to a domain via HTTPS, even if the URL says HTTP.
- TLS errors become unskippable.

Both behaviors are carried out by the browser and are not influenced by the specifics of the TLS connection itself (as long as a connection can be established).

> You can run dev builds - usually even the official ones - to turn most of those security features off. They're intended for your average non-power user.

But this is about average non-power users. Because the current trends force those users to place their complete trust in browser vendors or website operators, even if there were local administrators or third-party tools who could do a better job.
How about Imgur? And Reddit?
tumblr blogs began moving their audience to instagram and twitter years ago

instagram and tiktok are where kids are building their brands now

the nsfw sphere is on twitter/reddit

tumblr is/has been dead for years
I see this as great news; my first reaction to hearing it was excitement. A lot of comments here are talking about the porn but outside of that, tumblr has a community with a uniquely sardonic sense of humor and is a platform for a host of independent artists and creators, and I would be incredibly sad to see it die. IMO Automattic will make for decent stewards of the platform (hell, anybody would be better than Verizon + Yahoo) and I have cautious optimism for tumblr's future.
This is almost certainly what happened. Search YouTube for any political subject and you will only see videos from channels with a check. It’s just a dumb hard boost, on a hand selected list of authoritative channels.

I wouldn’t be surprised if the Google change is essentially the same, just without the visible check marks.
Okay, fine, we should build out public transport and start designing city and suburban features around public transport.

Is that satisfactory?