3 ms·
...and, then, there are the languages that we need to use, in order to accomplish our tasks. Most engineers (as opposed to coders) are fairly results-oriented.
by ChrisMarshallNY 5y ago
...and, then, there are the languages that we need to use, in order to accomplish our tasks.
Most engineers (as opposed to coders) are fairly results-oriented. We may have our differences about how to get the results, or even, what the desired results are; but we always have a deliverable in sight.
It's all about getting satisfactorily-functioning software into the hands of end-users. Put a bow on it. Stick a fork in it. It's done.
Speaking for myself, I write native Apple code (iOS/iPadOS, MacOS, WatchOS, and TVOS). I need to use Swift. I could use ObjC, but Swift is really where it's at, unless I'm doing really low-level stuff. Others may use JavaScript, or even C#, to write Apple software; using hybrid systems.
It is, indeed, mostly "gluing together calls to library functions," but there's a bit of algorithm, mixed in there, as well (not much. Many library functions provide better algorithm support than hand-rolled).
Other platforms have their most effective languages.
I probably could write Apple apps in FORTRAN. I think that there are FORTRAN compilers for Apple systems. I can use existing C or C++ code, to provide "business logic" (I used to run a shop that did just that), so I guess there's a lot of languages that I could use in the backend, and, maybe, some might be better choices, for certain tasks. Again, it needs to be results-driven. If a certain kind of algorithm is most effectively implemented in Lisp, wrapped in system calls, I could embed that in a Swift wrapper.
There's also something to be said for becoming a "native speaker" of a language. That means using it fairly exclusively, over and over again. Step and repeat. I have been writing Swift, almost daily, since the day it was announced, and I still discover new things, almost every day. I think that's pretty cool.
This is stuff that I would never have discovered on a "context switch." I've usually been fairly good at picking up new languages, but I am happy to be sticking with this one, for a while. In the past, I've had to know Pascal, Object Pascal, 68K Assembly, C, C++ (and simplified variants, thereof), and Objective-C, in order to program for Apple (yeah, I've been at it a while).
- Abhinav2000 5y agoAgree with you, and Swift is also such a great language. I went from it to Lisp, sometimes I ponder about returning back (however my use case currently is for Lisp).
- mark_l_watson 5y agoWhat are you working on in Lisp, if I may ask?
- Abhinav2000 5y agoMostly text based mathematical analysis. I couldn't stick to Swift as it would rule out a large section of the potential audience (Linux / Win - although Kotlin, which is similar enough, could bridge the gap to some degree), so I'm going more down the Web App route. For now, most of my I/O is in Emacs and later I may plan to work on the GUI side (via Electron or Web App, maybe but very unlikely CAPI or some CFFI). How about yourself? Do you still do programming in AI?
- mark_l_watson 5y agoI do, and I use a Lisp language for almost half of my work.
- mark_l_watson 5y agoI agree with you about Swift. I am fascinated by Apple's support for machine learning models as first class components in Swift applications. I have a Swift and SwiftUI app in Apple's store that is really a simple app (short code, written as a nice example for a "Swift AI" book I am writing) that leans heavily on two embedded deep learning models. Really great stuff from Apple.