Just read the story, thought it was very reminiscent of one of the plot points in Neal Stephenson's Snow Crash (1992) - until I noticed the publication date of 1988, 4 years earlier!
5,317 karma · joined October 27, 2011
Just read the story, thought it was very reminiscent of one of the plot points in Neal Stephenson's Snow Crash (1992) - until I noticed the publication date of 1988, 4 years earlier!
https://lwn.net/Articles/991906/
They have a follow-up "WordPress retaliation impacts community". It's currently subscribers-only for another week, but they do allow subscribers to generate free links provided subscribers don't abuse that - which I don't think this should count as?
https://news.ycombinator.com/item?id=41645867
> Oh.... they vendored everything, including a bunch of external x86 binaries. 32- and 64-bit. FFS.
> But also - I sure hope they got the licensing correct for those parts...
I was looking at the markings that are there, and they made it seem like traffic approaching the roundabout would have priority over traffic already on it.
I'm not sure that's the case. I think the strongest FOSS advocates gave up on Microsoft decades ago, and just don't engage with anything they put out. If MS release source-available stuff, strong FOSS advocates don't peep because they've not even looked at it. Why bother - it's Microsoft. If someone else does it, well, the FOSS advocates still had some hope that what they didn't wouldn't be terrible, so there's space for those hopes to be dashed.
...
750Mb later: WTF?
[tippety tappety clickedy clackedy]
Oh.... they vendored everything, including a bunch of external x86 binaries. 32- and 64-bit. FFS.
But also - I sure hope they got the licensing correct for those parts...
Not only is that not true, it's contradicted by the very page you link.
That page has a list of links to resources you can use to self-host git repositories you want to publish, so you don't have to give up control of anything.
(Although, against GitHub as I am, even I am unable to fathom how publishing things on GitHub could possibly mean relinquishing control of your fate.)
That doesn't explain why their civilian aircraft aren't just not the best product, but have gone completely to shit over the last decade or two. The 737 max is the most notorious example here, as it's their most recent development and has never been good from the start - but reporting suggests that the engineering on their formerly-good lines has been going downhill also, and it's only the fact that they started out as good products which means they've taken longer to fall as low.
And there's very little government revenue for the civilian aircraft design and manufacturing side of the business. It's all free market competition.
purity /usr/share/games/purity/hacker
will do the same thing, but local-first. Also: dpkg -L purity
or whatever equivalent lists package files on your system, will indicate the presence of other tests you can take.Also also, `purity-off`
One other approach that does occur is to just malloc() a 16GiB buffer to begin with. Only pages you touch should end up being backed by RAM(/swap). Then your finalize() operation is just a realloc() to "shrink" the buffer down to its final size. Any decent allocator should keep the data where it is, and just make the now-unused tail portion of address space available again, without ever having needed to back it.
Well, yes, you have to replace free() and calloc()/realloc() too. Sorry, didn't think that needed spelling out.
> > Why not entirely replace malloc() for the process?
> Now that's just rude.
Isn't that generally what alternate custom allocators do, though? Like dmalloc and jemalloc?
lol. We had 32-bit pointers on 386/486 systems in the early '90s, on systems with frequently less than 4MB of RAM.
If making pointers 4x bigger on systems with 2000x the amount of memory is a problem, I'm not sure how we're going to be able to solve anything ever again.
> Also, it confuses any code that assumes you can convert a pointer to a long (or long long) and back.
Well, that's why we invented intptr_t. Back in... checks notes C99. 25 years ago.
smh
(If you still need libc malloc for smaller non-growable allocations under the hood, you should be able to privately access it via dlopen()/dlsym() in your code, shouldn't you?)
I've got a 5-year old phone (thanks Apple for maintaining OS security support for my model for so long!), a 3-year old laptop I'm not planning on replacing any time soon, and the non-computer based hobbies I've managed to stick with for any length of time are running and bouldering, where the only gear you really need for both are appropriate shoes. And I only have one pair of shoes for each.
Yeah, I've got some light, breathable, non-chafing clothing that makes both less unpleasant to do, but I couldn't tell you with 100% certainty what brand they are, or exactly what they're made of. And I have a bottle of liquid chalk, whatever they were selling in the gym the last time I needed to get some more. But I'm not on Strava or whatever, and I don't track my per-km splits or my heart rate/zone or elevation gained or cadence. I'll time a whole run with a $20 Casio wrist/stopwatch, and sometimes calculate an average pace, but that's about it.
Not that I'm particularly good at running or bouldering, but I'm enjoying doing both at the level I'm currently at, so that's fine.
Anyway, any hobby that requires a bunch of gear is just a turn-off for me. The more gear I'd need, the more I want to give it a wide berth.
Computer software I love to nerd out on. But everything else? Hardware? That's a break from the nerdery for me.
So printf(1) is the man page for the /usr/bin/printf command, while printf(3) is the man page for the libc printf() function.
Alternatively, readdir(2) is the man page for the readdir syscall, while readdir(3) is the man page for the libc wrapper, which no longer actually calls readdir(2). See also syslog(2) and syslog(3).
Or, time(1) is the man page for /usr/bin/time to time how long commands take. time(2) is the syscall to return the number of seconds since the epoch. And time(7) gives you an overview of time and timers on the system.
"just" is doing a lot of heavy lifting in that sentence.
Doesn't this depend on how long you're planning on investing for, and what your criteria for selling your investments are?
If you're planning on investing for at least 10 years, and you're willing to give yourself a 2-3 year window for selling your investments once they reach a threshhold you decide on ahead of time, isn't the 10%/10% investment better?
(e.g. if retirement is 20 years away, you might consider putting your funds in that sort of investment for 10 years, with a view to moving them to something less volatile in the 5 years after that, as soon as they cross a 10% annualised return threshhold during that window.)
Sometimes, to lead people out of a wrong belief or worldview, you have to meet them where they currently are first.
It's like being a gambler, but you get to stack the odds in your favour, deliberately, tell people you've done so, and have everyone be fine with that. If you use any knowledge of future events to stack a few odds a little more in your favor, no-one's going to know any different, and they'll attribute any weird variances in your income to the punters who all made poor bets, rather than to your mad odds-setting skills.
If you're going to gamble, always be the house. Only a complete moron can lose money that way.