wym doesn’t speed anything up? they have a very thorough page of benchmarks

Google could have done that from the spec though. Google is doing that with chromium despite the source being entirely available

even agpl wouldn’t protect this tool in most cases if a company didn’t want to contribute back, since it’s probably just used in server side scripts and such. also companies aren’t required to upstream stuff, just make source available, which means hard to discover ftp site with a pile of code.

sure something more copyleft is better for large, more commercial projects, but this in particular probably gets more patches from the extra use in the rust community from MIT than they would forcing companies to open source changes

apparently gets a 2-5x speedup over rsync +nicer interface

you seem to have added a condescending comment before you understood the goals. 2-5x speedup over rsync (their benchmarks, but still) seems significant on its own, and an interface that doesn’t require aliasing to be useful is also nice

why is common lisp so barebones? it’s literally nothing but macros! WHERE’S THE SYNTAX

I think if they were planning this at all, we’d see linux support for maui. currently their linux use has been very focused on only for devs and servers

they might ship a proprietary lib with their os, encourage developers to use it, then license it out of being distributed

no it doesn’t, you just have to add them for apps yourself. the readme has a whole section dedicated to live tiles.

Bob Martin himself having moved to a different category

yeah, it’s a setting in the official rpi imager nowadays

are there not just 2 main libraries or so that all the compositions implement it via?

yeah but you still basically end up duplicating the internal structure of the react component but in a css file then.

there’s nothing definitive that makes one of those 3 options better, it’s all preference. any of them fit better than global css though

sure, but both of those are significantly better than a css file. tailwind tends to match the internal structure better, css in js tends to match the component structure better.

tailwind doesn’t have a runtime though, where css in js libs generally do. not that that’s a big point. the difference is mostly preference

it matches the component model of react etc

did you read their statement? they do.

ai detectors are not good. may as well ask your magic 8 ball

if it’s not clear if it’s ai, it’s not the code this policy was targeting. this is so they don’t have to waste time justifying removing the true ai slop.

if the code looks bad enough to be indistinguishable from ai slop, I don’t think it matters that it was handwritten or not.

you shouldn’t be able to tell if someone used ai to write something. if you can then it is bad code. they’re not talking about getting completion on a fn, they’re talking about letting an agent go and write chunks of the project.

you can also buy a nice USB/Bluetooth dac instead of the inline ones that tend to be more fragile. better quality than an internal one and the flexibility of Bluetooth if you want it. generally a little bulky but if you already have wired headphones I don’t think it’s significant

just to be clear since you said both again in different sentences, GUID and UUID are two names for the same thing.

I think that spec predates uuid4, it only mentions the time based/node based variants. 122 bits of auth token should be plenty, right?

the sheer unlikeliness of guessing that large a number, the original post is fake or something else is going on.