Are all posts read by Ghisler?

[ghisler(Author)]

Are you 100% sure about this?

Yes, I'm reading all posts which are not in the section "User to user forums in other languages". However, I do not comment on all posts, only on thiose where I think I can provide a useful answer.

Moderator message from: white » 2025-01-24, 13:40 UTC

Thread split from the topic Merging of older forums that went off-topic.

[Fla$her]

only on thiose where I think I can provide a useful answer.

Any answer to a question posed to the author is helpful to the user. But somehow you don't think so. It's sad.

[ghisler(Author)]

Sometimes I do not know any answer, and even a Google search didn't turn up anything useful.

[Fla$her]

But in reality, there are many questions for which you don't need Google at all.

[wanderer]

But in reality, there are many questions for which you don't need Google at all.

When TC30.0 is released

Are you kidding? The author is not immortal.

I'm guessing you didn't get by his answer that he implied that not only he is not immortal but also not omnipotent! In addition to that, there is the community that answers many of the questions so that Ghisler spends his time mainly on improving TC and not answering questions in the forums. That's what we users want from him, right???

[Fla$her]

2wanderer
I suppose you yourself didn't understand what questions addressed to the author are meant. There are a lot of questions that relate only to his wishes. This doesn't apply to other users.

[wanderer]

2wanderer
I suppose you yourself didn't understand what questions addressed to the author are meant. There are a lot of questions that relate only to his wishes. This doesn't apply to other users.

