5 ms·
The author is a bit inaccurate, depending on how you count things. At Microsoft we ship the C#, F#, and CB compilers on a cadence faster than 6 weeks; probably
by phillipcarter 7y ago
The author is a bit inaccurate, depending on how you count things. At Microsoft we ship the C#, F#, and CB compilers on a cadence faster than 6 weeks; probably every 2 weeks on average. New language features don’t make it in to each of these releases, but bug fixes and performance improvements certainly do. These releases are kore driven by tooling evolution (VS updates, .NET SDK updates) than language evolution though.
- wwwigham 7y agoAre those releases shipped in stable channels or only to, eg, VS preview users?
- phillipcarter 7y agoBoth. Preview features are enabled via a flag; the same compiler ships in both release and preview builds.
- pietroalbini 7y agoYeah, I only counted releases implementing new features, not every single one (both for Rust - even though we have few point releases - and for the other languages). Also some compilers don't have a fixed release schedule, which made gathering those stats a bit hard.
- correct_horse 7y agoIs CB compiler a typo for VB?
- tus88 7y agoAnd what on earth is "kore"?
- user5994461 7y ago.NET Core on kubernetes?
- phillipcarter 7y agoTyping on a mobile device.
- azakai 7y agoI assume the author is thinking of compilers like Clang and GCC when saying it's unusual to ship rapid releases. Yeah, there are definitely other examples, like you mentioned. Another example is Emscripten, which ships a new version every 1-2 weeks or so (which includes latest development LLVM+Clang). Most indications suggest that cadence works well for us, but it does have some risks.