[bartlomieju]

Bartek from deno.land here, happy to answer your questions should you have any.

Deno 1.13 is one of the biggest releases to date - we're especially happy with stabilization of native HTTP server bindings. We plan to focus on squeezing the last bits of performance out of it in the coming weeks.

Personally I'm most excited about type checking example code in Markdown files. It's critical to keep your documentation up to date and doing so for code blocks embedded in JSDoc comments or Markdown files was very challenging. With this release we got you covered - just run "deno test --doc" on your codebase.

[brundolf]

I haven't been following the Deno community super closely; do you know if people have converged yet on a go-to web framework, similar to Express? Does this stabilization play into that progression at all?

Last I checked there were several promising-but-fragmented options, so I'm hoping the community has or will pick a "standard" answer for "I want to make a web service", since that seems like one of the headlining (the headlining?) usecases for headless JS

I'm also, and this is more off-topic, but I'm wondering if there's an answer for NextJS out there on its way. The latter is eating (a portion of) the world a little bit right now, and could singlehandedly keep some parts of the industry on Node.

[bartlomieju]

Oak [0] is the go-to web framework in Deno ecosystem, it has Koa-like API. There's also Opine [1], Drash [2] and some other that are also highly spoken of by folks at the Discord. AFAIK Oak used native HTTP bindings since their inception (if you were running with --unstable flag); and now that API is stabilized it will use it by default.

As for the NextJS; there are also a projects that try to mimic its API like AlephJS [3] and Fresh [4].

[0] https://github.com/oakserver/oak [1] https://github.com/asos-craigmorten/opine [2] https://github.com/drashland/deno-drash [3] https://github.com/alephjs/aleph.js [4] https://github.com/lucacasonato/fresh

[brundolf]

Thanks for the info! Glad to hear that the ecosystem is coming along. I look forward to the day I get an opportunity to use Deno at work

[wuschel]

Hi Bartek, thanks for jumping in.

I am wondering whether one could forego Typescript and use one of the Ocaml/F# to JS converters for the frontend and backend code. Would it even make sense, and would it be convenient to use? How would one set up such a project?

[sprkv5]

+1 for Ocaml/F# and also the new ReScript. Would you be open to support these on Deno?

[bartlomieju]

If the tooling you're describing outputs JS sources there's nothing preventing you from using it. Currently there's no way to hook them up directly into Deno, so you'd have to resort to separate build step (via some kind of script, I presume this is just a matter of calling appropriate binary).

If those tools help you write better code and you prefer to code in Ocaml/F# then it definitely makes sense, but of course this is personal preference.

Drop by at our Discord server [0] to get some tips on how to set up such project.

[0] https://discord.gg/deno

[searchableguy]

I think you might be interested in this open issue about public API for compiler.

https://github.com/denoland/deno/issues/1739