4 ms·
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
by dgs_sgd 1y ago
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?
- dagmx 1y agoSwift 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 also in the same ballpark performance as rust or C++. 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.
- ngcc_hk 1y agoWhat are those issues I wonder. I used for one project and not sure how deep the rabbit hole might be. Just wonder.
- tgma 1y agoWhich 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.