Welp... there goes the last of the innovators I admired/followed at Apple. Edit: perhaps the problem is that you assume I'm just tossing gasoline on the ever-loved and popular rag-on-Apple fire. I have been an active clang/llvm user for 6 years, I have written numerous clang plugins over the years, and I am an active swift developer. Every device I own is made by Apple and has been since 2004. I am genuinely puzzled…
Update on the Swift Project Lead
91–100 of 159 posts
Re: Update on the Swift Project Lead
#92Windows support ever coming? I love Linux, but have to use Windows for work due to strict IT policies. It really frustrates me that almost all the new exciting tech can't be accessed by me outside of the hobby world. To me, C# just isn't very productive. Great language, just not for me.
Re: Update on the Swift Project Lead
#93I'm wondering if this means that the major work on Swift the language is complete? I've avoided it since it seems every year the language or the API changes... has it now settled? I really didn't want to go back rewriting code every year.
Re: Update on the Swift Project Lead
#94Windows support ever coming? I love Linux, but have to use Windows for work due to strict IT policies. It really frustrates me that almost all the new exciting tech can't be accessed by me outside of the hobby world. To me, C# just isn't very productive. Great language, just not for me.
Considered leaving your job? Life's too short to be a craftsmen who is not allowed to use the tools of his/her choosing.
Re: Update on the Swift Project Lead
#95Earlier quoted context omitted.
If you're truly worried, I would hold off just a little bit longer. Swift ABI stability is slated for Swift 4.
ABI stability doesn't really matter for users, unless you're using 3rd party pre-compiled libraries. It's mainly an issue for Apple, shipping system libraries.
Re: Update on the Swift Project Lead
#96Lots of great people leaving Apple right now, not a good sign.
Re: Update on the Swift Project Lead
#97Re: Update on the Swift Project Lead
#98Earlier quoted context omitted.
You tried to make it sound like you were talking about Apple, but really your comment was about you.
I don't follow your logic. Of course it was about me... and which engineers that work or (worked) for Apple I admire and follow. ¯\_(ツ)_/¯
you're all idiots.
Re: Update on the Swift Project Lead
#99Hmmm, going from someone with a pretty big Wikipedia page, to someone with just a linkedin entry. Guess it's fine. But Apple seems to be in a bit of a tail spin as of late. Sure they'll do amazing.
Re: Update on the Swift Project Lead
#100Earlier quoted context omitted.
It gets worse. My software has to run on my customer's computers. These can be any of RHEL 5, 6, or (rarely) 7. It'll be a few years before I can safely deliver C++ 11 software, and I snicker at the Pythonistas complaining about how people don't migrate from 2.7 to 3.x --- I frequently need to support Python 2.6. Rust, Swift, C++14, Python 3, etc... are all several years in the future for me.
Can you compile a completely static executable and ship that? Or do you need to compile on distributions as old as RHEL 5?