Imagine if Windows built a modern kernel, if Microsoft Windows was a full rebuild from scratch - its not. That’s why it’s only 4GB beyond the UI for x86-64 it’s pretty much all Windows 10 with a few learnings form Windows X.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Researcher Says Apple Ignored Three Zero-Day Security Vulnerabilities Still Present in iOS 15
- Thread starter MacRumors
- Start date
- Sort by reaction score
have you tried checking properties of the exe and setting it to run in compatibility mode to WinXP on Win7/10?
Its all Agile software development. I worked at four different companies in the last 10 years where Agile has become quite the standard. Sacrificing QA, rushing features out. It just leads to problems. Its not just Apple. I have had issues with these major Windows 10 updates that occur twice a year with new "features". Also with Adobe software. There was a Visual Studio 2019 update a few months ago that broke the compiler complaining about code that actually met C# standards since version 1.0. Instead of having it be in Visual Studio 2022, it released to 2019 and caused major issues with our development staff. It was confirmed by Microsoft that it was a regression from a new feature.
I agree, I would definitely prefer upgrades every few years instead of what we have now.
I won't be so sure. I still have had way more bugs in 21H1 than I have had in Big Sur.
No its not. I just replaced a 27" 4K monitor with a 27" 2560x1440 and it looks MUCH MUCH better on Windows. I tried with the 4K monitor at various scaling settings, but it was still blurry in a lot of areas. Meanwhile that same 4K monitor looked perfect on my Mac mini with scaling.
Also think Big Sur had been pretty stable, and I've used it extensively more or less daily since 11.1.
Windows OK to too, but that I only use for gaming.
Cook is still running the same game plan that Steve Jobs left him, but in the end, he's still a CFO/bean counter just trying to act like a visionary engineer. It's not a surprise to me that he's falling short.
Your definition of falling short might be different than the rest of the world as well as some MacRumors posters.
That's what I thought.
So yeah, those assets take a LOT of GBs. The day Microsoft finally optimizes Windows for high-density pixels displays, it will suddenly weight quite a few more gigabytes. I was quite surprised when I developed my own app on iPhone Retina displays a few years ago.
I want a new version every year. Manufacturers want to keep selling new and innovative products, which is what is there in the consumer electronics space.
I’d like to hear the full story and from both sides. Anyone who makes vulnerabilities public if they don’t like the company’s response or lack thereof is in the wrong. They should first go public on social media, tagging key people from the company to bring awareness. If after that fails, fine release the vulnerability.
There’s plenty of public figures to reach out to, there’s plenty of software engineers to ping on LinkedIn.
There’s plenty of public figures to reach out to, there’s plenty of software engineers to ping on LinkedIn.
I imagine it's bad. I'm pretty sure they'll fix it. Anybody realize how complicated this is? Look, I'd like 100% security, absolute flexibility, and I want it NOW. I don't care about Windows. I don't play games. It they get it down, whatever it is, in two months, that's probably good. They have evolved the last four versions of MacOS into brand new silicon, a new advanced programming language, and a very smooth network of Apple iPads, iPhones and Apple TVs. There's going to be some problems. Yes, maybe they should put in some new featured when they're good and ready. Good idea. But when they do it, people complain, of course.
You don't actually think Apple doesn't understand what they are doing or can't predict the result of their process do you? You're saying your pipeline would be more effective than Apple's? Apple somehow has no clue about the development life-cycle, agile management etc?
If they did what you're suggesting, everyone would complain that Apple never releases new features. In this consumer environment it's better to release new features that work pretty well and release updates to make them better along the way instead of waiting to release a perfect feature which in reality will never happen.
This is actually a reflection on the software industry. The only engineers that do not require certifications and have their own standards are software engineers. The closest thing software engineers have is IEEE and even that doesn't mean much. Imagine if structural engineers built things like software engineers. Most everything would crumble to the ground.
Before apps were a thing, that’s all the iPhone was. An iPhone without apps. 🤷♂️
Apple will keep being Apple until they see or think that we'll stop buying their products en masse.
The security researcher has no choice to go public if the company is blowing them off and not fixing the security hole. Maybe their devices being exploited by those vulnerability's will give them a kick in the ass to patch it.
When do you think that will happen? People will stop buying their products?
Frankly, there are two sides to every story. I would like to know Apple's side of this. But that will probably never happen.
I never suggested that would happen. Also flippancy aside they don't need every single person to stop buying, just a number significant enough to get them to look into the root cause.
Companies usually only respond or change their modus operandi when they get negative press or sales or somebody clever has 'done the sums' beforehand. Whether it's hardware or software a company will release their product very likely knowing there are design faults or other shortcomings and they make decision as to whether the loss of sales/face is worth them holding or and fixing said issue(s).
When things genuinely catch them out how they react tells a lot about them.
What I’ve described in this case IS the middle, though. On one end, Apple does nothing, on the other Apple drops everything to fix the “installed app on device” exploit. The boring mundane reality based middle is that there are definitely exploits that exist that are more serious than this, exploits that don’t require you
1. Obtain a developer account, with your personal credentials
2. Pay the $99 using your personal/business funds
3. Develop an app that’s able to be allowed on the app store
4. Submit a few successful releases with no exploits so the review process may get lighter? Maybe?
5. Submit the release with the exploit hoping that it’s not found, BUT if it is, it’ll be removed from the store, undoing all your work from steps 1 thru 4.
In the middle, you use your OS developers to focus on exploits that require no interaction from the user and use or App Store developers to create patterns to search for and help find apps that may be doing this OR might try to do it in the future. Then, when there’s opportunity, you have the OS developers make the redundant change on the OS side.
And, obscurity is a primary part of security. I get where the phrase comes from (and folks tend to gravitate towards the ones that rhyme
), but a big part of any security posture will always be “There’s some information about this that’s not going to be publicly available” or obscured. We all know how house access works, via some form of locking mechanism with a unlocking device that matches it. The ONLY thing keeping us from easily entering any house we want is that the keys are obscured. Now, if you were to send an email to everyone you know saying, “In order to be open and communicative, I’d like for everyone to know that the key I kept under the flower pot has now been moved under the mat because I got tired of moving that pot,” well, it’s definitely more open and more communicative for sure!
Not only did I read the article completely, I have personal experience with how Apple does security fixes.
Score your fake internet points somewhere else, please.