HN user

vi4m

47 karma
Posts1
Comments14
View on HN

I'm a bit confused about the "don't trust Apple" sentiment here.

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.

It’s not dead but nearly dead.

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.

Pure wonderful code that works.

Edit: read more here about their „progressive” transformation https://www.mozilla.org/en-US/diversity/2022/

Wrong. Apple officially provides:

* 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)

Really something we needed.

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.

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)

Maybe it's just me, but I don't like theese cool presentations filled with expressive words 'DO IT!', 'NEVER DON'T DO THAT' "bitches" "programming motherfuckers". It's funny, but not for 100th time.

Another example are pictures, or memes pasted into the presentation. Maybe sometimes it is funny, when there is one funny picture, or the subject of presentation is chalenging.

But very often amount of 'coolness' is too much to me to handle. I often find presenters not knowing subject enough for answering questions(they just make jokes, etc).

Maybe should we just go back to excellent but simple, polite, content(text) rich presentations ?