skysight-inc/HackerNews huggingface dataset:
> Assuming a closed dating pool (both geographically limited and no turnover over time)

I addressed both of those in my post:

1. Yes, you can theoretically date women in San Francisco if you live in San Jose. No, it will not be pretty. You will end up commuting for hours each way. Also, the ratio is bad in the whole Bay area, not just in San Jose. So even if you're willing to spend hours on the 101 every time you want to see you partner, it's not like it's easy to find dates on the 101.

2. There is turnover over time. The Bay and especially SF keeps getting less affordable for anyone except techies. As a result, mostly male techies move in, and more women leave. So it's not static - it's getting worse.

3. Of course there are some gay men and women, but the majority of men are still heterosexual. So out of these 27 men, maybe a couple would be gay. Balance that against a 5-6 gay women, and it's a wash.

Saying a huge 100/134 gender imbalance "means nothing" is extremely inaccurate.
That's called a predicate and is used in Scheme as well.
Information Facebook / Google store about you without you realising
A Mastadon instance for technology folks
Facebook May Have Consent, but Not Approval
I've read that there are quite a few people who sort of 'grow out' of their aspergers, often when they find a suitable partner. While obviously they might still be neurologically different, as a result the diagnosis might not strictly apply anymore.
I think GP is referring to the fact that dep may not remain the blessed solution for long; recently, Russ Cox posted a number of articles suggesting looking into alternatives https://research.swtch.com/vgo
The ones I've been in are roughly 60% grocery store.
No kidding. I'm so impressed with most of Go, but this is just silly. I feel like Rust started out with solid dependency management in place, at least it's been there from the early days. I work a bit with Node and Ruby too. Both have solid dependency management in place. I mean there are warts, but generally the problem is solved. Actually, now that I think about it, Yahuda Katz has had a hand in working out dependency management for all of those technologies, Rust, Ruby and Node. Maybe the Go guys should bring in Yahuda to help out. If nothing else, he could probably help them get out of the paralysis of analysis loop they seem to be in here.
A nice .io domain and endorsement by a hot tech company, I guess.
I don't want to waste my prime dating years in a very tough dating scene, unfortunately.
Post is referring to async programming in node's callback style (non-promise-based functions executed asynchronously) where return values cannot be captured even if you want to.
The P90 in the US is largely restricted to military and LEO, there is a variant, the PS90 with lower capacity (30) and longer barrel that is available.
the 5.7x28 round though isn't as effective in many ways at /killing/ people as other rounds. It's more intended to wound, and increase attrition.

If you want to see something more affordable, that is probably equally as, if not more deadly, look at "AR" pistols (chambered in 5.56x45) instead of the P90. (Or PS90).

Or, the SIG MPX, which while expensive, is also available.

Though, it sounds from your comment, that you and I are on very different terms in opinion.
Explaining Showering (2005)
The consequences of using a store loyalty card are not known to the general public either. Yet all transactional information is sold off to third party data brokers and aggregated into profiles where they keep track of you in minute detail. It isn't exactly fair that Facebook is going to be punished while the rest of the industry hides behind its fine print.
> For all practical purposes dependency management for programming languages is a solved problem

It's obviously not solved satisfactory.
This is why medtech has the FDA, and why the FDA has actual teeth.

"move fast and break stuff" is bad PR if you're facebook. It's a game-over felony if you're making medical devices.
Git Client Tower Launches It’s First V3 Public Beta
My initial reaction to Minimal Version Selection (MVS) is concern, that developers won't get security updates and bug fix patches in their dependencies applied.

But dependency software has been trending toward the use of lock files for a while now - and without explicit developer intent, those won't get bugfixes either.

I think I'm mostly concerned about how this affects transitive dependencies. My package Foo depends on Bar_1.3.0, which depends on Baz_3.2.4. If Baz gets a security update to Baz_3.2.5, either I need to add an explicit dependency "Baz_3.2.5" to Foo, or wait for Bar to release 1.3.1 that depends on Baz_3.2.5.

