309 karma · joined February 2, 2019
Perhaps at the time, Apple had a bunch of old 5/5S-style hardware that they needed to get rid of, and so to liquidate it all, they created the "iPhone SE" as a low-end phone to get rid of all of those extra components in that form factor.
If so, the fact we all bought it because it was a small frame device is actually secondary to why it was created in the first place. If this motivation is true, it's also likely that if there is an SE2, it's going to be iPhone 7 or iPhone 8 in size and part selection with the better SoC, and you will be getting an A13-based, 4.7", Touch ID that looks indistinguishable from the iPhone 7 or iPhone 8 depending upon what bodies they have a lot of sitting around (or a lot of manufacturing capacity therein). I personally don't suspect a modernized 5/5S style phone from Apple the next time.
So it seems like the problem is a cooling issue, which doesn't surprise me. "Ultrabooks" often seem to sacrifice decent cooling for the sake of thickness, and I think it is because most people really do not tax their hardware all that much. If you do - and you do not have a proper workstation-class laptop - you're likely to run into similar issues.
My Thinkpad X280 suffers from poor cooling that quickly leads to throttling, even undervolted. My old work A485 wasn't that great, either.
I think it's an unfair assumption to say that I'm scolding the teams I work with by trying to educate them on security issues - the fact that that is your takeaway from my last post says a lot about another issue with security organisations: that there often exists some adversarial nature between software engineering and product security. I moved into security from product engineering. I try my best to be the ally of the engineers, and educate them on bug classes so they can learn to deal with issues throughout the software development lifecycle, from early threat modelling and design issues to creating implementations that minimize weaknesses.
A helpful solution, as the child poster says, is to have frameworks that stop you from doing the dumb stuff, but smaller organisations sometimes don't have that luxury, and even still you can shoot yourself in the foot with your frameworks (Using front-end frameworks as an example, I've seen way too many extraneous uses of dangerouslySetInnerHtml and DOMSanitizer bypasses when I was a consultant.)
> scanners that are easy to use, helpful, and don't have lots of false positives.
I've written a fair amount of automation tooling to glue together COTS/OSS SAST/DAST applications. Most of even the better commercial tools still yield insane amounts of false positives and require human interaction to make sure that the bug is actually exploitable. Common web security tools such as Burp Suite Pro's scanner are effectively useless for most modern web apps. Some languages and architectures are better than others, some companies' internal rulesets are better than others, and it's a struggle to get something that works for even the majority case. Some of the most mature technology companies I've worked at are still trying to build these tools across their infrastructure, and they have better success in some languages/platforms than others, and they don't have the resources to keep up with the new languages / platforms / frameworks engineers want to use for this project or that. It's an uphill battle, and education is still just as important as tooling.
If most engineers just took a second to read the ones that were directly pertinent to their projects and tried to be cognisant of some mitigations, I'd find substantially less low-hanging-fruit vulnerabilities in the first review pass. Doing so actually makes my job significantly more difficult, and forces me to dig deeper - which is a good thing. Instead of writing up for the 100th time some input validation spiel, I can spend time searching for more complex bugs, writing protocol fuzzers, and doing real analysis in the time I have for the review.
Not to investors that want a quick ROI quarter-over-quarter on that share price.
I've done exactly this. I tried to run an NVMe drive and a SATA drive back-to-back in the same laptop to see if I could notice any difference in my day to day workload. I couldn't, and because of that I bought a 2TB SATA SSD instead of 2TB NVMe. SATA usually still has better power consumption than most NVMe drives, and they're cheaper too.
https://egpu.io/forums/mac-setup/script-enable-egpu-on-tb1-2...
[1] https://www.picocluster.com/collections/pico-3/products/pico...
Using tlp, setting all settings in Powertop and undervolting with intel-undervolt will get you some seriously crazy battery life. Battery life on my X250 is better under Linux than it is in Windows with these changes.
Buying used hardware is great, but really we should also be probably optimizing for performance-per-watt even with older hardware.
IMO the real issue is that most people just don't need more grunt than a 5-year-old machine is giving them at this point. What they really need is a solid state disk in the old hardware, and for Office and Chromium you'd never notice a difference. I still use a SATA SSD daily and while I've had NVMe in my work-supplied machines, for 99% of my workload it's just not even necessary.
[1] https://eridirect.com/blog/2015/06/how-does-e-waste-affect-t...
[2] http://www.electronicstakeback.com/toxics-in-electronics/whe...
I'm sure it will be exceedingly expensive, but IMO it is a bit of a return to old form. Now we can finally forget about the trash can.
I've been working on a similar project for a while, in order to see what the viability of reused Android hardware is if you make a minimal AOSP-based system. I'm trying to wean myself off of current-generation hardware as much as possible because honestly it's just not needed, and I don't want to feed the consumerist machine.
I'm using a Nexus 5 I bought used for $40, with the Nexus heavily underclocked for power usage and only the simplest required apps on it. The biggest problem I have had with this phone is that battery life on earlier smartphones is abysmal. I did replace the battery for $7 and it's made a big difference, but there's a level at which the old phone hardware just can't keep up with app bloat if you're using some newer applications.
For photos, even the old Nexus is fine for most use cases. For real photos,I just take along a used DX-sensor Nikon Coolpix A I bought on Craigslist.
This is the reason why technological solutions are popular among the Silicon Valley crowd. No matter what, political solutions are plagued by human emotion and self-interest, and thus they become sticky, "corrupt", and slow. Technological solutions are subversive of that structure at the least, and a force multiplier in others.
The computer will generally do what you tell it to do. You can spend hours of effort on something and get a deterministic result that will do the thing. You can spend your whole life in politics and get nothing out of it because the entrenched power structures won't let it happen.
The T490 does 100% Adobe RGB? I'm impressed. Seems like Lenovo has been really listening to people complain about the horrendous gamut ThinkPads have been afflicted with for some time.
I wish I would have had such a TA in my university. Instead, I got compressed deadlines and a "you figure it out or you fail" mentality in the majority of my classes. There were lectures and a textbook - if you couldn't sort it out and make it click on your own, alongside all of your other courses, you were SOL.
Hacker News has been whinging about this Apple dilemma for years. I'm sorry to say that I just don't think there will ever be the golden age of MacBooks again. The "Pro" ideas coming from Cupertino are gimmicky at best for developers, and we will be stuck working on various Linux machines and leave the MBP problems to designers. The hacker-type software engineer is not Apple's target market for the MBP, and I think even before it was likely coincidence.
If you look at the pro target even in this post, the majority of Mac "pro" use cases being displayed here are creative in nature. Devs generally aren't spending their days editing video or sitting in Maya and they are targeting those markets - people who need power but don't wrench into their OS internals or open a debugger when something goes wrong. Those customers are also a lot less flighty as long as their creative tools work.
As for me, I stopped complaining and wishing for a pony, accepted that the MacBook is dead, and moved to a ThinkPad for daily use. My 2015 MBP will stick around when I need macOS, but it's best to start converting my workflow to a different platform where I see a future for development work.
[1] https://www.amazon.com/Samsung-Endurance-64GB-Micro-Adapter/...