Design Meeting 2021-07-29

[kitsonk]

Q3 2021 Roadmap Review

• Remove native plugins API, introduce FFI API
  • Status update, that while FFI wasn't perfect, it was ready.
  • Action move forward, and improve things.
• Introduce new sub-process API
  • Deferred due to interested parties being unavailable.
• Stabilize native HTTP server API
  • Stabilized (except the web sockets)
  • Need to move everything over to the new API and find a way to deprecate std/http
• Add ability to ignore SSL certificate errors
  • @lucacasonato objected strongly to this, as well as @bnoordhuis is on record as also objecting in other forums. The feeling is it erodes security and it often used by people who don't understand the implications of what they are doing, and don't understand the right ways to address the issues they are encountering.
  • @ry strongly argued that it is a usability issue, and that other platforms (note-ably Chrome and cURL) how escape hatches.
  • Action move forward with a flag that is non trivial and makes it clear that you are doing something bad.
• Overhaul deno doc
  • @kitsonk has start working on deno_graph which was the first step in this process. Progress will continue when we have some of the fundamentals in place.
• More options in configuration file
  • @bartlomieju indicated that while the initial work was done, that a conversation with him and @piscisaureus led him to believe that the solution was nonviable, especially when it came to how it would align with Deploy.
  • Lots of discussion about the feature and the need. @ry and @kitsonk argued that it was very describable, as it was a big usability issue. There was general agreement about this point.
  • @ry suggested that some mocks and prototypes be made to see what would work, as it is really challenging to do through a pure "design document"
• Implement Class Workers
  • This is only internal purposes and web platform testing, as all the wpt tests related to workers and worker API use classic workers. Class workers ARE NOT desirable for end users, as they promote legacy patterns which we really don't want to support in Deno.
  • Action get them done to support web platform feature development and testing.
• Code Signing
  • Needs to be done.
  • @ry was going to source certificates.
• Prompt by Default
  • A lot of debate about whether this can be done in a minor release, and what sort of changes can be done
  • @ry strongly argued for it as a usability issue.
  • Action proceed, but it isn't the top of anyone's work queue.
• Don't type check be default
  • @kitsonk will attempt for 1.13
• Websocket support in native HTTP server API
  • Landed, a few issues
  • Wait until 1.14 to stabilise at the earliest
• Move docs to separate repo
  • Done
• Introduce cross-process BroadcastChannel
  • This is desirable, will still try for Q3

Language Server

We briefly covered the issues here, but ran out of time. Issue #11168 reflects things accurately.