That’s cool if people can agree on what maintainability is, which changes improve it and which changes hurt it.

You can get two people arguing for the exact opposite thing, while both of them use maintainability as an argument.

Is this a tax that domestic companies already had to pay, but foreign companies were exempt from? If so, then I wonder what took them so long.

So why don’t you at least try to run the numbers. Takes like 2 minutes. Total output, output per car, number of cars - it’s not rocket science.

The vibe reminds me of https://youtu.be/Jml7NVYm8cs

Kind of like every other job.

It’s not nitpicking, stuff like this is far more impactful than choosing between 5 lines vs 10 lines long methods, or whether the hasExtraCommissions “if” belongs inside or outside of calculateExtraCommissions. This kind of thing should immediately jump out at you as a red flag when you’re reading code, it’s not something to handwave away as a detail.

Why is it a void method? This only tells me that some state is mutated somewhere, but the effect is neither visible nor documented.

I would expect a function called “calculate” to just return a number and not have any side effects.

Self host with backups set up?

C is one of the few languages where using goto makes sense as a poor man’s local error/cleanup handler.

Peace treaty signed, then Russia invades 2 years later anyway and takes over everything?

Flutter - the framework - is great. Dart as a language is tolerable - lot of ugly boilerplate, manual codegen, and things you can’t quite express correctly are everywhere, but if you’re not too much of a stickler, Flutter is still worth it (at least until Compose Multiplatform matures - if ever).

At least Android also proactively asks them whether to disable notifications for an app if they always swipe them away, or if they haven’t used the app in a long time.

You have to go where the people are.

The default now is that apps have to first request notification permissions, on both iOS and Android.

deleted by creator

I don’t see the US restricting AI development. No matter what is morally right or wrong, this is strategically important, and they won’t kneecap themselves in the global competition.

Well you don’t have to place it in a separate function, nothing stops you from inlining that part and writing li or whatever directly there.

It’s up to you how you organize your components.

But why bother with creating a new language, and duplicating all the features your language already has, in a weird way?

If I want a list of UI items based on an array of some data, I can just do items.map(item => 〈Item key={item.id} item={item} /〉), using the normal map function that’s already part of the language.

Or I can use a function, e.g. items.map(item => renderItem(item, otherData)) etc.

JSX itself is a very thin layer that translates to normal function calls.

Still better than whatever the hell this is

https://vuejs.org/guide/essentials/template-syntax

The more you scroll down, the worse it gets.

And this too: https://vuejs.org/guide/essentials/list

A new separate language with features that already existed in the original language (and worked with all its tooling, etc.)

Custom template language and custom DOM attributes are way weirder than just using language-native constructs (ternary operator, map/filter, variables, functions, etc.) directly like you can in JSX.