snek

I'm so glad we have two shipping implementations now

It's been allowed since long before then, all the way back to the og html 4.01 spec in 1999

plot twist: it's a cluster of servers running deep dream

works fine for me (macos)

He should sue himself for going into high risk/velocity trading in the first place.

Oh yes, i meant that sometimes a paradigm is unused, not that one prevents the other.

To this point, JS has been very careful to not get in the way of functional programming, as it doesn't really try to stick to a specific paradigm. There is even a proposal to add pipielines: https://github.com/tc39/proposal-pipeline-operator.

Personally, I think forcing yourself to a specific paradigm is a waste of energy. I've tend to just write code that best expresses my intention. Sometimes the code turns out more oop, sometimes it turns out more fp, and often it's more of a mix.

If you somehow feel that firefox is moving too slowly (check the vcs history its very active) you can always contribute yourself, it's OSS :)

Friendly reminder that this is not a violation of free speech. https://xkcd.com/1357/

This is actually censorship. However, I personally believe that groups that incite violence should be censored.

The biggest issue is that google is forcing websites to use its own html subset by judging sites that use it instead of by judging sites based on actual speed. There are a lot of posts on HN about sites that got no speed increase or even regressed when switching to AMP.

If Google didn't penalize sites that don't use AMP, and instead just measured response, paint, etc times and such, I would agree with you.

Normally I'd rush to Chrome's defense here (see my post history) but I have to agree with others about Chrome kind of breaking the process here. Other browser vendors have large concerns with this spec, so it's quite surprising that it's shipping at this scale.

I can definitely agree here, It's really disheartening to see this. When I saw this headline I first thought it was Cloudflare using some sort of cool trick to redirect users back to the proper non-amp page, but was just met with disappointment.

Could Cloudflare accept a request header that would load up the full page instead of the AMP one? I suspect many people would use such a feature, and it would also be a good way to indicate to Google (and now it seems, Cloudflare as well) the dislike of AMP.

It's a side effect of the design of WebAssembly, as long as wasmer itself has a conformant implementation (the WASM spec itself is already formally verified).

i'm not sure if it's a default label but a huge amount of projects use it.

but the carousel didn't preload content before amp

...and end up keeping a websocket open, transferring far more than 30kb or even 100kb in state changes over the lifetime of the app, while also using up the devices battery and data limits? friendly reminder that 100kb of js can be cached on the device, while a stateful websocket obviously can not.

The reason I have gotten from google employees is that the top stories carousel preloads content, and that in order to preload content without leaking a user's searches, google needs to serve their own cached version of a page. in order to make sure that cached version of a page isn't doing anything tricky, they need to heavily limit what it can do.

it's not about making the internet faster, it's about making it easy for google's stupid scroller.

I'm not discounting the language at all, by your comment here perhaps some application of a common mathematical function such as an average or the fibonacci sequence would be a good front page example.

that just makes me more curious about what J looks like. and maybe a hello world isn't the best example for every language, but there should be some small example you can show.

why does no programming language website ever include an example of the language? just a hello world or whatever would go a huge way. this annoys me so much.

We're getting there. I made both node and web streams into async iterables, and have now proposed this for js standardisation: https://github.com/tc39/proposal-iterator-helpers

it uses a lot of infrastructure that node doesn't have, like Request objects and Response objects and Body objects and mime checking etc etc list goes on.

if someone feels like adding all those things to node and feels like arguing with our core maintainers about the duplication with http then maybe it will be added.

https://github.com/nodejs/node/issues/19393

it's not just promises. as the maintainers of request continue trying to try to fix architectural bugs they are finding it would be easier to rewrite it from scratch rather than continue modifying the current one. this is said in about as many words in the linked issue too, so make sure you read before commenting ;)

Just write idiomatic code, it's what all the major engines try to optimize for.

Maybe you can switch it out :) https://webassembly.org/

maybe they included compilation? it would make sense as that's a real world use of cpu/memory/energy.

>typical TypeScript programs are faster than typical JavaScript programs

Person who works on js engines here :)

You would think this is the case, but in actuality, js and ts are about on par in performance (assuming similarly written code). This is in fact due to the fact engines optimize for idiomatic js patterns, not idiomatic typescript patterns. often these will align, but in some cases (usually revolving around generics and inheritance) well written js will actually fall through the optimization pipeline faster due to following more patterns that have specific optimization checks.

which browser doesn't show that right? chrome and firefox have connected lines for me