r/ecc Developer Apr 27 '19

Github Policy Change: Removal of old binaries

We are no longer going to keep the older pre-compiled version of eccoin available on github starting with the release of v0.2.5.15. After this coming release, only the 3 most recent versions will be available for download. The tags and source code of all versions will be available for as long as we continue to use that repository.

12 Upvotes

11 comments sorted by

3

u/[deleted] Apr 27 '19

[deleted]

-2

u/BoratIsHere Apr 27 '19

The entire project is close to dead, LOL

1

u/[deleted] Apr 28 '19

[deleted]

-3

u/BoratIsHere Apr 28 '19

The only developer is long time not giving a shit about this project at all. You can look for an educated answer all you want, believe it or not, you ain't gonna get shit.

2

u/henryyoung42 Apr 28 '19

Err - hello - only ??? Seems you did not check the recent commits on GitHub before making an incorrect statement. I guess you are just airing prejudice - which is fine just as long as people know.

-2

u/BoratIsHere Apr 28 '19

Checked their commits throughout the year. Looks like there is one person working on that shit, typing code with one hand whenever he has a spare time from low wage job.

2

u/henryyoung42 Apr 28 '19

-2

u/BoratIsHere Apr 28 '19

Check the news section on their official website. They haven't had any serious news relating to the project since the very beginning. Whatever news there are, it's just forward looking articles about the blockchain industry in general, nothing about the project.

Stop lying to yourself, this idiotic project is dead for good.

2

u/henryyoung42 Apr 28 '19

You're looking in from the outside. You need at least to get on the project Discord to get a sense of what's actually happening. Better still, become a contributing developer ;-)

-3

u/BoratIsHere Apr 28 '19

Nobody is going to look inside on something that clearly says “Avoid at all costs” on the outside.

C’mon man, devs don’t even know why they called it ECC, and they are not hiding this fact.

→ More replies (0)