Even Tyrano has more options than Ren'Py, for some resons many people in here don't like Tyrano though.
Then there's Twine. While limited due to it's format (HTML) it is probably a much better tool than Ren'Py simply because it runs the games much faster.
This effect is proceeded in real time with Ren'py
Can you explain how to do the same with Tyrano Builder ?
And this also is fully proceeded in real time with Ren'py
It can obviously be faster with Unity, but still it isn't this slow.
One VERY BIG disadvantage with Ren'Py is that it is still based on Python 2.7, which 1) is unsafe to use now,
Python 2.7 not being supported anymore doesn't mean that it's unsafe to use it. Among the 23 vulnerabilities that Python 2.7 had, only 5 regard directly Python and/or a module used by Ren'py. It's more or less the same number of vulnerabilities that will impact your web browser, and therefore Twine, each year.
But anyway this is totally irrelevant. The threat of having a game made with a engine that potentially have some vulnerabilities, is insignificant in regard of the threat presented by the game itself. Who tell you that the game made with Unity that you last played do not use a zero day exploit on your OS to install a rootkit ? No one... Since we have access to the whole sources of any Ren'py game, if it happen with Ren'py, because it can happen, there's someone that will be able to tell it to you.
Security threats regarding a language are relevant only if the software you make with it are accessible from a third party, what is not the case with Ren'py. No game open a socket in listening mode, not even locally, what mean that the attack can only come from third party software that you already installed on your computer. And there's near to 0 risk that something like that will happen one day. If someone have the knowledge needed to hook its own code to a Ren'py process, this in order to then exploit the vulnerability, he also have the knowledge needed to target your web browser. Not only it will be a target that he'll found more often, but it will also be a target that will have way more vulnerabilities he can exploit ; cherry on the cake, it will be a process that your IP filter let communicate with the wild, what offer him an entry gate.
and 2) is goddamn slow compared to fx Python 3.8.
If you look at the
You must be registered to see the links
, and go back in time
You must be registered to see the links
, you find a speed difference around 10%, what is far to be a "goddamn" difference. Especially when you apply this difference to games that... pause between each dialog line. What is interesting is that even now there's still some of the benchmark where Python 2.7 is faster.
But anyway, the port to Python 3 will not make Ren'py go faster, because the effective bottleneck is the time needed by the user to read. It will just push back the limits in screens, yet those limits are never reached by games ; it need more than 200 interactive buttons displayed at once before you start noticing a slowdown. It will also probably benefit to custom made displayable, like the hologram effect shown above by example, but near to no games effectively used them on this scene.
For some reason, it doesn't seem like the Ren'Py devs hurry too much adapting Ren'Py to Python 3.7+ even though Python 2.8 has been marked as extinct (and unsafe) since 2014 or so.
So, in fact you absolutely don't know what you're talking about. ..
PyTom is porting Ren'py to Python 3, the version 7.4.0 is already partly Python 3 compatible ; and yes he take his time, because you don't port an application that have near to 300 000 lines of code just by clapping your fingers. Especially when the said application is intended to works on four OSes and one emulation ; and more especially when you have near to no test suits, but this is something else.
As for Python 2.8, it's marked as extinct because it never existed ; therefore, saying that it's "unsafe" is totally ridiculous. And support for Python 2.7 have been dropped only the 1st January 2020. What effectively mean that PyTom took his time to release the first version partly Python 3 compatible. But this is totally understandable.
After 17 years with an average of one update every two months, he can't stop the updates for a full year or more ; then updating every week to fix the issues due to the port. And neither can he do expect for any developer using his engine to adapt their own code in one go. He have to make this port progressive, keeping the Python 2.7 compatibility until the moment the engine will be fully ported. This permit him to maintain the visibility of his engine, to guaranty that the Python 3 version will be as bug free as usual, and to let to the developer the time they need to port their own code.