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.
they're different files generally, the only client that will automatically request them is a debugger.
you turn them off because you don't want to expose your full source code. if you would be ok making your webpage git repo public then making sourcemaps available is fine.
steam is one of the few commonly used 32 bit apps left on linux.
I imagine most of it is bc most other things are oss and have been updated/rebuilt already. having to run a 10 year old binary happens way less on linux than it does windows.
a handful of distros have tried to remove 32 but support they've gotten backlash bc they'd lose steam support. linux the kernel won't drop it any time soon, but there's a good chance that if steam drops 32 bit, so will fedora etc
yeah, ofc it should only be a curated set of errors where the consumer can do something about it. unknown errors should just be opaque 500s
sql as the language executed by the db hasn't changed notably, but I do think there's been significant developments in ORMs. for a lot of developmers sql is now just an intermediate target
more directly, sqlite was originally for tcl which is why they share the semantics.
also I'd argue that sqlite is a bigger contribution than tk, but I suppose in a more roundabout way
did you read it? apple throttled device performance. google is throttling charging speed and battery capacity for safety reasons. there are literally phones melting. also, battery capacity is something people assume will go down over time. also they're giving clear notifications when people are affected.
it's not really the same, and definitely not worse
NixOS, plasma rn but sometimes jump to sway. I'd say distro is more relevant. for the most part I just have an editor and a browser open, DE doesn't change much about my workflow. NixOS definitely does though
chosen by my team, company at large doesn't care but it's nice for everyone to be on something consistent. company devices
NixOS is a nice balance of the two
I generally just copy my personal setup, which I've spent a decent amount of time on, but because I enjoy it
not particularly, but nix supports all of the big ones
language and stack a little bit, it's all stuff that has good integration with nix. we deploy nix containers and then have consistent environment everywhere without having to work in a container. my team is a pretty standard team maintaining some full stack web stuff
it doesn't matter how it was made once it's secondhand since it doesn't support the manufacturer
I suppose there's people that bought the original item since it had resale value, but I really doubt that's significant overall, especially at most thrift stores
I'm saying we weren't taught when react was the way people wrote sites. if I was writing a site with pure html, css is great, especially modern css.
but if I'm already using react and their abstractions, opinions on that part aside, I'd personally rather lean on the react component as the unit of reuse. tailwind removes the abstraction that you don't need, since many people in react tend towards one scoped css file per component with classes for each element anyway
at this point I'd be more inclined to say for many sites the api and data fetching things are the content and html+css is presentation. csszengarden is cool but I haven't seen the html/css split help an end user, or really even me as a developer.
instead of using classes you just use whatever your ui library provides for reuse. stick a classname string in a variable and you have a class. use a component and it just contains all its styles.
unless you mean that if you look in the inspector you see a mess of classnames. I don't have a solution there
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