4 ms·
I don't like that blog post on "semantic compression". He's rediscovered refactoring but doesn't think so: > This is a very bottom-up programming methodology,
by carapace 9y ago
I don't like that blog post on "semantic compression". He's rediscovered refactoring but doesn't think so:
> This is a very bottom-up programming methodology, a pseudo-variant of which has recently gained the monicker “refactoring”, even though that is a ridiculous term for a number of reasons that are not worth belaboring at the moment. I also think that the formal “refactoring” stuff missed the main point, but that’s also not worth belaboring. Point being, they are sort-of related, and hopefully you will understand the similarities and differences more over the course of this article series.
Um, what? Refactoring is called refactoring because that's what it is: You're pulling out a "factor" of the program and reifying it into a symbol which then replaces the factored code. "semantic compression" is a great name for it, but it's been the done thing in Forth, for example, for many decades.
It's just like factoring polynomials.
This is a textbook example of what I call "half-smart": He's smart enough to write this article, but not smart enough not to.
(Also that site disables reader mode. Boo! Why would you do that?)