<p dir="auto">http/3 support?</p>
<p dir="auto"><a href="https://www.rfc-editor.org/rfc/rfc9114.html" rel="nofollow">https://www.rfc-editor.org/rfc/rfc9114.html</a></p>
<p dir="auto">Hi 👋🏻</p>
<p dir="auto">I have tried Deno several times, before version 1.0, and with the latest version. One obvious problem I see, and which I think is huge, is the permission system. Currently, when we run a script with Deno, we have to specify the different permissions we want using arguments like <code class="notranslate">--allow-run</code>, <code class="notranslate">--allow-read</code>.... or <code class="notranslate">--all</code> or <code class="notranslate">-A</code> in order to accept all permissions.<br>
The point is that by allowing all permissions on a program, we expose ourselves to serious risk to the machine or the user, but out of "developer laziness", we don't want to have an execution line like:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="deno run --allow-read --allow-net --allow-write --allow-env mod.ts"><pre class="notranslate"><code class="notranslate">deno run --allow-read --allow-net --allow-write --allow-env mod.ts
</code></pre></div>
<p dir="auto">That's why I propose a new way of working. Arguments are still important, especially for everything CI. At the same time, for a better user experience, I can see something like:</p>
<div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="deno run mod.ts
mod.ts needs the net permission. Do you allow it?
 - Yes
 - No
&gt; Yes
mod.ts needs the write permission. Do you allow it?
 - Yes
 - No
&gt; Yes"><pre class="notranslate">deno run mod.ts
mod.ts needs the net permission. Do you allow it<span class="pl-k">?</span>
 - Yes
 - No
<span class="pl-k">&gt;</span> Yes
mod.ts needs the write permission. Do you allow it<span class="pl-k">?</span>
 - Yes
 - No
<span class="pl-k">&gt;</span> Yes</pre></div>
<p dir="auto">Once the developer has entered his preferences, they are cached, so that he doesn't have to specify them again.</p>
<p dir="auto">An alternative would be to have a configuration file for this, specifically, add this possibility to the current configuration system.</p>
<p dir="auto">I think a better developer experience at this level would bring more developers into the project, or at least interest a part of the community.</p>
<p dir="auto">This is an open suggestion, and I would love to hear from the developers and the Deno team about this one.</p>