Arcsech

> Copyrighted by whom?

By people who would get angry if they could definitively prove their stuff was in OpenAI's training set.

I don't disagree with your points about connected cars, but at least for CarPlay (I don't know about Android Auto), it's entirely an orthogonal concern. CarPlay is a standard for, basically, connecting an external display to your iPhone - it doesn't need to connect to anything other than the iPhone itself, and doesn't grant the car any access to the internet or anything, and IIRC the phone can't read anything meaningful from the car either.

EXACTLY. This lazy, backwards approach to tooling and workflow is why I jumped ship from logic design to software despite having an EE degree. VHDL/Verilog tooling is heinously terrible and everyone in the industry seems to be actively opposed to doing anything about it.

Oh yeah, that paragraph really nailed it. Every place I've worked that's started to go downhill, it always started with executives, who never acknowledged their role in the problem or did anything to fix it.

I'm increasingly convinced that a large portion of our problems as a society is our absolute refusal to hold anyone in power accountable for anything.

My concerns about toxicity on Twitter are less about what I want to see (I don’t use Twitter anymore myself, even), and more about the incitement to violence we’ve clearly seen is possible on the platform. Twitter should not be a platform for organizing a mob to invade the capitol and attempt to execute the Vice President, for example.

That’s a disgustingly prejudiced statement. While I don’t like Mr. Musk very much myself, I’ve known plenty of autistic folks who do a great job managing communities.

If being forced to compete fairly requires them to drop their prices by 60%, I think that’s a pretty good argument that they’re not competing fairly at the moment.

I don’t see a personal attack here.

“Continually” is a pretty strong word for one change.

The author of that article is overly focused on the Linux (or similar) deployment model, which most definitely does not cover all uses of SQLite. The argument against 2) also depends on a feature available in specific versions of specific compilers, which again, a piece of software that supports as many use cases as SQLite can’t depend on.

Even in that model, I’ve long found that the arguments against 1) are weak in practice (especially with a well-designed and maintained lib like SQLite) versus the additional complexity added by depending on dynamically linked libraries.

Well, she went to a different doctor later who helped her diagnose & treat her allergies. Which made exercising easier too, turns out. Who’d have thought? (Her. One of the reasons she’d sought treatment is that the difficulty breathing through the nose was making it unpleasant to exercise.)

I dunno. He didn’t elaborate. We left pretty quickly after that and she found a doctor who helped her figure out and treat her multiple allergies.

This is a great question! In my experience, the differences come down to:

- The doctor is going off a very short explanation you gave in a 30-minute appointment. If you have a serious medical problem, you can dump days, weeks, or months into finding information that matches your experience down to the fine details, which can very much matter - especially if you have an unusual case of something.

- There may be new information since your doctor was trained. Medicine has advanced a lot, and while doctors do their best to keep up, there’s more new research than any one person can digest.

- You will always believe yourself, never dismiss your experiences as “exaggerated” or “drug seeking”, and never blame your conditions on obviously unrelated causes.

That last one is especially relevant to people who aren’t cis white dudes. I’ve witnessed, with my own eyes, a woman talk to a doctor about chronic nasal congestion, and his response was to tell her to lose weight. Doctors habitually not believing the experiences of their patients has done incredible harm over the years.

That’s exactly why I used the phrase “source-available”, not “open source” - because those licenses aren’t recognized by the OSI. I’m actually of the opinion that if AGPL is open source, SSPL is too, no matter what some dorkwads as the OSI say. But I’m employed by a company that uses the SSPL, so I try to use the generally accepted phrasing to avoid being accused of “sowing confusion”.

Even if you’re worried about this, there are source-available licenses like SSPL or Elastic License v2 explicitly designed to prevent this, and which have seemingly been successful at doing so. The exact choice of license would depend on the kind of thing you’re worried about.