> I don't think anyone has the ability to shoot down enough Starlink satellites to make a difference.
Not with rockets, but maybe with lasers? What damage can a single one do? Could a country deploy them at specific orbits to have enough coverage to destroy a sufficient amount?
> It's interesting that 17% are not satisfied with editor support for Go.
GoLand does a better job and is more stable and reliable than VSCode here, even having to restart the daemon from time to time for VSCode. Of course it could also be what you said, I can only write for myself. I hope they will be able to introduce stability and reliability of the former.
I have had issues with the recent go plugin for VSCode too. The new version is unreliable and the language server needs a reboot fairly often. It is a real pain because when it breaks it often shows a compile error that you end up scratching your head over and a simple restart of the editor will often fix it. It definitely wastes time and needs addressing soon.
Perhaps if a sample could be collected when healthy and frozen for long-term storage.
In my experience antibiotics were prescribed for acute symptoms that quickly worsened. I don't think they would have delayed my treatment for the hours or days needed to collect a pre-treatment sample.
I used the old Google Pay for both tap-to-pay and for organizing my various membership cards. Gas, grocery, coupons, things like that. Since sticking various memberships cards in it, some of the old physical cards have been lost and I hope the rest are still in my filing cabinet.
Because with "new" Google Pay, all of those membership cards are gone. They didn't just not migrate the data over; this isn't a feature present in the new one. I don't see any reason to continue using it. Apple Pay is working better for me for tap-to-pay, and I'm instead trying to replicate some of the old membership card organization with Apple Wallet, albeit without much success yet.
(Can't believe we have to use "old"/"new" delimiters here either, while Google gets to pretend it's the same thing.)
(Can't believe we have to use "old"/"new" delimiters here either, while Google gets to pretend it's the same thing.)
Well, there's also the "old old" Google Pay...or Wallet, or whatever it was called when I tried to use it. That didn't work well, thereby helping to accelerate the end of my Android experiment. But apparently, according to a friend at the time, the new Google Pay worked much better. But not well enough, obviously, because now Google is rolling a "new new" Google Pay.
I quit using a lot of Microsoft products because of rebranding bullshit like this. Which one do I use, and why is this one better? Oh, if I'm going to go to all that trouble, I'll just try a different product entirely, then.
I definitely had my membership cards migrated to the new app. I can see them by clicking on the credit card displayed next to my user icon in the top right. This opens a new screen with the loyalty cards listed at the bottom.
I agree with that person point on that not being a limiting factor. SciHub and all the networks of exchange of publications before that (I've seen exchange of proxy accounts and forums to do that since 2003, unsure about what existed before) have helped with that a lot.
Just to list a few points that come to mind:
Environment:
- A university that doesn't provide the ressources necessary (equipment, computing ressources with adequate expertise)
- Colleagues that are not supportive or worse putting you down for internal competition (just fame, attracting the most promising grad student of the year, or funding lines for grad students and postdocs)
- Intellectualy poor environment, colleagues that have no understanding and no willingness to understand your field of research
Money:
-Difficulty to compete when it takes you 80% of your budget to do 1/10 of a big lab (behind the name of a single person but really a group of 10s employees) can do with their large fundings. This is especially true of US vs many other countries.
Sociological:
- Gender (we know that women are not "allowed" to grow as much as men in some domains)
- University delivering a PhD, I still see people in their sixties being presented as a graduate from (pick an Ivy) and people ignored in discussions at a table of Ivy league graduates (despite that person being an expert)
It does not even have to be worse to be a problem. Maybe the battery requires certain loads and capacity at certain times to work efficiently and not age as fast. There are too many unknowns.
You already have to reboot into the Recovery environment and disable both System Integrity Protection (with csrutil) and OS root-volume signing (with bputil) in order to even (persistently) modify any of the files in /System now.
Malware can't do that, because there's no way for any executable that runs in the regular OS—and isn't signed by Apple—to get anything to automatically happen over in the Recovery OS.
(That's not to say you can't have persistent malware in macOS; just that it can't persist itself into the OS boot volume. It has to persist into the user volume—which is great, because that means the OS can, on boot, mount the user volume noexec and scan it for malware while running in a known-good base state. That's even without needing to boot into the recovery OS.)
So, other than OS updates, basically the only reason these files get modified is when people modify them manually. And the only people doing that are 1. people developing kernel extensions (or their friends, the Hackintosh community); and 2. enterprises burning low-level configuration changes into OS images for image-based deployment.
And both of those cases involve modifying things that are effectively "underneath the OS API abstraction", and therefore don't have the same ABI guarantees that the OS APIs themselves do. Thus the whitelist.
You know =what would be cool: If all apps had to register their pref config files into a single dir and that would be tracked and snapshotted - and then you could just have ALL apps look to the same dir for where their configs come from and you could have a single repo for ALL apps on your or ANY system - and then you could walk up to a terminal and plug in your "license key" which said what apps you had access to and what ones you had configs for and you could just run that app with all your input and prefs and mappings etc...
I actually wrote a white paper on just this in ~2003 or so - and met with several engineers from google and they said it was impossible.
The idea being that you only carried around with you your profile, and you could just come to a dumb terminal, plug in your key, three factor auth - and the terminal would give you access to the apps and resources they had...
This was basically the idea behind the Windows registry - a single configuration store. With mostly the same tree structure on Machine and User level, so your local prefs could override machine-level prefs. The 'user' part was portable between machines on a domain. And you have a single API to access or change settings
Opinions may differ on how well it was executed in practice. I'm not sure /etc/ with its hundreds of different file formats and Ansible or Chefs as an 'API' is that much better
> This was basically the idea behind the Windows registry.
Was it? I got the impression that the original (Windows 3.1) registry was a Windows-internal thing—a store of Windows settings, and a set of APIs to read and modify those Windows settings, e.g. COM/OLE class registrations. (See https://devblogs.microsoft.com/oldnewthing/20080117-00/?p=23...)
But then, third-party ISVs found the registry, and exploited it to store their own settings. And Microsoft being Microsoft, they accepted that unilateral design change and continued on with it.
Prior to the registry most settings were in files like WIN.INI, and ISVs put settings there. The registry took this idea, added more structure and an API so simultaneous writes don’t screw up.
With the registry, each vendor puts its stuff under a path like HKEY_LOCAL_MACHINE\Software\VendorName, even Microsoft.
Yep. The INI files were the original ways to store config info...
The registry was the next step. What would be great is an online serve for such - a machine gets booted and it asks for your config unam UUID etc - and then just slurps your snapshot down.
OK, disclaimer - I am going on over a decade since this happened:
There was a phone that came out (nokia??) that had a docking station and you could have a screen on it and a keyboard attachement etc...
I presented this in ~2004-ish as a white paper... (lost to hundreds of machines since, and poor data mgmt over time)
I met with a few engineers friends from google over this idea and they said they didnt think it was possible (which at the time it was not - even though I wrote about it in 2001) - and then there was that phone that came out which allowed you to have a phone docking station and use it as your primary computer.
This was at the same time whilst I was talking to my buddies at Intel about stacked procs - and they were doing 64 cores in ~2004 in test dies... and they worked.
It was in 1998 when I was at Intel that I asked "Why cant we just stack multiple CPUs on top of eachother?" and was laughed at...
I sat right next to Andy Grove, but I only spent all my time in the DRG Game lab testing games on AMD and Celeron procs to get subjective results on game perf.
Anyway... I posed a lot of things that were laughed at, which then became reality later.
I worked with a MIPS proc eng about Slot-Rack-Servers, in 1995 - this was deemed impossible... later we have HPE based systems... His name was Kent... he was one of the chief MIPS designers...
I was saying "lets make 'slots' that we can install a switch, a server, storage or whatever on the backplane..."
Yes - I am not lying - these were just things I imagined in the early-mid-late 90s....
I had a good career - but I cannot take any credit for these taking production due to I didnt ever implement any of these ideas... aside from expressing them earlier than others who were far more capable of executing.
Its just like IFTT - I literally whiteboarded IFTT for a bunch of engineers from Lockheed a few years before that existed... They have built a lot of what you interact daily with (netflix) among others...
My soul flaw - is that I think of something early, I have no ability to bring it to fruition and even though I have exceptional famous engineers as friends, I cant bring my ideas to market...
and then a few years later - things I designed hit the zeitgeist and hit market...
I have, as a consultant, made people MANY billions of dollars - and havent received anything in return.
Not with rockets, but maybe with lasers? What damage can a single one do? Could a country deploy them at specific orbits to have enough coverage to destroy a sufficient amount?