Hacker News Reader

Comment by brudgers | Hacker News Reader

I tried the try for free button.

The run took longer than my attention span. Since I'm not a potential customer, that's not a data point.

On the other hand, adding some text to the code editor page quantifying in minutes and seconds how long running example code will take would be a low effort way to manage user expectations.

Setting the context as a proof of concept is ok. It's honest. Letting people know it will be slow is good because it is honest, too.

Give people evidence that you can be trusted. Javascript that runs on back-button mouse over is not where to put your efforts. Good luck.

View on HN

Thanks for the comments, they’re good points. I’ll update the page as you suggested as yeah right now at the PoC stage it’s on the slow side.

Some of the time lag is due to us waiting for the build stage to complete, which isn’t actually the core part of the product and is only required for the playground site. I’ll try and make this more explicit too so that people can get a sense for how long the actual symbolic execution part takes, which is the actual delta that will be added if they were to use it in their DevOps pipeline.

We also have some speed improvements to the executor that we’ll be shopping soon. We’ve tested locally but just need to port to the cloud version.

I’m not quite sure what you meant by this statement

“Javascript that runs on back-button mouse over is not where to put your efforts.”

Was this something you observed on our site, or just a general point about prioritising the core product over fancy UI effects on the website? Would you mind clarifying?

I might be wrong, but I think he meant that JS runs, a new http request is made, when you hover over the logo. (Which is close to the back button, so it seems like JS is running, when you hover over the back button.)

Ah right yeah that makes sense. We built the website using NextJS so we kinda got this for free with their Image component.

Reply on news.ycombinator.com