4 ms·
This is the important list. I don't care about ES2015 or more—we'll always use Babel. I care about Service Workers and WebRTC more.
by sotojuan 10y ago
This is the important list. I don't care about ES2015 or more—we'll always use Babel. I care about Service Workers and WebRTC more.
- CoryG89 10y agoEven if you use Babel your users will still benefit from less polyfill.
- TheAceOfHearts 10y agoWe'll use babel for builds. Most development will be happening on modern browsers, so being able to reduce compilation requirements improves your iteration cycle and it makes it much easier to debug. Source maps have lots of issues. Compare debugging async/await usage between the compiled and native version. If you're working on a larger project, compilation times start becoming a huge pain. Cutting down on the number of transformations reduces development latency.
- untog 10y agoOf course, all of this is true. It makes the life of a developer marginally easier. Unless there are edge cases where Babel and browser-native functionality differs. Either way, WebRTC and Service Workers would allow us to expose totally new functionality to users. Huge difference.
- shellac 10y agoI wish someone would come up with something better than webrtc. It's such a mess, and appears to be impossible to standardise.
- gtirloni 10y agoIs WebRTC ready yet? Completion Score: 68.5% http://iswebrtcreadyyet.com/ http://iswebrtcreadyyet.com/ WebRTC 1.0: Real-time Communication Between Browsers https://w3c.github.io/webrtc-pc/ https://w3c.github.io/webrtc-pc/ Identifiers for WebRTC's Statistics API (Draft) https://w3c.github.io/webrtc-stats/ https://w3c.github.io/webrtc-stats/ Media Capture and Streams (Draft) https://w3c.github.io/mediacapture-main/ https://w3c.github.io/mediacapture-main/