Jump to content

Talk:Deno (software)

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

"Example" section does not belong to Wikipedia

[edit]

Wikipedia is an encyclopedia and not a guide book or manual. Example section is more of a guide on how to run a script, specify permissions and create a simple HTTP server. This content does not have a reliable third-party source and is not helpful to a Wikipedia reader. I suggest deletion of the entire section.

A good place to move this content is Mozilla Developer Network documentation pages about server-side programming. There is already documentation about Node.js and Express framework, so Deno would probably fit there as well.Anton.bersh (talk) 12:06, 14 May 2020 (UTC)[reply]

A small amount of sample code and commands does not constitute a WP:NOTMANUAL violation. Rather, the examples illustrate how Deno differs from Node.js (such as in requirement of explicit compiler flags, use of URLs for loading dependencies). The intent is to illustrate rather than be an instruction manual, which is totally acceptable in this kind of articles. SD0001 (talk) 09:56, 24 May 2020 (UTC)[reply]

Advertising-like claim not backed up facts

[edit]

FTA:

A standard library, modeled after Go's standard library, was created in November 2018 to provide extensive tools and utilities, partially solving Node.js' dependency tree explosion problem

I've seen this repeated a few times while reading about Deno and it doesn't make sense. 1) Node comes with a set of vetted modules -- same as deno. 2) How does this -- by any stretch of the imagination -- solve the problem of dependencies.

It should be explained or removed.

72.192.129.249 (talk) 05:56, 29 November 2020 (UTC)[reply]

Go has a very extensive standard library. Deno's standard library aims to be a loose port of this. As I understand it, the reasoning is to minimize the number of outside dependencies needed for a given task by including common functionality in the standard library rather than packing up each individual thing into a module, as you so often see on npm. Legowerewolf (talk) 08:04, 29 November 2020 (UTC)[reply]

Release history

[edit]

Is the release history section really worthwhile? It is just a large number of dates copied off GitHub, and doesn't seem particularly notable. Perhaps it would be better to just hit key dates of important changes early in development instead of updating the latest release number every other week. PiGuy3 (talk) 08:50, 13 October 2024 (UTC)[reply]