3 ms·
You said you make the utilitarian choice. By using C everywhere, you can use an even faster compiler that doesn’t insert those calls for you. So why don’t you?
by sandofsky 3y ago
You said you make the utilitarian choice. By using C everywhere, you can use an even faster compiler that doesn’t insert those calls for you. So why don’t you?
- lapcat 3y ago> By using C everywhere, you can use an even faster compiler that doesn’t insert those calls for you. In the previous comment you said I should use objc_msgSend, now you say I shouldn't. Make up your mind. ;-) Anyway, I'm using AppKit and UIKit to write apps. The API is Objective-C. That's why I write Objective-C. Whatever the heck you're talking about—you appear to be confused, so I don't know what exactly you mean technically—it certainly sounds like premature optimization, which is a waste of time and not the correct utilitarian choice. My Objective-C code is not "slow". Could it be infinitesimally "faster" in way that's not even perceivable by the user? Perhaps, but who cares?
- sandofsky 3y ago[flagged]
- lapcat 3y agoBen, don't play coy and pretend you weren't trollling when it's 100% clear now that you're trolling, and everyone can see that. I'm done here.
- sandofsky 3y ago[flagged]
- lawgimenez 3y agoJust figured that dude you respond to is the one who created Halide camera. Not expecting him of a troll type, until today.
- Apocryphon 3y agoHe's very active on social media.
- deleted 3y ago[deleted]
- solumunus 3y agoBecause of all the downsides. The utilitarian choice is about practicality, not pure performance. This line of questioning is silly.