Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Swift 5.3 Will Be Supported on Windows and Additional Linux Distributions

infoq.com

Post reply on HN
Print view View original

301–308 of 308 posts

Re: Swift 5.3 Will Be Supported on Windows and Additional Linux Distributions

#301

Post by seanparsons »

dep_b wrote: post #282
seanparsons wrote: post #244

Earlier quoted context omitted.

The exponential issue was still there in version 4 and I think 5 as well. Didn't say SourceKit crashed, but it was virtually useless because it functioned like a crap version of the language parser.

So what's particularly hard on the compiler are hard coded sets of data that have mixed types. For example a dictionary that reflects a JSON response that also has nested dictionaries. It helps if you test declare it like: let json: [String: Any] = [ /** lots of fields here */ ] String concatenation: could you give me a specific piece of code that fails? It could be that I really never write code that triggers the pr…

OMG, they actually fixed the a + b + c... issue I assume in version 5 (5.1.1 is what I have available in NixOS).

Re: Swift 5.3 Will Be Supported on Windows and Additional Linux Distributions

#302

Post by eggsnbacon1 »

mpfundstein wrote: post #140
eggsnbacon1 wrote: post #135

Earlier quoted context omitted.

I have doubts. We already have cross-platform languages with decent GUI like Java (people give it tons of shit but I bet you use a Java GUI every day without knowing it). Python has some decent ones too though. And of course Electron, which is somehow even worse than Java.

A colleagues computer lastly crashed. turned out pycharm took 14gb of ram.. wtf.

I have had IntelliJ open with multiple million+ line projects with thousands of source files and it hovers around 3GB. Its gotta be his settings. Java will use as much ram as you tell it to, it uses the extra ram to collect garbage less often.

Its super common to misconfigure Java to use all of your ram. You could have a terabyte and tell it to use everything and it will

Re: Swift 5.3 Will Be Supported on Windows and Additional Linux Distributions

#303

Post by lioeters »

brigandish wrote: post #147
zelly wrote: post #69

Earlier quoted context omitted.

You can still get around this because it's still possible to run Hackintosh in a VM.

Okay, but surely that's a workaround for devs who are primarily on non-Mac systems who want to use native features for Mac. What's the win with Swift if I'm developing on Windows over using, say, C# and benefitting from all the support for my primary base and then using something like Xamarin. I'm on a Mac already (Macbook with 10.14) - am I really going to have to run a VM because of a point release ? (That goes for…

> The standard of their laptops is not good enough any more

I'm with you on this. When I upgraded my 2015 MBP (or was it 2013?), I was still able to manually install new memory and SSD. Since then, newer MacBooks are not user-extensible, from what I hear, with sealed parts. They have a touchbar instead of function keys or escape (!), the keyboard quality is questionable, and there's no standard headphone jack. macOS has seen unstable releases with poor QA, with one bug bricking the machine.

In addition to those issues, I've been disappointed with Apple's stance and decisions about their proprietary operating system. I guess I've known all along, but it's become glaring. In newer versions I've noticed dark patterns, like being unable to set a different browser than Safari as the default application to open certain file extensions.

> the privilege of writing apps for Apple

This summarizes my feeling. Especially compared to what Microsoft has been pouring efforts into open-source, the way Apple is treating their long-time fans is luke warm at best, hostile at worst.

That's why, as excited I am about the potential of Swift as a cross-platform language, unless companies other than Apple are behind it, I won't be comfortable investing time into it.

Re: Swift 5.3 Will Be Supported on Windows and Additional Linux Distributions

#304

Post by The_rationalist »

merb wrote: post #293
AsyncAwait wrote: post #280

Earlier quoted context omitted.

Yes, some of these have been slowly added, similar with Java slowly moving to embrace features from Scala and Kotlin, but to me it doesn't feel as nice, rather sort of baked on and many of the libraries don't use these latest features. Swift was designed to seamlessly blend functional and OO styles from the get go. Fundamentally, there's still classes and inheritance everywhere in C#, which is also what I hated about…

> Now don't get me wrong, I am not saying C# is a bad language, just that when you compare it with Swift, Kotlin, Rust etc, it's clearly playing catchup. btw. it's the other way round. most modern stuff was in c# while the others played catchup and some still do. no language has async/await implemented as good as c# has, no language has nullable value types as good as c# no languages has a reflection api that is real…

no language has nullable value types as good as c# What's different from kotlin or typescript nullable value types + smartcasts?

Re: Swift 5.3 Will Be Supported on Windows and Additional Linux Distributions

#305

Post by VexorLoophole »

Sounds like great news! Am excited to see, where Swift will end. I am no developer but I like to code things and script tasks (at work that's even my job). Already tried many different languages. In the end I always used Python, because i feared that nobody can rewrite my code, if I write it in something more exotic.

Out of interest I spend some evenings in swift (server-side) and it felt some kind of fresh air. Python feels so 'slugish' all the time. But I am worried, if swift will ever be 'useful' server-side.

Re: Swift 5.3 Will Be Supported on Windows and Additional Linux Distributions

#306

Post by insulanian »

steveklabnik wrote: post #7
_bxg1 wrote: post #6

Earlier quoted context omitted.

Oh he doesn't? Didn't realize that

Yep! I’m not sure what he’s doing today. We’ve had several folks go between the two teams, and they’re generally very friendly with each other!

> I’m not sure what he’s doing today.

He seems to be back working on Stellar [1].

[1] https://github.com/stellar/stellar-core/commits?author=grayd...

Re: Swift 5.3 Will Be Supported on Windows and Additional Linux Distributions

#307

Post by apple4ever »

DagAgren wrote: post #254
apple4ever wrote: post #246

Earlier quoted context omitted.

I share it. I love Objective-C and feel its a far superior language over Swift. Swift is too clever by half, with its var, let, func, and the god awful question marks. Objective-C is verbose sure, but that helps readability. I'll never switch to Swift, as Objective-C is so much better in every single way.

I don't get the feeling you've really given it a fair chance, or tried to understand why it does what it does. Swift really is much more readable than Objective-C, too.

I have on both counts. I tried it a couple times and hated it. I've read the book and others justifications for it, but disagree.

Swift is absolutely less readable than Objective-C. Objective-C is known for its verboseness, which makes it easy to read. Swift has all kinds of easy ways to make it less readable, like the question mark. There is no way one can objectively argue Swift is more readable than Objective-C.

Re: Swift 5.3 Will Be Supported on Windows and Additional Linux Distributions

#308

Post by Diesel555 »

sophiebits wrote: post #110
Diesel555 wrote: post #101

Earlier quoted context omitted.

I really enjoy swiftUI. It appears like it tried to emulate react and succeeded on a few fronts, is better in a few fronts (child modifying parent variable), and worse in a few fronts (side effects). That being said, my experience with SwiftUI users is that they don't like it because it is so different from the standard Mac experience (props and re-renders and state...). And the documentation is poor (IMO has been Ap…

Curious to hear more about what SwiftUI does better than React… any place I can read more?

Sorry for the late reply.

You can change state without all the annoying purely functional programming stuff ([... previousState, newValue]). Just change it.

You can change a prop passed in and even pass a new value up to the parent. So you know the pass a function down so the child can change a value in the parent? Just pass the variable you want changed down with @binding.

Post reply on HN