Project future

[Shujee]

Hi,

Thank you for this great project. Just wanted to ask if this project is still being maintained? Just saw that the last commit was made in Aug 2024. My client was concerned about it and wanted to know if we should depend on it or create a fork instead in case this gets removed in the near future.

[sebastienros]

Both, it works, battle tested, and you should still fork it since you depend on it.

[rivantsov]

Hi,
thanks for your inquiry and for the appreciation. Sebastian, thanks for stepping in and helping. Yes, project is not in active development now for a few years, just no time, too much other stuff. Some stuff like Grammar Explorer cries for refresh.

I agree with Sebastian, the core Irony library is solid and tested; it is .NET Standard 2.0, so it should run on any future platform. and I cannot imagine a reason for it to stop working in the future. I myself used it in NGraphQL framework, and it works great there.
A bit clunky and some api pieces feel outdated - but it works and would save you a ton of effort if you need a parser. Just for your piece of mind, make a copy of sources.

I tried to persuade MS that .net platform needs a parser tech as part of the platform - so take Irony or anything else as starting point and build a real thing; but the response from AndersH was - compilers use specialized hand-written parsers, so c# team is not interested; and for anything else - there are open source projects like Irony, you guys are doing a great job! Thank you, but the truth is - I don't have time or resources to do 'a fking great job'. Irony does not pay bills. While parsers are everywhere nowadays, not only compilers. Whatever, this is a sad situation.

By the way, everybody, if I layout plans for Irony next big Irony rebuild (have a lot of cool ideas!), would anybody be interested to join in implementation?
thanks
Roman

[Shujee]

Thanks for the input @rivantsov. Really appreciate the amount of effort you have put in. I'd love to be part of your future version development, but unfortunately I don't have much experience with building parsers or compilers. I'm more of an app-development guy, but if there's any role you see in this regard that I could play, I'll be happy to discuss.

[jetloong]

By the way, everybody, if I layout plans for Irony next big Irony rebuild (have a lot of cool ideas!), would anybody be interested to join in implementation? thanks Roman

I am interested. I like the Irony parser project and I am using it as well in our company. Just afraid that I am not good enough. While I am used to contribute to libraries for my company, I am not yet experienced in the public domain. If this is okay I am very interested to learn and contribute, too.

[NicholasFreeman]

@rivantsov
You mentioned you have a lot of ideas for a future rebuild/design of Irony. Could you start a roadmap thread where we could contribute and workshop ideas?

[rivantsov]

I am writing it down, expect it soon, thanks for reminding me

[rivantsov]

I created new repo Irony3, read my thoughts there in Wiki: https://github.com/IronyProject/Irony3/wiki
thanks