Re:Why it took 4 years to get a lock files specification
by zx8080 on Sunday October 12, 2025 @09:50PM
(#45563928)
Good point! What are the other peoper languages in addition to golang and maybe c++ for such tooling? However people... don't like (hate? fear?) c++ nowadays. And I doubt that golang fits well here. So what else? (I'm not pushing towards rust! It just seems rust got into some vacuum, however not fitting it fully like a square thing in a round hole.)
[ Parent
| on HN ]
Re:Why it took 4 years to get a lock files specification
by frizlab on Sunday October 12, 2025 @10:31PM
(#45564160)
That I’m sure of: Swift is extremely underrated and actually very close functionally to rust.
I don’t know other languages, but I’ve heard a lot of good things about zig.
Re:Why it took 4 years to get a lock files specification
by zx8080 on Monday October 13, 2025 @12:28AM
(#45564670)
> swift
Not everyone would want to get into Apple vendor-locked language (formally not, but it's like saying Chromium is opensource and not related to Alphabet/Google) and its development environment. Especially after JetBrains closed its swift oriented ide [0]. I hate xcode, sorry, after developing for too many years in it.
Re:Why it took 4 years to get a lock files specification
by frizlab on Monday October 13, 2025 @03:02AM
(#45565546)
Swift has an open-source and fully supported first party LSP integration and VSCode plugin, as well as a very active and welcoming community (forums). Using Swift w/o Xcode is now 100% possible and very much recommended by some people when no Apple development-platform specifics are required (native iOS/macOS apps).
The language was initially very much Apple-platforms oriented (had to be), but now that pretty much all the Apple stuff works well they moved beyond that.
Finally where the language comes from does not impact whether you can write good code with it.