333 karma · joined May 11, 2017
The only complaint I have is that you can't run two external monitors off of it, but I have no doubt that the next generation will address that.
https://www.caranddriver.com/news/a35604138/usps-oshkosh-def...
I was using Firefox, but have recently switched Safari full time. It just seems to run better and isn't as brutal on the battery.
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 34 Celsius
Available Spare: 100%
Available Spare Threshold: 99%
Percentage Used: 0%
Data Units Read: 5,315,871 [2.72 TB]
Data Units Written: 2,249,290 [1.15 TB]I generally disagree with your premise here. Yes, you can do some pretty amazing things with image processing in software, but you have to have a decent starting point. A good example of this is just how minimal the image processing improvements are in the M1 MacBooks compared to their Intel counterparts — marginally better, but nothing to write home about.
I’m not at all an expert in optics, but I would expect the biggest constraint is the available depth for the lens and camera sensor within the upper clamshell of a laptop vs a phone. It doesn’t seem like it would be a huge difference but an extra millimeter or so makes a huge difference in the size of the sensor that can be used.
It’s honestly terrifying to me that anyone thinks that this is a sound idea that would lead to a better world in the long run.
If there is anything that human history has proven, it’s that you cannot prevent corruption and that the centralization of power only further incentivizes corruption.
It’s not logical at all.
A large subset of the population in the US is (rightly IMO) not okay with their state or local government dictating what businesses are forced to close or imposing restrictions that effectively put them out of business.
By approaching the situation in this way it’s only further politicized the issue. I worry what will happen when something worse than COVID-19 comes in the future.
> If you're over your storage limit for two years, Google may delete your content across Gmail, Drive and Photos
Honestly that seems far more generous than I’d expect — why should Google (or any other company) be expected to store your data indefinitely if you stop paying them?
There was a point in time that I was pretty deep into the Android scene, but at this point in my life I just want my phone to work consistently and have great battery life.
After many years of using Android devices (including many Nexus / Pixel devices), I switched to an iPhone 11 Pro Max last year. I've been very happy with that switch, my phone always makes it through a day of use and I haven't ran into any of the quirks that I encountered on my Android devices on a regular basis.
I completely understand why you would prefer Android, but there are definitely people (including myself) that are happier with iPhones.
Apple has pretty consistently had the fastest SoCs for phones and tablets for a few years now, particularly in single core performance. Here are some benchmark results of the iPhone 12 versus some of it’s Android competitors [1]. Notice that last year’s iPhone 11 Pro Max still outperforms Android phones from this year as well.
I think part of the reason this isn’t a major differentiator (for phones at least) is that phones have been “fast enough” for several years now. Given the very aggressive throttling that is utilized on these types of devices, I think the primary difference ends up being battery life / efficiency rather than raw performance.
It’s also worth noting that while the performance / efficiency gap between x86 and ARM seems to be pretty sizable at this point, the gap between various current generation ARM CPUs isn’t nearly as drastic.
1: https://www.tomsguide.com/news/iphone-12-benchmarks-this-des...
https://onlinelibrary.wiley.com/doi/full/10.1111/j.1467-9566...
AMD has done a great job with Zen 3 in particular, but IMO they are going to really struggle to compete with what Apple is able to do with ARM.
At one point I asked the forester what I could do to help promote healthy regrowth of the forest. His response was that I didn’t need to do anything and that “the best way to grow a new tree [in a forest] is to cut an old one down”. This honestly seemed a bit like nonsense to me at the time, but watching the way things have already started to rebound has been pretty incredible.
I started counting new seedlings this summer but ended up giving up after I had counted more than 200 poplar seedlings within a relatively small area. Obviously all of those won’t survive to maturity, but it’s given me a new appreciation for just how effective forests are at regenerating themselves when harvesting is done responsibly.
Honestly, all of the controls for residential mini split systems are pretty awful. My Mitsubishi system has the MHK1 thermostat [2] which is Mitsubishi specific version of the traditional Honeywell thermostat. The newer MHK2 looks a bit more modern, but honestly isn't really any different in function.
1: http://www.daikinac.com/content/residential/residential-cont... 2: http://www.nonul.mylinkdrive.com/item/MHK1.html
I think part of the problem is that modern repository software has built an 'additional layer' on top of git (IE: pull requests) that most of us have become accustomed to using in our day to day workflows. Git itself doesn't really have a 'lossless' way to persist that extra information.
Squashing commits at merge gets us close, but ultimately we’re throwing away potentially useful information by doing so. The main time I’ve seen it be problematic is when multiple people are working on a complex feature where PRs are getting merged into a long-lived feature branch rather than directly to the default branch.
Say I need to base my work on someone else’s WIP branch for said feature. If they squash their commits when merging their work into the feature branch, I’m going to end up with merge conflicts that need to be manually resolved as the individual commits that I had based my work on no longer exist, as they’ve all been squashed into a single new commit.
What if git supported a sort of 'soft squash' concept, where associated commits could (optionally) be grouped together with additional metadata. That would let the application consuming the git history (IDEs, CLI tools, etc) make the decision in how commit histories are presented to the user.
My point of view is that if work is being done on an individual feature or bug fix, having a view of the individual commits might help give any reviewers important context on how a final solution was arrived at. It can also be helpful to be able to see the specific changes that have been made since a prior review.
While in most cases I favor squashing commits when it comes time to merge into the parent branch, it seems like doing it manually just creates extra work and potentially throws away information that may have been useful to reviewers.