snek

https://snek.dev/10print :)

There has been some light discussion in the standards bodies about this, and so far the write-up looks like this: https://github.com/domenic/proposal-blocks

But they still haven't got .dev :(

Seems like the authors of this extension have a bias towards chrome.

WASM is interesting in that its memory design prevents reading anything outside the memory allocated for the vm. To this point, I don't think you would get much use from using this within WASM.

That's not to say, of course, that WASM VMs don't employ various security measures. V8, at least, uses (mostly) the same optimization pipeline for WASM that it does for JS, so all the years of security that have gone into JS are gained by WASM for free.

Well four years of a language won't result in you being a very good speaker anyway. The key here is that foreign language classes also teach you about other cultures, which is definitely important.

It's currently true, but that doesn't mean wasm is finished yet :)

major implementations are working on more efficient baseline compilers to further improve performance.

Any info on the camera(s) used for those first two reddit photos?

Damn shame to see the internet move backwards because Google refuses to use the standardized APIs.

Edit: Usually HN is so angry about Google not following web standards but everyone in this thread seems to be in favor of Google trampling the WebAuthn standard. Weird.

>Hacker News is publicly viewable without an account. Totally different.

What does that have to do with needing to acquire rights to redistribute your content?

>Discord tricks the user into using it as a private messaging platform.

Discord doesn't advertise security at all (they do mention keeping your IP secure in some support articles but that isn't advertising)

Beyond that, Discord exists to create big open public spaces. Why would you need encryption in a big open public space.

> Modern communication platforms don't have to be all privacy-oriented. Just like in real life, there are public and private places, with different expectations.

I wish more people understood this. Discord's primary design is large open public spaces; layers of encryption and e2e make no sense.

It absolutely is. You know who else has a license like this? hacker news. (https://www.ycombinator.com/legal/)

    By uploading any User Content you hereby grant and will grant Y Combinator and its affiliated companies a nonexclusive, worldwide, royalty free, fully paid up, transferable, sublicensable, perpetual, irrevocable license to copy, display, upload, perform, distribute, store, modify and otherwise use your User Content for any Y Combinator-related purpose in any form, medium or technology now known or later developed. 

also microsoft, google, reddit, twitter, etc, etc, etc, etc

How would they be able to distribute your content (messages, images, etc) to other people if they didn't have the license to do so?

Every chat service and social media has this clause because they couldn't send your messages without it.

https://www.reddit.com/r/discordapp/comments/3r3rrt/question...

Please do your research before bringing out the pitchforks.

It has some interesting dips that seem to be testing some form of sudden dip in altitude which could be seen as related to the system under scrutiny, a safety system designed to prevent stalls which could in some cases "send the plane into a fatal descent if the altitude and angle information being fed into the computer system is incorrect"

(not that any of this confirms that the MAX has issues or this is what they were actually testing)

You can read more about the use cases and targeted user here: https://goo.gl/kRnhVe

They mention Cobalt (to allow targeting playstation), react native, nativescript, pdfium, and chrome's proxy resolver.

Just to be clear, the "JavaScript Standard Library" and the "Web Standard Library" are completely separate. (they are worked on by a lot of the same people though)

Hi, I don't work for Google, but I do work on web standards.

In WHATWG, single vendors typically work on features until they believe they are good enough to be standardized, which is when they are submitted to the WICG. At this point, other vendors and spec editors can take a serious look at the proposal and decide if it should move forward, what changes should be made, etc.

kv-storage has in fact gone through this process, and has overwhelming support from vendors and developers.

aside from this, import maps have been in the pipeline for even longer, and have broad support ranging even into Node.js being involved.

I know it's tempting when a new web feature is announced to claim that vendor is destroying the internet but please take the time to consider all the work that is put in to making the web a better place for you.

Perhaps this is because CF doesn't actually provide a location to host random files. When people say CF is a CDN, they're talking about its caches. You still need your own server. (although they seem to be pushing dedicated workers @ https://workers.dev)

But there's something to be said about needing a lint rule for the API to be safely used.

I'd be wary to encourage useState. It seems too easy to accidentally use in loops/callbacks/etc where your state would then break because react tracks it via call order instead of call site.

but you introduce the danger of relying on an api that determines your state based on the order of function calls. if you accidentally take an api that pretends to work based on call site and use it in a loop or callback everything falls apart.

When you want to work with state in a component (so most of the time) but are too stubborn to admit FP isn't the right choice for the job

Why don't the rich people just move to New York?

you don't need that npm library. just `new Agent({ keepAlive: true })` works

I miss Larry :(

does facebook support otp 2fa, or just sms

normally these big tech companies have something mildly redeeming about them. google has a huge presence in oss, apple cares about privacy, etc. but it seems facebook has nothing. even their outreach into third world countries was a thinly veiled attempt to lock more users into their platform.

I think the goal is to let speak to your phone normally, not to continue having to speak like your phone is hard of hearing.

This was the reason I was given from a dev on the edge team. Do with that what you will.