goodSyntax

5 tahun yang laludiscuss

I don't understand the benefit of that. Could you explain please? It sounds to me like doing what you describe would prevent all the wins of serverless - scaling and only paying for the runtime you use. In what you describe, you get zero auto-scaling unless you implement it yourself, and you pay more than just lambda or just a http server. It sounds like adding another layer of complexity on top for no benefit

goodSyntax

5 tahun yang laludiscuss

I don't see how this would be useful for people other than Google/Amazon/Microsoft because, to my uneducated self, it seems like their problem is driven by this:

> Over the past decade of research and experimentation in memory overcommit, we observed a distinct trend across millions of servers and clients: the size of page cache has been decreasing because of the growing popularity of cloud storage. Nowadays anon pages account for more than 90% of our memory consumption and page cache contains mostly executable pages.

goodSyntax

6 tahun yang laludiscuss

https://github.com/rust-lang/mdBook

goodSyntax

6 tahun yang laludiscuss

i agree, the title and article is mostly hyperbole

goodSyntax

6 tahun yang laludiscuss

awesome job for a side project! looks very slick!

goodSyntax

6 tahun yang laludiscuss

Rust documentation uses markdown and it is amazing. Not sure what this person is on about. Everyone also knows Markdown very well. Also, if you are trying to color certain parts of your documentation blue, I think you're focusing on the wrong things.... Documentation should be about example code, which is perfectly fine in Markdown, you simply go:

```code <example> ```

Also I don't agree with the author's points about links in Markdown whatsoever.

comments