The only reason CMake is considered better than automake is because automake is so unimaginably dreadful. CMake is a lot worse than pretty much any competent piece of software.
Qt is moving to CMake too. And the latest versions of CMake are as good, or better, than qmake. Add to that vcpkg and you will have a fantastic solution for managing dependencies.
Maybe CMake is not the best but is good enough and the new standard in the C++ world.
It’s really not good enough, it’s ok to admit it. Nobody likes CMake, it just somehow won the makefile generator wars. Having to a learn shitty, esoteric language to compile my code Is not something that makes me more productive.
I agree. qmake was much, much better to work with than cmake. I tend to believe the reason cmake won is because qmake was so associated with Qt. The best tech does not always win.
Android also settled with cmake, while keeping the original ndk-build makefile based one, after doing a couple of failed attempts to switch to something else.
After 10 years they are finally introducing AAR support for NDK projects, which is also built on top of cmake.
we live in a world with lots of rules. some of them are dumb, but carry serious consequences if you're caught. the message is, if you're gonna break the rules, you need to at least get away with it. it's (usually) better to get caught by your parents the first time, rather than an institution like school that isn't as invested in the outcome for you as an individual.
not quite the same, but this reminds me of a conversation I recently had with my parents. they were fairly strict when I was a kid, and I was asking them as an adult why they were like that. they told me that they expected me to break the rules and considered it a healthy part of growing up. they set the rules conservatively so I wouldn't need to do anything terribly unsafe just to rebel.
The alternative is of course that, out of love and respect for your parents, you chose not to bend the rules even when you could have because you trusted that your parents placed the rules there for good purpose in the first place.
To then find out that a) the rules were placed to control you and not necessarily protect you, and b) they didn't trust you not to break them, and c) they wouldn't follow these rules themselves....
...that surely leads to some serious implications in how you view society if the only definitions of rules you've experienced are seen as temporary barriers to getting what you want
A company focusing on delivery can do the job more efficiently and competently. Just the fact that they can route deliveries more effectively instead of going restaurant-customer-restaurant is a big win.
The business model is to charge both a delivery fee and a commission on the sales price. That way, you can make it profitable, even when paying a fair price to couriers, as long as you can keep your business lean and your delivery routing efficient.
Doesn't seem like there would be much demand to run legacy Objective-C code on other platforms, as it would most likely be strongly tied into macOS or iOS APIs that would be availble anyway.
Indeed. Although, some of the things that Apple's ObjC Foundation provides that aren't in Swift's cross-platform Foundation are sorely missed — but I doubt there's much impetus to put them in Swift's cross-platform Foundation, either.
> But somehow after nearly 6 years Objective-C stills feels better
This experience is shared by basically nobody? I used to love Objective-C, which was unusual even before Swift, but I would not in a million years switch back to using it. Swift is so much better in every single way.
I share it. I love Objective-C and feel its a far superior language over Swift. Swift is too clever by half, with its var, let, func, and the god awful question marks. Objective-C is verbose sure, but that helps readability. I'll never switch to Swift, as Objective-C is so much better in every single way.
I have on both counts. I tried it a couple times and hated it. I've read the book and others justifications for it, but disagree.
Swift is absolutely less readable than Objective-C. Objective-C is known for its verboseness, which makes it easy to read. Swift has all kinds of easy ways to make it less readable, like the question mark. There is no way one can objectively argue Swift is more readable than Objective-C.
Yeah. There are _aspects_ of Obj-C that are still nice, but as a whole I find Swift way better to work with on day to day basis. For that matter, I prefer it over syntactically similar languages like Kotlin too. If I could just write Swift everywhere that’d be great.
