Pup Biru

along with most modern languages… it’s the way we deal with async when you don’t want callback hell. it’s just a complex problem domain

like… what… JITs are complex so that’s a problem for V8 specifically?

they’re talking about inheritance as a suggested new way to pay for your copilot subscription

it’s like how the linux kernel isn’t semver: the number after the decimal point has a maximum of .19 and then the first number increments

except that one time

kernel version 4.20 is the only .20 kernel version

tmux > gnome

a great illustration of the dunning-kruger effect

hard disagree on what belongs in the same commit history… a single merge should be an entire feature, and your commit history should read like a change log

Squashed commits are not atomic … overall task requires modifying multiple different systems

that’s why monorepos exist

i’d say squashed commits aren’t always atomic, but this is one of the biggest reasons people add the complexity of a monorepo: if changes cross multiple systems, ideally their merge/revert should be an atomic operation

you either have deployment complexity (ensuring the feature is in all deployed systems before switching over), code complexity (dealing with the feature only maybe exiting in parts of the system), or repo complexity (where tools manage a monorepo and thus commits and PR/MRs are atomic across your system)

either… some apps have just started to do single factor login with just email, profile options can be optional, if there are required fields or terms of service to agree to then that can come after email validation

i think these days the best practice for mobile apps re retention (other than sso or passkey) is to just ask for an email, then from the validate link continue with register

reason being that more steps to register means more ways people are likely to drop out of the flow, and this is basically about as short as it can be

when the user has validated their email, then they’re more invested so they are more likely to complete

that also fits nicely with what we’re talking about with good security

“not actively harmful” and “notionally the bare minimum” are pretty low bars and i’m glad that, for once in modern memory, mozilla cleared them

if only it were that simple in a social and professional context

i’ll choose linux + a user age metadata standard that’s technically compliant + shit professional application that i have no choice but to use - over windows + exactly that same application any day of the week

sure, but if an application “requires” age verification for whatever reason, would you prefer the functional equivalent to clicking “i’m over 18 pinky promise” as a standard, or they use biometric data that they all implement differently and then there’s like 33.7 leaks in the next 6 months?

like the whole thing is bullshit, but a file on disk is a wink wink nudge nudge sure we are compliant bud

the true unix way: if you text editor you own the world

i took the phrase

You don’t need to understand why they struggle, just accept that they do.

to mean that you shouldn’t assume someone is lying. they just might have different circumstance or needs. that doesn’t invalidate their experience, just that you’re solving different problems (which may not have been well communicated, and also may not even be technical problems).

if you’re trying to solve their problems, then sure that’s a discussing… but 99% of tech conversations on the internet like this are people berating others for “not understanding” the “simple” way it’s done because it works fine for them

slight disagree: proud version is actually when you become so disillusioned with your old code that you throw it all out and start again

well see when you’re too lazy to design a schema and just want to throw broken data into a black hole where you may or may not be able to retrieve it and deal with the repercussions in production - or better yet let the ops team handle it at 3am - then that’s when you’d choose mongodb

i’ve already linked the docs that state that native windows containers exist. whether or not specific images exist is not relevant

WSL, Hyper-V and Windows Containers are all options

they have to be built specifically for windows (of course the kernels are different, so the binaries are going to be different) but you can run Windows native applications on Windows kernel with a different implementation of containers using the standard Docker CLI and interfaces

Cgroups are just 1 (by far the most common) implementation of the container backend

what kind of monster writes a script without a shebang?

or fixing windows by only using WSL and reading the arch wiki

meta and ctrl switched, because if there’s something apple did right it’s using the thumb as modifier key for copy/paste/etc instead of pinkie finger which is far FAR less able to deal with repeat strain

but i also type programmers dvorak because i got pretty horrible wrist pain at one point so anything to stop me damaging my wrists :p