If go adds tooling to identify and make these transitive dependency upgrades as easy as "npm update", then I will be a little bit less uneasy.
Competition only works if the customer has relevant information. For a cable network's customers it's instantly apparent when their internet speeds suck; it's not apparent when someone sells your private data.

It doesn't matter that the information eventually comes to light, because they're the dominant social media company by that point, buying up their competitors, and it takes a lot more to get rid of them.
Yeah, right. I wonder how they got that number.[1] The people who immediately hang up on robodialers and block phone spam using caller ID probably weren't included in the survey.

[1] https://www.marketingsherpa.com/article/chart/how-customers-...
I just jumped onto Mastodon and love the community on this instance. All the conversation is based on technology or non-technology.. I mean, I know those categories are mutually exclusive but this is the perfect balance.

And unlike Twitter's echo chamber, people love to converse! Every single toot has had a reply, even my first "Hello World!" one.
Why not just put the full version number in the import path?

Both the manifest (dependency section) and lock files become unnecessary. It’s DRY.

Dependencies are specified where they’re used, improving componentization.

Upgrading and forgetting to update one location is easily fixable: tooling already scans go code for a list of imports, modify this to warn on version differences. Or even to update them.

Git history gets “cluttered”, but shouldn’t it be? The behavior of values in a file is changing. This constitutes a change of requirements on the file’s code, or at least needs a moment’s review to decide the code needn’t change. Seeing that change in history would make tracking down any bugs it causes easier. Besides, we’re talking more files changed in a single edit, not more edits.

Semantic versioning is a qualitative description, not a guarantee. Due to edge-case use or human error, every minor or patch update may be a breaking change. It would be better to have a layer of human interpretation between semantic versions and code changes, rather than tooling that assumes them to always be correct.
The regulatory costs of running a bank are much higher now than before the financial crisis. This means that the chance of an upstart challenging the big players has actually gone down, even though some of the regulation was meant to address concerns of "too big to fail".
I agree that the thrashing is a nuisance, but the 'reinvention' has nothing to do with Google except that Go didn't ship with a package manager by default because it wasn't useful to Google for the monorepo reason you cited. Regarding "features forced down our throats", I think that has only happened with aliases, and the community pushed back to the effect that the feature addition was halted until the community had time to properly review it. Mostly I think that was a one-off problem.

As for "it's a solved problem", is it? Until perhaps the last year, pip, npm, and most other package managers have been plagued with serious issues. I'm not fond of the situation in Go, but I think it's not unreasonable to try something different and less binding than a package manager until a solution emerges which solves the problems faced by other package managers.
Sure, but if you somehow manage to screw up the indentation then no IDE can possibly restore it for you because the information needed to do it is lost. And there are a LOT of ways that indentation can get screwed up. If your code ever leaves the Python ecosystem (e.g. gets published on the web) then all bets are off because the entire digital world outside of the Python-sphere is built on the assumption that whitespace is fungible.
This is interesting. Right now I'm of the mind that the best I can do is to continue to press on the inherent contradictions.
You are completely wrong. I have lived my entire life in Delhi and I can tell you that there is rampant caste discrimination in urban India. I can cite many anecdotes but usually the denial of discrimination, which your comment does, is in itself an indicator of bias.
Not at all, I'd argue this whole Tabs/Spaces, bracket placement, single/double quote discussion should be getting killed by code formatters.

At the end of the day you can do whatever you want with the code you're writing, and some pre-commit hook can run go fmt/prettier/whatever and then it'll all get standardized.

I've become a very heavy proponent of code formatters (I added prettier to the entire team) and I truly believe that talk about code formatting will never really die off, but at the end of the day you can do whatever you want on your side but still have a standardized looking codebase, and that feels extremely liberating to me.

