95014_refugee

7 ms·

1.
by 95014_refugee 9mo ago
@ooedotech https://youtu.be/urGmmkUDi20 etc.
2.
by 95014_refugee 1y ago
See also “information desert” and ask yourself why a survival-oriented species might behave in this fashion. Or don’t, it’s why they do.
3.
by 95014_refugee 1y ago
“sj placed cool first” … in what universe? Steve placed “Steve likes it” first. Many of the things he liked were terrible. Cool things happen(ed) at Apple in spite of executive leadership, not because of it. The better E-team players know t
4.
by 95014_refugee 1y ago
You are confusing waterfall with BDUF.
5.
by 95014_refugee 1y ago
I do wonder how much of the hate on “waterfall” is perpetuated by folks that never read the paper. It’s the “socialism” of development workflows…
6.
by 95014_refugee 1y ago
The exploit as described doesn't "brick" the device; that would require permanently disabling it. A tethered restore would be all that's required to recover in this case.
7.
by 95014_refugee 1y ago
It would never have worked. So many of the things that owning xnu has made possible would never have happened on top of Linux. The things you can do when you know each and every customer of the stack, and you all belong to the same business
8.
by 95014_refugee 1y ago
For a long time we held the line on not having file operations originate from within the kernel (layering reasons). Eventually less sane heads prevailed.
9.
by 95014_refugee 2y ago
No.
10.
by 95014_refugee 2y ago
One does not "hone in" on anything. To hone a thing is to make it sharper or more acute by removing parts of it with an abrasive. The word you are looking for is "home", as in a homing missile, etc. Yes, this is a critic
11.
by 95014_refugee 2y ago
Responding to a TCAS RA is not "overly cautious".
12.
by 95014_refugee 2y ago
It's not inoperable; warnings are still issued, but the RA (resolution advisory, i.e. "climb", "dive" etc.) functionality is inhibited.
13.
by 95014_refugee 2y ago
This makes some very naïve assumptions about the relationships between entities in a program; in particular that you can make arbitrary assertions about the representation of already-allocated datastructures across multiple versions of a co
14.
by 95014_refugee 2y ago
You mean “can’t resist the name placement kickback promises”, surely.
15.
by 95014_refugee 2y ago
Worth reading his son @snakesofself's comment below that video for additional context. As a fan of the show, and what it did to advance the art of visual storytelling, learning more (and understanding less!) about the artists just make
16.
by 95014_refugee 2y ago
It's always a compromise. Part of the exercise, whether it be making an existing codebase amenable to verification, or standing up a new one designed for it from scratch, is to identify, contain, and comprehend sources of entropy withi
17.
by 95014_refugee 2y ago
Viewing an ad is not “giving back” in any meaningful sense. Modern adtech primarily benefits the infrastructure providers, rather than providing a service to its “clients” or a revenue stream to site owners. Adblocking is the only meaningfu
18.
by 95014_refugee 2y ago
For sufficiently narrow interpretations of "working", perhaps. Otherwise, I think you might be a little optimistic here.
19.
by 95014_refugee 2y ago
> I've also wondered why the TLB isn't larger. Fast CAMs are (relatively) expensive, is the excuse I always hear.
20.
by 95014_refugee 2y ago
I’m not sure about the “sadly” part here. Whilst it proved that something could be done, it also taught us a lot about what doing it cost (a lot), how scalable it was (not), and whether it would be broadly applicable (no). Any strategy for
21.
by 95014_refugee 2y ago
... and the open-source clone (EmuTOS) has been widely ported since.
22.
by 95014_refugee 2y ago
Memory efficiency just for one. For most programs, and especially in the embedded space, 64b systems carry around (and process) a lot more zeros than 32b systems do. You can still do 64b math when you need it, but you don’t have to pay for
23.
by 95014_refugee 2y ago
At 34, not old. Maturing, perhaps. It’s worth reading the original Waterfall paper. If you’ve only ever heard of it as the bogeyman, it might surprise you. From your tone here, I think you are seeing “people over process” play out in your c
24.
by 95014_refugee 2y ago
Excruciatingly slow, mechanically and electrically unreliable, obscenely large. Inconsistent-to-zero quality of the inserted device leading to people complaining about how “you” lost the data on their US$3.00 card.
25.
by 95014_refugee 2y ago
The “holier than thou” flex is /particularly/ ironic.
26.
by 95014_refugee 2y ago
Try making a living as an indie developer and then bitch about pricing. As others have noted, the up-front honesty and realistic pricing are a lot more refreshing and encouraging than some race-to-the-bottom pricing that guarantees the dev
27.
by 95014_refugee 2y ago
It’s happened more than once. Itemis built a whole pile of tools on it, and the things it enables (stacked DSLs lowering to C, for example). Sadly, nobody wanted it. Check out https://mbeddr.com and weep for what could have been
28.
by 95014_refugee 2y ago
If you think that you want to live in a world where your life is heavily influenced by machines that were trained on the idea that you don’t deserve to exist, then yes, “toxicity” isn’t a problem. But you don’t think that. Even if you think
29.
by 95014_refugee 2y ago
There’s an EmuTOS port to m68k QEMU too.
30.
by 95014_refugee 2y ago
You... haven't worked on a large codebase, have you? The part that baffles me about this entire post is that it's trivial to obtain pointers to member functions legally, without the fragility associated with guessing VTable offset

More ›