Cyclone was supposed to be a safer dialect of C. Shouldn’t it have replaced C by now, while also adding some improvements and reducing the burden of legacy code?
You must log in or # to comment.
being closed source probably didnt help. The website cites Rust as being a successor for some of its ideas, though.
It is not close-sourced. There are various repositories out there:
Oh you’re right. The website wasn’t giving those vibes that’s for sure, and the wiki didnt suggest what license it was distributed under during its lifecycle. Was it always open source do you know?
The project is almost 24 years old, the same age as me. It does not appear to have any sort of license in it’s earlier stage, but later on, they’ve added GPL 2.0 and LGPL 2.1.
From their site:
Cyclone is no longer supported; the core research project has finished and the developers have moved on to other things. (Several of Cyclone’s ideas have made their way into Rust.) Cyclone’s code can be made to work with some effort, but it will not build out of the box on modern (64 bit) platforms).
I read their webpage, but it is really vague. From a legacy point-of-view, wouldn’t it be better to incrementally add better language features, and if there happens to be a huge, breaking paradigm shift, initiate necessary refactoring of code base?
Basically, what I mean is something like:
C --> Cyclone --> improved dialect v1 --> improved dialect v2 --> Memory-safe unintelligible future dialect
Who do you expect to be adding more features?
Eventually people will ask the sabe about Go… Rust seems to be on the path of success thought.
Why do you say Go is going away? Afaik it’s in heavy use atm.
