hmry

The column is measured in UTF-16 code units

In LSP, UTF-16 is not just for transport. Source locations are also referred to by their UTF-16 offset. That means applications are required to store a persistent mapping from UTF-16 offsets to whatever they use internally, keep that mapping updated as the document is edited, and map back and forth constantly.

Oh well. It was primarily designed to be a good protocol for VSCode, not for any other users. That's just the price you pay when using a corporate standard.

You don't get one, because UBI is an attack on your dignity as a worker.

Unlike being laid off because AI replaced your department, that's very dignified.

> acknowledges the issue

I don't see any acknowledgement in that text.

Without #[non_exhaustive], adding a variant is always a semver breaking change.

With #[non_exhaustive], adding a variant is not a breaking change, but only if that variant can safely be ignored. If it can't be, then it's still a breaking change, BUT you don't get a compiler error. That's a very big drawback IMO.

This makes me think of how the PNG format handles this. For context, PNG files consist of a list of chunks of different types (image data, color profile, text comment, etc). Each chunk has some flag bits that tell you whether it can be safely ignored when decoding the image, safely retained when the image data is changed, etc. That way the decoder can ignore unknown ignorable chunks and error on unknown non-ignorable ones.

Once the fix is released, people will reverse-engineer it and use the exploit on pages that haven't updated yet.

So they need to give time for infra people in all different time zones to wake up, learn about the announcement, and plan how to patch it.

The intended course of action is 1. take down website a few hours before the fix drops 2. apply the fix 3. only make website public again after it has been fixed

No worries! :)

I don't understand why you're replying to me like that

> You understand that ...?

Yes I do

I remember seeing this back in January

I personally found implementing an HTTP2 server from scratch quite difficult. The parsing and state machine was okay (and is also the easiest part to get from an external library), but correctly handling stream priority / bandwidth sharing and backpressure was really hard. Of course one could go HTTP1.1-only, but then you're losing out on the efficiency gains anyway :/

I'm a bit surprised the judges themselves didn't spot that it was AI. It immediately starts with things randomly appearing out of nothing.

AI-generated fake footage in medical science is one of the things that worries me a lot these days. Now there's practically a constant stream of papers getting retracted due to fake AI-generated microscopy, before/after photos, plots(!), ...

New frontiers in genuine ink cartridge enforcement, I'd suggest patenting that before Canon and HP can

When writing GPU shaders it's not uncommon to use extensions like ".vert.glsl" = "vertex shader written in GLSL", ".frag.hlsl" = "fragment shader written in HLSL", etc.

Yeah it seems very clear that the cheapest artstyle of the future will be whatever AI can output with minimal human editing or involvement. And some studios will go that route.

Although I don't see AI in game art becoming accepted by the wider public any time soon, and definitely not by the indie crowd.

I've also been thinking about this for animation. I foresee cheap limited animation (sliding layers, only mouth moving, etc) being replaced by incoherent un-/barely edited AI output instead.