171–180 of 187 posts
Earlier quoted context omitted.
python is rarely streamed across HTTP, I believe that's the reason js is treeshaked.
Guido is the one who picked Python's name. Wikipedia actually has an entire article on the history of Python: https://en.wikipedia.org/wiki/History_of_Python >
With JS having `import` these days, there really is zero point in bundling if you're writing normal modern JS. Just let the browser deal with caching, it's good at that, it's literally half of what it's been optimized for. The other half being JS execution.
Yeah, Ive wondered that as well. Whenever I see I have to setup a complicated build system just to run a simple hello world example, I just go yuck and stop
Earlier quoted context omitted.
You can easily build complex UIs without a framework. Chrome DevTools, Chrome OS, Photoshop, Firefox and other very complex apps have been built with web components.
Web Components aren’t an alternative to React so much as a complementary technology. Yes, you can build UIs without a reactive framework but it will involve compromises in expressivity, code organization, and whatever the Greenspun equivalent is for React.
Earlier quoted context omitted.
Ah, thanks! I'd never encountered these before. It seems like a handy way to make my code match the code in documentation that assumes a Node environment.
No problem! There's also a polyfill if you need to support Safari: https://github.com/guybedford/es-module-shims
https://webkit.org/blog/13878/web-push-for-web-apps-on-ios-a...
Earlier quoted context omitted.
I wonder how far fetched it would be to have just the syntax of Typescript on the browser without type-checking. We'd have to use tsc locally only for the typechecking, without the need of a build process, but that would be enough for me. I know there's JSDoc but the normal syntax is so much better. EDIT: Looks like there's a proposal: https://github.com/tc39/proposal-type-annotations
IIRC that's how the Flow type annotations worked, but of course it lost out to TypeScript.