Your theory seems to be based on the idea that Microsoft will cut off their revenue stream from you for no purpose other than buggery and to piss you off. Sorry but I just don't find this very convincing.
You are obviously new to to the world of commercial software. Most large software corporations exist solely for buggery and to piss you off. Or, at least, that is the impression they give the majority of their users.
PLEASE PLEASE PLEASE make.docx the default file format!
NO, NO, a thousand times no.
odt is a iso standard, documented well enough that it will still be readable on 50 years time. mandatory for government documents in many countries whose politicians are not controlled by MS.
docx is so badly documented it barely works now, and is not actually fit for purpose.
Introduce public hanging and flogging for even mentioning docx. It is even more urgent than stabbing systemd in the back with a stone axe.
Based on my observations of several tens of people diagnosed with this, I recon it is the medical term for "we know something is wrong, but we are not sure what", and the treatment is to give them a drug that prevents them from taking any decisions, on the grounds that it makes it less likely they will make a bad decision.
Why is it that people get so upset about something when the new option is more configurable than the previous options.
NO, You just don't get it at all why should adding more configurability fuck with the well established defaults which zillions of lines of code and millions of dumb users totally depend on to get things done?
This is something that is in the same league as casually kicking people in the shins for no reason, or spilling other people's drinks in a public bar, and you can't be surprised if it leads to a bar brawl - it is the conventional way to start one.
This is altering the system's behaviour, contrary to end user expectations, for no good reason
which should be considered a crime against humanity (well, against Unix philosophy, anyway), and punished by people using another distribution (but nuking from high orbit is fine in my books).
Radio4 news implied ad funded sites would have to do this too. They did point out that giving porn sites credit card details could lead to massive amounts of credit card fraud and blackmail.
The Honourable Minister for Extreme Stupidity said it was a price worth paying, despite the fact that Twitter etc would be exempt.
The whole point of this posting is that you should rewrite NetBSD in Rust. Without losing any portability. It is really quick and easy with such a modern and trendy language - you might even finish by next Thursday.
I expect it to work fine on a 6809.
Any failure will be punished by a lifetime PHP project.
Unfortunately, not everyone can play Premier League football or win Formula 1 races.
The real issue for most managers is "how to use the bunch of plonkers HR have hired" - its all very well saying "sack 'em and get some new plonkers" but the new plonkers will probably not be better than the old ones, and will have even less experience of your project.
Reality is a bitch
The issue is not how do you get good ones - that is easy - have a recruitment process that can tell the difference and pay more. Now, go on, just do that!
This also applies to teachers in schools and colleges (subject of griping in previous posts) - and politicians.
However, the sensible posts above all indicate that the best languages for some problems may not be the best for others.
For complex computation-intensive problems, Algol68 is the answer, and C is not. For low level hardware control C often IS the answer, and COBOL is not.
If you find a problem and Rust or Python is the answer, keep it to yourself. (And don't even mention Perl to anyone, ever).
Let me know if you find a problem for which Snobol is the best solution. Enquiring minds want to know.
On the subject of dialog boxes, my pet hate is boxes lie "Your system is totally fucked because of [OK]"
No, its NOT OK.
I once had a very nice piece of shareware where the dialog box said "Your system is totally fucked because of <insert total gobbledegook here> [Oh Shit]" - definitely better.
Ideally, there would be the option of getting a diagnostic dump to send to the developer or just aborting. Better still, developers could test their apps before shipping.
As for the idiot who shipped Ubuntu Mate 16.04 in a condition where you cannot access the CDROM drive with k3b or any other cd buring tool I could find, because it is no longer accessible as/dev/cdrom, and there is no documentation as to where it is - people like that should be removed from the OpenSource world - by force if necessary. I have moved to *BSD (ok systemd was part of the problem).
This looks like a CDC 163 - an early example of Seymour Cray's work, and nothing to do with IBM. Pre-1970 though. I would expect museums to be very interested.
The tapes are standard 1/2", probably recorded as 7 track at 556bpi NRZ, with the opposite parity to IBM - cos that is normal for CDC of that age. Probably readable by sprinkling iron oxide and counting the ridges or you could replace the electrolytics in the tape drives. SCSI compatible tape drives are available on Ebay..
Pretty sure there were Windows CE based smartphones as well that predate the iPhone.
Indeed there were - I had two!
They demonstrated all that has killed the Windows Phone today - and more!
The software looked good, and had the features expected of Windows of its day: There was never enough ROM or RAM, it kept locking up or rebooting itself or needing re-boots - which deinstalled all your apps!
And there were some extras, familiar to today's WinPhone users: It had few apps from third parties, and no bug fixes, ever. When the OS was upgraded, you were left behind. new OS versions could not be installed on the old phones.
What made the iPhone a massive hit was that the software had bug fixes, and updates - because Apple had the clout and good sense to fight the carriers.
If only Nokia had released regular bug fixes and software upgrades, and had ditched that appalling "SIgned for Symbian" that effectively blocked third party software, the world would be a better place. Who knows, perhaps Nokia would have been able to buy MS.
Eventually even the most hardcore socialists wake up, hopefully for the rest of us it's before they get to kill everyone else.
However, it may not be before the day of reckoning.
Meanwhile, various pillocks seem to thing that if one extreme is bad, the opposite is better. A plague on both your houses. Extremes are what is bad, and you American "Libertarians" fuckwits are no better than any other kind of extremist.
Considering that processor was likely made with the three micrometer lithographic process,
Not even close. It dates from before 1970. It was built with discrete components. I doubt it used printed circuit boards, but if it did, the process would have been closer to 3mm minimum feature size. The adder (as in hardware used to implement "add" assembler instruction) would have been a 15" square board, or more likely, a crate of 10 smaller wire-wrapped boards. The CPU would have been more than 4 off 42U racks. Compared to this, a CDC6600 (several years later) was a supercomputer. They were room sized (room - as in sports hall).
You are obviously new to to the world of commercial software. Most large software corporations exist solely for buggery and to piss you off. Or, at least, that is the impression they give the majority of their users.
NO, NO, a thousand times no.
odt is a iso standard, documented well enough that it will still be readable on 50 years time. mandatory for government documents in many countries whose politicians are not controlled by MS.
docx is so badly documented it barely works now, and is not actually fit for purpose.
Introduce public hanging and flogging for even mentioning docx. It is even more urgent than stabbing systemd in the back with a stone axe.
Based on my observations of several tens of people diagnosed with this, I recon it is the medical term for "we know something is wrong, but we are not sure what", and the treatment is to give them a drug that prevents them from taking any decisions, on the grounds that it makes it less likely they will make a bad decision.
On a scale of 1 to 5, how does it compare with a Zombie apocalypse?
NO, You just don't get it at all why should adding more configurability fuck with the well established defaults which zillions of lines of code and millions of dumb users totally depend on to get things done?
This is something that is in the same league as casually kicking people in the shins for no reason, or spilling other people's drinks in a public bar, and you can't be surprised if it leads to a bar brawl - it is the conventional way to start one.
which should be considered a crime against humanity (well, against Unix philosophy, anyway), and punished by people using another distribution (but nuking from high orbit is fine in my books).
Personally, I like the *BSDs.
I have never used CCleaner - and I have even deleted it from friends' machines - its advertising convinced me it was malware.
The Honourable Minister for Extreme Stupidity said it was a price worth paying, despite the fact that Twitter etc would be exempt.
Then I guarantee you will never get to be a tax advisor to a politician.
The whole point of this posting is that you should rewrite NetBSD in Rust. Without losing any portability. It is really quick and easy with such a modern and trendy language - you might even finish by next Thursday.
I expect it to work fine on a 6809.
Any failure will be punished by a lifetime PHP project.
Unfortunately, not everyone can play Premier League football or win Formula 1 races.
The real issue for most managers is "how to use the bunch of plonkers HR have hired" - its all very well saying "sack 'em and get some new plonkers" but the new plonkers will probably not be better than the old ones, and will have even less experience of your project.
Reality is a bitch
The issue is not how do you get good ones - that is easy - have a recruitment process that can tell the difference and pay more. Now, go on, just do that!
This also applies to teachers in schools and colleges (subject of griping in previous posts) - and politicians.
If you use Rust you don't need a security brain.
However, the sensible posts above all indicate that the best languages for some problems may not be the best for others.
For complex computation-intensive problems, Algol68 is the answer, and C is not. For low level hardware control C often IS the answer, and COBOL is not.
If you find a problem and Rust or Python is the answer, keep it to yourself. (And don't even mention Perl to anyone, ever).
Let me know if you find a problem for which Snobol is the best solution. Enquiring minds want to know.
No, its NOT OK.
I once had a very nice piece of shareware where the dialog box said "Your system is totally fucked because of <insert total gobbledegook here> [Oh Shit]" - definitely better.
Ideally, there would be the option of getting a diagnostic dump to send to the developer or just aborting. Better still, developers could test their apps before shipping.
As for the idiot who shipped Ubuntu Mate 16.04 in a condition where you cannot access the CDROM drive with k3b or any other cd buring tool I could find, because it is no longer accessible as /dev/cdrom, and there is no documentation as to where it is - people like that should be removed from the OpenSource world - by force if necessary. I have moved to *BSD (ok systemd was part of the problem).
The tapes are standard 1/2", probably recorded as 7 track at 556bpi NRZ, with the opposite parity to IBM - cos that is normal for CDC of that age. Probably readable by sprinkling iron oxide and counting the ridges or you could replace the electrolytics in the tape drives. SCSI compatible tape drives are available on Ebay..
Yes the do, but law enforcement takes no notice.
It won't make any difference to them.Correct.
If the transcript includes, "Mum, can you call me back on 07555 9998818", I think the cat is out of the bag.
Hold on, I think there are four norsemen with paperclips at my door ...
So you are brain dead.
Indeed there were - I had two! They demonstrated all that has killed the Windows Phone today - and more!
The software looked good, and had the features expected of Windows of its day: There was never enough ROM or RAM, it kept locking up or rebooting itself or needing re-boots - which deinstalled all your apps!
And there were some extras, familiar to today's WinPhone users: It had few apps from third parties, and no bug fixes, ever. When the OS was upgraded, you were left behind. new OS versions could not be installed on the old phones.
What made the iPhone a massive hit was that the software had bug fixes, and updates - because Apple had the clout and good sense to fight the carriers.
If only Nokia had released regular bug fixes and software upgrades, and had ditched that appalling "SIgned for Symbian" that effectively blocked third party software, the world would be a better place. Who knows, perhaps Nokia would have been able to buy MS.
Brings a whole new meaning to "Invasion of privacy"!
These are already not valid in Europe.
However, it may not be before the day of reckoning.
Meanwhile, various pillocks seem to thing that if one extreme is bad, the opposite is better. A plague on both your houses. Extremes are what is bad, and you American "Libertarians" fuckwits are no better than any other kind of extremist.
So "Windows compatible" then.
If you don't like crashes, Multics is not for you. (See my previous post).
Not even close. It dates from before 1970. It was built with discrete components. I doubt it used printed circuit boards, but if it did, the process would have been closer to 3mm minimum feature size. The adder (as in hardware used to implement "add" assembler instruction) would have been a 15" square board, or more likely, a crate of 10 smaller wire-wrapped boards. The CPU would have been more than 4 off 42U racks. Compared to this, a CDC6600 (several years later) was a supercomputer. They were room sized (room - as in sports hall).