To improve productivity in the office MS-Office is getting a new UI ... or well it's getting a new default font and some new colours anyway. No more yellow! How this will improve productivity or make people write or calculate or power-point better is probably unclear, it's probably not even the purpose. This seems like change for the sake of change.
Unfortunately they are making the default font a non-serif font again, but they are changing the name cause you can't have a font named "Beer Town" as the default font. Bring back Times New Roman!
https://www.theverge.com/2023/8/14/23831190/microsoft-office-new-default-theme-font-release-date
This discussion was created by Fnord666 (652) for logged-in users only, but now has been archived.
No new comments can be posted.
MS Updating the Office UI (Again)
|
Log In/Create an Account
| Top
| 35 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
(1)
(1)
(Score: 5, Insightful) by Anonymous Coward on Thursday August 17 2023, @06:13PM (18 children)
Starting with Windows 3.1 and versions of Office after Office 97(?) the mantra has stayed the same,
"Reduce your productivity with Windows."
ps: Office 97 works better than ever, really fast on current hardware! Bonus is that it never calls home.
(Score: 5, Insightful) by canopic jug on Thursday August 17 2023, @06:21PM (16 children)
Indeed.
There are additional questions raised by this move which went unanswered in The Verge's article. Without any additional data to the contrary, I would have to guess that the UI changes are to burn staff time around the world on re-training so as to preempt spending that might have gone to re-training on Calligra or LibreOffice. Similarly, what about the patents and copyrights on the new type faces? Especially the latter, copyrights, can be used as an effective weapon to ensure that documents afflicted by m$ Office will fail to render correctly because the fonts will be unavailable to competitors. Lastly, given the long history of tweaking its proprietary file formats to impair compatibility, one has to ask what changes have been made to its proprietary format? Don't give me any BS about their false claims to supporting ODF, they don't. It's partial support and they go out of their way to ensure that their software deletes the parts it does not understand rather than just passing over them and leaving them unchanged.
Money is not free speech. Elections should not be auctions.
(Score: 2, Interesting) by Anonymous Coward on Thursday August 17 2023, @06:45PM
> ... new type faces
Good point. I may have to edumacate people in my project group that get this new UI to switch back to old standard fonts for engineering documents (like Times & Arial). They work at big companies where IT forces these new versions... but I have a tiny independent company, and won't be using this new version.
(Score: 5, Interesting) by JoeMerchant on Thursday August 17 2023, @09:41PM (8 children)
>burn staff time around the world on re-training so as to preempt spending that might have gone to re-training on Calligra or LibreOffice.
I find this to be a universal aim of Microsoft products: engage the users in mindless time wasting activity. Users so-employed end the day more refreshed and happier with their work experience than workers who are more productive and have to actually think about problems more difficult than how to use the tools. Lower per-employee productivity = more employees per company = more seat licenses = more profit for Microsoft. More through observation than deduction: it also creates a workforce resistant to change, all the better to lock-in Microsoft contracts.
Personally, I prefer to use the more productive tools, get more done in less time, and f-the-hell off when the work is done, regardless of what the wall clock says. Over the years, it generally has taken me about a year to code up a Qt interfaced device - one man year. Our .NET based UI development team of about 4.5 programmers took roughly 6 years to develop the first iteration of our current product, 27 man-years for a facelift of an existing product. However, retraining 3 of those UI developers from .NET to Qt would have been nearly impossible... tough call...
🌻🌻 [google.com]
(Score: 5, Interesting) by canopic jug on Friday August 18 2023, @03:50AM (1 child)
However, retraining 3 of those UI developers from .NET to Qt would have been nearly impossible... tough call...
The mindset required to play all day, every day with M$ products for six years in a row without producing a result is the polar opposite of what you'd need in a productive programming team.
For the m$ products, a tolerance for illogical operation as well as an aptitude for rote memorization. Then there is the lack of accurate documentation, thus resulting in an oral tradition where the work-arounds are spread by word ... but only to those who demonstrate full loyalty to m$.
For working software in contrast you require logical thought processes and work flows plus an aptitude for analysis and planning. Then there is the need to be able to read well and know how to learn by reading the extensive pool of written documentation out there which is mostly good but of varying quality.
Simply put, you cannot re-tool Microsofters to learn proper computing. M$ is a staffing problem, not a technical problem. The only way forward is through a mountain of pink slips for the Microsofters and use the saved money to hire a few skilled staff to replace them. The challenge there is getting the data out of the legacy systems. While the EU and maybe some other zones consider the exit costs as part of the Total Cost of Ownership for a product or technology, m$ considers it an externality and an unsupported one at that.
Money is not free speech. Elections should not be auctions.
(Score: 3, Interesting) by JoeMerchant on Friday August 18 2023, @02:47PM
To be fair, those one-man-year projects were for small companies with minimal regulatory compliance anxiety, English only interfaces, etc. I would have needed some "team" to help with the added burdens happening here in the bigger, more conservatively managed company.
As things are, I work on the back end - making things happen that the GUI team can just put a button on and they don't have to worry about the mechanics. I do it in Qt over Linux, and I actually code up my own GUI in Qt as an example for the "User Facing" GUI team to try out and reassure themselves that: yes, the problem really is in our .NET code, we see it working in the back end interfaces. I let them screw around with globalization, usability studies, font sizes, color schemes, branding meetings, feature selection scheduling meetings, etc. and... in some ways the M$ environment may be a tiny bit better at those things - not enough to make up for all the crap I see them sitting and spinning on for months at a time, but the arguments over which one is better certainly are counter-productive.
As for "hiring for the right mindset" - that "I must be optimally productive" mindset tends to go insane in this environment. A colleague started here out of college (I didn't get to "the big leagues" until after 23 years in startups) - they had been in the big company for 15 or so years, decided to see what it was like on the other side, took a promising job with a promising company - did lots of interesting stuff, but after 5 different employers in 6 years they're back in their old desk, picking up their project that they set down 6 years ago and slowly pushing it through the development pipeline again. I think he's learned to adjust his mindset to be more compatible with the stable employer, I know I have in the 10+ years I've been here. A senior engineer took the early retirement offering last year and in his exit party speech he talked a lot about what it takes to work successfully in "the big company environment" for 30+ years, and it has a lot to do with accepting the process, accepting that you could do more better faster and more efficiently, but the company as a whole just can't, and the company as a whole (for reasons good and bad in the big picture) is very much more successful in the business of making money and paying employees than the startups that are less than 0.1% of its size. By the way, in the big company, the I in team is in the A-hole: https://careerpunk.com/team-player/ [careerpunk.com]
For working software in the big company environment, you need documented requirements. You need a product development process that management understands and respects which allows the time to get those requirements sufficiently detailed that the test team can write effective test cases for them to execute and ensure that the software does what it should. My second project in the big company was an OS port from an older Debian Etch to Ubuntu 14.04 - and while we're at it let's shove the system into new hardware with a new video capture card and port the GL rendering code from an NVidia card to Intel embedded graphics. I was entirely unfamiliar with the product, as was my newly hired from school tester, but with the documented test cases and requirements, test found all the problems in the port, I fixed them, and we delivered the ported software on-schedule. My manager also had me hire a consultant to help with the GL code issues since it was outside my experience, that was a near total waste of time, compounded by the ask to keep him employed through the contract term doing "something useful." You need requirements, process, etc. as a division in the big company, we are still "maturing our process" to get there, as evidenced by software that gets released 100% tested and still has significant bugs found in the field. For all that idealistic speaking, I actually had a very PC people manager / software developer say in a Zoom call last week: "software test is where people who can't develop software end up working." And, culturally, that is actually a good fit: you want your software to be easily used by people who aren't as technically inclined as the people who write it.
>you cannot re-tool Microsofters to learn proper computing
No, but the are a valuable part of reliably profitable enterprises. It's not an ideal world, far from it, you could get more than twice as much done in less than half the time if you just let the competent people do the difficult work, but a big organization doesn't thrive on only hiring the best of the best. Whether by government incentive, or the natural reality that the best people are rarely available to hire in large numbers, the big companies run best when they can be adequately staffed by average (or below average)_employees and still make profits.
>a mountain of pink slips for the Microsofters and use the saved money to hire a few skilled staff to replace them.
Make me king of the world, give me 100 years of dementia-free life in which to reshape things as they are into things as they should be, ensure my decrees are followed without question at the highest levels and that my security from assassination is assured. I could certainly fix it all, and getting people into the best jobs for themselves would be a part of that. Pink slips for the Microsofters would probably be at least 30 years into the 100, there's an incredible inertia in the human capital infrastructure as-built, it would be a better world after we got there, but... I don't think we've got any cohesive world leadership that will carry us in any one direction for 20 years, much less 100.
🌻🌻 [google.com]
(Score: 3, Informative) by stormreaver on Friday August 18 2023, @02:46PM (5 children)
And it would have been a bad decision since the Qt API is broken frequently. I wrote, among many other Qt programs, a Qt 3-based database schema designer and code generator back around 2004 or so when Qt 3 was the current official version. I worked on it in my spare time for a couple years, and it was really useful to me (and it still is).
At around that time, former Qt developers who had written a bunch of stuff in Qt 2.x posted about how they dropped Qt because none of their 2.x projects could be built with Qt 3.x since Trolltech had intentionally broken source code compatibility when creating Qt 3. Since I got started with Qt 3, and never used Qt 2.x, I disregarded their complaints and continue on my merry 3.x way.
Then Qt 4 was released, and none of my Qt 3 programs would build. The compatibility libraries didn't work on any of my projects either, so I decided it was time to port my most useful project (the aforementioned schema designer and code generator) to Qt 4. It was the only one of my programs that I absolutely couldn't live without, for both personal and professional reasons. It took a full year to port that one program in my spare time, and I hated every minute of it.
After I finished the porting, I decided that I was done with Qt. I had previously done a lot of Java programming, but I had moved to Qt because the Java GUI and printing systems were absurdly bad. It was then that I had researched changes in Java and found that Project Mustang had made all parts of Java MUCH faster and much more flexible. As a result, I decided to return to Java.
All of the Java programs I had ever written still ran, and I was still able to maintain the code without having to modify a single line. The only work I had to do was to create Netbeans projects out of my command-line projects of the past (everything I did in Java before moving to Qt was command line based), but that was trivial.
I just realized that I have no first-hand knowledge of the C# (or other Dot Net-based languages) API stability over time, so my entire posting revolves around the assumptions that the API's don't break backwards compatibility, but feel free to correct me if that assumption is wrong.
(Score: 3, Informative) by JoeMerchant on Friday August 18 2023, @03:05PM (4 children)
Oh, yeah, it's far from ideal - I was witness to that pain on the blogs and boards when I started with Qt 4 in 2006. The 4 run was pretty good, 5 didn't start to detract from it until about 2013, and the transition 4-5 was relatively painless. I'm still in 5 today, the transition to 5-6 looks even smoother than the transition 4-5, but I've got no incentive to give up 5 yet.
I think it depends on what parts of Qt you are using... the Qt multimedia experience has been crap from 2006 onward, everything is broken all the time - OS updates? Qt media interface breaks again.
I don't know what you have been doing in Java, but Java has been a worse than a festering hemorrhoid any time I have been forced to use it. There are certainly areas where Java and javascript are "the thing" for the application, but seemingly never anywhere I end up working with them, quite the opposite. Other than multimedia, all my old Qt code still runs today - porting the 4 code to 5 is usually a 5 minute exercise or less. The widgets GUI and Creator widget layout tool are less than perfect, but better than anything else I have ever used. The "QtQuick" javascript based ui has never worked well enough for me to do anything in it... so, yeah, like all things: a mixed bag. I stick with Qt Widgets and the API regions that work for me, bring in outside libraries otherwise, and it's all semi-instinctive, especially after 17 years of experience.
I've never been deep into .NET or C# - I did write a C# code generator in Qt for a while... it was pretty stable for what I was doing there, but I was far from doing anything fancy. My experience with M$ development was in the 1990s, starting January 1991. In those days they would release a new DOS every year or less that was "99% compatible" with the previous version, which meant that in a 10,000 LOC application, you'd end up rewriting 100 lines, after you figured out which 100 lines broke, which for us was usually the RS-232 interface - you know: the core of our product functionality. That continued into Windows 95 development until I finally bought a serial interface library that seemed financially stable enough that they would be around for more than a year or two and when M$ broke their interfaces again we just got an update from our library vendor. For Windows 95 development, the Borland objects API was tremendously more productive than the win32api or whatever M$ called it at the time. My impression of .NET today on the outside looking in is that they have a typical 5-7 year cadence at which they release "new improved" things that promise to be better, but are really more of the same 99% compatible with the previous generation.
Also back in 2006, I made the decision to go with Qt/C++ over Carbon-Cocoa/Objective C since: A) our product was being developed for deployment on Mac Pro hardware, and B) hiring anyone with Objective C experience required a nationwide search, flying the candidates in to our University (with a huge software engineering department) town, etc. and we were just too small to screw with all that. Also: by 2007 the Mac Pro hardware was (all too predictably) thrown under the bus by the investors and we ended up porting 3 man-years of code development from iOS deployment to Windows/PC deployment in less than a day - how would that have looked in Objective C?
🌻🌻 [google.com]
(Score: 2) by stormreaver on Saturday August 19 2023, @10:13PM (3 children)
I'm usually puzzled by statements like this, but only until I realize that people making these statements are using it for website development using application servers like Tomcat or JBoss. That is, indeed, worse than a festering hemorrhoid.
I use Java for desktop apps, where it's a real pleasure to use. My only real complaint is that its memory usage model is still stuck in the rut it dug for itself when its primary use for for browser applets.
(Score: 2) by JoeMerchant on Sunday August 20 2023, @01:17AM (2 children)
One unpleasant Java project involved dusting off an old Java DICOM file handler that no longer worked as an in browser app in the updated Slackware/Chrome release because basically everything it did had been labeled a security hole and disabled. Getting all that functional in the new release took several days.
Then we had the corporate mandate to use a particular Java tool to generate a SBOM for security audit purposes, and of course this was just a few months after a huge Java security bruhaha over some particular package that this particular SBOM tool required, so my SBOM generation script would first install Java and the required packages, run the SBOM tool, archive the report, then immediately scrub all traces of Java and Java packages from the system so we can add a note to the report stating that the audit failing packages were only installed long enough to use the required tool to generate the required report in the required format.
Other memories are vague, mostly around different apps only running in particular releases of the Java engine, having to update for some, roll back for others.
Then we get back to 2001/2; when our idiot CEO suggested recoding our (compute bound, already slower than ideal) C++ product in Java for the portability. Luckily, his Scotch soaked brain wouldn't hold an idea like that for more than a few hours. Sadly, he would forget having previously proposed the idea and the infeasiblity of the proposal, so I had to explain it at least four times over the span of 18 months.
🌻🌻 [google.com]
(Score: 2) by stormreaver on Sunday August 20 2023, @02:47PM (1 child)
Most of those have little to nothing to do with Java (except for the browser issue, which is what I anticipate when most people complain about Java), as they could have equally applied to anything else. I've seen my C# coworkers deal with some doozies, and I've had major headaches with C++ projects adapting to new releases.
Java certainly has limitations (though Minecraft is a great example of someone accomplishing something I would not have thought possible with Java), but it fits right in with all the desktop productivity programs I write.
(Score: 2) by JoeMerchant on Sunday August 20 2023, @03:17PM
About the security issue: in 17 years of using Qt I have never had a "mandatory patch to address security issues" come up. They may exist, they just never impacted me, and if they did the patch would likely apply as a .x release update which have gone 99.9% seamlessly for me in the literally thousands of times I have applied them.
Now, if the security problem is in your Qt 3.x and you want to patch it today with 5 or 6.x, yeah, that's gonna hurt.
As for using a browser as a cross platform OS, I think that works brilliantly when you have a server serving HTML, CSS, and similar with the work being done on the server, that works brilliantly in my experience. Things that push the heavy lifting from the server to the browser all look like hamster wheel exercises to me: constant recoding to stay compatible with browser updates. Almost as bad as coding for Android/iOS.
🌻🌻 [google.com]
(Score: 3, Interesting) by psa on Friday August 18 2023, @06:02AM (1 child)
We managed to get markdown set up as a standard document format at our very large company. So now we have lots of people writing bad markdown in MS Word, saving it to their OneDrive, emailing the documents with Outlook on M365, and uploading them to Sharepoint. Microsoft is crying all the way to the bank.
Next, we're going to tackle the diagramming standard, since Visio support keeps getting more expensive and less cross-platform. The leading candidate? PowerPoint.
Sometimes you can't win for losing. There's an inertia here that boggles the mind, and it seems to have the whole world in its grip. I would guess that the new Microsoft office branding will have more impact on their free money streams than any technical capabilities.
(Score: 2) by JoeMerchant on Friday August 18 2023, @11:45PM
trac with the graphviz plugin still works for me although I am making more drawings in Krita with my 22" touchscreen these days, and embedding them in the unavoidable M$ DevOps wiki documents.
🌻🌻 [google.com]
(Score: 5, Insightful) by driverless on Friday August 18 2023, @07:18AM (2 children)
Yup. The term "UI refresh" is business-speak for "we've absolutely totally run out of ideas for what to do next, there's simply nothing we can think of any more", the equivalent of a change of command inventory in the military: We've got a pile of guys standing round doing nothing, what's something that will keep them pointlessly occupied for about the next month?
If you're familiar with Jimmy Reeves, imagine that being explained with a side order of "Jason, Jason, Jason...".
(Score: 4, Funny) by kazzie on Saturday August 19 2023, @06:32AM
Or JSON, JSON, JSON...?
(Score: 4, Informative) by driverless on Saturday August 19 2023, @07:11AM
Argh, typo'd it, I was referring to Jimmy Rees [youtube.com], Australian comedian.
(Score: 3, Informative) by Anonymous Coward on Friday August 18 2023, @10:38AM
I think one reason is because the patent on Calibri is expiring soon. So they need to use a new one.
https://en.wikipedia.org/wiki/Intellectual_property_protection_of_typefaces#United_States [wikipedia.org]
https://en.wikipedia.org/wiki/Calibri [wikipedia.org]
Date released = 2007.
2007+15 = 2022.
The other reason could be many people in MS need to show that they are doing something. Just holding the wheel steady and fixing bugs isn't good enough.
(Score: 5, Insightful) by Anonymous Coward on Thursday August 17 2023, @08:44PM
You should really consider trying OpenOffice, LibreOffice, StarOffice, OnlyOffice, Calligra Suite, Collabra Office, NeoOffice, or Open365.
They run pretty well when you ditch antiquated versions of Windows for a modern operating system.
As a bonus, they all have dumb confusing overlapping names that all sorta meld together like Microsoft 365, Exchange 348, Office 360, System Center, but without the E1, E3, E6 bullshit.
Even better, if you file bug reports against any of them, you'll basically get the same response that you do from Microsoft. Crickets, or a promise that it'll eventually maybe be fixed some day.
(Score: 5, Insightful) by SomeGuy on Thursday August 17 2023, @06:35PM (5 children)
MS-Office has almost turned in to an exhibit for bad UI design. Yet, web crap still finds ways to be worse.
Color. Really? Windowing, toolbar, dialog elements, etc. are supposed to follow the Windows color settings. But no, lets hard code colors like it is Windows 3.1 all over again.
Font? Again, fonts are supposed to generally use the Windows fonts, but, no, too boring. I'm still pissed at Microsoft for overriding the standard MS Sanserif with Tahoma. I still have a renamed version of the font as "MS Sans surfh" to override their overriding.
And don't even get me started on that awful ribbon shit. Bring back standard menus. At least ribbons have slowly been evolving back in to something that vaguely resembles drop down menus.
Are they going to bury the non-subscription version of Office even further? It's not really even standalone any more since it requires a remote Microsoft Account. Both are just retarded ridiculous. Why would anyone want to RENT a word processor! jut to type a letter? Why let it phone home every time you type a shopping list? Why let it save your document to their mainframe (mean cloudz storage!)? That is what the entire personal computing revolution was about, getting away from the control of big companies and big iron.
I hate this planet.
(Score: 3, Informative) by Samantha Wright on Thursday August 17 2023, @07:08PM (3 children)
RTFA. They're just replacing the default accent colors for use in documents. The UI is not changing at all. This submission is hot garbage.
(Score: 2) by Freeman on Thursday August 17 2023, @07:24PM (2 children)
https://www.theverge.com/2023/8/14/23831190/microsoft-office-new-default-theme-font-release-date [theverge.com]
According to the article, they're changing the default font as well. Though, that's hardly much of a "UI" change. Changing default color palette, not exactly earth shattering either. Changing style, could be, but again probably not in this case. Sounds like someone wanted to do stuff, so here's some stuff. Just don't take away my dark mode settings. I would not be happy with that.
Joshua 1:9 "Be strong and of a good courage; be not afraid, neither be thou dismayed: for the Lord thy God is with thee"
(Score: 3, Informative) by Samantha Wright on Thursday August 17 2023, @07:46PM (1 child)
The font in question is replacing Calibri as the default for documents, and has been in the works for years. It looks more like Helvetica [theverge.com] and less like a bad joke. The interface will not be affected by this change. So, again, horrifyingly misleading headline.
(Score: 5, Interesting) by JoeMerchant on Thursday August 17 2023, @09:44PM
Agreed, however - the change is probably more impactful than a UI change: all the documents produced with the default themes are going to be impacted from the update forward. Templates will break, tempers will rise, and things will look "different" when produced by workers who haven't updated. Yes, you can override all these defaults, but only if you know how...
🌻🌻 [google.com]
(Score: 3, Informative) by driverless on Friday August 18 2023, @07:21AM
And that's saying something when you've got Google with their trifecta of interfaces that work like nothing anyone is used to, mystery-meat navigation everywhere, and a UI that changes randomly twice a week.
(Score: 3, Insightful) by Opportunist on Thursday August 17 2023, @07:38PM (2 children)
How do you turn it off?
(Score: 2) by Freeman on Thursday August 17 2023, @07:56PM
In this case, it just seems like all you need to do is choose your own theme and default font. Since that's about the extent of the "UI changes" they made.
Personally, I use dark mode.
Joshua 1:9 "Be strong and of a good courage; be not afraid, neither be thou dismayed: for the Lord thy God is with thee"
(Score: 5, Touché) by turgid on Thursday August 17 2023, @08:08PM
Install LibreOffice?
I refuse to engage in a battle of wits with an unarmed opponent [wikipedia.org].
(Score: 5, Touché) by turgid on Thursday August 17 2023, @08:01PM (1 child)
Innovation is what we have come to expect from commercial software. We pay willingly for these ingenious enhancements that can only be conceived and implemented by highly-educated and highly-paid professionals.
Take that, GNU/Hippies.
I refuse to engage in a battle of wits with an unarmed opponent [wikipedia.org].
(Score: 0) by Anonymous Coward on Friday August 18 2023, @08:27PM
Until the MBA/Investors leverage it into an extortion scheme.
Stepping in a "proprietary blob" is often quite time and resource consuming to remove it.
(Score: 2) by bart9h on Thursday August 17 2023, @08:43PM (1 child)
It was at version 2.0.
No, seriously.
(Score: 3, Insightful) by JoeMerchant on Thursday August 17 2023, @09:46PM
Before the internet we used Ami Pro by Lotus. It was twice as productive and polished as whatever garbage M$ was peddling at the time.
Then somebody e-mailed us a document, and our little utopian garden of productivity was overgrown by the corpse flower that was the M$ word processor du-jour.
🌻🌻 [google.com]
(Score: 2, Insightful) by Anonymous Coward on Thursday August 17 2023, @11:34PM
Force your customers into another round of upgrade, lest you cannot work with the latest people who buy our product legally.
We are a business, we have shaken hands with Congressmen, who have already passed Copyright Law to keep the new people from simply running off copies of code that works with the existing username.
So now, we can change stuff everytime we want a new round of sales or force everyone into our subscription models. And they can't do a thing about it but pay what we ask.
How much perfectly good stuff goes into the trash just because of incompatibility with a protocol change? Of course we can compensate for this inefficiency by having our legislator friends outlaw their cars.
Some people call a relentless chasing of their tail to be progress. To me, it's just another way to keep people in debt. What they have this year won't be good enough next year.
Keep up with the Joneses!
Nobody's gonna hear your anguish over paying bills for yesterday's handshakes. You took advice from a Marketing Bullshit Asshole and now you will pay the price for your gullibility. Poverty.
You will have new crap and a miserable life if you keep buying into their paradigm that you have to keep up with them.
They can cheat, lie, steal, and avoid accountability. You can't.
(Score: 2) by DannyB on Friday August 18 2023, @02:40PM
Someone must have patented using the color yellow in office suite software.
Apple? Did you do this?
When trying to solve a problem don't ask who suffers from the problem, ask who profits from the problem.
(Score: 4, Funny) by DannyB on Friday August 18 2023, @02:45PM
PowerPoint was originally developed as a less expensive way to euthanize cattle. After a number of successful lawsuits by the ASPCA, the practice was declared inhumane and had to be ended immediately.
Looking for a new market, Microsoft discovered that Power Point could be used for corporate presentations. This is why corporate meeting rooms always have the doors locked from the outside. It is a weeding out process. Those who survive the presentation are able to continue their corporate work and get promoted into management.
If these ribbon changes to office will also affect PowerPoint, will this finally cross the line into
cruel and unusual punishmentenhanced interrogation techniques? Even worse than being forced to listen to Justin Bieber music? Are the font changes just to make the suffering worse?When trying to solve a problem don't ask who suffers from the problem, ask who profits from the problem.