ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Manuel P." <ayeye.sysforge@gmail.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Thoughts on ConTeXt: ditched
Date: Tue, 29 Dec 2009 13:48:11 +0100	[thread overview]
Message-ID: <4B39FA8B.4080009@gmail.com> (raw)
In-Reply-To: <4B38F1E9.1080005@wxs.nl>

Il 28/12/2009 18.59, Hans Hagen ha scritto:
> On 28-12-2009 14:44, Manuel P. wrote:
>
>> Another "problem" is the "fluidity" of ConTeXt: it changes rapidly and
>> the documentation is left behind. It's good because it responds very
>> quickly to the real world and users needs, on the other hand it's bad
>> because a new user has to be "in the club" for some time to figure out
>> everything.
>
> most of context (interface) is quite stable and hasn't changed in 
> ages; however with luatex/mkiv we can move forward and do things that 
> are impossible in good old tex but it's not neccessarily functionality 
> that you need now (after all, we have been producing pretty complex 
> docs with mkii and mkiv has hardly be touched the last years)
>
> Hans
>

Well, I'm using context for far too short time to know this. I was just 
saying what I've read around the internet, and since this is not the 
case: sorry! I'm simply too inexperienced :)

I've come to realize (as I was suspecting) that my problems comes mainly 
by my largely inadequate knowledge and experience with context. And this 
is fine and natural. My only wrong choice was picking context for my 
thesis (with a very near deadline) without knowing it sufficiently, not 
my interest in it.

So the message is: context is good and powerful, but not the best choice 
for this particular project since I don't know it so well. My choice and 
my error. Lesson learned: for important projects, stick with whatever 
you know well. Leave the experiments for free-time.

-- 
Manuel P.

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2009-12-29 12:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-27 15:54 Manuel P.
2009-12-27 18:41 ` Wolfgang Schuster
2009-12-28 13:44   ` Manuel P.
2009-12-28 15:12     ` Khaled Hosny
2009-12-28 17:59     ` Hans Hagen
2009-12-29 12:48       ` Manuel P. [this message]
2009-12-29  2:48     ` berend
2009-12-29 12:57       ` Manuel P.
2010-01-03 18:45         ` Piotr Kopszak
2010-01-04 21:46           ` Manuel P.
2009-12-27 19:16 ` Peter Münster
2009-12-27 21:11   ` Hans Hagen
2009-12-28 13:48   ` Manuel P.
2009-12-28 17:19     ` Peter Münster
2009-12-28 11:30 ` Gour
2009-12-28 12:36 ` R. Bastian

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

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

  git send-email \
    --in-reply-to=4B39FA8B.4080009@gmail.com \
    --to=ayeye.sysforge@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.nl \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 NNTP newsgroup(s).