Personally, I am discovering the world of No-Code and I am a little surprised by the reaction of some to Yes-Code.
I thought having the ability to create special or personal functions would be welcome and increase the power of Glide.
If the YC is a problem then you should remove the RichText, because CSS is the same thing, it is also code, except a lot of advanced users use CSS. And I don’t see a difference between a CSS and a YC script. It may still be too early to judge the YC, it may be necessary to give it time to make progress as some users do for CSS.
It’s super easy these days to find snippets of code and learn new things.
I’ve posted a few YCs that suit my personal needs and once or twice user requests. 100% of the codes are super simple and boil down to a few lines of code.
I like the idea that the Glide team can experience a certain function and that’s why I participate in YC as well.
I’ve also made the effort to provide the source or an image of the code each time so that everyone can learn or find out how it works. This may be a mistake, because obviously in the no-code world you like using external services but not knowing what’s inside!
But the greatest strength of Glide is its community, there are always friends to help others and share their tips and tricks just like CSS. And I’m glad to see some comments from less experienced users saying that they’ve learned something.
I think it’s a good thing that Glide leaves an open door to YC and CSS, free for everyone to use or not.