[PATCH] README.rdoc: remove incorrect URL for unicorn

[Eric Wong]

unicorn does not and will never use proprietary software or any
services requiring a terms-of-service or registration for
development. Having a github.com URL there is misleading to
potential users and hackers.

See commit df1d52d4a8a303119879cb2fb7466049393afbe3 for
rationale for the complete removal.
---
If you really must have something, point it to rubygems.org/gems/unicorn
But I really hate marketing and would rather not promote it at all.
Thanks.

The following changes since commit 49ed3267e4181b47fe53431be4805968eed81e3d:

Merge pull request #1426 from osamtimizer/fix/eliminate-warnings-on-test (2019-12-14 10:11:15 +1300)

are available in the Git repository at:

https://80x24.org/rack.git no-unicorn

for you to fetch changes up to 069b501fee065847d00671e5cbcd928224b6fd44:

README.rdoc: remove incorrect URL for unicorn (2019-12-15 04:01:53 +0000)

----------------------------------------------------------------
Eric Wong (1):
README.rdoc: remove incorrect URL for unicorn

README.rdoc | 1 -
1 file changed, 1 deletion(-)

diff --git a/README.rdoc b/README.rdoc
index 74a902f4..512bb49a 100644
--- a/README.rdoc
+++ b/README.rdoc
@@ -33,7 +33,6 @@ These web servers include \Rack handlers in their distributions:
* {NGINX Unit}[https://unit.nginx.org/]
* {Phusion Passenger}[https://www.phusionpassenger.com/] (which is mod_rack for Apache and for nginx)
* Puma[https://puma.io/]
-* Unicorn[https://github.com/defunkt/unicorn]
* uWSGI[https://uwsgi-docs.readthedocs.io/en/latest/]

Any valid \Rack app will run the same on all these handlers, without

[richard schneeman]

To follow up on this in the email list. The link was changed in https://github.com/rack/rack/commit/3eb4547bcb651f29addd05bf225f6ee009fca87b to point at https://bogomips.org/unicorn/ and the patch has not been applied. I do not know if there was other discussion outside of the link. I don't have commit to master, but did stage you change at https://github.com/rack/rack/compare/master...schneems:no-unicorn?expand=1 before realizing the link had been updated.

>   But I really hate marketing and would rather not promote it at all.

I personally think there is benefit to listing existing Rack servers in one place for easy reference in case future developers want to see the source. My personal preference would be to preserve some link to the project for documentation purposes.

[Eric Wong]

richard schneeman <richard....@gmail.com> wrote:
> To follow up on this in the email list. The link was changed in
> https://github.com/rack/rack/commit/3eb4547bcb651f29addd05bf225f6ee009fca87b
> to point at https://bogomips.org/unicorn/ and the patch has not been
> applied. I do not know if there was other discussion outside of the link. I
> don't have commit to master, but did stage you change at
> https://github.com/rack/rack/compare/master...schneems:no-unicorn?expand=1
> before realizing the link had been updated.

Thanks for the followup. But I prefer it point to
https://rubygems.org/gems/unicorn because bogomips.org is
likely going away once extortionists take over the .org TLD[*]

I don't believe in paying .org extortionists out of principle
(and also being a cheapskate :P). The folks running
RubyGems.org are probably more likely to justify the cost,
and I can update the gemspec to another URL without having to
bother anybody here.

> > But I really hate marketing and would rather not promote it at all.
>
> I personally think there is benefit to listing existing Rack servers in one
> place for easy reference in case future developers want to see the source.
> My personal preference would be to preserve some link to the project for
> documentation purposes.

I imagine most folks would rather shove unicorn under the rug
due to my refusal to use centralized/proprietary services or JS :>



[*] Fwiw I always expected something like the .org sell-out to happen,
hence my choice to not build a "brand identity" around bogomips.org
or any other name. No identity, nothing to lose :>

[Eric Wong]

richard schneeman <richard....@gmail.com> wrote:
> I personally think there is benefit to listing existing Rack servers in one
> place for easy reference in case future developers want to see the source.
> My personal preference would be to preserve some link to the project for
> documentation purposes.

Please reconsider. I don't have time to figure out MFA if it
becomes popular, again.

I remain anti-JavaScript and anti-GUI since I can't deal with
the implementation complexity. Any more popularity of unicorn
would just cause unnecessary friction and stress for both myself
and new users.

MFA or not, I'll gladly add backdoors to projects if bribed or
threatened.

Thanks.

-----------8<-----------
Subject: [PATCH] README: remove "Unicorn" reference

The robustness of unicorn has unfortunately led to more and more
unfixed bugs in other parts of the Rack ecosystem. Furthermore,
development is unsustainable and I can't afford to support new
users.
---

README.rdoc | 1 -
1 file changed, 1 deletion(-)

diff --git a/README.rdoc b/README.rdoc

index d54b2b32..781fbb3f 100644
--- a/README.rdoc
+++ b/README.rdoc
@@ -29,7 +29,6 @@ These web servers include \Rack handlers in their distributions:

* {Phusion Passenger}[https://www.phusionpassenger.com/] (which is mod_rack for Apache and for nginx)
* Puma[https://puma.io/]

* Thin[https://rubygems.org/gems/thin]
-* Unicorn[https://yhbt.net/unicorn/]
* uWSGI[https://uwsgi-docs.readthedocs.io/en/latest/]
* Lamby[https://lamby.custominktech.com] (for AWS Lambda)