Swift is compatible with WASM and embedded systems. It has a well-defined concurrency standard, and as a compiler, it's been tested with massive codebases worldwide.
The community is incredibly supportive (Ted Kremenek's team is super active, attending community conferences and supporting the Server Side Workgroup). They also have an open swift-evolution process that mostly works.
Xcode not being open-sourced? Not a big deal. It's an older codebase optimized for different use cases. Their approach is to break Swift down into smaller, focused components (Package Manager, LSP server, a formatter, etc.)
JetBrains didn't open-source their IDEs either, and people don't complain about it. So, it's the same story, but it's better since you don't have any historical issues like "Oracle JVM" lurking around, causing trouble for the community.
> I'm a bit confused about the "don't trust Apple" sentiment here.
Let me help you out; replace "Apple" with "Microsoft" and it will make a lot of sense suddenly.
The Open Source community has heard all this before. We've seen Sun Microsystems "generously" publish their Java spec to the public, we've seen Microsoft "give" their community C#. In the end, it's always more trouble than it's worth to cooperate with these language stewards and someone (either the business or community) ends up getting burned. I don't think many developers look at Swift with optimism that it won't end in the same Dotnet/Mono nightmare we've seen in the past.
You can lead a horse to water, but you can't make them drink. Apple has invested heavily in a language that, like C#, has a bunch of incredible features. Unfortunately they have yet to invest in the developer relations requisite for making such a language popular. Lord only knows that I'm not wasting my time to do Apple's work for them just to get a cross-platform app to compile with upstream LLVM and Clang. I could use any other language - nobody is going to commit to an ecosystem that treats them as a second-class citizen.
The question is why they focused on DEI, weird social activism so much and not on engineering itself.
Look at SQLite. SQLite is notable example where they don’t even have CoC(!) and focus only on getting engineering done. No marketing, events, sponsorships.
> Look at SQLite. SQLite is notable example where they don’t even have CoC(!) and focus only on getting engineering done. No marketing, events, sponsorships.
They kind of do have a CoC, called Code of Ethics.
But it's probably not what "tolerant" people are looking for. And it's
fine.
Also, SQLite is open-source, but not open to contribution, so they can
"get away with it". Although I completely support their model of doing
development.
So you want absolute religious zeal in open source? As opposed to "tolerance" quotes from your link ..
"First of all, love the Lord God with your whole heart, your whole soul, and your whole strength. "
"Obey in all things the commands of those whom God has placed in authority over you even though they (which God forbid) should act otherwise, mindful of the Lord's precept, "Do what they say, but not what they do." "
"Fulfill not the desires of the flesh; hate your own will. '
I hate sjw corrupting coc's invading the foss meritocracy as much as the next guy but this is so radicaly on the other side of the spectrum I think I hate it just as much .. being reactionary to sjws like this is still letting them win.
All I've said is that I support their development model, meaning that I
support their choice not to allow thirdparty commits in their code.
As for your highlighted excerpts, the first one says about having
respect for the rules. Second one is about respecting the chain of
command. Third rule is about having self control over oneself, and
discipline.
Of course you've also failed to mention that in that COE there is also a
comment that you're free to not obey those rules. They've just written
those down, but you're not expected to follow it.
* linux, windows and wasm compilation targets. They hired the maintainer of wasm project as well.
* LSP language server for Swift, to power VSCode and others editors, even though, they use Xcode that doesn't need it
* well tested server side libraries similar to netty/jetty (they even have a former Akka developer)
Swift has such low memory usage, that it's an order of magnitude easier on resources, than those Electron wrappers. At the same time, it gives what you loved about React - expressiveness for UI.
I wrote a lot of apps in SwiftUI, and it strikes a good balance between type safety and expressiveness, it's cool that we have something similar for GKT/Gnome now.
Interoperability is about practicality and performance cost. I think Swift is quite practical and efficient in this regard - from day 1 it has near-zero C-lang integration costs, and now it has C++ support.
Also, https://github.com/swiftwasm shows how the modularity pays off. Comparing it to the other languages that got stuck with incompatible frame conversion (Golang) or JIT memory management problems (JVM) it's not bad at all.
libimobiledevice works just fine on Linux. Your distribution's version may be out of date, but the upstream version gets updated to match any iOS changes pretty quickly.
Until you try to do first presentation on some conference, when your connected display crashes and you start typing xrandr / fighting Wayland/xorg drivers ... I see it all the time, never happened to Macs.
Can we dial back the FUD? I present all the time with my Linux laptop that does not require any dongles to connect to HDMI, VGA and DVI projectors. Oh yeah and airplay works just fine too. Been that way for as long as I can remember. This isn't 1997.
'It works for me' is not an solid basis for the opinion that OP is posting FUD. Clearly the problem exists for some subset of people, or we wouldn't be talking about it. That doesn't meant that most people encounter it - but it's still a problem.
Also setting up printer, external monitors, battery saver (if you want to close your lid and not worry about whether that will drain the battery), and updating your packages and realizing something broke right before an important deadline.
SSD in Macbook Pro is crazy fast. So fast that finally, after many years, we can think about "replacing" RAM with it.
LPDDR3 RAM speed = 17 GB/sec, SSD read - 3 GB/sec. As much as it sounds crazy, i believe, SSD will eventually replace big and inefficient RAM's (which consume 6 W of power for each 16 GB slot)
Swift has been working seamlessly with Linux and Visual Studio Code for years now. You might be surprised to learn this, just like this guy was https://www.youtube.com/watch?v=LTP5c4NqA8k&t=5484s
Swift is compatible with WASM and embedded systems. It has a well-defined concurrency standard, and as a compiler, it's been tested with massive codebases worldwide.
The community is incredibly supportive (Ted Kremenek's team is super active, attending community conferences and supporting the Server Side Workgroup). They also have an open swift-evolution process that mostly works.
Xcode not being open-sourced? Not a big deal. It's an older codebase optimized for different use cases. Their approach is to break Swift down into smaller, focused components (Package Manager, LSP server, a formatter, etc.)
JetBrains didn't open-source their IDEs either, and people don't complain about it. So, it's the same story, but it's better since you don't have any historical issues like "Oracle JVM" lurking around, causing trouble for the community.