fractaled

Pretty sure we can't resolve brown dwarfs farther than a few 10k ly (well inside the confines of our galaxy).

Even ignoring the AI costs, 'rework' is going to be more expensive as soon as you have customers. For example any sort of data migration. Or UX expectations. Or public API interface. None of these can change without some thought, so one would be leaning on these specs quite a lot.

I'm not sure you'd need to directly fetch to determine if they resolve. One could probably inject an img tag and see if it resolves.

96% of us are already given ~5k a month for 40hr/week of work.

If UBI is just printed, then sure there would be economic problems; but I think the idea is you redistribute it via taxation.

You'd never have a `compare(std::string a, std::string b)` function in your code base. It would make copies of the strings (and destroy them). So it seems to me the article is comparing their new thing to a straw man.

It's hard to know how to take this given that their first example (function call overhead) seems deeply flawed -- you'd never have a 'compare' strings function take std::string by value. (Maybe const string& or string_view). Also, the alternative would have to have a destructor of some type (unless it is a string_view analog) to make it an apples to apples comparison.

Does being the destroyer in the dark forest scenario not reveal yourself to other destroyers?

Also while I'm sure a relativistic kill vehicle could neutralize a planet, will it also get all the populated moons/orbitals in the system? What if the target species is already multi-system?

It might be better to say raw_ptr<T> is a dumb pointer wrapper. raw_ptr is discouraged in favor of unique_ptr/WeakPtr/RefCounted; but it is used in places where you'd have a T* at rest.

IMO the friendly fire on his camp was a cover/false flag to begin the "march for justice". The coordination/speed his coup attempt had couldn't be set up in such a short amount of time (since the "friendly fire" incident), so it was planned for at least a few weeks.

I don't think this logic applies to the demographics of today. The total number of humans to have ever lived is calculated to be ~105 billion. So assuming you're applying that logic to today, you're one of the most recent ~7%, which doesn't seem that remarkable -- at least not to the point of assuming fatalistic scenarios.

I'm pretty sure the issue with Spectre/Meltdown is about an OS process reading other processes' (or kernel) memory. These are fundamentally chip issues, not developer issues.

See https://googleprojectzero.blogspot.com/2020/02/escaping-chro....

* Planet Nine discovered/spotted * No evidence for Dark matter WIMP theory * Firefox switches to blink

What doesn't work with short division and multi-digit divisors?

A web search says your approach (which I admit I don't follow) is off by a factor of 40 -- the Sun moves approximately 500k mph around the galactic center. A speed 8x slower than the star mentioned in the article.

FWIW, Bill Warner's PhD is in math & physics.

It wouldn't be JSON then. Give this new thing a new name and move on.

I read that to mean there was only one study that was randomized & controlled.

Basically when you say "there are studies that show X" you aren't saying anything because "studies" are cheap unless your methodology is rigorous and sound, which isn't the case a lot of the time.

Speaking of scale, Pluto is more than 2.6 billion miles from Earth at closest approach :).

Setting up the wait for 10k file descriptors will still be O(n), the actual wait is O(1). And presumably you're waiting many times, and not changing which 10k files you're polling for each wait. Each wait is O(1) because the kernel just calls you back when your wait is satisfied -- it associates a list of waiters for each file descriptor.

So, to paraphrase, "if things were not as they are we could come to a different conclusion". Yes, that is a thought, it was not worth writing down though.

In Seattle, over the last 8 years I've averaged 2933$/year on my car (which I own outright). That includes insurance, licensing fees, parking, gas, maintenance, tickets, rental costs, gps, and tolls.

I don't think you can make a compelling case for a taxi service vs car ownership based on cost -- but rather convenience.

I think the core of COM is sound (pure interfaces, QI, refcounting, IDL).

I think the ugliness is due to threading issues and being welded on to Win32 message pumps. If you have a dedicated COM thread/pool you'll mostly be fine (security stuff can still get complicated). But on the other hand if you start doing COM things on a thread you own where you share control of the message pumping, you open yourself to a world of mental anguish.

For Excel 2007 (on Win8.1) you 'just' middle click (wheel-click) on Excel if it is pinned to the task bar (which is how I happen to have things set up -- same thing as opening two instances as mentioned elsewhere). I agree, not very obvious, but I think multi-mon puts you in the 'top' 5%* (so you won't get as much help from a scenario point of view).

*can't find a reference for that, so I may be off.

How about if you want to override just one part?

It doesn't make much sense with "padding", but for something like "border: red solid 2px;", how do you override just the color if you don't have the individual components broken out?

Your zoom appears to be set to 125% (not sure if that absolves IE or not -- I see similar lines in Opera when zooming). Looks okay to me at 100%.