adamwk

5 ms·

31.
by adamwk 1y ago
I’m confused, that is how it works. If a developer increases their target version to say iOS 18, a user running iOS 16 would be able to download the last app version that supported it, even after factory resets. If the third party developer
32.
by adamwk 1y ago
Where copying is expensive (most Swift collections are backed by classes for COW semantics). Where location stability is necessary (where you need a mutex). Resource allocation. Those are the primary examples that noncopyable types are mean
33.
by adamwk 1y ago
The way to write performant Swift is classless so without ARC, but classes have been necessary for many areas. Recently, Swift’s been leveraging a lot of ownership features similar to Rust to make it possible to do more without classes, and
34.
by adamwk 1y ago
Yeah I’ve had that in various forms through my life. I’m now in probably my best state. One thing that helped was switching from vyvanse to concerta. I don’t know why but vyvanse didn’t really help. It just made me hyper focus on anything b
35.
by adamwk 1y ago
There are lazy collections, but they’re not default. Why the protocols are designed the way they are is until very recently all types were implicitly copyable, but most of the collection types like array and dictionary were copy on write; s
36.
by adamwk 1y ago
There’s a section in the proposal about this: https://github.com/swiftlang/swift-evolution/blob/main/propo... Tl;dr: Sequence and Collection are incompatible with noncopyable types and conditionally conf
37.
by adamwk 1y ago
Agreed, I left the episode thinking I didn’t take the right college courses to understand it. There were a lot of “proof is trivial” or “draw the rest of the owl” types of explanations
38.
by adamwk 1y ago
I guess this is a side-effect where, as things stood, developers were incentivized to just forgo IAP and force users to jump through hoops to find how to give them money; and that in turn wasn’t customer friendly. But in general I much pref
39.
by adamwk 1y ago
Yeah NSURLSession is great and I always find whatever library I’m forced to use clunkier than using it directly with some helper methods.
40.
by adamwk 1y ago
Tim Sweeney has his own app store that does the same thing as Apple.
41.
by adamwk 2y ago
Odersky forcing through major syntax changes for Scala 3 was such an unforced error. It's baffling add new syntax on top of major semantic changes to the type system.
42.
by adamwk 2y ago
I’m curious about the name. Since the move from cats to California regions, they’ve seemed to be regionally or biom grouped. We were in sierra regions for a while (10.10-10.13) then beach regions (10.13-13). 14 was Sonoma so I would’ve expe
43.
by adamwk 2y ago
It happens every year? Just buy the iPhone 15, which will drop in price next week.
44.
by adamwk 2y ago
I’m skeptical that this will be a win for users. Most Gamers are upset when they have to use any launcher besides Steam and I don’t see how this will be any different. Android always had third party app stores, yet nobody uses them.
45.
by adamwk 2y ago
What's purpose of the left-eye shield?
46.
by adamwk 2y ago
I agree. It seems like you're back to the typesystems of c or java 1.6. The very typesystems that drove people to ruby and friends in the previous decade.
47.
by adamwk 2y ago
I guess to me it looks like yet another monads for JS library. I get its a marketing page but marketing to whom? Maybe there's a better document to share on HN that shows how Effect improves those features?
48.
by adamwk 2y ago
the rust traits are not overloading though (at least not in the same way as swift), that’s just implementing a trait on a type. I think the distinction is that with traits or protocols you get a lot of expressivity, reducing the need for ov
49.
by adamwk 2y ago
Swift's ownership features are still new and going through evolutions; so its current state isn't the necessarily the vision or where it will be in a year. E.g., here's a proposal that allows one to create a lifetime dependen
50.
by adamwk 2y ago
60% of those people were not employed, unlike the Amazon workers workers
51.
by adamwk 2y ago
But I don't think that's true either. See: the Inquisition where even converted Jews weren't safe
52.
by adamwk 3y ago
It's the same on iPhone for i'm guessing DRM content
53.
by adamwk 3y ago
I agree its pretty niche; but i still think its better for users, who will probably never interact with it directly, than placing an arbitrary ceiling for certain functions
54.
by adamwk 3y ago
How is it stunted or limited?
55.
by adamwk 3y ago
Swifts enums can be recursive though as can rusts
56.
by adamwk 3y ago
I may be out of my depth here as I've only casually used Rust, but this seems similar to Swift's proposed lifetime dependencies[1]. They're not in the type system formally so maybe they're closer to poloneius work [1]:
57.
by adamwk 3y ago
Screen size isn’t the problem for mobile, it’s tap targets
58.
by adamwk 3y ago
Well going off the article he’d at least not have a criminal record
59.
Better effect type management with coroutines (2022)(cohost.org)
1 points by adamwk 3y ago|0 comments
60.
by adamwk 3y ago
A lot of work is going into move only types for swift to avoid the need of ARC in fundamental types like you mentioned. Classes aren’t going away but Apple is trying to evolve the language to cater to various performance needs. https:&#x2

More ›