Slashdot Mirror
Apple To Review Software Practices After Patching Serious Mac Bug (reuters.com)
Apple said on Wednesday it would review its software development process after scrambling to patch a serious bug it learned of on Tuesday in its macOS operating system for desktop and laptop computers. From a report: "We greatly regret this error and we apologize to all Mac users, both for releasing with this vulnerability and for the concern it has caused," Apple said in a statement. "Our customers deserve better. We are auditing our development processes to help prevent this from happening again."
Was it an H1-B developer or something that was sent to India?
Apple should start giving a shit about something besides hardware for but a moment. Their software quality has been in the gutter the past two years. Which then means their expensive hardware isnâ(TM)t even worth toilet paper because itâ(TM)s not usable.
I hate android but iOS has been such a hot pile of shit lately Iâ(TM)m gonna try one out again.
Those responsible have been sacked.
They say Macs never get viruses or get hacked. Now you know how Windows users feel. Linux and BSD users are next.
Iâ(TM)d guess itâ(TM)s the other way around, some MBA holding cunt says âoethese processes arenâ(TM)t efficient, agile, synergy, buzzwords! Now letâ(TM)s institutionally chastise anyone who disagrees.â
People then leave who used to hold it down because they know through experience this prickâ(TM)s suggestions are crap.
I just can't believe them any more, they keep shipping crap software and crap hardware.
over it.
I canâ(TM)t reâ(TM)d this crâ(TM)p.
Not a Mac fan, but this is the most honest, respectable response to a mistake I've seen from a corporation in a long time.
Props, Apple.
A government is a body of people notably ungoverned - AC
I translated it as this was a known issue to the underlings, however it never was allowed to be addressed by the middle managers or this problem was a very to spot problem (probably some debug code that didn't get removed) that was allowed to get released.
However compared to other companies, at least Apple is publicly admitting the problem. While some companies may patch the problem, but not state any details about it.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
You're releasing it wrong.
That's what I call courage
And just yesterday I was reading posts by Mac fanboys claiming the latest bug was not that serious. Given Apple's announcement, the fanboys' heads must be exploding because either the bug was serious and they were wrong about that, or else the bug was not serious and Mac is overreacting (which means they don't know what they're doing anyway).
I think this is a much broader problem. This isn't just about Apple. This is about almost all software today that has been developed by Millennial (some people use the term "Hipster") developers.
Millennials have been in the industry for about 10 years now, and these past 10 years have been some of the worst in terms of software quality.
Just look at the destruction they've left behind them. Windows 8, 8.1 and 10. GNOME 3. Firefox 4 and later. Systemd. Wayland. Slashdot Beta. NoSQL. The list goes on and on.
The Gedit text editor is an excellent example of how formerly-usable software has been destroyed. This is what Gedit used to look like. At that point it had a sane, easy-to-use, functional UI. This is what Gedit has become. It's like 50+ years of accumulated experience and knowledge has been discarded for no good reason, and the end result is a disaster.
What we have is a generation of software devs who are far too focused on aesthetics and trendiness, with little to no care put toward usability, security, and reliability. They go out of their way to ignore everything we've learned about doing things right. They do things their own way, and it's a disaster.
This isn't even a get-off-my-lawn situation. Many of us who are appalled by these developments are late Gen X'ers. We aren't even that much older than the Millennials who have caused so many problems! In fact, many of us spend our days trying to bring some sanity to otherwise disastrous workplaces. We remember how software used to be developed, yet we're so outnumbered by Millennials that we just can't keep up.
It was excusable when security flaws and usability problems were accidentally introduced by earlier generations because they were doing pioneering work, and the concepts behind these security flaws and usability problems hadn't even been discovered yet. But the industry should be far beyond that now. The knowledge is there, it's just that Millennials choose to totally ignore it.
This was posted as recently as November 13, as a "solution" to an issue of not having an administrative account: https://forums.developer.apple...
TL;DR
The last generation of programmers are too focused on the shiny.
#DeleteFacebook
All bugs are also features. Depends on what you want them for.
Seems like something Slashdot needs to fix in their rendering. No other website I use on iOS has this problem.
Open v closed source is a trade-off.
That open source is always more secure is a fallacy. Open source on small projects can be a terrible idea: it gives attackers the source code.
HOWEVER, for big projects, and especially one of the biggest in the world (Apple operating systems), open source tends to strongly outweigh closed source. Tim Cook, it is time to open the source code.
Yes, yes, DOS and Windows 95 were the glorious days of security. The Blackberry was unhackable and IE 6 was teh gratest web browber ever!! Napster still lives on in my heart.
There's all kinds of cosmetic and usability bugs floating around, and Apple doesn't seem to be in a hurry to fix them. They're the kind of bugs that aren't showstoppers but are still very annoying or can result in bad data.
The Calculator bug in iOS is one example of a recent bug that can produce bad data and wasn't fixed. Until iOS 11.2 (which isn't out yet!) even though it was reported way back in 11.0 beta, before the OS was released to the public.
Another recent issue, though less important, is that the Weather widget will randomly stop updating, so you'll be seeing last night's weather instead of right now. This bug was also reported several versions ago and is as of yet unfixed in the latest 11.2 beta.
I know bugs happen; nobody is perfect. But these are obvious, reproducible bugs that are not being fixed after being reported months prior. What the hell, Apple?
The bar is pretty low.
You bet they are "taking it seriously", in different words.
Words sound nice.
That's a really bad summary. Yes, part of the problem is that Hipsters care too much about looks. But you ignored the other serious problems that the GP mentioned:
1) Hipsters go out of their way to be ignorant. They don't want to learn about security, so we get atrocious security flaws in the software they write. They don't want to learn SQL, so we get atrocious NoSQL databases to deal with. They don't want to learn about how their users use software, so we get awful UIs. They don't want to learn C++, so we get a terrible language like Rust.
2) There are too many Hipsters. No matter how much effort responsible programmers put in trying to fix the many problems created by Hipsters, these responsible programmers will always fall behind just because the Hipsters crank out so much crap at such a fast pace. It's like riots and looting, where a relatively small number of police officers and store owners are absolutely overwhelmed by a much larger crowd of thugs.
I'd like to add another problem:
3) Too few people are willing to identify the real problem: Hipsters. The blame is placed on companies or entire open source projects, for example, rather than the Hipsters who are responsible for the problems. It really doesn't help that the Hipsters have adopted Codes of Conduct into their projects that they then use against anyone who dares point out the problems they've caused. That's why Rust has turned into the mess that it is, for example. Criticism and pointing out of flaws is strictly forbidden within Hipster-dominated software projects.
hey it's your logic at work
...but this is hardly news. Developers know how much the app dev and review process is has become degraded over the past few years.
True enterprise level bugs, only from Apple
Give 'em a break, they've only been developing software for 40 years
I don't know the meaning of the word 'don't' - J
Did you even read the GP comment? It covers that very clearly:
When you're doing cutting edge work, you'll make cutting edge mistakes.
DOS was the first OS that saw huge mainstream adoption. Of course this situation would bring up unanticipated problems.
Windows 95 was the first OS that saw huge mainstream adoption during the era of mainstream Internet usage. Of course this situation would bring up unanticipated problems.
BB devices were the first to see huge mainstream adoption at the earliest stages of the modern smartphone era. Of course this situation would bring up unanticipated problems.
IE 6 was the most advanced browser of its day, pushing the boundary far beyond what Navigator did. For example, IE 5 and IE 6 were the first browsers to give us AJAX, which is still used today. Of course this situation would bring up unanticipated problems.
The issue here is that Millennials/Hipsters aren't doing cutting edge work. They're doing very basic work most of the time, but they're making mistakes that we knew about, and how to avoid them, decades ago!
OSX has *ALWAYS* had a method to bypass password verification and login as a root user. Almost always designed in a way which the end-user can't disable.
I had a friend who worked tier 1 tech support for Apple a few years back. He found out like a half dozen tricks for bypassing various security features once logged in and at least two ways to bypass the login screen, one was a three keyed salute during boot, and another was at the login screen (one or both were disable-able, but were included by default so Mac Gurus could seem 'mystical' and recover systems for idiots who had forgotten their password.)
Expect to see customer satisfaction with the Mac store guys to go down after this has been 'fixed'.
Apple's response is just PR-driven BS, and your comment does NOT deserve the "insightful" moderation the shills and sakura gave it. The only insight from your comment is that you have minimal contact with Apple.
Try and honestly criticize Apple in an Apple-controlled venue and you will find out what total lack of respect means in a profit-dominated context. For example, if you had tried to describe this rather horrendous security problem and gotten too negative, I predict you would have found your comment blocked. Based on my years of experiences involving a MacBook Pro (which I still use on a daily basis for certain tasks), I actually think Apple has automated the censorship using sentiment analysis of the draft comment. Or perhaps it's profile-driven by the secret dossiers they have on each of us?
I could write a more substantive response on the topic, but here on Slashdot such a comment would merely be shouted down by pro-Apple fanbois with mod points to burn. Not worth the time, though I will donate a few seconds for a rerun of the capsule version:
Capitalism and communism are dead. Our new religion is corporate cancerism. There is no gawd but profit, and Apple is gawd's chief prophet.
Freedom = (Meaningful - Coerced) Choice != (Speech | Beer^2), and sad sock puppets' bad mods avail them naught.
"Just get it done by tomorrow, and if there's an issue we can fix it later."
LOL apple admitting the problem. And it didnt even take the threat of a class action lawsuit this time. If apple could have they would definitely have covered it up. That is in their DNA.
Comment removed based on user account deletion
Your negative assessment is only accurate as far as it goes. If the Slashdot moderation were not so borken (sic), that could explain your lack of an "insightful" mod, though I'd prefer to think it was your omission of the positive side (in the fantasy context of good moderation). I think your missing keyword is "priority", as in security is not a high (or high enough) priority at Apple because something else is. That something else is profit, as summarized in my earlier reply.
Freedom = (Meaningful - Coerced) Choice != (Speech | Beer^2), and sad sock puppets' bad mods avail them naught.
Now dump the thin is king hardware devs! and get some real workstations. IMAC pro no ram door come on it's not that hard!
I translated it as this was a known issue to the underlings, however it never was allowed to be addressed by the middle managers or this problem was a very to spot problem (probably some debug code that didn't get removed) that was allowed to get released.
However compared to other companies, at least Apple is publicly admitting the problem. While some companies may patch the problem, but not state any details about it.
Exactly!
Blah, blah, blah. Just fix this shite.
I'm curious what companies patch the problem and not state any details about it? I've always seem MS and linux distros provide very concise details about exploits and the fixes for them.
I totally agree that waterfall planning for software doesn't make sense, but IMO neither does Features Features Features, 10 deploys a day, release now/patch later, and all the other things we've gotten as the pendulum shifted all the way to the other side. I'm on the Windows side of the fence and it's been an interesting couple of years watching them run through release release release and gradually slow it down a bit as they see quality dropping.
Operating system or application code, running on machines people own and potentially controlling sensitive processes/data, need to be developed a little alower and safer than the average phone app. Phone apps only have a couple of client devices and a known back-end...operating systems are still within the user's control to some extent. OS bugs are very public, potentially very dangerous, and can't be changed by some Red Bull-fueled developer pushing a quick hack change to production. Even if you automate patching, a patch still needs to be released and regression-tested.
I'm hoping every software company will take some of these lessons into account, because I like the faster pace of development and don't want projects to turn into bug-ridden messes because someone read one too many Agile books and isn't focusing on the actual work.
I think Rule 3 of Agile is to fire the QA team. Not sure if that's the McKinsey or Accenture version of Agile though... :-)
Microsofts stripped all useful information from their updates. So now you don't know wtf is getting installed. Nice transparency.
They probably all do. But for some bizarre reason apple deserves to be praised for it.
Apple's response is just PR-driven BS, and your comment does NOT deserve the "insightful" moderation the shills and sakura gave it. The only insight from your comment is that you have minimal contact with Apple.
Try and honestly criticize Apple in an Apple-controlled venue and you will find out what total lack of respect means in a profit-dominated context. For example, if you had tried to describe this rather horrendous security problem and gotten too negative, I predict you would have found your comment blocked. Based on my years of experiences involving a MacBook Pro (which I still use on a daily basis for certain tasks), I actually think Apple has automated the censorship using sentiment analysis of the draft comment. Or perhaps it's profile-driven by the secret dossiers they have on each of us?
I could write a more substantive response on the topic, but here on Slashdot such a comment would merely be shouted down by pro-Apple fanbois with mod points to burn. Not worth the time, though I will donate a few seconds for a rerun of the capsule version:
Capitalism and communism are dead. Our new religion is corporate cancerism. There is no gawd but profit, and Apple is gawd's chief prophet.
Why use so many words? You could have packaged all that into a single sentence:
Blasphemy!! Summon the Holy Inquisition !! BUUUUUUURN THE HERETIC!!!
While you're on the money about the fact there's a specific subculture that is regressive and counter-productive to software quality that is apparently belligerently persisting to fight against industry best practices, should we really be using the word "Hipster" as a label for them? Don't get me wrong, I've got no special love for "Hipsters", and all their tight-pants flannel-wearing beard-sporting shenanigans, I'm not sure they actually have anything to do with this. As far as I can tell it seems to be actually a flood of current, former, and aspiring Microsoft programmers causing this, with some inside help from RedHat (who we never really should have trusted anyway) and while some of them may incidentally be Hipsters, I don't think most Hipsters are actually even coders. You may be wrongfully lambasting the wrong subculture here.
Apple developers can't write good code anymore because of their butterfly keyboards. Writing code became too painful, so they're skipping the test part.
You mean the mystically well-documented single-user boot feature?
https://support.apple.com/en-us/HT201573
And provides a link to a KB article with all the details... Of course they don't give you all the gory details right in the windows update window.
IOS has a "feature" that the OS pops up a request for your Apple ID credentials at random times. Open Pandora and you'll get a popup. Open pretty much anything and the popup appears. There's no provenance to the pop up so you don't know what part of OS is asking for the credentials or why. Backup works without answering the request as you can be signed into iCloud and still get the pop up.
My response is to dismiss the pop up and continue with what I'm doing but it's a PITA. A naive user will enter their credentials in the hope the "feature" is mollified which it sometimes isn't.
The correct way for IOS to ask for the credential is for the popup to say "Open Settings/icloud ( or whatever) and enter your AppleID." Settings would second the request by posting a little icon indicating there's a response pending ala a text message. An animation within settings would guide the forgetful user if the path is more than one level deep in settings so they'd navigate to the proper IOS setting to satisfy the pop up.The point of all that is you know you're talking to Settings when you provide credentials.
The current scheme is ripe for an app to steal your Apple ID. Write an app that does something kind of useful, wait for the 10th, 20th, run and pop an identical pop up that looks just like the OS popup. The user can't tell if it's the app or IOS asking and enters their credentials. Voila, you have access to the user's Apple ID. A little more elided hacking will circumvent 2 factor if it's enabled.
Too much water has gone under the bridge that I guess an obvious attack is new again.
If the Slashdot moderation were not so borken (sic), that could explain your lack of an "insightful" mod
Moderation doesn't matter: karma is just a number on a server somewhere.
I think your missing keyword is "priority", as in security is not a high (or high enough) priority at Apple because something else is.
If Apple puts more priority on security, there are a lot of things they can do (for example, do managers include time in their sprints for the programmers to think about security?)
The reality is though, even if you have really nice processes, if the people writing the code don't care about security, then you'll end up with bugs like this. You can make process requirements that every line of code has a unit test, but then you will get people writing tests that check for nothing.
Of course you can make a process of "anyone who doesn't care about security will be fired," extreme but true.
"First they came for the slanderers and i said nothing."
Paging Scott Forstall....
At least the devs who keep bringing us Objective C, Swift, and whatever is next that requires completely rewriting our apps.
And maybe they'll hire some devs who can figure out how to avoid sending out multi-GB updates to XCode.
This seems like they need to.. revamp their processes completely. Don't you think any new PRODUCTION software being released, during the increased hack threats ever being reported... during the busiest shopping of the year.. would have been verified across 3 different points at least?? Development -> Testing of changes across at least 3 environments Quality Assurance -> Verifying only what's changed works as expected? Maybe lets spend a bit more time on that one. Security Review -> Verifying security points through automated & manual review pertinent to the change? Something with accounts, passwords, users was changed. Additional security review of files, users... lsof and strace work on a basic level when you don't work at Apple. Apple.. this is Kindergarten stuff.. it should be embarrassing with a follow-up assurance package for a year verifying security on offline, local levels..for all of your AppleCare customers. Experian, Red Code.. Every Apple across the world? Common guys.. Kindergarten. -B2
I'm not sure millennials are to blame. Driving this breakneck pace of software development is corporations looking to make a quick buck with little thought or care given to security or quality. It's crank it out or we'll get someone who can. So they inspire this sort of crapfest.
I don't believe in karma, I just call it like I see it.
Something's fishy about the "auditing our development processes" response. Maybe somebody was deliberately trying to slip in a back door?
All of the back ways in CAN be disabled, but nobody does. Apple even provides a howto.With the modern full-disk encryption they are less useful as long as that is enabled.
As someone who works in DevOps, I would pin the blame squarely on the Scrum master, the PMs, and the PHBs. If a co-worker stops doing their demanded 5-10k lines of code a day to work on security, he or she will be crucified come tomorrow's stand-up meeting because they didn't get their stuff done during a sprint... and dev environments are -always- in a sprint state, just like the IT department I was in was always in a "oh shit, FIRE!" state. One guy who was looking to re-engineer some code so it actually had some security was fired, because the PM considered security to be a waste of time, where if the company got sued due to a breach, it wouldn't be the PM or the devs who would feel the heat.
The millennials are doing their damndest to keep employed. They have zero say. Blame the MBAs who don't give a flying fuck about anything but how sleazy they can be to profit from things. Blame the managers whose management style is to fire people as their first recourse, and then blame others why their department has such a high turnover rate, or the manager who is using contractors with B-1 visas (where the fines for visa fraud are tiny and part of doing business.) Blame the C-level staff who intones "security has no ROI" like it is a mantra to the next plane of enlightenment. Blame the government for not stepping in and putting the hammer down on the disinterest to protect people's data.
"Uh oh, better add a user story for not allowing the world to login as root and put that in the scrum backlog"
Modern software development is just completely fucked.
Nice try, Apple fanboi. Go polish Tim Cook's cock some more.
It's not a bug, it's Apples's latest innovative feature.
We greatly regret this error and we apologize
Of course they do. What company would not copy/paste the security breach boilerplate in such a situation? It could even be automated: if +"security flow" +apple yields something in the news, send the press release.
Management who failed to protect the public from an obvious flaw:
1.Ivan Krsti @radian on twitter
2. Viresh Ramdatmisier https://www.linkedin.com/in/vireshramdatmisier/
They obviously didn't smoke test this release sufficiently and should be held accountable.
Apple rakes in billions and should be held to a higher standard of software assurance.
If you can't understand what I wrote and actually want to, please feel free to ask for clarification.
If you can't understand what I wrote and don't want to, that's certainly your prerogative.
If you have nothing to say, why don't you just say nothing?
Let me check again. Yes, rereading your so-called reply and making suitable allowances for your poor writing, I can confirm that there is nothing there that has any relevance to anything I wrote. FYI.
Freedom = (Meaningful - Coerced) Choice != (Speech | Beer^2), and sad sock puppets' bad mods avail them naught.
It's not even just that - High Sierra is a mess. I have software crashing on me that never crashed before. For example Preview crashes when I try to open certain PDF files. Or it will crash if I try to rotate an image. I have a brand new Macbook Pro with the touch bar, and it honestly feels like a lemon! That's how bad it is. The display will glitch a lot (display driver bugs?), copying files from an external drive to the internal SSD will cause the machine to freeze and prevent you from doing any work (APFS bugs?), and this is just off the top of my head. It makes me feel like something is terrible wrong with Apple lately.
I just bought two Macbook Air laptops the last two weeks. They still come with MagSafe adapters, and no USB-C. iPhones are still using Lightning adapters instead of USB-C. I mean c'mon Apple! What the hell is going on? How can a multi-billion dollar company screw up this bad?
All those moments will be lost in time, like tears in rain... time... to... die...
Went back to check your original comment. Rather than receive the positive moderation you might deserve, I see that you have received undeserved and meaningless negative moderation. I am certainly not defending either the quality of the moderation or the way it is implemented. However, I think it could be improved. VAST room for improvement. You mentioned karma, which should be part of such improvements. There's a natural symmetry there that is lost in the current approach.
Not sure about the longer second part of your reply. I could interpret it as agreement with examples, or that you are going in a different direction. I think that I definitely agree with you about the trade-offs, so perhaps I can address it with a pie-in-the-sky solution implemented via tax policy.
Let's start with the premise that Apple is doing a good job of serving the customers and deserves the profits. My more controversial premise is that Apple's customers would still benefit from more freedom in the form of additional choices. Perhaps it would sound less controversial if I reworded it in terms of the lack of a perfect solution for every person? Apple's best offering might be perfect for some people, but never for everyone--even if that assumption would maximize their profits.
So imagine that dominance in their market increased their tax rate. At some point it would make good sense to consider reproduction of the good ideas. Not a penalty for success, but rather an incentive to create more copies of the good ideas and let them evolve into the future. Divide Apple (or MS or Google) into competing companies with equal shares of the resources. Actually starting with the same profits, but divided among the daughter companies. If they want to maintain a standard platform, they could keep doing that, but the platform standards would have to be shared in public.
You might want to buy your next machine from a division that decided to put a higher priority on security. Based on my experience to date, I would be looking for the company that remembered physical security with a Kensington lock anchor on their machines. We might even get a hotkey screen lock on both options because of the competition.
Freedom = (Meaningful - Coerced) Choice != (Speech | Beer^2), and sad sock puppets' bad mods avail them naught.
But don't be fooled: one thing Apple remains firm on—Apple's customers don't deserve software freedom. Apple will continue to pursue its walled garden, ever restrictive practices built around DRM, proprietary software, app store censorship, and so on (see more about how Apple's malware adversely affects its users). The latest insecurity should not be taken as a sign that Apple's users deserve to fully own their computers. Apple will remain firmly in control over their users no matter how capable or willing they may be to want to run, inspect, modify the software, or share improvements to help make things better for their fellow Apple users. I'd like to be able to say to users: pay more for Apple because they sell you software freedom and that deserves extra money to help keep them in business treating you, the prospective computer owner, right. But I can't say that about Apple, so I recommend that you take your business elsewhere and do business with other distributors.
Digital Citizen
That's what happens when you use Waterfall software development process!
MY god! You just hit the nail on the head. I have been really hating this new interface style that has been spreading like a bad rash but couldn't really put my finger on what it it was specifically. As of recent (and by recent, I mean over the last 12 years), I found that overall software has become far less efficient to use. I'm thinking about the same time that Microsoft introduced "the ribbon" in their office suite software was the start of the real decline. Enter Windows 8, metro interface, no desktop, etc.
I was just writing it off as me getting old, and "You young whippersnappers...." and "Get off my lawn", resistance to change... But now I'm going back to thinking it is just p1$$-p00r design/implementation of technology. Something that really irked me in the late '80s and throughout the '90s - the only difference then was good established worked processes trumped trendy and aesthetics, while now it is the exact opposite.
Who would have thought that 'everyone gets a trophy' would have such a disaster on software development and user-interfaces.
You're blaming the wrong people. Millennials didn't give the go-ahead for Windows 8; that decision was made by considerably older people. Millennials implemented a lot of it, but they were working to somebody else's stupid ideas and inane specs. If they'd have tried to give it a decent UI, they'd have been fired.
Systemd? Lennart Poettering was born in 1980, and that's generally considered to be the previous generation.
They're focused on aesthetics and trendiness? Do you know one consistent thing about developers from a long time ago? They're pretty good on providing what they're asked to provide. If they're rewarded for great aesthetics but not for good security or human interfaces, what do you think you're going to get?
There really aren't that many problems attributable to the developers. Most of the problems are management. The developers were told to do A, even when sound software development principles are to do B. Guess what they do? They're told to crank out the code and not care about security. Guess what they do? The manager wants to put NoSQL supervision on his or her resume. Guess what the developers use? Management wants to cheap out on developers and pay the least possible amount. Guess what happens to the code quality?
It's amazing the amount of self-contradictory crap the Millennials get. Earlier generations raised them. Earlier generations manage them. If there's something you don't like about what they produce, Boomers and Xers, it's your generation's fault.
"When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
First, you're wrong. Windows 95 was very simple compared to modern versions of Windows. There's always cutting-edge work going on. Modern versions of Windows would scoff at the attacks available in the late 90s, and a 90s OS would be totally pwned today.
Second, the educators, who are usually not millennials, are failing, or the managers, who are usually not millennials, aren't paying for expertise or requiring their developers to learn or giving them enough time to do a good job, or the previous generation, which are not millennials, is crap at passing along knowledge and wisdom.
"When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
The Wikipedia page on Gedit lists Paoli Maggi as the top person involved. Maggi got his Ph.D. in 2002, and is hence not a millennial. If you dislike modern interfaces, blame Generation X.
There's a lot of crap out there by millennials. There's a lot of crap out there by Gen Xers. There's a lot of crap out there by Boomers.
You know? I'm going to blame this crap on Generation X, since it's usually Gen X that makes the bad decisions.
"When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes