yahns Ruby server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: yahns-public@yhbt.net
Subject: tentative plan for yahns 2.x...
Date: Tue, 12 Jul 2016 02:43:43 +0000	[thread overview]
Message-ID: <20160712024343.GA13340@dcvr.yhbt.net> (raw)

Remove kgio and unicorn (and kcar) as dependencies.

kgio should not be necessary for Ruby 2.3 users, and I'd
rather not depend on Ragel or C any longer.

In retrospect, I think my decision to start kgio removed enough
impetus from improving non-blocking I/O in Ruby that Ruby was
set back several years because of it.

I think the only thing we really need C extensions for is
epoll/kqueue; and that might even be reasonably done with fiddle
nowadays (or ffi) since kernel ABIs are guaranteed to be stable.

Dunno what the timeline would be, but this is definitely
a long-term plan.

I've actually been enjoying Danga::Socket in Perl5 land which
uses Sys::Syscall under Linux.

                 reply	other threads:[~2016-07-12  2:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/yahns/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160712024343.GA13340@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=yahns-public@yhbt.net \
    --subject='Re: tentative plan for yahns 2.x...' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

	../../yahns.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).