weegee101

6 ms·

1.
by weegee101 1mo ago
Sure, but then Clean Code goes and directly pushes for polymorphism in an area (branching) where indirection and polymorphism is known to be costly for both complexity and performance. An aspect of this that I wish Muratori had touched on w
2.
by weegee101 1y ago
The issue with this in practice is that there are always cases where panics are absolutely the correct course of action. When program state is bad enough that you can't safely continue, you need to panic (and core dump in dev). Otherwi
3.
by weegee101 8y ago
You're right, it is easy to over engineer sites these days. It boils down to tooling for SPAs vs traditional static sites. The tooling for making static sites, even the most modern tooling such as Hugo or Jekyll, simply pales in compar
4.
by weegee101 8y ago
Haha, that "sample security test" is hilarious. Basically just a link to SSL Labs saying they meet industry standard. That's great, glad they can meet low hanging fruit. How about proving that they can do better?
5.
by weegee101 12y ago
Yes, and I think people should head to Swift if it fits their needs. That is very different from Objective-C losing support however. Objective-C is not going away.
6.
by weegee101 12y ago
This is not even remotely similar to that situation. Obj-C is far more important & integrated than I think you realize.
7.
by weegee101 12y ago
That is extremely unlikely. Enough so that I would bet money on it. Swift is targeted at the largest user base of the Obj-C language, the iOS developers. Obj-C will be around for a long time both for legacy purposes and because Swift doesn&
8.
by weegee101 12y ago
No, it doesn't. It is a great way to do 99% of the tasks most developers do. There is, and always will be, a place for Obj-C on the Macintosh platforms. Apple recognizes that most developers don't need the verbosity and tight-knit