https://github.com/endojs/endo/tree/master/packages/ses
https://github.com/tc39/proposal-compartments/
It has usage already, eg. metamask snaps
309 karma · joined January 11, 2012
https://github.com/endojs/endo/tree/master/packages/ses
https://github.com/tc39/proposal-compartments/
It has usage already, eg. metamask snaps
Also, on its way to being standardized in tc39
The actions you can take can be based on owning the trademark or copyright on the logo of the meetup.
Also, attempting to draw a sequence diagram and fixing it as you go trains the brain to handle a mental model of a large process.
What we're discussing here is merely a starting state of something that'd have to rebuild itself.
Or maybe evolving modalities within one network is easier than putting it together.
These PhD papers were apparently the easiest to quickly edit from someone else and push past the uninterested reviewers.
Keet.io and whatever comes next
But! I'm forever grateful for the things learning prolog did to my brain
It's always possible to find people who are so much ahead of you that you'll need to put effort into just following the conversation with them. And when you do, they're your peers and you're proud to be a 0.9x developer alongside them.
I wrote a simple app to turn an inperson tabletop conversation game accessory (pieces of paper) into something that can be used remotely in a pandemic. totpal.vercel.app
And I wrote a bunch of debugging/diagnostics tools for node.js. some for fun, some I actually needed. NPM: debugging-aid
Getting permissions involved will require mapping them to packages in a policy file and there you go - an environment where you can use packages and they can't surprise you with data exfiltration etc.
https://github.com/naugtur/aframe-point-component
Didn't do the fancy glows and backgrounds though. This is much better looking.
Also, there's a bunch of tools you could use before you deploy blocked-at or async hooks at all.
Note it's midnight here and I'll stop responding very soon :D
Regular eventloop blocking by synchronous processing is the middle ground.
Performance issues with utilization of resources, too many promises or broken backpressure - that's where the fun begins.
If you can run your software locally and simulate load, just use node clinic. It's the best looking one ;)
Get in touch over email if you want to explore further.
Some quick comments:
- I didn't notice the node version or you didn't state it. The impact from async hooks is _vastly_ different between node versions
- I need to update the package a bit, I've got a known perf improvement to add AFAIR.
- your implementation is likely to produce false positives. The trick to prevent (some) false positives is the most valuable part of the lib.
Also, take a look at the event loop utilization metric introduced last year https://m.youtube.com/watch?v=WetXnEPraYM&list=PL0CdgOSSGlBa...
And for more of my diagnostics experiments see debugging-aid package https://www.npmjs.com/package/debugging-aid
Theoretically though in representative democracy you choose the government to represent you and be an agent for making your decisions. You are responsible for what your government does in part that equals 1/Population
Let me plug this as it contains a lot of references https://dev.to/naugtur/do-you-need-help-with-your-npm-audit-...
Meanwhile I'll try to get someone from IBM involved in the OpenJSF collab space
There's a push to address the npm audit situation. It's an initiative under the OpenJS Foundation. I kinda started the whole conversation by implementing a tool that makes it acceptable instead of ditching npm audit.
It's called npm-audit-resolver and I've written about it here https://dev.to/naugtur/do-you-need-help-with-your-npm-audit-...
Also check out the collab space and the tool itself https://github.com/openjs-foundation/pkg-vuln-collab-space https://www.npmjs.com/package/npm-audit-resolver
If the chaos produces a new kind of behavior the result of the ANN may be totally wrong. In other words - it works well, often.
Is my simplistic thinking right?
So that I read the lawyer explain ApachePrivacy1.0 and can reuse that knowledge going forward. And it seems like startups would benefit from that a lot. They tend to copy-paste the lawyery bits anyway.
I'm scrolling the comments looking for this and having trouble believing nobody thought of it. Is it obviously impossible or something?