• You should really not need to do a PR across multiple repos. If you need, you are breaking your code wrong. Some functionality may require multiple PRs, but you should always be able to do those at different moments and test them separately.

• The monorepo tools are exactly software that emulate the features of a multi-repo so that you can have thousands of people on the same repository. We also have multi-repo tools that emulate the features of a monorepo, but people don’t hype those online because they are simple and free.

Well, half of a head. We don’t draw the Earth map this way.

It also doesn’t use the up and down borders.

I mean… The one thing they can’t expect on step 3 is growth.

Profit is at least theoretically possible.

By the way, I’d say step 2.a. is “make its usage mandatory for the system to work”, and 2.b. is “bill for usage”…

MS chat bots are practically in every desktop out there. What growth were they expecting?

Well, if anybody can do a “terminator 2” and literally walk out of it, it’s him.

Looks like just a good policy to me.

Hum… The brain links are way less direct, that’s for sure.

Looks like you are trying to describe the Federation…

GraphQL has all the right combination of abstracting a really hard problem, ignoring the hard details, and giving you enough toggles to pretend you can solve the worst problems that makes hyping it really, really easy.

The process people do with cheese is called “aging”? That’s a simple answer, it will be easy to remember :)

One of those laser weapons that are supposed to take drones down or a laser pointer?

But the libraries the FB devs publish are considered state of the art on the web frontend community!

And if you complain, there’s always somebody to say “if you are so good, why aren’t you working at FAANG?”

It’s stronger, a bit bitter, and with a sweeter aftertaste. It’s great for making juice, but too strong to eat.

Kept in storage for a season like we do with cheese.

Literally seasoned. Dried in a ventilated area for a month or so.

(By the way, I have no idea what’s the modern word for that. I know the origin of that one, and can’t find anything in a translation dictionary.)

best eaten fresh

Certainly said by somebody that has never eaten it seasoned.

Yours is labeled in a much clearer way.

It’s a badly assembled fork of Debian that doesn’t have the same maintenance work and will both break sooner or later and have really large odds of not ever completely working.

Tried Suse and Red Hat before Fedora existed… Also a lot of stuff that isn’t on this graph, and made a system from scratch two times because of strict requirements.

No plans of moving from Debian. Why TF can one argue that those two are more productive? The only reason to use Fedora in particular is if you are stuck with it due to some hardware or contractual requirement.

I can’t even tell anymore if AI is really this bad, or if it’s the people that want to use it that are this bad.

But I’m sure the layoffs will help improve things, people. It’s just a matter of waiting a little more. \s