alexarena

Brian Krausz

Sad, but not surprising to see Apple discontinue the Pro Display XDR. Hard to go back to 5K once you’ve used 6K.

In 2006 the iPhone was announced without an App Store and Apple’s party line was to just build/use web apps.

Fast forward to 2008 and the App Store is launched along with Super Monkey Ball – a day one app – the perfect game to demonstrate the power of a true native app that could _never_ be achieved on the web.

This is very cool. It seems like the prompt is asking the LLM to one shot an answer. Have you tried asking it to make a group, confirm whether it's correct, and repeat with the remaining words? (like a human would)

Curious how you’re implementing the background queue for publishing? Something custom in Rust?

interval.com founder here, this is correct! Everything w/ us is defined in our SDK.

So instead of writing React code or using a drag-and-drop builder, you define everything ranging from simple forms to more complex views in Node.js or Python code using our SDK.

Thanks! On the differences between Retool: the output (customer support tools, admin dashboards, etc.) is pretty similar between both products, but _how_ those tools are built is really different.

Something like Retool gives you a drag-and-drop UI builder, Interval is made for backend devs and lets you create UIs directly in your backend code. So you don’t need to learn another drag-and-drop tool or frontend framework.

Re: where the code actually runs… this is another really cool component of Interval. We host the UI for you on interval.com but the actual backend code (including everything sensitive like your environment variables, business logic, etc.) runs on your infra and Interval can’t see it by design.

Founder of https://interval.com here. We're somewhere in-between Retool and Windmill which was mentioned on this thread.

Like Windmill, Interval is heavily code-focused. Our model lets you define tools in your existing TypeScipt/JavaScript codebase.

Like Retool, you can use Interval to build complete internal dashboards that handle the "view stuff" side of things, not just the script/workflow "do stuff" pieces.

This is cool! Curious if it would be possible to run the model on device?

Honestly kind of impressed that the HegartyMaths guy independently found this and then handled it without (explicitly) threatening to sue you.

Congrats! Cool to see a new class of JS runtimes springing up. Lots to be excited about here, but cold start time seems like a game changer for building at the edge.

Thanks! We just switched to Docusaurus, would absolutely recommend. We started w/ a separate marketing site and docs site, but since our team are basically all engineers, we just decided to use Docusaurus for everything.

Their availability sharing is top notch, too.

Recently started using Cron, happy to hear they plan to continue to develop it as a separate app + excited to see Notion take on more of the traditional office suite.

Both of those seem great, we just have a slightly different approach, primarily around our model for integrating into your codebase and how we collect input/display output. Ravi, hopefully you recall the context for that call was us investing in our prototype version of Interval vs. use something like Airplane that was being built commercially. Thoroughly enjoyed our chat but just want to be clear that our take on this problem predates our conversation and was disclosed during it :)

Haha love the name Wooey for that. Also, very cool to see other people exploring the same space. We experimented w/ a similar arg parsing system, but ended up w/ our current approach so that it's possible to build multi-step workflows that conditionally show different inputs at different stages of the workflow.

Yes, letting non-technical teammates run stuff that was previously only accessible on the command line is basically the perfect use case. In terms of the specifics of your setup: without having worked with an HPC cluster before, I'm not 100% on exactly what it would take, but I'm pretty confident it's possible. The SDK component is super lightweight, so if we can get Node.js running, we can get Interval running. Feel free to email me (alex at interval dot com) and I can help you with this.

Thanks! "Seamlessly providing a front-end for interactive scripts" is a really solid description of what we're doing. Honestly the interactive part is what I think is the most important to get across. A big part of why I started building this was I wanted to prompt for input/display output across multiple steps, basically in conversation with the script.

I've been using this for a bit and it's incredibly cool to write plain markdown files VS Code and see them reflected immediately online. Well done + exciting step forward in Bring Your Own Client.