deploy_feedback VS Preact

Hey all, Andy from the Deno team here. We're excited to share with you Deno Subhosting, an easy way to extend your platforms functionality by securely running untrusted JavaScript written by your users.

When we first launched [Deno Deploy](https://deno.com/deploy) in 2021, we were surprised at the volume of requests from companies about getting access to the APIs needed to run Deno Deploy. Many companies wanted to give their users the ability to write custom logic in their app, but setting this up in the cloud presents security concerns and a ton of infra work/maintenance.

We realized that there was an opportunity for Subhosting to solve a larger problem, which is allowing companies to easily and securely run custom code written by their users, without the hassle of maintaining said infrastructure.

Though we do have a few subhosting customers (Netlify being one of them), this launch makes our Subhosting product self-service, so any development team interested in extending their platform via their users' custom code can do so by [signing up](http://dash.deno.com/subhosting/new_auto) and [reading our docs](https://docs.deno.com/deploy/manual/subhosting). We have [an updated pricing model for Subhosting](https://deno.com/deploy/pricing?subhosting) as well, including a generous free tier fit for kicking the tires and building a proof-of-concept.

We'd love to get your feed back. Have you ever talked to your co-workers about allowing external devs to "have at it" with your platform? What would it look like to unlock the final 10% for your top customers? How have you approached this problem in the past?

Thanks for reading and the Deno team will be responding to comments!

[Read the announcement blog post.](https://deno.com/blog/subhosting)

That means we don’t need to transpile the Typescript code to ESM or CJS. Currently, only Deno Deploy can run your Typescript function out of the box. However, in order to keep the code small, we still need some sort of bundling. Luckily, Bun is also a bundler 😉

What type of apps do you code for your day-job? (I program for fun and curiosity, so that is why I ask that lame question.)

Do you use node.js? Deno is brought in part by the Node.js creator, Ryan Dahl, who wanted to fix/improve a lot of things he didn't like in node.js.

They also have "Deno Deploy" (with a free tier) to run your code on different servers scattered throughout the globe: https://deno.com/deploy

One of the reasons I love the `deno` executable is you can use `import` statements in your code and then tell `deno` to merge everything into a single .js file. I would then take that and publish it to Cloudflare Workers. I know you can do this with node.js and a bunch of tools, but it is so much simpler with `deno`.

The online version of DocTrack is hosted through Deno Deploy and is accessible here.

It runs on https://deno.com/deploy which runs on gcp at the moment but my understanding is that the underlying cloud provider could change at any time.

For deployment Deno offers it's own service, Deno Deploy:

https://deno.com/deploy

Disclaimer: Haven't used it yet.

Deno functions. Its different than docker containers that auto scale. https://deno.com/deploy

One of the biggest annoyances with Deno deploy/functions is that there is no way to store any data. This would be very useful to e.g. cache an auth token, store a key/value pair, etc. See also: https://github.com/denoland/deploy_feedback/issues/110

Is any work being done to fix this? Or is this out of scope currently?

One of the valuable features of Solid Start is that you can use so-called "adapters" to completely change the output into something deployable basically everywhere that serves pages and with quite a lot of options: there are adapters for amazon web services, cloudflare pages and workers, deno deploy, netlify, standard node server (the default), vercel, and static deployment - the latter allows us to build something that we can put on github pages.

In this post, we get to know more about Preact, one of this year's trending libraries. And we'll compare it to React to see which one suits better for our projects.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Those who want to develop a library that can be used by any other reactive framework. I often see SignalLike type that tries to subtype it.

https://github.com/preactjs/preact/blob/757746a915d186a90954...

The official Preact documentation.

At the very bottom of the image, there are 3 blocks that I chose to call application components. If you are building a cross-framework library, these can be built with whatever tools you want! Only catch is, all the tools you use to build it, will be needed by everyone consuming it. So choose wisely, and be mindful of how many kilobytes of third party code you will need in order to ship. In Schedule-X, I chose to use Preact. You will probably be fine with most lightweight virtual DOM libraries, and just like with frameworks there are a few to pick from.

>> React is not traditionally used for making games, but that's part of the fun and the challenge. R

> MS Flight Simulator cockpits are built with MSFS Avionics Framework which is React-like and MIT licensed:

https://github.com/microsoft/msfs-avionics-mirror/tree/main/...

preactjs may or may not be faster: https://preactjs.com/

Million.js is faster than preact, and lists a number of references under Acknowledgements: https://github.com/aidenybai/million#acknowledgments

https://million.dev/docs :

> We use a novel approach to the virtual DOM called the block virtual DOM. You can read more on what the block virtual DOM is with Virtual DOM: Back in Block and how we make it happen in React with Behind the block().*

React API reference > Components > Profiler:

DEV is a Rails monolith, which uses Preact in the front-end using islands architecture. The reason why I mention all this is that it's not a full-stack JavaScript application, and there is no state management library like Redux or Zustand in use. The data store, for the most part on the front end, is all data attributes.