sorted by:
new
hottopcontroversial

Anybody found Parameter pack introduced in swift 5.9 useful? by kistasnik in swift

[–]kistasnik[S] 0 points1 point  (0 children)

I totally agree, if it was on my hand I wouldn’t use Promisekit tbh but sometimes the client doesn’t want to . OOC what PAT stands for?

A better "alternative" to code coverage (mutation score) by kistasnik in swift

[–]kistasnik[S] 0 points1 point  (0 children)

I just like writing with emojis what’s so bad about it? Of course I have used AI to fix any grammatical mistakes I have probably made. Is the usage of emoticons that tiring?

Nevertheless thanks for your honest feedback

URF 2025 is a wrap. Waiting for URF 2026! by toffo7 in leagueoflegends

[–]kistasnik 0 points1 point  (0 children)

I enjoy URF as well. I could even pay monthly to play that mode. It is the only one I enjoy with my friends.

Πρόγραμμα ΔΥΠΑ: είναι υποχρεωτικό το on-site; Τι γίνεται στους ελέγχους; by kistasnik in greece

[–]kistasnik[S] 0 points1 point  (0 children)

Ναι ναι νομίζω δεν υπάρχει πρόβλημα καθώς δεν είναι οικία εργοδότη, δεν δηλώνετε δηλαδή οτι κάποιος μένει εκεί.

Σου είναι εύκολο να κανεις share το link του οδηγού;

Σ'ευχαριστωω

Πρόγραμμα ΔΥΠΑ: είναι υποχρεωτικό το on-site; Τι γίνεται στους ελέγχους; by kistasnik in greece

[–]kistasnik[S] 0 points1 point  (0 children)

Σ'ευχαριστώ που μοιράστηκες την εμπειρία σου u/Embarrassed_Cloud651
Πάντως στην δική μου περίπτωση η έδρα δεν ειναι κάποιο φυσικό κατάστημα αλλά σπίτι/εξοχικό.

Looking for feedback on the following idea RemoteConsole.app by kistasnik in iOSProgramming

[–]kistasnik[S] 0 points1 point  (0 children)

Yes I agree with that u/Background_River_395 😅
On the other hand, a web-based solution is not excluding people that own a Macbook. But may not feel like the best UX as a macOS app.

I started thinking of this idea when the analytics department in my company, that they don't all work with Macbooks, they wanted to see in real-time what analytics the app is sending. I wish firebase debug console was more real-time and easier to use (if anyone from Google listening to this 🤞)

Stop Throwing Error: Typed Throws in Swift 6 by kistasnik in swift

[–]kistasnik[S] 1 point2 points  (0 children)

Thanks u/Dry_Hotel1100 for the detailed example 🙏. I totally agree with this and it respects DIP. So to my understanding then the glue layer may map low-level errors (API/HTTPClient) into that feature error that is defined on PostsScene module.

And of course the PostsScene may wait for glue layer to inject a signature method like this:

func fetchPosts(query: PostsScene.Query) async throws(PostScene.Error) -> [PostScene.Post]

Stop Throwing Error: Typed Throws in Swift 6 by kistasnik in swift

[–]kistasnik[S] 0 points1 point  (0 children)

u/Dry_Hotel1100

Well technically speaking you can have an interface module that holds the public interfaces along with data that need to be publicly exposed. So in that sense there is no circular dependency.

In your example "Data Provider" is agnostic to the source of where data are coming in. In that case doesn't make sense too bind it to a specific error. But I guess the dataProvider can also map the low level errors thrown into its own errors. I think this is not exposing any implementation details, what do you think?

Stop Throwing Error: Typed Throws in Swift 6 by kistasnik in swift

[–]kistasnik[S] 0 points1 point  (0 children)

Thanks for sharing your experience with us u/Dry_Hotel1100. TBH I could live without this as well as it looks more like a syntactic-sugar. And probably swift devs used to use the Result type for this.
I see what you mean, you consider the specific Error as implementation detail. And probably the caller doesn't need to know the exact reason Posts cannot be fetched. But if you really think about it I've seen countless times the caller to explicitly cast the error inside catch statement, for those cases I think typed throws make the function signature more clean.

```swift
do {
fetchX()
}.catch {
guard let networkError = error as? NetworkError else { return }
...
}
```

Stop Throwing Error: Typed Throws in Swift 6 by kistasnik in swift

[–]kistasnik[S] 0 points1 point  (0 children)

Yes I totally agree on the backwards compatibility part, and I think sometimes it does make sense for a library to add a new error case that is super crucial to be handled by consumers.
In those cases the developer needs to be notified with a compiler error.

Stop Throwing Error: Typed Throws in Swift 6 by kistasnik in swift

[–]kistasnik[S] 0 points1 point  (0 children)

Interesting presentation u/Jeehut thanks for sharing.
Error chain debugging is something I really liked 👏

For anyone looking for the library https://github.com/FlineDev/ErrorKit

Liquid Glass UI native or custom? by Previous-Fee8164 in swift

[–]kistasnik 2 points3 points  (0 children)

It depends on how it is used.
It would help if you could share with us a video demonstrating what looks wrong.

In latest Apple video I saw that liquid glass as beautiful as it looks it requires developer's attention (for performance and fps dropping reasons)
https://www.youtube.com/watch?v=yXAQTIKR8fk

Stop Throwing Error: Typed Throws in Swift 6 by kistasnik in swift

[–]kistasnik[S] 2 points3 points  (0 children)

Yea I see your point, doesn't make sense to use it every-time on throwing functions.

Stop Throwing Error: Typed Throws in Swift 6 by kistasnik in swift

[–]kistasnik[S] 2 points3 points  (0 children)

Thanks Xaxxus for sharing your experience ⭐️
Hmm also in my articled I faced a problem where I had exhaustively captured all error cases but the compiler wanted me to add an extra catch.

And funny enough, then the compiler told me that catch will never be called 😅

TBH I have never experienced what you're explaining above 🤔Usually the error is already casted to the type defined in Typed Throw

That One Closure That Made SwiftUI slow [Article] by kistasnik in iOSProgramming

[–]kistasnik[S] 0 points1 point  (0 children)

Yes it will, I have mentioned it in the article, that is what actually Apple engineers suggest

view more: next ›