1,940 karma · joined September 20, 2016
[ my public key: https://keybase.io/styfle; my proof: https://keybase.io/styfle/sigs/k5Jx2P3fJ9JOZsHyU2TLChLetDsvmL2mHK7wJMj-nKk ]
That doesn't seem like it's enough time. I would expect one year or at least 6 months.
I have been watching these types of tools (desktop js frameworks) and I'm glad the DeskGap docs[0] explain the difference between existing tools like Electrino and Quark although the most notable difference is that those two projects are no longer maintained.
I just added DeskGap to my list of Awesome Desktop JS frameworks[1].
[0]: https://deskgap.com/#there-are-already-similar-attempts-elec...
https://www.destroyallsoftware.com/talks/useing-youre-types-...
There is a much better typescript playground[0] that supports all options in the permalink, for example see this link[1] that has `removeComments` enabled.
[0]: https://typescript-play.js.org
[1]: https://typescript-play.js.org/?removeComments=true#code/PTA...
[1]: https://zeit.co/now
https://css-tricks.com/on-xlinkhref-being-deprecated-in-svg/
"V8 release v8"
At least when it's spelled out like this, they always use capital V8 for the engine and a lowercase v8 for the version.
I can imagine the verbal V8/v8 confusion probably forces everyone to say "version 8"
I have this same problem with a 3 node cluster, no Kubernetes. This was using Elasticsearch 2.3 and it worked for a year or two and then all of a sudden, any network interruptions would cause the thing to get split brain and all indices would go red. It would take 8+ hours to go back to green and usually required a reboot of all servers or else it would never recover.
It was happening often enough that the decision was just run a single ES node since the total data was only 25GB :(
No, you don't need to inherit or implement which is one of the great features of TypeScript!
In this example, the `greeter` function accepts any object that has a `firstName` and `lastName` property defined, regardless of what the object/type is called. No need for inheritance.
In fact, the `Person` interface is not even emitted in the JS output because interfaces are only used at compile time, not at run time.
One thing to point out, is that 4 of those are country-specific TLDs (or the historic .net) which have been around for awhile so they might still have some familiarity.
It starts to look very unfamiliar to non-tech people when URLs have a long TLD, such as:
example.blog
example.website
example.foundation
example.engineering
example.international
This training will take some more time for other TLDs and will take more time to become normal.
Even now, companies that start with a strange TLD but grow large enough will eventually buy the .com which repeats the cycle that only .com is legit for commercial services.
Anyone know of popular companies in the USA that don’t use .com?
Let's assume you want to use 3 different HTML templates on a page (the html content doesn't matter much for this example).
Here's the example usage of HTML Templates from html5rocks.com:
<script>
function handleLoad(e) {
console.log('Loaded import: ' + e.target.href);
}
function handleError(e) {
console.log('Error loading import: ' + e.target.href);
}
</script>
<link
rel="import"
href="example1.html"
onload="handleLoad(event)"
onerror="handleError(event)"
/>
<link
rel="import"
href="example2.html"
onload="handleLoad(event)"
onerror="handleError(event)"
/>
<link
rel="import"
href="example3.html"
onload="handleLoad(event)"
onerror="handleError(event)"
/>
<script>
function importHtml(selector) {
var content = document.querySelector(selector).import;
var el = content.querySelector('.warning');
document.body.appendChild(el.cloneNode(true));
}
importHtml('link[href="example1.html"]');
importHtml('link[href="example2.html"]');
importHtml('link[href="example3.html"]');
</script>
Now let's compare the same feature with ES6 Modules and Templates using a `helper.js` file. export async function importHtml(url) {
try {
let res = await fetch(url);
let html = await res.text();
let template = document.createElement('template');
template.innerHTML = html;
let el = template.content.querySelector('.warning');
document.body.appendChild(el.cloneNode(true));
} catch (e) {
console.log(`Error fetching html: ${url}`);
}
}
Then we can import the modules on the page in a very clean way...no HTML Imports spec here. <script type="module">
import { importHtml } from './helper.js';
importHtml('example1.html');
importHtml('example2.html');
importHtml('example3.html');
</script>
My point is that you don't need HTML imports and you'll have to use JS even with HTML imports so just use JS all the way :)In particular, CodeSandbox has come a long way by basically running VS Code in the browser.
There is no decorator feature in the ES7 (ES2016) spec.
However, there is a proposal for decorators that it is not finalized yet.
https://github.com/styfle/packagephobia/issues/141#issuecomm...
Everything can be heard and seen in an open office so I think it makes communication worse.