nagaiaida

the fragment of a word you are thinking of means "two"

yep, same with guitar. go to sleep fumbling through a riff even though you "know" it, wake up playing it smooth as hell

this sort of grammatical error in the defense of ai copyediting does not exactly instill confidence in your supervision of said ai copyediting: "of course an LLM ... were used". perhaps you could still pay an editor to look things over.

decidedly off topic but since i've stumbled across you again, i'm still over here wondering what the hell you meant a couple months ago by arguing that doing bare syscalls on linux from a forth is an emulator.

it was quite perplexing to be called a sovcit who was imagining some software i've written just because it was rhetorically inconvenient for you that said software existed

saying "10x smaller" is like saying "1000% cheaper"

yeah sometimes you end up making something very cool almost by accident. i tried to make shell pipelines properly concatenative like forth and friends and that had a lot of unexpected neat digressions in metaprogramming

> we generally do our very best to do what is right historically speaking. It's hard to see that if you get lost in the politics of things.

or there's a much simpler explanation: the awful things we do very visibly (or simply casually declassify and admit to decades later¹) are a perfectly reasonable basis to condemn basically the entire history of this country and there's no reason to believe in some sort of political dark matter that balances the moral equation.

¹ for instance, if you were right, you'd think there'd be more widely-agreed success stories coming out like this, but no, it tends to be more in the vein of "we destabilized another democratically elected government because that's not the side we think should have won". i wonder what's up with that

saving rocket league replays to watch yourself play from your opponent's perspective was super helpful in 1v1

and as soon as one tries to meaningfully add features to this sort of metainterpreter, the usefulness of homoiconic syntax becomes abundantly clear

