Aleph.js – Fullstack Framework in Deno
github.com
Aleph.js – Fullstack Framework in Deno
1–10 of 54 posts
Re: Aleph.js – Fullstack Framework in Deno
#2> WE ARE CURRENTLY REWRITING THIS FRAMEWORK, MANY THINGS ARE STILL SUBJECT TO CHANGE AT ANY TIME.
Noticing a pattern here with deno projects.
Re: Aleph.js – Fullstack Framework in Deno
#3> WE ARE CURRENTLY REWRITING THIS FRAMEWORK, MANY THINGS ARE STILL SUBJECT TO CHANGE AT ANY TIME. Noticing a pattern here with deno projects.
[deleted]
Re: Aleph.js – Fullstack Framework in Deno
#4[deleted]
Re: Aleph.js – Fullstack Framework in Deno
#5> WE ARE CURRENTLY REWRITING THIS FRAMEWORK, MANY THINGS ARE STILL SUBJECT TO CHANGE AT ANY TIME. Noticing a pattern here with deno projects.
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.
Re: Aleph.js – Fullstack Framework in Deno
#6Am I missing something? Or is there no actual documentation for its current incarnation? Clicking the link and then following the link for documentation is an infinite loop.
Re: Aleph.js – Fullstack Framework in Deno
#7> WE ARE CURRENTLY REWRITING THIS FRAMEWORK, MANY THINGS ARE STILL SUBJECT TO CHANGE AT ANY TIME. Noticing a pattern here with deno projects.
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 saying I'm noticing that rather than documenting through breaking changes people would prefer to make prominent disclaimers that are essentially buyer beware
Re: Aleph.js – Fullstack Framework in Deno
#8What is "fullstack framework" supposed to mean? "It can do everything"?
Re: Aleph.js – Fullstack Framework in Deno
#9Am I missing something? Or is there no actual documentation for its current incarnation? Clicking the link and then following the link for documentation is an infinite loop.
[deleted]
Re: Aleph.js – Fullstack Framework in Deno
#10> WE ARE CURRENTLY REWRITING THIS FRAMEWORK, MANY THINGS ARE STILL SUBJECT TO CHANGE AT ANY TIME. Noticing a pattern here with deno projects.
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”?