The question isn't whether we should replace filesystems, but rather if we should move core file system services *into* the filesystem. That is, should we embed all of the things that locate does into the filesystem? My answer would be "no" (I prefer single-task entities where possible), but making a filesystem "hook" wouldn't be bad (i.e., trigger X when a file is updated, where X might be an indexing operation). Perhaps we should standardize more metadata, where it is stored, and how it is accessed. There's nothing wrong with storing that *somewhere*. Whether it is the filesystem or elsewhere is a bit of an implementation detail.
My wife and I teach a homeschool co-op, so we have had to do a lot of searching for low-cost solutions for mixed-mode classes. The same results would probably work well for less in corporate offices.
I had thought I disabled automatic updates by following a guide online. I was giving a presentation in front of over 100 people on my laptop, which because it is a laptop mostly used in the field is not on my domain. You can guess what happened when I booted up.
Luckily I was able to borrow someone else's laptop and they had Powerpoint installed and I had the presentation on a thumbdrive.
Fuck Microsoft. I complained to them but they said it was my fault for wearing slutty clothes.
Are you just trolling or do you not understand anything about the words you are saying? CMR and SMR are physically different ways of storing the data on the surface. Why doesn't my car have a setting to be an airplane?
I read a fiction so I know this is possible... durrr
And any app that takes advantage of this will be uninstalled instantly.
use 2FA on all your important financial and identity accounts so your password will be insufficient to login in. protect your password manager with a very strong master password and 2FA. that will be the one and only password you have to remember.
It is very important not to reuse the same password on multiple sites. Therefore it is impossible to memorize all of your passwords and you must use a password manager. Once you use a password manager you should go all in on using completely random passwords or passphrases - it doesn't matter which as long as there is enough entropy. So pick 16 character random letters numbers and punctuation or pick 6 word random passphrases from large dictionaries. Since more current websites accept 16 characters than 30+ characters the password choice makes more sense.
There is a security bit in every packet that your browser can check to see if it is being used "for evil". It will be relatively easy to secure WebAssembly, at least compared to Flash and other things that came before it. https://www.ietf.org/rfc/rfc35...
For anyone who wants to see what SPU code looked like, here is a an old article of mine from IBM's DeveloperWorks on the subject:
I can't count how many times I've saved my photos on Google Photos and thought, 'If only there were a way to initiate a chat with someone right now to talk about this photo I just uploaded.'. I healed my misery by going into my PDF viewer and making a connection over my PDF viewer's built in social app -- this is not a joke, my PDF viewer has a F*!^@#^ social sharing feature with a separate social media network for sharing PDFs... wtf?
Yeah, I want a copy too for the same good and unsuspicious reasons!
Yup, that's when I dumped Foxit PDF Viewer. All of the sudden my PDFs were attached to some crappy social network nobody uses. Why the hell would I want to share my private PDFs on some social network?! Nobody anywhere ever asked for this feature. Uninstalled.
Anywhere where you have a second derivative where the variable with which you are taking the derivative with respect to is dependent on another variable. You would previously have to use Faa di Bruno's formula to properly take care of this situation. Now you can just do algebraic manipulations.
Reality must take precedence over public relations, for Mother Nature cannot be fooled. -- R.P. Feynman
