What you are describing is what's called free float market cap and is generally what market indices use to weigh stocks. That way you're only trying to replicate the market of stocks that are actually available to trade. There's nothing new about SpaceX in that respect, plenty of companies have float much lower than their total.
> If I was an APT, compromising Tailscale would be priority number 1!
Crowdstrike would be at a much higher priority. They already have a cloud connected root console to all the machines in entire corporations. Compromising your network is small potatoes compared to that.
> The computer I'm writing this on has 64 GB of RAM, 1024 times as much. By comparison I have a 20-core Intel CPU with up-to 3GHz speed or somewhere around there, even pretending each core could run at that max speed simultaneously (which they can't), that's only 133-times as much CPU power.
Over that time CPUs have also increased their instructions per clock by 3 to 4 times, so the comparison is a bit closer than that. 5Ghz in CPUs is also common these days which would make it even closer. RAM has also improved in more than just total size though.
It was still more secure than the default if I understand this correctly. On resume from suspend the laptop would still be locked by the encryption key and without access to the disk even if you can somehow circumvent the lock. The only insecurity was that somewhere in the kernel memory the key still exists so if you can somehow extract that from the live system you can unlock it.
+ battery too. I've wondered if a mini pc with battery would make for a good form factor. I often move between places where I have a desk with a screen but still use a laptop because I want to just suspend and resume. If a mini pc had a small battery just to hold its RAM while suspended I could move between places and just plug in a single USB-C cable and have my full workstation up and running. The thermals could be better than in a laptop and having a built-in UPS better than with a desktop. But last time I checked no one packaged things like that.
That seems wrong. If you have a way to maintain enough propulsion for long enough you can escape the gravity well at any arbitrarily low speed. You "just" need to maintain that speed long enough for the escape velocity from the gravity well to go below it as it diminishes with distance from the mass.
There seem to be some 15 inch all-in-ones but these days if what you want is a small form factor the answer is surely a laptop. Even if you're just going to keep it on the same desk forever that's what you'd get if you want 15 inch or smaller.
I once made a criminal complaint because of a sewer line that was frequently allowed to overflow into a creek. The prosecutor refused to prosecute the case with the argument that the root cause was "real estate pressure" and so the county (that licenses and taxes any new construction) and the sewage operator (that coercively charges anyone that can physically connect) couldn't possibly be blamed.
Another advantage is you can place the fans all along the wing getting you better stall resistance as the flow doesn't detach as easily. There's already a prototype of a hybrid plane that does this:
That's great if you're compiling for use on the same machine or those exactly like it. If you're compiling binaries for wider distribution it will generate code that some machines can't run and won't take advantage of features in others.
To be able to support multiple arch levels in the same binary I think you still need to do manual work of annotating specific functions where several versions should be generated and dispatched at runtime.
I'm curious if that's still the case generally after things like musttail attributes to help the compiler emit good assembly for well structured interpreter loops:
> agents were previously spending 3-5 minutes after each call writing manual summaries of the calls
Why were they doing this at all? It may not be what is happening in this specific case but a lot of the AI business cases I've seen are good automations of useless things. Which makes sense because if you're automating a report that no one reads the quality of the output is not a problem and it doesn't matter if the AI gets things wrong.
In operations optimization there's a saying to not go about automating waste, cut it out instead. A lot of AI I suspect is being used to paper over wasteful organization of labor. Which is fine if it turns out we just aren't able to do those optimizations anyway.
> They are perfectly good machines as servers and desktop terminals.
On the power usage alone surely an upgrade to a still extremely old 64bit machine would be a significant upgrade. For a server that you run continuously a 20+ year old machine will consume quite a bit.
Thanks! By retrofitting I mean having to have a new protocol with this new opt-in method where some apps will be getting integer scales and go through a transform and some apps will be getting a fractional scale and rendering directly to the output resolution. If this had worked "correctly" from the start the compositors wouldn't even need to know anything about scaling. As far as they knew the scaling metadata could have been an opaque value that they passed from the user config to the clients to figure out. I assume we're stuck forever with all compositors having to understand all this instead of just punting the problem completely to clients.
When you say you supported this for quite some years was there a custom protocol in KWin to allow clients to render directly to the fractionally scaled resolution? ~4 years ago I was frustrated by this when I benchmarked a 2x slowdown from RAW file to the same number of pixels on screen when using fractional scaling and at least in sway there wasn't a way to fix it or much appetite to implement it. It's great to see it is mostly in place now and just needs to be enabled by all the stack.
Seems like the support is getting there. I just checked Firefox and it has landed the code but still has it disabled by default. Most users that set 1.5x on their session are probably still getting needless scaling but hopefully that won't last too long.
That's what I referred to with "we'll be finally getting that in Wayland now". For many years the Wayland protocol could only communicate integer scale factors to clients. If you asked for 1.5 what the compositors did was ask all the clients to render at 2x at a suitably fake size and then scale that to the final output resolution. That's still mostly the case in what's shipping right now I believe. And even in integer scaling things like events are sent to clients in virtual coordinates instead of just going "here's your NxM buffer, all events are in those physical coordinates, all scaling is just metadata I give you to do whatever you want with". There were practical reasons to do that in the beginning for backwards compatibility but the actual direct scaling is having to be retrofitted now. I'll be really happy when I can just set 1.3 scaling in sway and have that just mean that sway tells Firefox that 1.3 is the scale factor and just gets back the final buffer that doesn't need any transformations. I haven't checked very recently but it wasn't possible not too long ago. If it is now I'll be a happy camper and need to upgrade some software versions.