search

NancyFx / Nancy

Lightweight, low-ceremony, framework for building HTTP based services on .Net and Mono
http://nancyfx.org
MIT License
7.15k stars 1.47k forks source link

When will Nancy 2 be formally released? #2872

Open bluetentacle opened 6 years ago

bluetentacle commented 6 years ago

2.0.0-clinteastwood was released more than a year ago :(

m-barthelemy commented 6 years ago

Hi,

I have the same exact question. Nancyfx is still fully relevant even with the latest asp.net releases.

It's a bit scary to see that the whole project seems to have slowed down a lot, with this 2.0 pending release that doesn't have public pre/beta releases anymore.

Is there anything that basic users could help with, without having to fully understand the internals of Nancyfx?

Please take no offense, this is precisely because it's a great project that I/we express such questions and concerns.

hikeeba commented 6 years ago

I would also like to know what the plans are. This is a great tool and if there is anything that can be done I'd like to know.

khellang commented 6 years ago

Is there anything that basic users could help with, without having to fully understand the internals of Nancyfx?

You could sponsor some work through the Patreon?

m-barthelemy commented 6 years ago

You could sponsor some work through the Patreon?

Done!

Jaxelr commented 6 years ago

Likewise,

May i suggest adding the Patreon information on a more noticeable place (maybe the readme file)? Didn't found out until i read this thread.

bloritsch commented 6 years ago

What is left to do in Nancy? I mean what's the point in donating money to a black hole? Last update was a couple months ago, but it appeared to be really minor. I just want a solid base to do web services with. I need the NetCore support of Nancy 2, but I don't need any view support. I just need something that works out of the box. Nancy has been answering the mail on that, but I wonder if I should just use Owin directly.

sebandres commented 6 years ago

This Issue had a checklist of what was needed before 2.0.0-d could be released. But it is now closed without all checks being ticked so no idea.

Was actually wondering the same myself about the progress and what was left in the roadmap (to event see if I could contribute).

thecodejunkie commented 6 years ago

We've pretty much baked what we want in 2.0.. I'm just looking for some personal time to get the release out the door. My hope is that we can make that happen this or the week after!

sebandres commented 6 years ago

Cool @thecodejunkie! Looking forward to it. Would that be version 2.0-d or a final 2.0 release??

thecodejunkie commented 6 years ago

Most likely final :D

sdmimaye commented 6 years ago

I think we can all agree that the 2.0 Release will not gonna happen. I have been looking at this framework for a while now and i guess its no longer actively developed.

snavarropino commented 6 years ago

Any news? I am also thinking we will never have Nancy v2 released :-(

herrgruebner commented 6 years ago

Any update on Nancy 2.0? Last mention was "My hope is that we can make that happen this or the week after!" about two months ago...

williamhbell commented 6 years ago

Hi Andreas, do you have any thoughts about wrapping up the Nancy 2.0 release? Is there anything that can be done to help? Best regards, Will

sebandres commented 6 years ago

I think at this point given the direction that aspnet core 2.x has taken which aligns to some of the reasons of why nancy was born there isn't probably much value in investing into this framework anymore. Specially at the rate that .net core is moving and given the fact that it is also open source.

Perhaps it would be best to just archive this project so that people don't keep asking when v2 is going to be released?

pruiz commented 6 years ago

Well, there is people still using Nancy for already existing projects.. so I would favor releasing 2.0 and letting it clear there wont be a 3.0.. this way, the people who trusted the project wont be left alone in the dark.

turbo commented 6 years ago

In fact, there are even people using Nancy for new projects. A formal 2.0 release would be nice.

herrgruebner commented 6 years ago

Or upgrading their existing projects to net standard/core from framework. Having to use an old prerelease isn't great.

On Thu, 23 Aug 2018 at 09:06, turbo notifications@github.com wrote:

In fact, there are even people using Nancy for new projects. A formal 2.0 release would be nice.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NancyFx/Nancy/issues/2872#issuecomment-415180039, or mute the thread https://github.com/notifications/unsubscribe-auth/APNeJrYGnvytfQe3961b5sAhIdh3mV_Yks5uTcfagaJpZM4SiLQS .

sebandres commented 6 years ago

Yeah I second herrgruebner, also using a prerelease version in a mission critical system given the frequency of commits might not have been the best course forward for a project and that is fine because things change.

Just flagging this as a production ready release if there is no confidence in it (otherwise it would have happened already) might give the wron impression and encourage more people to fully adopt it which might do more harm than good if the community is no longer there to actively fix issues.

On Thu., 23 Aug. 2018, 7:42 am herrgruebner, notifications@github.com wrote:

Or upgrading their existing projects to net standard/core from framework. Having to use an old prerelease isn't great.

On Thu, 23 Aug 2018 at 09:06, turbo notifications@github.com wrote:

In fact, there are even people using Nancy for new projects. A formal 2.0 release would be nice.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NancyFx/Nancy/issues/2872#issuecomment-415180039, or mute the thread < https://github.com/notifications/unsubscribe-auth/APNeJrYGnvytfQe3961b5sAhIdh3mV_Yks5uTcfagaJpZM4SiLQS

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NancyFx/Nancy/issues/2872#issuecomment-415190633, or mute the thread https://github.com/notifications/unsubscribe-auth/AND4tW7Wbuc4vw9MoifrFkboMm0bjn4Tks5uTdA3gaJpZM4SiLQS .

pruiz commented 6 years ago

AFAIK there is an active community asking for a new release. If someone is not willing to use Nancy anymore, he/she is more than free to (not?) do so.

herrgruebner commented 6 years ago

Yeah, at this rate I am intending to migrate away from nancy, and I don't think I'll make anything new with it. The .net framework -> .net standard migration was enough of a headache without having to swap out Nancy at the same time, which is why I haven't already.

Although from what's been said earlier in this issue, nancy 2 is ready for release, and people do want it. If there's no further support, that's fine, but if the work's been done and people want it, I think it makes sense to release.

On Thu, 23 Aug 2018 at 09:53, Sebastian Andres notifications@github.com wrote:

Yeah I second herrgruebner, also using a prerelease version in a mission critical system given the frequency of commits might not have been the best course forward for a project and that is fine because things change.

Just flagging this as a production ready release if there is no confidence in it (otherwise it would have happened already) might give the wron impression and encourage more people to fully adopt it which might do more harm than good if the community is no longer there to actively fix issues.

On Thu., 23 Aug. 2018, 7:42 am herrgruebner, notifications@github.com wrote:

Or upgrading their existing projects to net standard/core from framework. Having to use an old prerelease isn't great.

On Thu, 23 Aug 2018 at 09:06, turbo notifications@github.com wrote:

In fact, there are even people using Nancy for new projects. A formal 2.0 release would be nice.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NancyFx/Nancy/issues/2872#issuecomment-415180039, or mute the thread <

https://github.com/notifications/unsubscribe-auth/APNeJrYGnvytfQe3961b5sAhIdh3mV_Yks5uTcfagaJpZM4SiLQS

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NancyFx/Nancy/issues/2872#issuecomment-415190633, or mute the thread < https://github.com/notifications/unsubscribe-auth/AND4tW7Wbuc4vw9MoifrFkboMm0bjn4Tks5uTdA3gaJpZM4SiLQS

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NancyFx/Nancy/issues/2872#issuecomment-415193467, or mute the thread https://github.com/notifications/unsubscribe-auth/APNeJuFm5BpQy1TZaAhfbKtv0PrFfTsMks5uTdLAgaJpZM4SiLQS .

grumpydev commented 6 years ago

Andreas and I intend to look at this when we are both back off holiday, there's some things that need updating so they work with the latest bits (again), then we will put a release out.

cguedel commented 5 years ago

Any update?

jdixon-86 commented 5 years ago

Yeah this is the first I've seen about Patreon. Unfortunately I've also started converting my projects because I thought this wasn't actively developed anymore. I have the same Razor issue that I posted about in April of 2017 still open.

aespinoza commented 5 years ago

Yes, this is sad. I have also started to port my projects. I am currently looking at using Asp.Net Core with Carter.

GusBeare commented 5 years ago

Shame. I love Nancy and have built a web site, a simple CMS and various web services with it. But Nancy lives on at flicka20.com and many sailors out there enjoy the site it delivers!

PedreHavenga commented 5 years ago

Also keeping an eye on this as we want to .Net Core soon. Please any update if the 2.0 would get a release or is this dead in the water?

nkosi23 commented 5 years ago

I think people talking about the death of the project are being a bit harsh. The project has been alive for many years and the last commit was made 4 months ago which is not that old. There is no outstanding critical bug in the last stable release. So maybe we can say that the unpaid volunteers who have done an outstanding work creating Nancy have been too busy lately to ship the .NET Core support feature, however I think it is premature and unnecessary to bury the project and talk about its death. If I was the creator of the project, I would find this kind of feedback rude and ungrateful, as if all the work done and the history of the project do not matter if a hype feature is not shipped in real-time.

Regarding future relevance, Nancyfx is still highly relevant and the experience of developing websites/web services with Nancyfx is fundamentally different than the one offered by the framework shipped with .Net Core. I do not even understand how people can compare the two. There are also all these people using Nancyfx under Mono (which supports platforms, hardware architectures and build tools that .NET Core have no intention to ever support - at least not in the foreseable future). So Nancyfx is more relevant than ever. As far as we are concerned we are starting our new projects with Nancy with peace of mind.

But quite frankly, Nancy is one of the rare open source projects that we'll fork without hesitation even if it went unmaintained, because otherwise we'd simply end up creating the same thing. Nancy is a very elegant and unique solution to the problem it addresses. Thanks to its flexibility, we've built frameworks on top of it in ways that would have been much more difficult with the asp.net/.net core paradigm.

I appreciate and respect the frustration of those needing this feature but I felt it was important to counter-balance the direction this thread was going to so that the core devs can know that there are many people out there who have no intention to jump ship. Please be patient or invest time to submit a pull request if .NET Core support is so important for you, it will be time well invested. Remember that the source code is out there (and it is well written).

Nancy does not strike me as a dead project or a project without a future. The level of activity is the one I would expect for an already mature open-source project not even having corporate sponsors.

turbo commented 5 years ago

But quite frankly, Nancy is one of the rare open source projects that we'll fork without hesitation

I suspect that has been done by many already. Actually, we're currently in the process of doing that. Nancy is easy enough to understand to fork and maintain it because you can choose only to fork the parts you need.

m-barthelemy commented 5 years ago

So, now it's starting to get very embarrassing. @thecodejunkie @grumpydev What's going on? As I respectfully asked in this same issue 9 months ago:

Is there anything that basic users could help with, without having to fully understand the internals of Nancyfx?

If you plan to stop work on Nancy, please state it clearly. Don't make us have false expectations and hopes.

snavarropino commented 5 years ago

I also think the better to clearly show current status and plans. If nancy is already stopped (unfortunately as it seems ) there is no value to hide it.

JeancarloFontalvo commented 5 years ago

I'm newbie in this wonderful framework, me and my team, wants to know if is it good to start developing for a production project with this version (2.x) or to use the 1.x one?

Thanks for answering... :smile: and thanks for this awesome masterpiece.

btecu commented 5 years ago

@JeancarloFontalvo neither, use ASP.NET Core.

JeancarloFontalvo commented 5 years ago

@btecu But why? :open_mouth: I think Nancy seems easier to go also it "just works". Cand you provide your facts to go with go directly with .Net Core, It'd be helpful. :smiley:

btecu commented 5 years ago

@JeancarloFontalvo ASP.NET Core has borrowed the best ideas from Nancy (which were not really original to Nancy but still). In addition, Nancy hasn't really had anything merged in the last approximately six months. You don't want to use a framework that's not being maintained.

Jaxelr commented 5 years ago

Similar alternatives, Carter comes to mind, which of course lives atop ASP.Net Core.

crmtogether commented 5 years ago

Nancy just works and if you use docker/mono imo you need not worry too much about the project being maintained as you define the environment and don’t have to worry about OS upgrades. Every bit of software has a limited shelf life anyway. The people working on Nancy did this out of their own time and if they’re busy making money now good luck to them. They don’t need to answer to anyone either. If you have a bug, well then offer to pay for the fix. The guys or someone might be willing to do this in a timely manner of paid. If you don’t want to pay for it we’ll then it’s not really an issue for you.

webseb commented 5 years ago

@crmtogether

They don’t need to answer to anyone either.

Absolutely right. Offering OSS does not obligate you to spend your free time with free-of-charge support as well.

But: If the maintainers of an OSS project do not answer questions for an extended period of time that would be a strong indicator that I should look elsewhere for a suitable solution to my problems.

With this kind of radio silence I would not start a new project using Nancy@NetCore.

snavarropino commented 5 years ago

Totally agree, they don'y have to work in Nancy anymore, but at least, they clould crearly state what is happening with this framnework and if there is any plan or not

grumpydev commented 5 years ago

Before this turns into an argument, does anyone active on this issue actually want to help get this done? It would be good to get a netstandard 2 (or 2.1?) release done, including all the sub projects, but I have (intentionally) done very little with netcore etc. so far, and had nothing but hassle when I have used it, its not something I can just crank out.

snavarropino commented 5 years ago

I have some experience with netstandard and .net core so I could help somehow, but I am going to require some guidance...

crmtogether commented 5 years ago

If you look at http://thecodejunkie.com/2015/08/28/i-am-now-taking-contract-work-for-nancy/ I think this explains were things are at (even though it was written in 2015).

So the answer is perhaps to have a consolidated effort to raise some funds or pay a monthly subscription towards development *. How many people/companies would pay 50/100 per month for this?

*I'm assuming that the devs would want this ...but maybe not. We can ask after we get some commitment.

janoserdelyi commented 5 years ago

as an individual i'd be willing to pay some amount per month

gudatcomputers commented 5 years ago

I'm already contributing a small monthly amount via Patreon but would be willing to help get this working. We've come to love Nancy and use it alot. Specifically how great it is to test as compared to ASP.NET Core. Being a TDD shop this is super important to me. Is there a place where I can see what works is remaining for this? Or is it more just get in there and make it work?

danielmoncada commented 5 years ago

@khellang @thecodejunkie @jchannon any update regarding a 2.0 production release?

PedreHavenga commented 5 years ago

I am also keeping an eye on this thread. We are fully committed using Nancy in our organisation.

danielmoncada commented 5 years ago

@PedreHavenga We ended up switching to Carter, which provides Nancy like syntax on top of ASP.NET Core routing. Check it out: https://github.com/CarterCommunity/Carter

Dreamwalker666 commented 5 years ago

Can a list of issues be associated to this so people know what needs doing / completing for a 2.0 release? It's about time it got finalised.

Jaxelr commented 5 years ago

You mean like this milestone?

PedreHavenga commented 5 years ago

Can a list of issues be associated to this so people know what needs doing / completing for a 2.0 release? It's about time it got finalised.

I can maybe get a Dev or two to work on small issues if we can get a list of Tasks/Bugs that needs to be done to get V2 ready for Release. This will be slow going but we can give it a shot.