snek

Damn I remember back when the TK1 was the new kid on the block. The nano looks awesome, I'm gonna have to get my hands on one of these!

I installed Manjaro about a week ago and it cold boots in ~5 seconds (not counting the grub menu to select between windows and manjaro)

lolwut GE is #21 on the fortune 500

Unfortunately this website doesn't talk much about the shortcomings of DEC64. Just to start, numbers in DEC64 have multiple representations, meaning even a simple equality check can take tens of cycles. Don't get me wrong, it's a cool way to store numbers, and it does have purpose, but it is not suited for general use like IEEE754 is.

This site really needs HTTPS. The app is fun, but please add HTTPS.

Caustics look pretty good after increasing the number of passes: https://gc.gy/28927731.png

IIRC in a hashbang isn't posix compatible

You could also just set your dock to autohide. That's what I do on my MBA 2015 and it's great, especially considering how small 1440x900 already is.

Very cool idea! For all of you thinking of writing native modules for node, please remember to use napi, not nan. napi is fully abi stable, while nan is not!

https://nodejs.org/api/n-api.html

We also have a c++ wrapper: https://github.com/nodejs/node-addon-api

This would be a fine idea if Google didn't control the Chromium source code. The changes Google is making for webRequest v3 manifests will land in the Chromium repo. The changes Google makes for adding non-standard features happen in the Chromium repo. You can see them all here[1]. You can even sign in with your Google account and comment/review any CL you wish, but that doesn't mean Google listens.

[1]: https://chromium-review.googlesource.com

I've had this a lot, thought this was a bug in firefox's rendering or something. Glad to know it isn't, but now I'm somewhat more annoyed to know the real issue.

Apple can both make choices and improve user security and make choices that hurt user's ability to repair their devices. They should obviously be commended for things like this app tracking, but that doesn't mean they don't do bad things.

Using the correct semantic element goes a huge way for people using screen readers and other assistive tech. One of the things I hate most about react/vue is how casually people use divs for everything from inputs to images. Over 20% of people use some assistive tech, whether that be zoom, contrast controls, screen readers, etc. Even if you can't test all this, being aware of it when building/coding is a huge step forward.

Not just a belief, it's been studied many times, and it is in fact illegal to have "native" advertising on children's TV shows, at least in the U.S.

If you want to make a browser and show any content encrypted with Widevine (which is the majority of DRM content), you need a Widevine license, and they straight up refuse to issue those. How are you supposed to compete with Chrome when Google prevents you from playing Netflix and Spotify?

It's pretty much all the paid media on the internet. Spotify, Hulu, netflix, cable providers, amazon, etc.

I guess if you literally only watch free YouTube videos it's not a problem? Totally not an anti-trust issue...

Honestly it would be pretty incredible for Chrome to be split out of Google, and I for one would love to see that happen.

they're not advocating that you do it (and I think stealing from Chick-fil-A is probably ethical to a lot of people)

edit: for people not aware, the last part was in reference to pride month and Chick-fil-A's "relationship" with the LGBT community. I'm not advocating one way or another, just replying to the above comment.

in ##javascript on freenode this comes up so often we have a macro saved to one of our irc bots explaining why forEach, map, etc are better alternatives to reduce in many common situations. by far the most common situation is people reducing arrays into an object when they could be using a simple forEach. The first example in the article is actually this exact thing. It's also awkward considering they mention they're trying to do a "lookup" which makes it sound like they could just do find on the array and be done with it.

sidenote, i really do enjoy code typeset with typewriter fonts for short codeblocks like in the article

I feel like the android ecosystem is so diverse its hard to write any comprehensive review about it.

I've had a fantastic experience on my OnePlus devices over the last few years.

To this point, I would have titled this "hello moto whatever and samsung whatever"

After John Lennon was murdered it became less common for media outlets to publicize the identities of murderers beyond maybe a name and a mugshot.

With the more recent shootings there has been a bit of a revival of going into the profiles of the murderers (mostly, it seems, on cable tv) but that is a bit of a departure of the norm.

An optional GC is being added: https://github.com/WebAssembly/gc/blob/master/proposals/gc/O...

(Emphasis on optional)

I've been using firefox as my daily driver on a 2015 macbook air for the last year. It's been fantastic, not at all slow.

I haven't tried to use applescript/automator with it so i can't comment on whether or not that works, but that doesn't seem like the biggest issue for most users, or even most developers.

i've been using firefox on macos for a little over a year now, it's been fantastic. good battery life, good performance, etc.

Firefox is often faster than chrome for me on my 2015 MacBook air

To clarify why WHATWG exists and why W3C lost power over the HTML spec:

Around 2004 W3C abandoned organizational effort on HTML in favor of things like XHTML2, XEvents, semantic web, etc. The WHATWG was formed in reaction to that, rewriting HTML completely from its W3C HTML 4.0 version for example to make it better for web applications and to specify things in more detail.

Since the formation of WHATWG, W3C HTML specs became copy-pastes (often not even correct copy-pastes) in an effort to satisfy paying member companies (https://github.com/w3c/charter-html/issues/14#issuecomment-1...).

You can see everything WHATWG maintains here: https://platform.html5.org/ (they are the green question mark)

The W3C still maintains a good chunk web standards though, such as CSS, Wasm, web security, etc.

in v8 at least, we just plugged wasm into v8's existing jit. no need to make a new one from scratch.

We already tried JVM in browsers, remember java applets? I sure remember the security and compatibility problems :)

WASM has been designed from the ground up with portability, security, and stability in mind. It is also a lower target than JVM bytecode, which makes it more suitable to represent languages like rust and go. It has also been designed to take advantage of the sandboxed JIT engines that browsers already have for running javascript. Additionally, WASM is an open standard that anyone can contribute to, which is something that is greatly valued on the web.

the chrome team released a similar tool a few months ago (https://squoosh.app). I'm curious how these compare.

I've had a 1+1, 1+3, and 1+5, and I never had this issue on any of them.

Disclaimer: Austin Cheney works for the US Army.