oce 🐆

It’s mostly silicon.

Proprietary matplotlib

This interface is bloated

Snake island

Didn’t FB use some shady practice to make their users fall into Threads without noticing?

I don’t know if it does yet, but if ChatGPT starts providing source for every information, then it would make it much faster to find the relevant information and check their sources, rather than clicking websites one by one.

Big companies will take 5 years just to get there.

Same as ChatGPT is better web search.

Submodule commands are such mess, which is sad because it is a great feature.

If it was dead simple you wouldn’t need to learn 10 new concepts and google commands regularly even after using it for a couple of years. You probably forgot how you struggled at first. I have taught it multiple times and I see how beginners struggle.

It was conceived for experts so the new user experience is shit and the UI is not intuitive. But it has become such a widespread standard that it is very hard to completely overhaul the UI.

That supposes to have a clear idea of what you’re going to code. Otherwise, it’s a lot of time wasted to constantly rewrite both the code and tests as you better understand how you’re going to solve the task while trying. I guess it works for very narrowed tasks rather than opened problems.

Misses the noose for the junior who is hired to maintain the project.

Your knowledge of data engineering may be limited. SQL is predominant in data processing nowadays. FOSS tools such as DBT allows to write efficient data processing pipelines with SQL and some YAML config without the need for a general purpose coding language.
Why would anyone want that? Because SQL has the interesting property of describing the result you want rather than describing how to compute it. So you can put inside the database, a query engine with decades of optimizations, that will make a much better job at finding the best execution plan than the average developer.
It also means it’s easier to train people for data processing nowadays.

But think about the neck gains!

Why would it need to encapsulate that Git is a pull/push model ? What the name should do is describe what it is, and it is a call for reviews before merging, so “review request” or “merge request” are names that would make sense. When web interfaces weren’t used, it made sense to ask for reviewers to pull for reviewing, but now it’s a minority of them that are pulled by reviewers.

I wish MR would become the standard, I almost never pull an MR, PR doesn’t make sense anymore.

You may try to divide us but we’ll always be as one.

Not extreme is rather moderate. Conservative estimate means there’s a tendency to not change what was estimated in the past. Moderate would mean that a small change would be accepted.