I brought up web accessibility concerns with them almost a year ago and as far as I can tell all they've done since then is add `tab-index` attributes. Probably best to avoid this until they improve it more.
HN user
snek
Gotta appreciate the part implying that anyone who finds this document amusing is a "novice" programmer.
I've been using this locally for a few years, figured others might enjoy it too. Feel free to contribute additional tool configs.
One of the biggest issues was that stakeholders were uncomfortable with having to ship their browsers with multiple engines to handle different versions of JS (or having to build one engine which could efficiently switch between all the features of different versions).
There is a lot of excellent information on ES4 (and other things) in Allen Wirfs-Brock's "JavaScript: The First 20 Years": https://zenodo.org/record/3707008
archive.is returns A records 1.1.1.1 and 1.0.0.1 (cloudflare ips) back when you query them using cf dns. This means that your browser sends a request to 1.1.1.1 with the host header set to "archive.md". cloudflare's proxy tries to find the relevant config for archive.md, and not hosting it, tells you it doesn't host that page. it also helpfully informs you that if you just added your site to cloudflare, it might take a minute for it to show up.
False, archive.is serves 1.1.1.1 and 1.0.0.1 as A records back to people who try to resolve it using cf dns.
Related: https://github.com/AndrewBelt/WiTeX or my modified version here: https://gist.github.com/devsnek/9689917c8095febbf48b91c2f8f5...
As is mentioned in the article, u64 was used to future proof for wasm's upcoming memory64 type: https://github.com/WebAssembly/memory64/blob/master/proposal...
there are no "async" or "sync" imports in js. there are static and dynamic imports. An implementation is free to spend as much time as it likes between parsing a file to get the static imports and actually running the file doing whatever it likes, including fetching urls, reading the file system, etc. dynamic imports return a promise but the implementation is free to resolve that promise immediately (e.g. `return Promise.resolve(loadSync(module))`)
The lineup continues to balloon in price. A lot of students would the TK and TX models for robotics and whatnot, since they were only 200-300 bucks.
The extension has nothing to do with DNS, a more accurate name would be "autocorrect over wikipedia".
The rust server set up with dnsmasq is a legit DNS server though.
archive.org doesn't block you based on which dns resolver you use: https://web.archive.org/web/20190914012706/https://www.teleg...
JS functions go back and forth because they're trying to provide optimized representation of functions based on guesses they make about the code. WASM plays an entirely different game. WASM bytecode is generally already extremely optimized (compiled with compiler -O flags, etc), the optimizations that a browsers apply are more about the machine the WASM running on (dealing with register allocation, simd instructions, etc). There is no guessing or opportunistic optimization like there is in JS.
helpful mnemonic for remembering the difference between "log in" and "login": "I'm going to log in on the login page"
and did you know that IEEE-754 floating point can represent a "negative zero" that you can use for an error code in functions that return float or double?
I am begging, please never ever do this. NaN literally exists for this reason. NaN even allows you to encode additional error context and details into the value.
Working with chromium/v8, I can honestly say google's code search infra is one of the most valuable resources available. I really hope they open source the backend at some point.
add this to the list of things I wish I could unlearn
It is moving forward, albeit slowly. With or without DoH/DoT, non encrypted SNI is a problem, and DoH/DoT have privacy improvements in their own right.
There is already support for enterprise situations like you describe: https://support.mozilla.org/en-US/kb/canary-domain-use-appli...
If you're about to comment on how dumb this is because SNI isn't encrypted please halt and search "ESNI"
Yeah I think you're missing the part where you only added that file after being called out on twitter lol. The only reason I say "habits die hard" is because you consistently refuse to acknowledge that this ever happened.
functions are the part you compile, everything else is just runtime data
wasmer used a large amount of wasmtime code without proper attribution. I'm not sure this is a problem anymore but habits die hard and the owner of the company has not been shown to be the best person (won't go into that here since it's not as tech related)
You already have to rely on a third party to get a domain (and to get an IP address)
tcrowe is known to me for his past behaviour of harrasing lgbtq members of the node.js core development team and stalking them on social media. very unfortunate if he has schizophrenia but bigotry is not a symptom of it.
This launched around December of 2019. It is the same service that companies like Google[1] and Akamai[2] have provided for a while.
[1] https://peering.google.com/#/options/google-global-cache
[2] https://www.akamai.com/us/en/products/network-operator/akama...
You can go talk to TC39 delegates in #tc39 on freenode right now (it will be kind of quiet for the next few days though since there is an in-person plenary and people are not looking at IRC as much). We also use https://es.discourse.group/ for async communication.
Also, many entities listed on Ecma's membership page are not there for TC39, and talking to people working for them will not get you anywhere.
I've had a lot of fun playing the alpha so far, it runs really nicely on my computer (can't say exact specs but it surprised me how well it runs)