191–200 of 308 posts
> . It is hard to think that any Windows programmer would prefer Swift as a language over .NET languages, as many commenters pointed out on Reddit, but a port of Swift UI on Windows could be a game changer. Everybody would jump to Swift [for new projects] if it meant a cross-platform GUI framework.
Swift is also a much nicer language than C# in my opinion.
Earlier quoted context omitted.
That's an outdated but sadly common perception. TensorFlow for example is pushing Swift pretty hard: https://www.tensorflow.org/swift/ Disclaimer: I work at Google but not on TensorFlow.
I don't believe TF4Swift will go anywhere. Fortran, C++, Python and Julia drive the show and work with full tooling across UNIX flavours, Windows, macOS today.
I've never tried Swift, but it seems it could have all the required features. I guess it's just lacking a lot of libraries that work on Linux.
Earlier quoted context omitted.
It's a fully fledged programming language. An open-source programming language, at that, with a lot of community input and involvement. Not a macOS or iOS app creation DSL. It's also quite pleasant to use, and has already seen a few uses beyond macOS and iOS apps, including some backend development (Vapor, Kitura, SwiftNIO, probably others). So you could use it to write command line tools. To write Linux or Windows a…
I'd say swift is currently probably the best languages out there. Language features, standard library, performance, memory management.
Earlier quoted context omitted.
In my opinion, the integration between Objective-C and Swift is so incredibly seamless, that there's no need to translate existing Objective-C code. When I started working at my current client, there was a huge existing Objective-C code base to talk to an internal HTTP API. I just started coding. When I needed to add functions, I subclassed Objective-C classes in Swift.
There is need to translate existing Objective-C code: on platforms where the Objective-C bridge is unavailable (Linux and Windows), Swift code can not call Objective-C code, nor toll-free bridge with Objective-C types, and therefore Objective-C types cannot be subclassed. For non-Apple platforms, you have to use a different implementation of Foundation — which has pretty good but not identical coverage to Apple's one…
> . It is hard to think that any Windows programmer would prefer Swift as a language over .NET languages, as many commenters pointed out on Reddit, but a port of Swift UI on Windows could be a game changer. Everybody would jump to Swift [for new projects] if it meant a cross-platform GUI framework.
Swift is also a much nicer language than C# in my opinion.
Not to mention that developing C# in Visual Studio or Rider feels years ahead of what's considered good enough IDE assistance in other languages. Comparable with Java even.
Earlier quoted context omitted.
Just checking my notes...and the answer is no.
Dismissive responses like this are frowned upon by the HN community guidelines. Give your reasonings, not a snide remark.
- Slow compilation, I think even now immutably concatenating a handful of strings makes the compile time exponential.
- Over reliance on keywords and special case syntax, magic doesn't compose. A bunch of it just supports Optional for example.
- Xcode, nuff said.
- Equatable and Hashable for tuples were implemented with invisible compiler magic, so they wouldn't work with generics.
- Variance is hot garbage, it has variance, but no way to control it.
- No higher kinded types, so useful FP abstractions become a chore to implement.
- I regularly had compiler crashes on comparatively simple code.
- Sometimes absolute nonsense compile errors pointing at random parts of my code.
- SourceKit didn't handle basic stuff like type aliases.
Going on the various things I've seen since we switched our project to JavaScript from Swift it looks like the keyword soup has gotten worse.
> . It is hard to think that any Windows programmer would prefer Swift as a language over .NET languages, as many commenters pointed out on Reddit, but a port of Swift UI on Windows could be a game changer. Everybody would jump to Swift [for new projects] if it meant a cross-platform GUI framework.
Creating a good cross-platform GUI framework is probably harder than creating a good cross-platform language.
Earlier quoted context omitted.
Yes it will look out of date. But whats important? A functioning app or good looking one? We all know that websites written for ie6 are out there today making millions in revenue. It always comes down to the functionality not the looks
Both. If you have only one, you have a shit product nobody wants.
Earlier quoted context omitted.
SwiftUI lacks many basic widgets like table.
To specify, it does contain what SwiftUI calls a List. And each row in the list can of course contain a number of widgets, so you can approximate a table. However for the desktop, a good real table, with columns, would be nice.