You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2020. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,9 +128,11 @@ Before you decide to use the framework for new projects, please see the followin
128
128
>
129
129
>Then, a few months before my PhD defense (which happened very well, actually!), Microsoft announced that they wanted to make ML.net (which I actually fully support), the standard approach for machine learning in .NET. While this is great news (because I fully support MS giving more support for all ML practitioners out there), this eventually meant**that Accord.NET would eventually become obsolete as ML.net was on its path to become the de-facto ML library for .NET** in the foreseeing future.
130
130
>
131
-
>I think that the reasons above would have been already enough to explain why I decided to not update Accord.NET anymore after that. However... in addition, I have to say that, as a researcher, and not solely as a developer, I have also published in, and attended to,**the most important machine learning conferences in the world to date, and under this context, I need to say that in the academia world, no one has ever heard of the framework or the project itself**. Actually, from my experience, people in those conferences can laugh or even mistreat you,**if you ever mention you have ever developed anything in C#, specially for machine learning, as everyone[understandably] uses Python nowadays to accomplish tasks in this domain** (this is actually kind of true, as I myself only use Python to do my work, and while I love C#/.NET, I have to say that there is nothing that can compete with Python/Pytorch nowadays).
131
+
>I think that the reasons above would have been already enough to explain why I decided to not update Accord.NET anymore after that. However... in addition, I have to say that, as a researcher, and not solely as a developer, I have also published in, and attended to,**the most important machine learning conferences in the world to date, and under this context, I need to say that in the academia world, no one has ever heard of the framework or the project itself**. Actually, from my experience, people in those conferences can laugh or even mistreat you,**if you ever mention you have ever developed anything in C#**, specially for machine learning, as everyone[understandably] uses Python nowadays to accomplish tasks in this domain.**This happened even when those people were from Microsoft itself**.
132
132
133
-
>Therefore, in the past months, I have been pondering about archiving the project. To avoid that,**I am willing to make someone who would like, also an administrator of the project**.
133
+
>I could actually understand the reaction, as I myself only use Python to do my day-to-day work, and while I love C#/.NET, I have to say that there is nothing that could even remotely compete with Python/Pytorch at this day and age).
134
+
135
+
>Anyways, therefore, in the past months, I have been pondering about archiving the project. To avoid that,**I am willing to make someone who would like, also an administrator of the project**.
134
136
>
135
137
>I am also willing to change the license of any file where I am the single author (you can check the copyright headers in each file) to**MIT** so people can reuse individual pieces of code more easily. Anyone who becomes administrator is welcome to slice the parts of the project that still make sense to exist (e.g., the FFmpeg wrappers, statistical distributions, statistical tests and the simple transforms like PCA) and even start new libraries (hopefully in .NET Core) providing only them if wanted.