borntyping

> Can someone explain why anyone would want non-squashed PRs? > > For the 5% of engineers that diligently split each PR into nice semantic changes, I suppose that's nice. But the vast majority of engineers don't do this.

I think cause and effect are the other way around here. You write and keep work-in-progress commits without caring about changes because the history will be discarded and the team will only look at pull requests as a single unit, and write tidy distinct commits because the history will be kept and individual commits will be reviewed.

I've done both, and getting everyone to do commits properly is much nicer, though GitHub and similar tools don't really support or encourage it. If you work with repository history a lot (for example, you have important repositories that aren't frequently committed to, or maintain many different versions of the project) it's invaluable. Most projects don't really care about the history—only the latest changes—and work with pull-requests, which is why they tend to use the squashed pull request approach.

It doesn't mean anything useful in this context. It's a leftover from when PyPI was called "the cheeseshop", which in turn was a reference to a Monty Python sketch.

Nearly all binary searches and mergesorts are broken in languages with bounded integers.

I've been looking for something exactly like this for a while — a small Python library for generating HTML that isn't prescriptive about framework and doesn't introduce any particually weird syntax. Jinja2 macros are... not great when you want to turn your HTML into lots of smaller functions.

I'd suggest there's a correlation between the size of those package repositories and how much they get talked about. npm has several times the package count of PyPI and RubyGems together, and I don't think that can be accounted for just because it's common to make "micro" JavaScript packages.

> This is not doing science. It is “publishing articles written by scientists that you happen to find emotionally appealing”.

Have scientific journals ever _not_ worked this way? They're generally curated by an editor who curates the articles the journal peer-reviews and publishes.

Because package managers are used for more than just source code - many packages want or need to distribute intermediate or compiled artifacts.

"Just block ads" isn't a useful answer here - this is about being able to see who is advertising to the people who aren't using ad-blockers (which is most users on the internet), and being able to do research into who is paying for advert and who they are targeting. As long as the advertising industry still has a presence on the internet, this information will be important.

Definitely impressive. The short description seems a little vague or misleading to me though. "Internal tools" can mean a lot of different things - deployment tools, testing tools, data management, etc - so I expected something more generic by the title.

The second function only accepts strings defined at compile time, meaning it can't be called with strings created at runtime (i.e. any string containing user input).

I'm sure I've something similar come up a few times recently, but never with any source discussing the health insurance plans that supposedly collect this data.

Has anyone come across anything on these insurance plans? I'm sure it's something many companies would love to do but I remain skeptical.

There are millions of working, reusable electric cars; and tens of working, reusable rockets (maybe even less than that). Tesla is having problems building factories, but that certainly doesn't mean electric cars are hard to make.