如何评价 Clean Code 作者对 Swift 与 Kotlin 的看法？

it’s a matter ofprofessional survival

Instead of one big code pile, activities will gently enforce a clean, standardized way for organizing code.

I like the clarity of this approach instead of stuffing it in initialize.

First of all, we want names to exhibit truth and beauty: to be the right names, and to make our code clean and beautiful. At least, this is what we want to think about our code, but naming’s importance is far more practical.

By abstracting the cleanup process in the cleanUp function, the three callbacks — timeout, success, and error listener — look exactly the same. The only difference is whether they resolve or reject the promise.

I'm more likely to use it than alternatives in future projects - it's simple and clean

I was just expressing that, even thought I like React, I dread having to still manually handle everything, instead of just using a directive, a la Vue.JS. This is what I consider boilerplate. Hence my comment on how I could leave React for Svelte just because of that. Clearly a Svelte side-by-side code comparison shows a much cleaner code for Svelte.

When we don’t feel confident in our code, it is tempting to attach our sense of self-worth and professional pride to something that can be measured.

It allows the module code (and subsequently dependants on the module) to not use preprocessor hacks, source code changes, or runtime detection hacks to identify which code is appropriate when creating a client bound package.

It allows your source code to remain clean and free of hacks.