Deno: discussion: struct the browser-compatible APIs

[yorkie]

@ry @qti3e I just have a proposal about which Web APIs should be supported:

• High level
  
  
  
  • [x] Console
  
  
  • [x] URL
  
  
  • [ ] File/FileList/FileReader/Blob
  
  
  • [ ] XMLHttpRequest/Fetch
  
  
  • [ ] WebSocket
  
  
  • [ ] URLSearchParams
  
  
• Middle level
  
  
  
  • [ ] AudioContext/AudioBuffer
  
  
  • [ ] Canvas
  
  

Btw, supports WebGL that makes like tfjs could run at deno, and make use of the GPUs, it might be interesting personally :)

[qti3e]

Thanks, Yazhong! I like supporting WebGl btw, it's a cool idea! (ML in Deno!) : )

PS I checked Console as we've started supporting it : )

[monkingxue]

Maybe we should support XMLHttpRequest or WebSocket first because they are basement.

[qti3e]

It's a good topic and discussion, but we should consider that Deno is an early-stage software and it's a bit buggy for now, above everything, we should make it work in a good way and build all the foundations of the project much stronger then we can start working on new features : )

[ztplz]

@ry @qti3e I think we should write a todo-list of api that we need to implement next.
I am glad to make PR for this great project.

[benjamingr]

What about URL and URLSearchParams?

[qti3e]

@benjamingr yeah right,but we already have URL, see url.js

@yorkie I've updated your TODO list, I hope you don't mind : )

[yorkie]

Never mind, feel free to update the list :)

[ry]

Yes I want to have browser APIs like this. Submit PRs otherwise please keep the issues quiet for technical matters.