what is “disgusting” about showing you accurate testing?
The JavaScript column is not experimental
The math column is JavaScript at the end… so you do not have any merit in your claims.
JS is always faster… in simple and complicated cases
there is no “experimental” in the folder name of the JavaScript column… (look at the images above)
it is easy to figure out what columns I’m using… icons represent the number column, javascript column, and math column (Glide certified expert should have no problem with that, LOL)
It looks like everything you say… is total made-up statements
Ps: Glide math column is a fantastic tool… it can detect so many formats and methods, but it will run a bit slower than precise JS code.
So… if you do not have thousands of rows, and you don’t need to use your calculations outside Glide… or your calculations are covered by the Math column… yes, there is no need to use JS; the difference will be just a few milliseconds.
I believe the Glide Data Editor is written in TypeScript.
As I said, in my experience the Glide Math column gives the most reliable results when working with dates. Your experience may be different, but I don’t care about that, because you don’t build my Apps, nor would I want you to.
The eighter way is not a direct code… it has to be translated and executed…
Why would someone like you want anyone to build the App for you? LOL
My point is that it is faster and more reliable if you stick to the JS format from the beginning. I always use it when making an App that interacts with the outside world or has over 25K rows.
For small native Apps… of course, the math column is a no-brainer.
I’ll give you a real-life example…
I have a system that updates my customers’ Google Sheets with my job worksheet… my customers are from all over the world…, and the dates from the date picker are fetched as a text… and written as the time in my time zone… now… there is no way that the math column will read that correctly… I hope you agree with that.
