Live data from Hacker News

Aleph.js – Fullstack Framework in Deno

github.com

31–40 of 54 posts

Re: Aleph.js – Fullstack Framework in Deno

#31
post #22

Earlier quoted context omitted.

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.

And that’s a good decision. It lets you choose fast start times and run your type checker in your editor or a separate console, which is what I do in all of my Node applications.

Re: Aleph.js – Fullstack Framework in Deno

#32

The only thing I ask to Deno is to make typescript development as immediate as running python. I'm exhausted by webpack and similar

You can think of Webpack as a really powerful, fully-featured, plugin-oriented webserver (to serve your JS, assets, data etc) for Nodejs.

You can rebuild the whole thing in Deno or whatever but you'll probably end up with the same boilerplate if you want it to cover all the features Webpack has.

Re: Aleph.js – Fullstack Framework in Deno

#33

The only thing I ask to Deno is to make typescript development as immediate as running python. I'm exhausted by webpack and similar

There is no way to do that because the v8 engine interprets and compiles JavaScript, not TypeScript. You can use esbuild, which is much faster than webpack. Deno uses swc, which is faster than webpack as well. You don't need to use deno to get that experience though.

Re: Aleph.js – Fullstack Framework in Deno

#35
post #22

Earlier quoted context omitted.

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.

Sounds like that could be resolved with a simple alias in your shell?

Re: Aleph.js – Fullstack Framework in Deno

#36
post #10
post #5

Earlier 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.

That doesn’t sound right to me. Rust 1.0 released in 2015. Facebook had a source control server in production in 2018. Does that count as “real”?

Deno 1.0 is roughly two years old. It's also apples to oranges. Deno is a JS runtime plus a std library. Aleph is still an experimental web framework. If you want to make a more apt comparison look at the web framework/library stuff in Rust that has frontend affordances/capabilities, which has a similarly immature v0.X feel to it.

Re: Aleph.js – Fullstack Framework in Deno

#37
post #34

Earlier quoted context omitted.

Probably can do both the server and client side.

Yes, but what it does mean ? What are the actual capabilities? There are no docs.

I couldn’t find docs either I reckon this has been posted here a bit too early

Re: Aleph.js – Fullstack Framework in Deno

#39
post #5

Earlier 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.

How many years before a language is mature enough that it's not to be expected? I'm thinking 5 years is starting to push it, but others may have other opinions. on edit: when saying push it I mean sort of still reasonable, but maybe a bit troubling? 7 years would definitely feel like too much to me. I wonder if there are any studies.

Deno 1.0 is actually only 2 years and not 5 years.

Re: Aleph.js – Fullstack Framework in Deno

#40
post #17

Earlier 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)

> 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)

Java strips type info and runs it as JVM byte codes. There's no native Java runtime, AFAIK(it doesn't enforce types at runtime, only at build time).

What's the problem?

Post reply on HN