Well, i imagine that if a question is pointed specifically to Ghisler, he will do his best to answer it if possible (in any case, that's the polite thing to do and AFAIK, Christian has not given any indication that he is not polite). If there have been some questions that have been left unanswered, there must be a good reason for it. Let's not forget this whole thing is practically a one-man show (ok, a few others may be involved but it's essentially one man behind it)...

[Fla$her]

Let's not fantasize, wearing rose-colored glasses, about what is and what is not. In many cases, I don't see any good reasons other than a banal reluctance or laziness to do it. And this is our common show, since we are its accomplices, and not just observers.

P.S.: There is no point in quoting the entire previous post.

[oko]

The author may spend more time creating the program than using it, so it seems logical and normal to me that:
a/ Users can give better advice than the author, because they provide solutions from practice, there are more of them, and they have the time and opportunity to react more quickly.
b/ The author can give better reaction to requests (suggestions) and bugs, as he/she is the best judge of what can and cannot be done, or the pros and cons of a suggestion and of course if it reachs your product line (development trend).

I personally miss more reactions from the author to suggestions. Because the users have no feedback as to whether the proposal was addressed to author, author's opinion, whether it will be implemented, and when (at least tentatively), or why not. Paradoxically some minor improvements take 10 years to be implemented and some more complex ones are implemented right away, and users may be frustrated that they must endure inconvenience for years. Perhaps some way of tagging proposals (not to be implemented, to be implemented in next version, to be implemented in future-higher priority, to be implemented in future-lower priority) would be a step in the right direction.

However, big respect to author for TC and active posters here on forum for good advices and opinions.

[wanderer]

Paradoxically some minor improvements take 10 years to be implemented and some more complex ones are implemented right away, and users may be frustrated that they must endure inconvenience for years

Well, it's all a matter of prioritization. What you say is true and has indeed been an annoyance for me that there are some (minor most of the time) suggestions that would probably take perhaps even less than 1 hour of his time, but still stay dormant since... forever. There are several large enhancements though (at least in major versions) so TC is advancing, no complaints there. I still insist, it's a one-man show and he can't grant every wish users may post, regardless of how small it may be.

IMO at some point, Christian could define a release which would include as many minor requests as possible, just to cleanup the todo list of all these years. There is no need to have major changes in all releases. Perhaps (and only if he decides to proceed with such a release) a post could be started (and pinned) in which users could post what they consider small (only) but important-to-them wishes, so that Christian can extract as many as possible from it and implement them all-at-once in 1 or 2 point releases.

[Fla$her]

oko has described everything correctly. I didn't think it was necessary to spell it out for the regulars. The key point here is:

The author can give better reaction to requests (suggestions) and bugs, as he/she is the best judge of what can and cannot be done

Some of the bug questions also remain unanswered from time to time.

I still insist, it's a one-man show

I'm afraid this is a one-sided view. Beta testers, authors of plug-ins, helps, automation tools, ideas and assemblies are all participants in the "show", on which its development and popularization depend. Everyone who has contributed is a part of this process, no less.

IMO at some point, Christian could define a release which would include as many minor requests as possible, just to cleanup the todo list of all these years. There is no need to have major changes in all releases.

I wouldn't say that there were major changes in all the releases. But your idea has definitely been in the air for a long time, if we talk about small but important improvements.
The main problem is not that there are major changes, but how supplements are prioritized. Often you are waiting for some important improvements, but some dubious and less useful husk appears.

Perhaps (and only if he decides to proceed with such a release) a post could be started (and pinned) in which users could post what they consider small (only) but important-to-them wishes, so that Christian can extract as many as possible from it and implement them all-at-once in 1 or 2 point releases.

The post/topic itself can be created by any user, who takes responsibility for monitoring and editing. I myself wanted to do this many times, but I gave up as soon as I thought about these dubious priorities and indistinct feedback.

[wanderer]

I still insist, it's a one-man show

I'm afraid this is a one-sided view. Beta testers, authors of plug-ins, helps, automation tools, ideas and assemblies are all participants in the "show", on which its development and popularization depend. Everyone who has contributed is a part of this process, no less.

I don't agree. Beta tester contributions depend on what Christian implements. He decides which way to go and they just follow. It's his product and he is one man only, that's the truth.

As far as plugins, automation tools etc, they are independent additions to TC, with their own direction, todo and wish lists. It's not Christian's decision which way they follow. He can only add new parts to TC in order to make their lives easier or give them new tools to add more features.

Perhaps (and only if he decides to proceed with such a release) a post could be started (and pinned) in which users could post what they consider small (only) but important-to-them wishes, so that Christian can extract as many as possible from it and implement them all-at-once in 1 or 2 point releases.

The post/topic itself can be created by any user, who takes responsibility for monitoring and editing. I myself wanted to do this many times, but I gave up as soon as I thought about these dubious priorities and indistinct feedback.

I agree. It would be pointless to create yet another such topic, unless Christian also agrees that it would be useful and that he will prioritize the implementation of as much as possible of those wishes in the near future. TC is his product though and he may have a todo list which he wishes to continue following. It's his decision if he wants to follow the suggestion we propose here.

[Fla$her]

I don't agree.

You used the term "show". All your arguments do not explain in any way why this word cannot be applied to participants in a particular process, product development, etc.

Beta tester contributions depend on what Christian implements.

It depends primarily on their own desire.

It's his product and he is one man only, that's the truth.

It's about development. Take out all the people I have listed and the development (the show) will stop.

As far as plugins, automation tools etc, they are independent additions to TC

There can be no independence where there is direct de facto dependence.

I agree.

Good.

[wanderer]

2Fla$her

You used the term "show". All your arguments do not explain in any way why this word cannot be applied to participants in a particular process, product development, etc.

From your answers, one may get the feeling we are talking about different things. Let me try to explain my point of view in more details.

TC is a one-man-show, meaning that Christian is the only developer for the core TC application (so there is a limit to how much code he can write in a certain amount of time). What the TC plugin developers develop and what they desire has no effect on TC itself and by that i mean if you remove the core TC product from the equation, the plugin developers have nothing to develop. In that sense it's a one-man-show (by show, i refer to TC itself, without the plugins).

Plugins are independent: Yes, they depend on TC but once a plugin developer decides to implement something, he can do whatever he wants and follow whichever direction he wants. Granted he is limited by the interfaces TC offers but he can base his work on them and do whatever he wants within those limits (hence the "independence").

[Fla$her]

TC is a one-man-show, meaning that Christian is the only developer for the core TC application

It's a mistake to take authorship alone as a basis; it's necessary to look at the essence of the term as a whole.

by show, i refer to TC itself, without the plugins

It was worth starting with this clarification, but I pointed out not only the plugins.

Plugins are independent: Yes, they depend on TC ...
... within those limits (hence the "independence")

Casuistry in contradictions.

In general, there is no more point in getting into polemics; these little things do not relate to the subject.