Update on IDE Extensions | NUKE

[giscus[bot]]

Update on IDE Extensions | NUKE

We are withdrawing our presences from extension marketplaces. Moving forward, extensions are provided exclusively through the website and are available as community and professional editions.

https://nuke.build/blog/2024/01/22/update-on-ide-extensions/

[muwanguzij]

When I click download.it keeps redirecting to this page.I have already starred

[mbedded]

Hello you two,

as first: I understand your decision and I like Nuke a lot (I haven't done that much yet but I want to use it more in my current and upcoming projects). As like other tools it makes builds on different machines and in CI/CD environments much easier. Especially everything is written in C# and it can be debugged locally.
I came across this post because the plugin is gone on the Rider marketplace. Thank you for clarification, why the plugin has been removed from there. There are still some questions/topics I would like to discuss:

1. What I can't really understand: Why is "debug configuration" a professional feature? I'm just starting with nuke and the "click and debug" shortcut in Rider to debug or execute any Target (especially when you are learning Nuke) is very handy. The other professional features may be nice, too. At the current state I don't need them.
   From my perspective it would be handy for first time users to get a good experience and see the "Helpers" like Solution-property or GitHub-property in action without much effort. I assume it was moved to the professional package to have a handy feature to nudge people/companies to support this project. From business view it's comprehensible.
   But I think the limitation to hide "click and debug" in the professional package can be seen negatively for new users like no to low support in the basic variant in their IDE.

2. Maybe you could point out what you expect when someone is blogging (mentioned in Sustainability Contributions) about Nuke.
   On the one hand, I want to avoid someone taking advantage of the rules like "write 4 articles per year". On the other hand, the question arises how often you can write something new about Nuke without quoting the release notes 1:1 (based on the example of 4 articles per year).

3. About sponsoring: Is it sufficient to sponsor you via Github (using the link above on your page) and the download page will automatically list the professional plugins, too or is there some additional work to do? Is there a difference between a one-time payment and a monthly sponsoring via Github (besides the benefits listed)? On a personal level I like to have a yearly payment/sponsoring when I support a project instead of a little bit every month. Will there be additional ways like Patreon/Buy me a coffee/Ko-fi/Paypal?

4. As a general question: Do you have a preferred way to "contact us"? There are some channels linked e.g. Mail, Github, Mastodon or Discord. Maybe a general "how to contact us" page with the preferred method (or maybe even a web form) would be helping :)

Sidenote: I saw that I used Nuke v6 back then, so my first steps are some time ago.
And please don't get me wrong: I appreciate Nuke and I appreciate the work to provide plugins to make its usage easier. As a developer myself I can fully understand that you and your project want to be supported especially when larger companies make or save some money by using OSS without anything in return. I tend to support projects and developers by paying something for their services, too. But in my current situation I don't do it yet, because it is only 1 hobby project and the 2 clicks to "change run configuration" are done quickly. If I use it more (especially in business projects) I will be happy to sponsor it.

Please keep up the good work! I just saw that v8 has been released and I guess I have to read some release notes now :)

Best regards
Matthias