761 karma · joined November 24, 2009
Maybe give feedback here? https://github.com/WICG/webusb/issues/
I interpret the definition of "dead" here to be:
No other implementation than the one in Chrome
Rather than: No implementation or spec work at allRuns at 70 MHz
A “user tracker” sets cookies and follows a user around, knowing what the user have or have not done before.
A “site tracker” (bad wording I know) follows what happens to a site, what device types accesses it etc.
Sure, making direct requests to the analytics servers exposes IP and possibility to somewhat track the user. Tracking based on IP is pretty inefficient though, due to shared IP-addresses, IP-address changes when jumping between networks, VPN:s.
Ideally SimpleAnalytics would provide a tiny proxy/washing script that one can host on ones own server and which one includes on ones site rather than including it directly from SimpleAnalytics servers. That way one can guarantee ones users that no IP-address is leaked to a third party (which would also make a Data Processing Agreement completely unnecessary from a GDPR perspective)
RISC-V isn't really about price or performance – it's about innovation, agility, exploration and new frontiers.
The main CPU is just one of many chips in a computer nowadays – even some cables have ARM-chips built into them to convert signals. RISC-V can probably be an even better fit there as its open design makes it a lot easier to customize it so that its tailored for such specific tasks.
Google should not be happy about this.
Makes it harder for them and everyone else to push web standards forward.
I guess the Chrome team itself aren’t happy about this. Will make standards work harder for them. Better to have the Edge team build alternative implementations of standards in their own engines than to implement even more stuff in Chromium.
Chrome already has a hard time not running ahead of the rest of the web, they don’t need more people to speed it up even further.
Remember: Chromium itself is an “obscure fork” of WebKit...
If they won’t continue to use Chakra, what happens to that project then? It is open sourced and there’s work to make Node.js use it: https://github.com/nodejs/node-chakracore
All the more important to support Servo and Gecko – we can’t have all browsers be of WebKit origin – we rather need more initiatives like Servo, that reinvents the engine from scratch, optimized for modern environments.
I would guess that Microsoft would keep using Chorus rather than adopting V8, but if they aren’t, then V8 has contributions from eg. Node.js
And as states in the article: Edge on Android and on ARM seems to already be Chromium based
WebSub is a spec from the very same working group that published the ActivityPub spec and WebSub is actively used by eg. the IndieWeb movement that do indeed very much solve social network monopoly as everyone hosts their social profiles themselves there.
I'm eg. myself running a service that makes it simple to accept WebMentions on something like a static blog: https://webmention.herokuapp.com/
Free hosting: https://pages.github.com/ – currently using for a couple of sites and it works very
Paid hosting: https://divshot.com/ – thinking of using for some sites – mainly because I can get https on a custom domain there, which I can't at GitHub Pages
Eg. check out the ParallelArray() from the River Trail project by Intel: http://wiki.ecmascript.org/doku.php?id=strawman:data_paralle... & http://en.m.wikipedia.org/wiki/River_Trail_(JavaScript_engin... At least Firefox has an initial implementation: https://developer.mozilla.org/en-US/docs/JavaScript/Referenc...
The benefit if asm.js being based on ordinary javascript is that they can use these improvements to javascript itself right away more or less.