stackghost

I know this is in jest, but because of the "hurr durr" connotations, only the absolute most bearded of free software zealot neckbeards are going to ever run GNU Hurd beyond simplytest driving it.

Open source continues its unbroken streak of showing us why naming things is important.

The problem with a reel mower is that if you let the grass get too long the reel mower won't cut it, so you pretty much have to do it every few days when it's growing fast.

Depends where you live, what season, and what equipment.

I live in the PNW where the grass grows crazy fast in the spring, and I use a reel mower since my yard is small. It needs to be done regularly, and I'm not even a "lawn guy".

There's always Full Disclosure, I suppose. I would imagine that open discussion and disclosures have moved underground to closed groups.

>All you did was waste three times the gas.

They don't mean do all those cuts each time you mow. You mow the grass in one direction one day, and then a few days later when it needs cut again, you mow a different pattern.

Police officers are also statistically more likely to abuse their spouses. Don't let the women you care about get involved with cops.

Legally, perhaps. Behaviourally not so much, in my experience.

That's definitely an option, though I prefer to just put a README. No reason you couldn't have the default make target just execute `cat README.md`

It's an 18 year old kid talking up their accomplishments two years ago on Twitter.

When I was 18, I also thought I was hot shit. No surprise they're being self-aggrandizing.

I do this with plain ol' makefiles.

Even for projects where Make isn't part of the build pipeline, like Rails or C++, I have a standardized makefile I put in the project root, using includes for "secrets.mk", so I can do things like "make deploy" and it Just Works(tm).

Sometimes the old ways are best!

>all you get is the possibility to [...] execute code

Anyone who's ever done even a beginner CTF knows that achieving code execution is a big deal.

MathCAD or GNU units work well enough for me

The longest I've spent in a dentist's chair is perhaps an hour, when I had braces as a teen.

Being cooped up in a metal tube for 13 hours, knowing you had to do the same thing tomorrow, and then the same thing two more fucking times on your way home, is not worth any vacation to me.

These calculators are, without question, excellent little devices and the HP ones in particular had great engineering behind them. I had an HP48 in undergrad, which was considered pretty much mandatory for engineering. There was a thriving student sneakernet of programs you could get that would trivialize certain problems. Some friends had the HP49G which was, in my opinion, a step down in terms of build quality. Years later I bought an HP50 which was the best of both worlds.

I still have my HP50 but there's just no reason to use it. Anywhere I go I either have my phone or a computer. When I was in the air force I would have to go into EMSEC zones where you couldn't bring external devices, such as SCIFs, but the number of people with needs to be running engineering calculations in such an environment rounds down to 0. Certainly I wasn't one of them.

Even "in the field" nowadays, you're likely to have satellite connectivity and a laptop. There's just not really a use case for graphing calculators that I can think of. It's too bad, because they're awesome.

>2x13 hours plus a few hours airport time.

That sounds like pure torture

I thought the original purpose was to rEwRiTe iT iN rUsT and replace gecko in Firefox?

I guess? That's pretty confusing wording, and a bizarre rant if so.

>How do you make an std::array of a given type? Wrap the existing type in an extra layer of std::array, we all know this

huh? where is the extra layer?

    std::array<int, 5> array_of_ints = { 1, 2, 3, 4, 5 };

>How do you make a C-array of a given type? Oh boy, "prepend the array specifier before the list of existing array specifiers"

?

    int c_style_array[5] = {2, 3, 5, 7, 11};

>"Slow is smooth and smooth is fast."

When I was in basic the instructors repeated this incessantly. About two thirds of the way through what Americans would call OCS they made us walk into "the gas hut" which is a concrete bunker-like building in the middle of a field near the rifle range.

Inside the hut is a hot plate with an old shitty skillet. Inside the skillet are pellets that give off tear gas when heated. You walk into the hut and immediately get slapped in the face by what I might charitably describe as the worst onion-eyes you've ever experienced, multiplied by at least 100.

But the training is fantastic because in that moment as I was standing there with my eyes scrunched and burning, I unconsciously whipped out the gas mask, put it on, did the proper drills with the filter and decon cream, and had no conscious recollection of having done so. The urge to rip off the mask and rub your eyes is overwhelming. The instructor told me "good drill" and sent me on my not-so-merry way.

Same thing with mag drills. You slap that forward assist without even thinking. Anyways, slow really is smooth which really is fast.

Yes it will hurt the game. Americans already have the NFL if they want to watch commercials. Leave soccer alone.

I would imagine lots of occurrences of "demo scene" are due to autocorrect on phones.

Imagine being so pedantic that you're gatekeeping because of a whitespace character. Couldn't be me.

Sounds like a dream job, tbh

>FWIW, at a FAANG!

Do you work on ITA? Only FAANG I'm aware of using Lisp is Google.

Yeah I'm not sure why it's not in the manual, as it's had arena allocation support since at least 2.4.x, but basically:

- use SB-VM:NEW-ARENA to make a new arena

- use SB-VM:WITH-ARENA to redirect ordinary allocation into an existing arena like you would use WITH-OPEN-FILE or similar macros

The only real doc is this internals note, and it doesn't even cover NEW-ARENA which I guess is left as an exercise to the reader: https://github.com/sbcl/sbcl/blob/master/doc/internals-notes...

For an object with the mass of a cow, the gravitational effects are minute, and thus if we study small gravitational interactions we would surely want to model the distribution of mass of the cow.

Either way, no layperson (to whom this black hole sim is targeted) would consider a simplified spherical cow to be accurate. That's why the spherical cow is a meme.

Perhaps you're getting the pushback you're getting, because you have a different idea of what accuracy in physical simulations means.

Edited my comment for clarity. I meant "friendly local" as a euphemism, like "neighborhood pub".

Anyways. Ask Claude.

>I don't see "simplified" as being opposite to "accurate".

Is it accurate to model a cow as a sphere?

Pretty sure 37signals' email/calendar offering ("Hey") works this way.

I'd ask your friendly neighborhood LLM for design advice, but off the top of my head, so long as `static_assert(std::atomic<whatever>::is_lock_free)` passes, you could build a lock-free SPSC queue with just plain ol' std::atomics and probably liberal use of `alignas()` calls

>realistically you'll need 16x for context / throughput optimisation

Sounds like I'm buying a lottery ticket this week so I can drop $800k on hardware.