What’s gone on at trycf ? It used to be simple “type here, run”.
Now it’s got a billion options, a complicated default, and takes x10 as long to run simple cfscript… ![]()
What’s gone on at trycf ? It used to be simple “type here, run”.
Now it’s got a billion options, a complicated default, and takes x10 as long to run simple cfscript… ![]()
See Slack
Hey all! After 13 years, I finally rebuilt trycf.com — something I’ve wanted (and tried) to do for a long time.
The classic scratchpad is still there: write arbitrary code, run it against any major CFML engine. But the new version goes a lot further:
More engines— every CFML engine you’d expect (Lucee 4.5–7, Adobe CF 10–2025, BoxLang, Railo, RustCFML), plus Node.js, PHP, Python, Bun, Deno, and static sites
More IDE-like— proper file tree, multi-file editing, syntax highlighting, LSP for CFML
Unlimited scratchpads— create as many as you want, no more single-file limit
Multi-file projects— the most-requested feature, finally here. Build an entire application, share it, and (if you want) deploy it to your own subdomain
Real databases— SQLite out of the box, plus MySQL, PostgreSQL, and Redis available for your projects. No more mocking it up to test queries
It’s in public beta — paid tiers are fully production-ready. Feedback and bug reports very welcome.
Check it out and let me know what sucks!
Ta for the update !
Hmmm. It now just gets stuck on an endless pod warm up routine. What a shame. It all looks very fancy but it doesn’t work.
This feels like a case of over engineering??? ![]()
The original scratch pad was perfect.
If we want more of application feel, we can just spin up a server using CommandBox?
TryCF was always just about quick dirty testing of either syntax or a UDF or some kind of code idiosyncrasy?