MatthewPhillips

12 ms·

91.
Thoughts on Worker Rendering(medium.com)
2 points by MatthewPhillips 10y ago|0 comments
92.
by MatthewPhillips 10y ago
Shadow DOM fixes CSS scoping with the caveat that it fixes CSS scoping. If want to allow a 3rd party to style inside of a shadow root CSS variables is the only current way. While this works, it's pretty painful to pass variables for ea
93.
by MatthewPhillips 10y ago
This is what I was most curious about, but it looks like --flat is a cli option but not the default. Definitely moving in the right direction though!
94.
by MatthewPhillips 10y ago
Setting async to false doesn't make it synchronous. Try adding another <script> after this one that uses $ and see what I mean. document.write() is the only way to synchronously inject a script.
95.
by MatthewPhillips 10y ago
That you're only breaking a small section of a site is a false assumption. You really have no way of knowing that. You will be breaking the entire site in the case of a site that writes all of its content using JavaScript obtain from t
96.
by MatthewPhillips 10y ago
Google isn't a new gatekeeper, there's tons of documentation on their domain already that instructs developers to use/not use certain features for the sake of pagerank. Go look at PageSpeed for example. It would be great if
97.
by MatthewPhillips 10y ago
The lightning icon is a carrot, you're assuming malice where it doesn't exist. The lightning icon will go away when being fast is the expectation.
98.
by MatthewPhillips 10y ago
I was told by cramforce that there's no need to use AMP if your page is already fast on its own.
99.
by MatthewPhillips 10y ago
I mean, AMP is a bunch of custom elements and instructions not to use certain features that degrade performance. I'm not sure what part of this you want to be an "open standard", can you be more specific? AMP is more of a bes
100.
by MatthewPhillips 10y ago
It's available in Edge if you have Windows Insider (the Edge equivalent of Chrome Canary). There are some bugs there though. Note that the browser's module support is stricter than Node's, you have to point your imports to th
101.
The Future of Modularity on the Web(matthewphillips.info)
2 points by MatthewPhillips 10y ago|0 comments
102.
by MatthewPhillips 10y ago
A large setup cost discourages you from creating many small projects; from creating experiments that may/may not pan out. This is why the browser/text editor flow of development will (eventually) win out. Hopefully people working
103.
by MatthewPhillips 10y ago
Check out DoneJS which gives you everything you need: https://donejs.com/Guide.html donejs add app my-app cd my-app donejs develop A full environment with hot module swapping included, code-splitting for producti
104.
by MatthewPhillips 10y ago
> I don't feel like I have to re-learn everything I know about web-dev when using react like I do with Angular. I find it odd that you feel that way given nearly every React tutorial absolutely does do things the "react way&quo
105.
by MatthewPhillips 10y ago
That won't work, you can't eval modules.
106.
by MatthewPhillips 10y ago
I don't see a practical difference between bundling and server push to the developer. You are still using tooling that traces your dependency graph and produces... something. In the case of a bundler it produces a concatenated script a
107.
by MatthewPhillips 10y ago
There's no such bundling format under consideration, as far as I'm aware. System.register is a SystemJS API, not a spec one.
108.
by MatthewPhillips 10y ago
Just to clarify, the mappings for names to paths isn't enough to load an NPM-based project. With NPM you can have multiple semver-incompatible packages. It's very common to happen, actually. For example, you might depend on "
109.
by MatthewPhillips 10y ago
You still have to fetch a module before you know it's dependencies. So if A depends on B which depends on C, you must fetch those sequentially. With a deep dependency graph this will be a problem.
110.
by MatthewPhillips 10y ago
That's a really smart idea, I hadn't considered that. Once you add in caching you might get pretty reasonable performance.
111.
by MatthewPhillips 10y ago
Yes, it makes separate requests, like if you made separate script tags (just using module semantics instead). With HTTP2 it will be ok, but you will still need something that understands your dependency graph so your server knows which modu
112.
by MatthewPhillips 10y ago
For those thinking about using this, it bears mentioning that there are a few caveats to script type=module that makes it difficult to use with a lot of modern workflows, namely: 1. No way to dynamically import a module (the article explain
113.
by MatthewPhillips 10y ago
I wouldn't say es6ml was "guessing", it was based on the old loader spec that was removed from ES2015, and was quite accurate. It's no longer relevant though, since whatwg/loader is quite different.
114.
An Introduction to Zones using can-zone(davidwalsh.name)
2 points by MatthewPhillips 10y ago|0 comments
115.
Script type=module polyfill(github.com)
6 points by MatthewPhillips 10y ago|0 comments
116.
Loading a Modern Application with <script type=module>(matthewphillips.info)
2 points by MatthewPhillips 10y ago|0 comments
117.
by MatthewPhillips 10y ago
I'm not sure how a user can possibly resolve conflicts when 2 libraries are using 2 incompatible versions of some other library. Those need the versions they depend on. You might not want multiple versions of Angular in your script bun
118.
by MatthewPhillips 10y ago
Modules are not flat in reality though, any non-trivial sized app likely has multiple versions of the same module being used. I don't see any reason to think that's going to change in the future, extreme modularity is the norm in
119.
by MatthewPhillips 10y ago
If you don't find JavaScript modules confusing, you should. I work on a module loader [1] and I find it quite confusing. To clarify we have 3 things: 1. import and export syntax, this is defined in ES2015. It's just syntax, it doe
120.
What the Func – JavaScript functions(matthewphillips.info)
1 points by MatthewPhillips 11y ago|0 comments

More ›