1,245 karma · joined September 27, 2013
It's not even April yet...
I utilized the N9 for a few months a couple of years ago and just loved the OS. Of course there were bugs, but that's expected from an open source OS. However, the main reason I decided to move on was because of the app ecosystem.
TempleOS (formerly J Operating System,[1] SparrowOS and LoseThos)[2] is a biblical themed lightweight operating system created over the span of a decade by the American programmer Terry A. Davis. The software is a x86-64 bit, multi-tasking, multi-cored, public domain, open source, ring-0-only, single address space, non-networked, PC operating system for recreational programming.[3] The operating system was designed to be the Third Temple according to Davis and uses an interface similar to a mixture of DOS and Turbo C. Davis describes the operating system as a modern x86-64 Commodore 64 with C in place of BASIC.
At least good old hard cash still works.
Maybe it'll change your mind
Link to Elon Musk's tunnel plan: https://www.bloomberg.com/news/features/2017-02-16/elon-musk...
Correct me if I am wrong, but does that mean Alphabet is suing itself since Alphabet owns both Google Venture, Waymo and has an investment in Uber...?
The designer did a great job drawing it...but something just doesn't feel right...
I think they were going for a "friendly" approach but it just doesn't do it for me. Now, you may argue that the logo isn't important but some users will utilize a tool purely based on aesthetics...why a creepy giraffe? Am I missing something in American pop culture..? (I'm Canadian...)
"Use By: (date)", or "Best if Used By: (date)"
However, the article still claims there are no guarantees of adoption.
Will this likely happen? Nah.
The article mentioned a very important point. Apple itself has not adopted Swift as fast as the developer community. This is because (I don't know this for a fact, but am quite sure), a large portion of hw/sw engineers know how to write C, C++, and Obj-C. They don't just know how to write it, I bet a lot of them are damn good at it and if not, top in the industry. Why convert? As many mentioned in the comments, it would be a huge overhaul and what about Apple's internal engineers? Would they put themselves out of a job?...Not likely.
Maybe in 20 years (if there still is an Apple...), there will mostly be Swift engineers. I just don't see them shooting themselves in the foot by removing obj-c in the near future (as in 5-10 yrs).
I suppose that's how they differentiate the good students from the just okay students. Personally, I don't think youtube videos will help that much when it goes down to the nitty gritty. You really have to sit down, think, and understand.
That being said, it's definitely a smart move to invest time in swift (I did play around with some swift libraries), as it does seem the industry "might" move towards some kind of hybrid obj-c and/or swift + React-native app. I've personally decided to invest more time in JS than Swift.
Yes, the React syntax and JS in general also wasn't as easy for me to catch on vs. obj-c (I wrote a lot of C in my previous job). As you write more, you'll get use to it.