Is it related in any way to Fresh?
Aleph.js – Fullstack Framework in Deno
21–30 of 54 posts
Re: Aleph.js – Fullstack Framework in Deno
#22Earlier quoted context omitted.
It is. Deno runs TypeScript out of the box.
It strips type info and runs it as Javascript, though. There's no native typescript runtime, AFAIK (it doesn't enforce types at runtime, only at build time)
You do realize deno is based on the V8 JavaScript Engine and there isn't such thing as a typescript runtime even by Microsoft the developers of typescript?
Re: Aleph.js – Fullstack Framework in Deno
#23New web framework, why?
Why not? Is it a problem?
I wish every developer I had to work with had written their own framework at least once in their lifetime. It teaches you a lot.
Re: Aleph.js – Fullstack Framework in Deno
#24Earlier quoted context omitted.
Well deno is about five years old. That is to be expected, isn't it ? The timing feel similar to rust to me. It needed almost a decade to have real production ready project. Mozilla was an exception as they built it.
Maybe I'm spoiled, which I'm willing to consider being true. However, one could assume that projects at this stage would use versioning, pinning, and documenting the changes to the api, which obviate the need for these types of disclaimers. All caps disclaimers like this could discourage those who are otherwise capable from giving it a shot. Im not saying this is deno's fault, maybe it is and maybe it isn't, I'm only…
I'm currently developing an "experimental" piece of software, i.e. I am not even sure some features I want to add are possible, meaning I had to rewrite it a couple of times (and won't be the last). Having strict versioning, pinning, and documenting everything before it reaches a semi-stable state would discourage me from developing it altogether.
I agree with the approach they are taking, keep the disclaimer, put it out there, get some visibility to find early adopters and contributors and stabilize it. A year from now people will have forgotten about this thread and will see it a new and stable framework.
Re: Aleph.js – Fullstack Framework in Deno
#25Earlier quoted context omitted.
It is. Deno runs TypeScript out of the box.
It strips type info and runs it as Javascript, though. There's no native typescript runtime, AFAIK (it doesn't enforce types at runtime, only at build time)
Most languages intentionally avoid checking types at runtime except in specific situations where it's required (e.g. explicit typeof checks.) You do not want run time type checking on every variable access.
Re: Aleph.js – Fullstack Framework in Deno
#26Earlier quoted context omitted.
It is. Deno runs TypeScript out of the box.
It strips type info and runs it as Javascript, though. There's no native typescript runtime, AFAIK (it doesn't enforce types at runtime, only at build time)
You can always use one of the million different runtime type-checking libraries at IO boundaries.
Re: Aleph.js – Fullstack Framework in Deno
#27Is it related in any way to Fresh? https://news.ycombinator.com/item?id=31720110
They are different projects, Aleph is more or less the Next.js for Deno.
Also AFAIK Fresh uses a different architecture, where it can compile your app as micro frontends or island architecture if you like, you can check out Astro[0] to understand better this architecture.
Re: Aleph.js – Fullstack Framework in Deno
#28Earlier quoted context omitted.
It strips type info and runs it as Javascript, though. There's no native typescript runtime, AFAIK (it doesn't enforce types at runtime, only at build time)
You do realize deno is based on the V8 JavaScript Engine and there isn't such thing as a typescript runtime even by Microsoft the developers of typescript? https://en.wikipedia.org/wiki/TypeScript
Deno used to run the type checker with the `run` command, but now you need to pass a flag to run the type checker.
Re: Aleph.js – Fullstack Framework in Deno
#29New web framework, why?
Why?
Because most if not all frameworks run on Node.js, while Aleph seems to aim to be the Next.js for Deno.
Re: Aleph.js – Fullstack Framework in Deno
#30Earlier quoted context omitted.
It is. Deno runs TypeScript out of the box.
It strips type info and runs it as Javascript, though. There's no native typescript runtime, AFAIK (it doesn't enforce types at runtime, only at build time)
Im not sure why are you down voted, because your statement isn’t wrong, I’m not sure of Deno internals, but what GP said is also true, AFAIK is similar to run your TS app with ts-node but without the need to add a dependency, so it means that you just execute `deno run index.ts` and it worke, I’m not 100% sure but I think is also works with tsx/jsx files.