@Lensflare I guess there's node-gyp but it's so terrible to work with from the C angle that I'm convinced the intended extension mechanism is just to write all the libraries directly in JS on top of Node's networking and disk IO.

@Lensflare JS isn't really glue though, before WASM it was impossible to call out to other languages from it, and even with WASM the targets must be designed with the limitations of WASM in mind. I call Python glue because it's usually used to call out to C libraries that weren't written with Python in mind at all.

@Lensflare It's glue, It should have the simplest options for everything. The only argument I can see in favour of concurrency is that C# has blocking and green threads rather than async, and if you don't care at all about efficiency, this saves you from function coloring.

For dev stuff: Kevin Fang, LaurieWired, Developer Voices, CppCon, Sebastian Lague, and a few that upload even less frequently than these.

@12bitfloat I'm not sure why the narrative is that it's a dev version, but I'm like 95% sure that the current feature set is permanent and will only ever be deprecated, not removed, as is usually the case with stable web APIs. The solution for bindings seems to be mostly to write very specific JS glue distributed alongside compilers like Emscripten that the browser can trace compile. Cooperative GC is an unbelievably hard problem, and switching between WASM and arbitrary (uncompiled or dynamically typed) JS is pretty slow, so I don't expect we'll get many features to encourage using them together.

@BordedDev That's odd, I could've sworn that Rust's wasm support uses a virtual stack to allow "blocking" the "invoking thread" which all looks like regular async work from the JS side. I mean, Rust at least actually has a type of async support that makes no assumptions about the executor so you can use that. But still, it surprises me that the general solution isn't to lift all work into promises while we're already on a compilation boundary where anything goes.

@BordedDev what has cors got to do with the parallelization of client-side programs?

@whimsical I look forward the most to the end of Javascript's hegemony and opening the floor to languages with better static analysis and opportunistic parallelization potential, although that may be a bit ambitious. Otherwise, I hope it can become a democratic distribution method for indie games. Since payment providers like Stripe aren't too difficult, the biggest argument in favour of Steam for many devs is actually player convenience.

Not all is lost though, there will probably be a different WASM target with native threading support. I look forward to the third WASM target that will use WASI threading.

MFA would only have been nice as an "any 2 of N" deal. For small values of N larger than 2, this provides both better accessibility and better security. Implementors just decided to piss in the pot by turning it into a "password + any 1 of N" and only providing second factor options that aren't substantially different in nature, if there's a choice at all.

@D-4got10-01 I'm just nitpicking, don't worry about it.

For text I like "verbatim" or "word for word" which practically means that the words, their order, and higher level grammatical structures cannot change, but every transform that preserves these is fair game by default. You could say, as many do, that this is nitpicking, which is absolutely the case, but nitpicking specs which are likely to cause disagreement both covers my ass when people complain and steers the conversation in a more productive direction.

@D-4got10-01 The input is Unicode, the output is an image on a screen, so there has to be some translation in between, the responsibility for which is split between the app and the GUI framework. The entire reason the issue exists is that this translation system does its job differently than expected. I always fight against "the same" in a technical description as a relation between two things of completely different nature exactly because it always hides a huge pool of assumptions, in this case relating to fonts and text layout.

@D-4got10-01 Personally, I appreciate if the opening and closing quote marks are visibly different, but don't care in the slightest about the nature of the difference as long as both are obviously quotation marks, since the first one in a body of text is always an opening quote. Hungarian uses „this type of” quote mark but nobody cares enough to actually use them unless Word does it for us even though they are present on the standard keyboard layout.

@D-4got10-01 It's a bit hacky but easy enough, tampering with font files is hard if you don't already have a designer who dabbled in typeface editing.

I mean, is the text fed into another computing system, or is it only ever displayed? If it's only displayed, this could be classified as a rendering error and there could be a transform in the GUI code that would look for the weird opening quote and replace it with a regular " quote. It's not perfect, but hey, it's better, and it also works correctly the next time a translator writes their lines in MS Word.

@Lensflare yeah the automod is terrible. I've taken to avoid engaging in conversation on YT because sometimes it decides that a comment is problematic weeks later for no apparent reason, and subsequently prevents me from commenting in the same thread altogether.

At the same time, I completely agree that youtube's comment system sucks donkey balls from the garbage update propagation to the insufferable opaque and unhandled censorship that leaves broken UI behind when automatic moderation deletes a comment.

Idk I think it's a bit weird to be upset that you don't get a report of the outrage you caused beyond that it outweighs the support you garnered.

@Tounai hey, at least they include the errors. Look on the bright side. Live support callers have us put on PPE and walk down to the factory floor to take a photo of a fucking error message before we could even begin debugging because the reports are like "terminal 3, does not work". Two people besides the actual L1 support have to drive two hours each day to provide this support, there's no other reason for them to be on prem.

@BordedDev I don't fully understand what you mean, but generally I would say that Zig seems to favour user-defined memory management. In this model, destructors - whether automatic or manual - have to be user-defined, since the actions needed to release memory are part of the memory management scheme.

I admire Rust's insistence on grouping async stackframe allocations aggressively, but it's completely misguided.

- fewer large allocations are not universally better than many small ones

- the programmer is not well positioned to make this decision because the size of async stack frames is unspecified and highly variable due to other optimizations

- this is a perfect job for an optimizer with dozens of algorithms and constantly evolving research

- the optimal solution is almost certainly a custom allocation strategy specifically for async stack frames with a mergeable free list that conserves locality.

@12bitfloat They are a good idea, but I'm very curious if we manage to come up with an even better idea to address the same problems, and if we ever do, it'll probably be due to people's autistic commitment to all the maxims destructors tend to violate.

I used to use Droid Sans Mono because it's nice and roomy, but actually I like Fira Code more now

I'm waiting for him to accidentally rediscover RAII

I thought the N-word had no power in Hungary where there are basically no black people. I was completely blindsided when I explained the origin of "glowie" to my D&D group and the air froze in the room.

@antigermanist I don't think a lesser industrial capacity to enslave people is any sort of redeeming quality. You can't massacre, rape or enslave "a little". Any amount is a maximal moral failing.

I want to use something like NixOS occasionally but then I look at the hardware requirements and decide against downgrading my laptop by two price classes.

The correct way is to install an interactive text editor, read the existing config file, figure out all the relevant options from the manpage, guess which flavor of config syntax this particular - ultimately completely irrelevant - program uses, then guess how your desired changes would interact with the distro-specific configuration which isn't documented and differs in arbitrary ways from the default, and reason from there.

Pacdiff is the best way to handle upgrades because all the better ways are reserved for OSes you use like a product and not like a contrib framework on which to develop your own installation like a unique software project.

WASM was the right choice because to get a successor language off the ground you need to justify its support on its own merit. It's been a decade and it'll be two more at least before it's a legitimate substitute, but it's perfectly positioned and has plenty of resources.