1. It causes windows to restart itself rather than restarting the computer (so no power up self test)
2. It causes windows NOT to run things in the startup folder.
265 publicly visible posts • joined 7 Mar 2013
I remember at Cambridge (UK) undergraduates had allocated online 'tokens'. The charging rate went up at busy times of day. We very soon learnt that attempting to compile an algol68 program at lunchtime burnt out your online tokens in about 15 minutes. As a result we did most of our online work after tea before disappearing to the college bars (which at that time closed when they felt like it rather than the closing time enforced in pubs. and of course the college bars were somewhat cheaper).
People have been the problem since for ever. The Roman emperors found out that bread and circuses kept the masses happy and they (or at least the ruling classes) could do more or less what they wanted. That hasn't changed much in the last 2000 years. The bread is now fast food and cheap booze and the circuses are provided by the media/social media.
It's the "You must open an account in order to pay for something" bit that really annoys me. I'm AT the place I'm purchasing from, you do NOT need my email or my home address in order to make a delivery because I'm right here. Why should I need to open an account?
I can't help feeling that a class called SoapHttpClientProtocol accepting anything a target that explicitly says not to use Http or Https is a bad idea. Writing to a file is not using http.
So yeah, I sort of agree with the researchers on this one - it should either error or ignore the protocol part - preferably the 1st.
unfortunately "localhost" is just a hostname that by convention maps to 127.0.0.1 - if you happen to edit /etc/hosts and put a different value for localhost in there, you'll get strange behaviour on your system. Especially if there is no server at the target.
It's be interesting to know if they broke 127.0.0.1 or just (I use the word loosely) localhost.
banks make money from the paltry sums in your current account as well. not to mention the time it takes for money to transfer between account. it mysteriously takes 3 days for cheques to clear, during which time the banks are making money - according to a lecture I went to from the BACS people the underlying systems can do the clearing overnight
Even Stroustroup makes mistakes. His reason for not having exceptions checked at compile time was that
float mysqrt(int a) { return sqrt(a < 0 ? -a : a); }
would never throw an exception but the compiler would insist it could and might refuse to compile code that used it and didn't state they might throw the appropriate exception.
mysqrt(MININT) anyone?
Also, to be frank, that's such an exceptional case I'd rather put the try/catch in myself.
Pretty sure that cont pointers and const refs are pretty close to viral annotations - const correctness is a PITA if some low level thing guarantees not to mutate something it is passed in the documentation but not in the API. Especially those things that have APIs where the mutating and non mutating version of the code are differentiated only by a passed flag.
Although the authors are careful to say "it's not necessarily discrimination", it does seem to be a particularly pernicious form of discrimination - using a particular AI says nothing whatsoever about the candidate and their ability to learn different techniques. we appear to be moving from ageism to AI-ism
So in my first job, I was put onto doing the programming for a completely programmable video display - so programmable you had to have a program loaded into its rom for it to do anything. And one of the things they did was decided to have a removable keyboard.
Obviously a terminal without a keyboard is going to be hard to enter data on. So, I made the code able to detect various conditions including keyboard being removed/added. On removal it flashed up on the top line "give my keyboard back, you thieving basket" and then replaced that message with "thank you" when a keyboard was detected, which message went away after a short while.
This was apparently so impressive it got demonstrated to customers as a feature of our system. and it was several years before someone complained about the content of the message!
i use it for most of my day to day stuff at home. seems to render the majority of page fine. It even goes as far as letting me write these posts.
"using the last truly FOSS cross-platform web browser standing" nowhere says 'which uses multiprocessors in such and such a way and provides sandboxing of pages'. So.
Huh? If m/s have decided it's a good time for bad UI to die, why aren't we going back to the windows 7 UI? Because that was so much better than windows 10/11.
What this article means is microsoft have decided everything should look like a dull and lifeless web page and to kill of usual visual prompts, but aren't actually dealing with what needs to be dealt with - such as storing user settings outside of the registry so that when you update your machine, reinstall your favourite gam-err-software and restore everything from backup, you don't have to go through various voodoo rituals to get things working again.
And it's not like settings actually makes it easier to find anything. Because it doesn't.
I'm not sure what the author of the article is drinking, But it should probably be prescription only.
Urgh. The registry is evil. It stops you being able to back up your settings and restore them on a new machine. I can understand this for *some* bits of the system, but every damn application uses this for all of their settings, the vast majority of which have no relationship to what the machine you're running on is.