3 ms·
Yes, Swift is definitely losing the mindshare race for server side compiled languages, but to be fair it started way behind. However, just because it is not win
by oflannabhra 3y ago
Yes, Swift is definitely losing the mindshare race for server side compiled languages, but to be fair it started way behind. However, just because it is not winning mindshare doesn't mean it isn't useable or that it is a failure.
The real story of server side Swift is a small but dedicated working group [0] continuing to make real measurable progress. Most of the frameworks have fallen out of favor or have been abandoned, except for Vapor, but the workgroup is active with representatives from several major tech companies. Obviously the workgroup's scope is much broader than just a single framework, and their current initiatives identify and address most of the shortcomings noted in the article. [1]
[0] - https://www.swift.org/sswg/ https://www.swift.org/sswg/
[1] - https://www.swift.org/blog/sswg-update-2023/ https://www.swift.org/blog/sswg-update-2023/
- ezekiel68 3y ago> However, just because it is not winning mindshare doesn't mean it isn't useable or that it is a failure. A supposedly wise man once said "...you can not fool all of the people all of the time." [0] Plenty of things that are usable are also failures (e.g. Microsoft Zune was, by all accounts, a competent media device). Any technology that is not winning [sufficient] mindshare over time will be considered a failure soon enough. [0] What, you don't know who said this? Copy pasta plus a three-second search on any search site or AI chat will set you straight.
- oflannabhra 3y agoThis seems pretty reductionist and zero-sum thinking. Taking your line of reasoning to its end, one would expect there to be a single web framework, and that is evidentially not the case. Additionally you are mixing current state with future state, and most of my comment was focused at the current state of server-side Swift. Defining "sufficient" here is important, and I think that server side Swift's progress meets a bar here that prevents it from being a failure. That might not last though.