A: divhunt and toddle are built for different purposes. divhunt is a website builder, similar to webflow. Both are mainly intended for building static websites. If you want to build anything more complicated you have to write code.
In this case "exporting code" and "rendering the website" is essentially the same thing. (potentially minus some code minification etc.)

toddle on the other hand is designed for building applications. Specifically complex applications that can scale. While the tools look very similar the differences are quite significant. Most of the problems toddle are designed to handle, divhunt delegates to the user by having them write code. (just to be clear this is not a criticism :) This is a good choice by divhunt since they are mainly focusing on static websites.

At its core toddle is a programming language designed specifically for building web applications. But rather than programming toddle with code, you use a visual editor.
Our hosting platform is built specifically for this and is a critical part of running a toddle application.

By building an integrated language, editor and hosting platform we are able to handle a ton the issues that would traditionally be left to the developer (coder).

Does this mean that code export is impossible? No. but it would take a substantial amount of work, and the end result would be an application that did not perform nearly as well as the hosted version.

What we have chosen to do instead is to export individual components. This is both beneficial for extending the functionality of other platforms (e.g. divhunt) but can also help developers move off toddle step by step if they should wish to.