Quantcast

path forward

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

path forward

Torsten Curdt
Folks,

I've been a little out of touch with the project the past year. But
now that I want/need to use it I encounter problems all over the
place. It's a little annoying to say the least. I look at `docpad` and
feel jealous. Almost tempted to migrate.

The question is what people think is the way forward.

There is the question of 1.8 support. I would like to just drop
support for it - unless someone comes up with a very good reason. That
should fix the current mess with the `listen` gem.

What's the story with the asciidoctor gem? The least we should do is
have the dep listed in the Gemfile to avoid the unpleasant "getting
started" experience because of the leaked dependency.

Another thing we should discuss is to provide is a default web server.
Rack is all nice and dandy - makes it easy for people to plug in their
own server. But this is a web server for development. I am not even
sure it matters much which one to use. (Unless you use Thin which is
horrible for this use case)

So at least it should give the user a working-out-of-the box
experience on the first install.

It would be nice if we could discuss and agree on the next steps.

cheers,
Torsten

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: path forward

bobmcwhirter
Administrator
> There is the question of 1.8 support. I would like to just drop
> support for it - unless someone comes up with a very good reason. That
> should fix the current mess with the `listen` gem.

I agree.  Dropping 1.8 seems very reasonable.

> What's the story with the asciidoctor gem? The least we should do is
> have the dep listed in the Gemfile to avoid the unpleasant "getting
> started" experience because of the leaked dependency.

Yes. Or integrate it with the Tilt stuff?  I’m pretty ignore of Tilt, but however markdown/etc work, so should AsciiDoc.

> Another thing we should discuss is to provide is a default web server.
> Rack is all nice and dandy - makes it easy for people to plug in their
> own server. But this is a web server for development. I am not even
> sure it matters much which one to use. (Unless you use Thin which is
> horrible for this use case)

As long as it works, I have no opinion.

> So at least it should give the user a working-out-of-the box
> experience on the first install.
>
> It would be nice if we could discuss and agree on the next steps.

I agree completely with you.  We should spend some time improving OOTB and also ensure we have a non-pre gem that we can recommend.  `gem install awestruct` should be all that’s required to get started.

        -Bob
---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: path forward

Torsten Curdt
>> What's the story with the asciidoctor gem? The least we should do is
>> have the dep listed in the Gemfile to avoid the unpleasant "getting
>> started" experience because of the leaked dependency.
>
> Yes. Or integrate it with the Tilt stuff?  I’m pretty ignore of Tilt,

Same here.


> but however markdown/etc work, so should AsciiDoc.

Agreed.


>> Another thing we should discuss is to provide is a default web server.
>> Rack is all nice and dandy - makes it easy for people to plug in their
>> own server. But this is a web server for development. I am not even
>> sure it matters much which one to use. (Unless you use Thin which is
>> horrible for this use case)
>
> As long as it works, I have no opinion.

Same here. Thin and ctrl-c just aren't good friends.


>> So at least it should give the user a working-out-of-the box
>> experience on the first install.
>>
>> It would be nice if we could discuss and agree on the next steps.
>
> I agree completely with you.  We should spend some time improving OOTB and also ensure we have a non-pre gem that we can recommend.  `gem install awestruct` should be all that’s required to get started.

Word!

cheers,
Torsten

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]

Loading...