This acquisition seems like it will massively reduce competition in the sector of video games journalism and as such I encourage everyone to report it to the Competition and Markets Authority, which you can do here: https://contact-the-cma.service.gov.uk/
While I concede that there may be some concerns that are valid for some people, this whole "stay away from this, that and the other" makes it seem like the FSF is starting to become a tin foil hat brigade that wants everyone to go off and live in a cabin in the woods growing their own food and never interacting with anybody because it might be dangerous.
- compartmentalization of files and folders, not having "excessively open" file and folder permissions that would prevent the less-educated, less tech-savvy, and less reliable employees from being able to do too much damage if they screw up How does this prevent ransomware?
The folder permissions thing helps limit the impact of ransomware because don't forget, it's only running as the user who opened it, so it only has as many permissions as they do. Sure, it could maybe use some exploit to get local administrator access on the desktop it's running on, but who gives a shit if a desktop gets encrypted? Just reimage it and move on. It's the files on the servers that need to be protected.
I do think it's an absolute crime though that anti-virus vendors sell anti-ransomware as an entirely separate (and expensive) product and don't include this functionality in their main programs. Sophos Intercept-X, I'm looking at you here.
Is there a list anywhere of specifically which versions of Adobe software are affected by this?
Cue: Hear about the constipated mathematician? He worked it out with a pencil.
Was it a #2 pencil?
With gcc 4.8.4 I'm getting: misc.h:71:41: error: storage size of 'ts' isn't known
Yep, this is one of the errors I am seeing also.
This is by Eric Raymond. C99 _is_ modern. Not to you, not to me, but to some people.
I managed to get past the C99 error by compiling compile.c manually and then bodging -std=c99 everywhere in the Makefile, but now I'm getting a bunch of errors about macro DATIME.
So yeah I'm guessing this thing needs a lot of work before people can actually run it on a current system.
I downloaded this to my Linux box and tried to run "make", but it complained about needing to be in C99 mode. Is this release only compatible with the original hardware and OS it was written on or something? I thought from the README it was supposed to be a port that works on modern computers/OSes?
What happened to the freedom of speech?
That (freedom of speech, ie. the 1st Amendment) only applies to the government.
Run Windows Update before you leave the office. I do. I never take my laptop anywhere new without making sure it is all up to date, just one of those things you have to do.
Installing updates right before a presentation sounds like a recipe for trouble. It's not unheard of for updates to break things.
"The geeks shall inherit the earth." -- Karl Lehenbauer
