STRML

Titanfall did this. If I recall correctly, the full install size was about 48GB, 35GB of which was just uncompressed audio. And that was back in the days when 120GB (or less) SSDs were common. A total self-own and never fixed or understood.

It's not like decoding audio takes enough time on any modern multi-core processor to disrupt the game loop. It's not even on the radar.

Sure, but it's also 20% cheaper to get the ARM setup, so I don't think it's fair to discriminate this way. In the end what matters is what I can buy, and ARM both offers more cores per socket and per dollar.

How? That command doesn't even hit the network...

The Cannonball Run has very, very little to do with repeated 0-60 pulls.

Can confirm this; we've gotten more than 20 reports and demands for bounties for "public access" on our open data subdomain (backed by S3), which literally is `public.`.

Then they beg to have the report closed as "informative". We don't comply unless it really is an honest mistake; I don't like the idea of low-quality reporters evading consequences again and again, sending scattershot bug reports in a desperate attempt to catch a team not paying attention.

If you're having color banding, you may need to force RGB on your external monitor [1]. I had to do this a few years ago, it massively improved the picture.

That said, I was in disbelief that this was a problem that both was common enough to be all over the Internet, and so involved to fix. Amazes me that OSX doesn't simply have an advanced setting for RGB/YPrPb, and instead requires that you boot into Recovery Mode (!!!) to fix it!

1. https://spin.atomicobject.com/2018/08/24/macbook-pro-externa...

It's not even that expensive, so it's a much easier product to recommend.

Compare to the 2012 MBPr, a similarly innovative Apple laptop. The 2012 was $2,199 in 2012 dollars (nearly $2,500 today). This is that kind of leap, and more. $999 (sometimes $899) is a bargain.

People on HN still want to talk about the M1. It's just such an exciting product. So this will still sit on the front page for a while, despite the relatively terse source material.

It's excellent. I have the 8-core i9 16" Pro and I prefer the Air in every way for development. The keyboard is better (no touchbar), it doesn't get as hot, the battery life is better, it's faster, and it cost 1/4 as much ($999 vs about $4k). I bought the 16" in February, only 10 months ago.

What a leap.

Yes, the store is terribly slow. That's almost certainly at the UI layer, which may indeed be something like Electron, which would explain the slowness.

Node.js isn't slow, especially for this use case, but any sort of HTML-based layout definitely is.

That's normal. My i9 does the same. It is heavily, heavily reliant on turbo boost for performance and regularly boosts up to 80W (!!!).

As soon as the last kinks are ironed out for M1 there's no reason imo to use the Intel Macs ever again.

Could be worse, see https://www.amazon.com/CalDigit-Connect-10G-Thunderbolt-Ethe.... Looks like the controller generates significant heat, so there's a tradeoff between active cooling or increased thermal mass.

It does. The developer kits, however, did not.

One of my own stories: in which I discover that you should never ever attach a clone of a bcache backing device to a live server: https://blog.bitmex.com/postmortem-downtime-july-5-2017/

The quine introduces a few concepts I've not yet seen before, and I always appreciate deep-dives into the (very) sloppy and forgiving parsing that browsers do to forgive the developer's perceived mistakes. One can argue, quite convincingly, that this was a bad idea™ and should never have been done; given that we can't break web backcompat, it's here forever, to live alongside all the sloppy coercion hacks and "did you mean?"s living in PHP & JS.

It is truly surprising that:

    * { display:block; }

actually displays the whole contents of <head>. It makes no sense, but neither does most of HTML, so why not?

The basic function is simply defined as:

  function clamp(num, min, max) {
    return Math.max(min, Math.min(num, max));
  }

That is, if you don't try to do anything fancy and make any parameters optional. Lodash does and it makes the implementation much more complex.

  _.clamp(input: number, lower?: number, upper: number): number;

https://github.com/lodash/lodash/blob/ddfd9b11a0126db2302cb7...

See https://news.ycombinator.com/item?id=24135424

This is honestly really impressive on such a short deadline! Looks really great.

A practical problem to solve there: where do you put the cameras? I would actually prefer putting them behind the screen if possible - a few small pinholes wouldn't be that noticeable. If you could put multiple wide-angle cameras in multiple places, you could stitch them together in software and create a real feeling of closeness.

JFYI, pressing `esc` on your page takes me to a squarespace login page, which was rather jarring.

Dreading? I doubt it. It's a relief when the problem your library solves no longer needs solving!

It is not that simple. Cookies can have attributes such as "HTTPOnly" (don't allow access from JavaScript), "Secure" (only send on TLS-enabled sites), and expiry. While it may seem possible to replicate some of these with JavaScript, there are a few problems:

1. Not everybody has JS enabled (your content site shouldn't require it)

2. If using localStorage, users can write their own data. Depending on how you store data, this ranges from "not a problem at all" to "serious attack vector". At the least, it increases risk if an attacker gets XSS.

3. Data stored in localStorage can't be transmitted upon page load, it has to be transmitted after the initial load, once scripts have executed. For some things, this is fine, for e.g. auth, this is pretty bad.

They are different technologies: localStorage & sessionStorage are not a full replacement for cookies.

That said, tracking is rampant across the web and with it, cookies. Getting rid of them would make some of this harder - but not at all impossible - while breaking other legitimate flows.

No, it's an argument that social programs are smart, and prevent pain in the future. Long-term benefits are not extortion.

Is eating healthy and exercising extortion? Is investing in education to get a better job extortion? Is saving money to take advantage of compound interest extortion? No, it's all just long-term decision making.

Even better, `tig reflog`, which makes it easy to check out the content of a commit or the history of a branch in context with the reflog.

You hit the nail on the head as to why people don't use Slack & Jitsi, and barely use Hangouts: it's the call quality, stupid. Zoom drops out less, video & audio quality is better, screen sharing works. It's as close to a "gets out of your way" piece of videoconferencing software as has ever existed.

Competitors, take note. Get the basics right - don't concern yourself with fluff - and customers will flock to you.

Absolutely fascinating, high-quality, deeply technical article with a healthy dose of nostalgia. I'd love to see more of this (even though we often have quite a bit!) on HN.

Does anyone know if this technique was ever used again on the N64?

Jitsi's P2P nature is great for 1:1 or small group conversations if everyone has solid connections. From experience it starts to break down with larger groups, and becomes pretty useless overall if one or two participants have spotty connections.

Which isn't really enough, considering SNI and subdomains.

Assuming that you can access them diagonally -- not 100% if this is so - that layout should work.

Yeah, Cert Spotter does this (https://sslmate.com/certspotter/). It's a huge help both to be able to monitor cert issuance for a domain and all of its subs, and to be reminded when a cert is expiring.