As a PS: If you are a diehard tab proponent/different bracket placement/whatever but your team formatter configuration uses spaces instead then you can also use code formatters to do spaces -> tabs locally, say, on file open. Once you commit your file your precommit falls back to the team configuration, which removes your tabs. Everyone is happy.
It is just the reality of the situation, when you publish something on the internet and then delete it, even if it is an entry in your private blog that runs on a Raspberry Pi on your desk if you had at least one visitor you can't guarantee they didn't save a copy and that hey won't distribute it again later.
> because it is based on the idea that there is an element of chance inherent in who gets sick

That statement is true, but health "insurance" covers lots of non-chance things, because it covers lots of things that are not a result of "getting sick". Some examples:

* Birth control.

* Basic childhood vaccination.

* Well-child checkups.

* Annual health checkups for adults.

* Basic screening tests for adults (mammograms, colon cancer
screens, that sort of thing).

All these things should be provided, imo; insurance is the wrong vehicle for providing them. Politically, I _think_ (hope?) there would be a lot more support for "provide all children with basic health checkups" than there is for the ACA. Of course there would be less support for the "birth control" item, which is why people like to bundle these all together, and with things like emergency medicine and end-of-life medicine. Which are _also_ quite different in terms of their risk profiles, tradeoffs, and elements of chance.

It also covers some things that in an ideal world would not be chance but are in practie (e.g. routine births with no complications; they are more chance than they should be because as a society we suck at birth control, on both the organizational and personal level).

I really wish we separated our "health care" a bit more along some of these axes, because I suspect that the "right" answer is to have single-payer for some aspects of it, an insurance scheme (private or public or both) for other aspects, and "you're on your own" for still others, with expensive and invasive end-of-life interventions heading this last list.
I've worked with kids with autism, I can tell you your comment is very accurate in my experience. The amount of difference between kids with autism (in the way it presents itself) is huge. Its not a single disorder.
The gun just doesn't fit as a product that can be made obsolete by future designs. Most guns were designed for the military to be field serviceable. Any attempt to make a cheap gun will just push consumers back to the established platforms. So the gun industry can't be run like other consumer industries, as we have seen with this bankruptcy. Investors came in thinking they could bleed an established brand of it's value, but evidently, consumers noticed and moved on.
I speak Spanish (native) and Italian (fluent) on top of English (best language).

I found French class hard growing up. Until I realized that this "latin" language had as much in common with English as it did my two romanance language.
Show HN: Tool to Convert a YouTube Channel to an Alexa Skill
website: https://www.alphavoice.io/demo.html

Alpha Voice helps you create voice applications for Alexa without coding. Convert your Youtube Channel or Podcast to a voice application in 10 minutes.

Looking for Any and All product feedback.
I found this bit particularly chilling in the context of high school shooters:

https://en.wikipedia.org/wiki/FN_P90#Ammunition
Greeplum, Postgres and PostgresConf
What platform are you on? I've experienced no major issues with the vscode vim plugin on Mac or Windows.