well, this is more applied and less straightforwardly categorical, but thinking along the lines of solely looking at compositional structure rather than all the properties of functions we usually take as semantic bedrock in functional programming (namely referential transparency) is how you start doing neat arrowized tricks like tracking state in the middle of a big hitherto-functional pipeline (for instance automata, functions which return a new state/function alongside a value, can be neatly woven into pipelines composed via arrow composition in a way they can't be in a pipeline composed via function composition)

well, hyphenation will most likely insert a lot of regular dashes for easy comparison to rule out "this font is blessed with uncommonly long dashes" and the differing uses of both en and em dashes will cluster along grammatical lines (with em dashes separating clauses and en dashes relating concepts or bounds) which ought to eventually make it clear even to someone who initially bins those together separate from hyphens.

it's still far easier to write a metainterpreter to play around with language semantics if you have homoiconic syntax. consider the feasibility of altering the search strategy in prolog compared to changing something about c# linq semantics.

i just have a little script called session (invoked as session namespace name and mapping to a tmux session called namespace/name and searching all namespaces if the namespace is elided) that just does the right tmux invocation for the various intersecting cases of [in or not in a tmux session already, target session does or does not exist] which also has the side benefit of leaving shell history breadcrumbs i can follow between sessions later if needed

sorry, can't say i've ever cooked from a recipe, but i highly recommend caramelizing already-crispy tofu with soy sauce, sriracha, and ginger (+ fish sauce if you swing that way)

> Good flavors and mouth feel (not tofu!) are important

as one of those vegetarians who isn't particularly compelled by anything intentionally imitating meat, this is always somewhat funny to me. tofu already has good flavor and mouthfeel if prepared well, and presumably the rest of this alleged market segment is as capable of preparing tofu adequately as i am personally. so even if beyond was to pivot to (also) being beyond tofu, i fail to see how that would capture appreciably more of the market.

i could be wrong, but it's always seemed to me that most of the apparent demand for something better than tofu is not in fact coming from inside the house.

plenty of people prefer to go by "it", so i'm not sure this is the slam dunk you seem to think it is. no one is claiming chaucer as an authority; we're claiming you don't seem to know enough to be worth listening to in a debate about the usage of pronouns.

tell that to the public universal friend

that is your prerogative, but this seems to me far more discourteous than somebody putting information down in a format you're perfectly capable of reading yet dislike.

perhaps the command by l sprague de camp would be more to your liking if you're more interested in a story more explicitly about bear uplift like that

if you're forgoing go features to get c interop anyway, why not just roll back to whatever go version gccgo supports at that point?

under what circumstances does deleting files fail on a full pool? i have one that fills up semiregularly and i've never had issues that required me to truncate files

> People with two broken PCSK9 genes have close to zero LDL and have noticeably completely plaque free arteries as adults. I do think this does pretty fatal damage to the theory that you must have some other health issue for LDL to be bad.

i'm not sure i follow this extrapolation from low-ldl individuals to any direct statement about causes and effects at higher ldl levels.

if there was, for instance, some thought-harmless virus endemic to a large portion of the population which somehow caused plaque buildup but only at sufficiently high ldl levels, people with naturally low levels their entire lives would still have plaque free arteries and we would still, as we do, see a broader range of plaque buildup among people with high levels. how do you propose to distinguish this hypothetical (and admittedly most likely biologically incoherent) explanation from yours by only looking at people with naturally low levels?

your assertion that such individuals are an excellent approximation to an experiment on the arterial health effects of lifetime low ldl seems reasonable enough, but you then appear to draw unfounded conclusions about the nature of potential inverse effects at higher ldl levels.

you seem to have articulated precisely the advantage that makes it serve a purpose for me: supporting the version of android on my phone. presumably i am far from unique in not having android 16

remote unlock is also useful when you're not gaming so that feels like the wrong aspect to focus on

okay, i questioned whether i need all that stuff and i've landed on still wanting the same set of capabilities i currently have at the cost of what used to be a reasonable number of menu bar icons.

so now what

in raku, versions are specified for imported packages, not for installed packages; you can specify in the code a dependency on a particular version

?

i'm not so much imagining an environment per se¹ as describing one i've already written, so i'm not entirely sure where any of this is coming from. if you care to have some additional assurance this isn't somehow an elaborate rhetorical trap, a previous comment about forth tail call elimination with a bit of demonstrative assembly is presumably only a short scroll down my profile. ctrl-f for cmov if you want to find it quickly. as i recall, it came up for similar reasons then because people often make similar incorrect generalizations about lots of things that implicitly sit atop a c runtime in their minds. that said, you're the first one to call me a sovcit before asking any clarifying questions so at least there's some new pizzazz there.

i was clear that i was talking specifically about linux precisely because this isn't something one can do portably for exactly the reasons you're describing (which, yes, makes porting things built like this off of linux before the point you've built up enough to be able to go through libc annoying and ad hoc at the very least).

the fact remains that i can, right now, non-theoretically, on a well supported common unixlike os, and entirely unrelated to whatever weird crusade you seem to have invented to stand in for my side of this discussion, link a pile of assembly with -static -nolibc, fire up the repl, and mmap files into memory as i please with nary a bit of c on the userspace side.

as i originally said, i'm happy to consider linux a weird exception to the point you're making in a wider context since this isn't something you can do portably, but there still are entirely useful things one can do today with mmap that involve zero userspace c code on a widely supported platform.

edit: lol forgot to even get to this part. i'm also somewhat curious what you mean with this bit: "you're running what amounts to an emulator." perhaps i'm not firing on all cylinders today but i fail to see how it's useful to characterize performing bare syscalls from assembly (or something more high-level built out of assembly legos) as an emulator in any way, but i'm open to having missed some interesting nuance there.

¹ unless you mean trivially (seeing as this is code i imagined and then proceeded to write) in which case i suppose i agree

and if i directly do an mmap syscall on linux from a freestanding forth that doesn't go through libc for anything? sure, c unfortunately defines how i have say, pass a string, but that's effectively an arbitrary calling convention at that point; there's no c runtime on the calling side so it's not particularly useful to contend that what i'm using is a c api.

or perhaps mmap is incontrovertibly a c function on platforms where libc wrappers are the sole stable interface to the kernel but something else entirely on linux?

if the ceasefire only applies when targeting civilians, was agreeing to a ceasefire in the first place thus an admission of targeting civilians?

tangential, but deploys/builds that involve worktrees happen to neatly sidestep this since then .git is just a pointer to the real one. i use this to avoid having to otherwise prevent docker from wasting time reading the git info into the build context (especially important for latency if feeding local files into a remote image build)