Our great sponsors
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
-
windmill
Open-source developer platform to turn scripts into workflows and UIs. Fastest workflow engine (5x vs Airflow). Open-source alternative to Airplane and Retool.
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
One issue that's been bothering me about Deno is this one:
https://github.com/denoland/deno/issues/14244
You have to use a third-party Docker container if you want to use Docker locally and develop on an M1 Mac (I use Docker to separate my different dev environments). And the issue was just ignored and became stale.
I recently built a full-stack app with Deno (and their Fresh framework https://fresh.deno.dev) called Invo (https://invo.ee) and the whole experience was delightful. I was able to move really fast and I never had to touch a configuration file, which also immensely helped with my motivation of actually building something - far too often I get stuck in a pile of config (I do Clojure mostly) and lose any motivation I had.
Have a look at https://github.com/esbuild-kit/tsx
_tsx is a CLI command (alternative to node) for seamlessly running TypeScript & ESM, in both commonjs & module package types.
It's powered by esbuild so it's insanely fast._
https://github.com/standard/standard/issues/384
I love deno so much and all of its ideas highlighted in the article (dependency management, security, performance) so much that I've build an entire framework around making scripting enterprise grade that is centered around deno support. The project is open-source [1], we even expose a web monaco editor and made the lsp support available using websocket and json-rpc. The goal here is to build enterprise-grade one-off script and workflows in deno, that can benefit from permissioned credentials, autogenerated UI (by parsing the main function parameters)
We have a hub [2], centered around deno, that serves as our library of integration. An integration for us, is just a script that uses the right dependency to do an atomic action like fetching data or doing a POST.
We are betting big on deno, and are hoping with windmill to be the framework to make it enterprise-ready for other things than webservers (which most of the deno framework currently focus on).
[1]: https://github.com/windmill-labs/windmill
Developed using Fresh framework (https://fresh.deno.dev) and deployed to Deno Deploy (https://deno.com/deploy). For persistent storage I use a simple MySQL instance from DigitalOcean.
AssemblyScript is a bit like that: https://www.assemblyscript.org/
But it probably goes into a slightly different direction (the design goal was a "TS for WASM", not a "TS with go routiens".
Decorators in TypeScript is still an experimental feature which may change depending on if/how it's implemented in JavaScript.
> To enable experimental support for decorators, you must enable the experimentalDecorators compiler option either on the command line or in your tsconfig.json
https://www.typescriptlang.org/docs/handbook/decorators.html
> ..the current decorators proposal, which is a work in progress
https://github.com/tc39/proposal-decorators
Oh, but I see that the proposal is now at Stage 3, which means the specs and syntax are stable ("completely described") and ready for browsers to implement.
On further digging, it seems decorators will be a standard feature included in TypeScript 5.0 planned for release on March 14th.
TypeScript 5.0 Iteration Plan - https://github.com/microsoft/TypeScript/issues/51362
Decorators in TypeScript is still an experimental feature which may change depending on if/how it's implemented in JavaScript.
> To enable experimental support for decorators, you must enable the experimentalDecorators compiler option either on the command line or in your tsconfig.json
https://www.typescriptlang.org/docs/handbook/decorators.html
> ..the current decorators proposal, which is a work in progress
https://github.com/tc39/proposal-decorators
Oh, but I see that the proposal is now at Stage 3, which means the specs and syntax are stable ("completely described") and ready for browsers to implement.
On further digging, it seems decorators will be a standard feature included in TypeScript 5.0 planned for release on March 14th.
TypeScript 5.0 Iteration Plan - https://github.com/microsoft/TypeScript/issues/51362