that_jojo

> Their houses still stand today

Was this some intensely sprawl-based city like Dallas? Because the only way this seems realistic to me is if by 'house' you mean actual single-family detached housing. And there aren't many highly populated cities that have a lot of that within their municipal borders.

> a detached single family home, though often inside the city limits

Wow, to even have that as a viable upgrade path.

I don't even live on the coast and in my metro, with the local range for a middling middle-class income, having a detached house within the city limits is an absolute pipe dream.

I'm from the Flint mtro, currently working ~50 minutes away from Flint, my mother lives in Flint across the street from Mott.

I have literally never heard a single person from the area say anything but neutral to positive things about Obama's visit.

And the filtered water in most places has been EPA-compliant for a long-ass time.

> You give the system a callback and it calls you with an event

Maybe I haven't done enough WinAPI programming, but where is that true? I know there are a few helper functions that automatically dispatch an event to a callback, but I thought in general all events had to be intercepted and dispatched in the message loop

> and apply a mask before using it for memory accesses

So it never goes onto the address bus. So it never causes an addressing issue.

The 24-bit issue of the 68000 is fundamentally different. Those tagged 32-bit pointers were used directly, but truncated by the width of the actual physical interface so they never touched the outside world.

...until Motorola released CPUs with full 32-bit address pins on the package. Oops.

It's worth going into why the two CPUs.

Basically, the original 68000 isn't capable of atomically restarting an instruction interrupted during a memory access cycle, and so there's no way to implement a standard MMU.

So Apollo just chucked in a slave CPU that would detect the interruption of the master CPU, halt it, deal with any remapping or what have you, and then just completely reset the master CPU.

Super late, but I think a good approach would be to use an issue/work tracker of really any flavor (even manually), log all of your to-do headings as issues, and then just name each branch after the associated issue/job number.

It's kind of interesting, when you compare WinAPI to classic Mac Toolbox, how incredibly similar their core concepts are.

Especially when you take into account that the first GUI application MS made was Excel for the Macintosh. And then they more-or-less wrote Windows as a runtime environment for porting Excel to PCs.

Not getting into any of that old-school MS-stole-the-GUI flamewar business, I just think it's genuinely historically interesting to note the parallels when you play with each.

I've been playing around with VMS on my MicroVAX 3800 lately, and between that and getting into Windows internals I'm just super fascinated by the difference in feel, when it comes to what the system-level APIs provide, of these highly-integrated, enterprise-oriented operating systems versus the *nix family. Particularly how robust things like user identity management are.

Not saying it's better or worse, of course. Just interesting.

I'd really love to play around with something as hyper-integrated as z/OS or something. So if anyone's got an old ES/9000 or something kicking around that they wouldn't mind sending me, let me know.

I may be totally off-base, here, but isn't WPF independent from Win32?

When would you be creating a branch to do work without knowing what work you're doing?

Most ideas in CS are old as dirt. There was a flurry of theory advancements mid-century and a lot of work since then has been putting those ideas into practice.

It's inertia. Among other things, the much higher inertia of the broomstick has a damping effect on changes in its motion.

In what way? Regardless of whether they're using CI they still have to pull and mainline your change.

Wow, so I just decided to do some digging because I hadn't heard about this and I wanted to educate myself.

Literally the only thing I can find that paints that transcript in remotely the light you're implying is an absolutely garbage Fox News article referencing a Slate article. That Fox article is 18 sentences long, and is mostly a bunch of op-ed ranting sprinkled with some absolutely mutilated quotes.

Ironically, the content of the Slate article paints a picture of the NYT dealing with its readership complaining that they're not tough enough on the administration, and their vigilance and ongoing struggle with remaining as neutral as possible.

Am I old? Everyone's talking about whether this new 'cheese grater' name will take off. But that's what we called the old aluminum case since the G5.

No, he's talking about classic SGI machines like the Tezro:

https://d2w9rnfcy7mm78.cloudfront.net/746965/original_3c751a...

Who on earth is moving from the well-typed, statically compiled world of C# to some dynamic scripting language? I mean, not to besmirch the merits of scripting languages, but C# and, ex, JS excel in very different domains.

I think it probably helps when you're not only good at what you're doing, but also are super into the project.

My performance is abysmal at my day job because I really can't bring myself to be interested in the subject at hand. And yet I'll regularly work until the wee hours in the morning on personal projects without even realizing what time it is.

How did I leave this comment here without any memory of doing it?

I can't remember if it's the same with chrome, but firefox actually uses its rendering engine to render the window chrome as well.

There's a major gap between 'technically superior' and 'subjectively superior'. You sound pretty out of touch here in a time when LPs and casettes have made a comeback, chiptunes are pretty hip, some artists have literally released albums on floppy disk, and, as already mentioned, contrary to your own sarcasm low-poly graphics are already a an indie game trope.

Just because something has more impressive metrics doesn't make it fun.

Maybe I'm really dense, but what on earth does loop unrolling have to do with concurrency or asynchronous code?

Lets not forget that Bloomberg was also the publication that ran with and defended that whole 'Supermicro is totally getting spy hardware added to their motherboards by the Chinese government even though no one can seem to locate it' story. Something's... possibly askew with them of late.

Totally different jojo, sadly.

My god. Sun invented the Taptic Engine.

Are you intimating that she learned a breakthrough technique in how to be old?

I think his point was that it would be a bit silly to put this kind of solution into a product -- which is, in a word: jank -- when capacitive touchscreens are already a tried and true solution in production devices.

Even then, isn't the 'capacitive sensor' just a conductive coating on the glass?

Bizarrely, I was at +4 moments ago and now sit at -1