The escape key issue you mentioned was the only problem I've also had, but it's due to conflicting keybinds between the vim plugin and the vscode bindings for dismissing notifications and context help. I rebound all of those to shift-esc (and I believe the plugin's bindings now do this by default) and the problem went away.
This is purely related to private equity shenanigans and has nothing to do with the recent protests. Speaking of which, it's an interesting paradigm shift that people typically march for rights, but this weekend's marches were aiming to remove others' rights.
Since this is Hacker News, it's worth noting that the Remington Arms company (Remington Outdoors) and Remington-Rand (maker of the Univac, latter merged with Sperry and turned into Unisys) started out as the same company. Remington-Rand in fact produced a version of the famous "M1911" automatic handgun (well after the arms company had split off from Remington Typewriter)

The Wikipedia entries on these companies are quite thin, actually, but you can follow the thread, if you care, this way:
https://en.wikipedia.org/wiki/E._Remington_and_Sons
https://en.wikipedia.org/wiki/Remington_Rand
Why does this make sense? Do the owning companies get to rid themselves of debt they transferred to the child company?
Considering the fact that it's an incredibly expensive rifle and that a quick FBI crime stats search shows no usage of it, and I cannot remember ever hearing about it being used in a crime, there's a high likelihood that nearly every owner of it uses it recreationally.

How many Porsche 911 Turbos or Audi R8s are used as getaway cars for bank robberies?
It says it is reproducible but is depending on mutable git repositories? In an earlier post they mentioned proxy servers to have some kind of cache, will there be an official one?
Sadly, they've changed the extractor design on the 870, which is prone to breakage... Making the cheaper Mossberg 500 a better alternative at times.

Though, I do have a major soft spot for the 870 as visually it's much nicer.
I think you're missing his point. What good is a diagnosis if its not accurate?
The (undeveloped) argument seems to be that the costs for university research are borne by everyone (don't start about tuition) but only few people get to enjoy the fruits, and they get to do so disproportionately. A successful founder has wealth measured in tens of millions or even more (when Joe Schlessinger sold Plexxikon it was for 805 millions says Wikipedia), but any drug that falls out of it is expensive and might not be covered by your health insurance. This is a problem.
Where does this leave things relative to previous years? Does it completely counter any cuts made in recent times? Counter them over-all but still leave some areas under-/un- funded compared to a previous state of affairs?
This is great news and all, but I thought that the administration wanted to slash research spending? Did they change plans, or is this how US politics works.
open about:blank, right click, inspect element, start hammering code into console. You can still get pretty far with plain JS these days without touching the quagmire that is modern webdev world.

Sure there are some other issues in picking JS, but it is both readily available and (somewhat) scalable to "serious" projects.
The slow scrolling key-repeat issue was recently fixed.
Adult Entertainment on Blockchain, Spankchain CEO Ameen
Debt holders should be suing the private equity people for their losses. Otherwise it is a loophole that is easily abused.
I agree with you, but FB has been pretty blatant about how they misuse their user's data. If you are the biggest and most obvious, then you will probably be the first one targeted.
Ask HN: How low can Facebook stock go?
Does anyone see this anti-facebook wave putting the company into oblivion and wiping most of its value?
For public companies in the US, they are mostly incapable of making decisions like this as if can be shown to negativity effect enterprise value they can be sued by shareholders that do not have the same moral issues.
Is there an announcement of some kind of change? Are they still owned by Google? Or is this the thing where sometimes existing solutions will hit the front page of HN? :)
Just give me an opinionated ${LANG}fmt utility to do it for me so I don't have to care and don't have to waste time arguing with other zealots. Let the tool be the zealot.
Faster communication and cooked birds to eat, what's the downside?
> Most people don't understand restructuring and professionals call it bankruptcy too.

It's called bankruptcy because it is, in fact, a form of bankruptcy established in the Bankruptcy Code under Congress’ Constitutional power to set uniform rules for bankruptcy. See, e.g., the info about chapter 11 reorganization bankruptcies from the US Courts website:

http://www.uscourts.gov/services-forms/bankruptcy/bankruptcy...
I agree with you.

I think the statement (ish) “don’t use if/else, use return” deserves some qualification, and one natural place to use it is for errors.

When people start dropping returns all over massive multi-screen branching and looping structures, readability may suffer, and debugability quite often takes a big hit.

In general, I like to use guard clauses for any big at-entry branch asymmetries. If they’re farther down the logic tree and/or unwieldy, it may be time to call some more functions.
It does specifically mention the DOE Office of Science, which is part of the DOE budget, so they can apparently recurse beyond the top level.
The National Debt: Why Fret Over Something That Doesn't Exist?

https://realmoney.thestreet.com/articles/10/25/2016/national...
Deleted mine as this is exactly what I was trying to say.
It's not that the author didn't get to chat about people's lunch on Facebook every morning. It's that the author wasn't invited to things he should have been invited to because to many people, "I invited everyone from my FB list" sounds like they invited everyone they reasonably could. Which is not true. The author explicitly says that he is easy to find. And his school friends should take the extra several minutes to searchengine each person they didn't have on facebook if the event is relatively big and organized. It should be the default response. And the author is rightly frustrated that it isn't, because people are lazy and can unintentionally be careless.

That isn't comparable to not being invited to a spontaneous dinner in 2 hours at 9PM by someone clicking invite all of their contacts list tagged as classmates because you're living in the mountaints a one-hour flight and a two hour hike away without any communication tools around you and you don't even believe in flights.

I don't mean these examples to sound flippant, they're here because I'm trying to underline how there's reasonable compromises between convenience and being a good friend / event organizer, and not being on facebook doesn't make you hard to contact. It definitely didn't in the case of the author.
As someone who plays pokemon a lot, this reads false. While it's true Electric is a good type because of the only one weakness (Ground attacks) and Ice is cool because it has 4 super advantages (Fly, Dragon, Grass and Ground), it's a terrible type because it also has 4 weaknesses (Fight, Rock, Steel, and Fire).

This analysis just feels wrong. In pure type advantages, sure it's correct. But Pokemon can learn other types of attack besides it's 2 typings! (Infernape, for example, has the typing Fight/Fire. It's weak to Psychic, Water, Flying and Ground. But it has access to moves to get around those weaknesses, meaning that it's typing isn't as bad as this analysis would suggest it is.)

I guess you can say, hmm, that's interesting, but in terms of game play, strategy, and how good a pokemon can be, the typing is usually one of the lesser concerns.
Death throes of a dying ideology.
On the contrary, all three of the pages I linked about the etymology of "stereotype" explicitly address the etymology of the word with reference to prejudice. I am at a loss as to why you would say they did not.

Also, the cards with the two images were not referred to as stereotypes, and they were not printed from stereotypes, because it was not possible to print photographs from stereotypes until the invention of halftoning, which entered commercial use in 1873/ It is wholly implausible that this would result in changing the popular name of stereoscopic images, some 30 years after the invention of the stereoscope and 10 years after they became popular. Even after the invention of halftoning, stereoscopic images were almost invariably printed instead using photographic processes, which do not use stereotypes. Even in the late 20th century, View-Master discs were made using photographic film, not ink.

There is no attested history of using the word "stereotype" to refer to stereoscopic images.
Interesting that you choose location information. I believe location privacy issues on Facebook pale in comparison to Apple and Google who share your exact location information with 3rd party app developers.
Considering the enthusiasm at display here, I feel like this project would deserve bit better demo video for people like me who do not really understand HyperCard.
I'd say it's the opposite. Code formatters are winning. It's becoming increasingly trite to bikeshed over formatting when projects are using code formatters.
They are marching for their right to life.
Of course, but this is not the 1970s, and young males aren't moving to SF specifically to practice an openly gay lifestyle in an otherwise intolerant nation. It's unlikely that the hordes of male engineers, relocating to South Bay / SF for professional reasons, are substantially more likely to be gay than the women.
I'm ok for now putting everything in one GOPATH as if I were google.

> How many iterations of this do we have to go through?

Fewer iterations than Mr. Cox has gone through. Isn't it great?
The `err, result` function signature implies the function is an asynchronously executed node-style callback, which can never return anything anyway. Well, it can return something, but nothing internal reads it and there's no way for user code to access the returned value so return becomes only useful for short-circuiting.
No - most of their users (or "used" as is more accurate) are either oblivious or ultimately not caring.
It's one of my fondest hopes right now.

I would pay for the privilege of seeing Mark Zuckerberg reduced to cleaning toilets and struggling to make his alimony and child support payments after Priscilla Chan dumps his broke ass and takes him to the cleaners, and indulging in the sweet, sweet schadenfreude.
Google's rolling out mobile-first indexing
Next, you're going to tell us it's called a magazine, not a clip.
I don’t think I associate those hobbies (or lack thereof) with any sort of condition. I’ve seen many people in different boats or take and do not take interest in them.