Re:Swift at Apple: Migrating the Password Monitoring Service...
by dgs_sgd on Tuesday June 03, 2025 @06:25PM
(#44175439)
Interesting. If IBM was trying to solve for memory consumption, why do you think they picked Swift over alternatives that might also have achieved lower memory consumption?
[ Parent
| on HN ]
Re:Swift at Apple: Migrating the Password Monitoring Service...
by dagmx on Tuesday June 03, 2025 @07:22PM
(#44175828)
Swift is at a good middle ground of performance, safety and ease of use.
It has higher level ergonomics that something like rust lacks (as much as I like rust myself), doesn’t have many of the pitfalls of Go (error handling is much better for example) and is relatively easy to pickup.
It’s not perfect by any means, it has several issues but it’s quickly becoming my preferred language as well for knocking out projects.
Re:Swift at Apple: Migrating the Password Monitoring Service...
by ngcc_hk on Thursday June 05, 2025 @05:39PM
(#44196047)
What are those issues I wonder. I used for one project and not sure how deep the rabbit hole might be. Just wonder.
Re:Swift at Apple: Migrating the Password Monitoring Service...
by tgma on Wednesday June 04, 2025 @02:15AM
(#44177692)
Which other sufficiently popular modern language that's more efficient than Java lacks a tracing GC?
Rust and Swift are pretty much the only two choices and Rust is arguably much more pain in the ass for the average joe enterprise coder.