On 2026-05-04 10:04, Mr wrote:
> 
> Initiatives, brainstorming are always good ! And POV development is indeed not
> at all in decline but I wouldn't look at macros to advocate that (because core
> developers know best the real gap between lowest levels and the SDL, I would
> rather look at master codebase pull requests:[...]
 >

There is a, almost natural, discrepancy between developers and users of 
a program. They have different interests, goals. Nothing wrong with 
that. They speak different languages (in life and in code (in POV-Ray's 
case)). English bridges the gap between my Dutch and your French. What 
if there is no gap at all, in coding language? Front end, back end 
middle ware all in the same language. Coders and users speak the same 
language, they all "code". That removes "friction". That can enhance the 
product.

I'm in no way suggesting that in such a case users can suddenly be core 
POV-Ray developers. Knowing the moves of chess pieces don't make me a 
chess player.

Decline; It always saddens me when I mention POV-Ray within a relevant 
context that the response is, "yeah, I used that 20 years ago, is it 
still around?".

Anyway, thoughts like this made my give it a try and see wether it would 
work. As said, it is the first working version. In theory the concept is 
very extensible up to the question: is POV-Ray the plug-in to the 
modeller or is the modeller a plug-in for POV-Ray. Don't want to quote 
Goehte here, yes, boundaries should be set, but first have to be 
explored. So far, it's just a little fun project.

ingo

Post a reply to this message