stormbeta
Especially as the convenience in this case seems quite minor even ignoring the incredibly steep cost, particularly as I do not trust any of the companies offering these services to accept proper responsibility and accountability for failures, even ignoring the privacy issues.
Anything more complex and it becomes one of the worst choices due to the confusing/unintuitive structure (especially nesting), on top of having less/worse library support.
YAML's structure is straightforward and readable by default, even for fairly complex files, and the major caveats are things like anchors or yes/no being booleans rather than the whitespace structure. I'd also argue some of the hate for YAML stems from things like helm that use the worst possible form of templating (raw string replacement).
The harder part is figuring out how to handle public content, because there are still innocuous or positive uses for it as well.
You have that right at least.
I cannot understand anyone who promotes the use of systems that catastrophically increase the risks of human error, particularly for the most vulnerable, and which pointedly ignore that other solutions may work better.
Particularly when the people promoting those systems have an obvious financial incentive to misrepresent them.
This is highly inaccurate, particularly on the used market. People want cards that can handle whatever games they play within their budget. A lot of older cards run tons of games quite well still, especially if you accept lower framerates / resolutions.
RTX in particular isn't actually that coveted by gamers from what I've seen. It's seen as a nice-to-have at best.
1080p and 4K are both terrible choices for 13-14" screens, yet that's all you see anymore, and even on higher end models trying to get accurate info on panel quality and color accuracy is a nightmare.
I don't think it's a coincidence that even a decade plus later, the primary use cases for crypto still seem to be grey/black market deals, speculative investments, and pyramid schemes.
* No ability to show thumbnails in folder icons
* No ability to use single click + hover to highlight
* Relative sizing feels way off - everything in Finder always seems to be simultaneously way too spaced out while also being way too small.
* Never seems to remember view preferences properly, and often defaults to confusing arrangements.
* Doesn't like to stay connected to network drives, despite any number of tricks I've tried.
* The usual cut/paste/delete operations being needlessly complicated to perform
I do prefer macOS overall, partly because I'm tired of having to constantly tweak and fix Linux whenever I try to use it as a desktop system, and because of things like iTerm2 and BetterTouchTool.
But I really hate trying to do any kind of real file management with Finder, and most third-party apps I've tried just seem to replicate everything I dislike about Finder.
It always surprises me how little cryptocurrency advocates seem to understand basic macroeconomics and unintended consequences, especially on sites like this.
I felt a lot safer using something like KeePass, and synchronizing the encrypted database using something like Dropbox.
There's not a central target that would get caught up in large scale attacks aside from Dropbox itself - and even if they get access to that somehow, they'd then have to care about me specifically enough to run expensive offline attacks on the encrypted database. Anyone targeting me directly with those kinds of resources already has better avenues of attack.
My Pixel 3 at the time I bought it was one of the smallest decent quality phones that wasn't iOS, and even after a year and a half I still notice how much my hand has to contort for basic usage.
I don't think it's just you - there's a lot of basic everyday functionality that is pointlessly difficult and cumbersome in iOS.
E.g. data management is still the worst of any modern OS by a huge margin, and data sharing between apps is still a half-broken mess. Even things that _should_ work with straightforward data types often don't - e.g. you can't share audiobooks to iBooks even though it can play them, or trying to share an image to an art app might simply open the app with no indication of where the image went or what went wrong. Lack of default apps means you often have to open files the long way around through a convoluted series of download/share steps. These are all things that work fine on Android, and were never a problem on desktop OSes to begin with.
However, you can change the button to control noise cancellation level instead, and that's actually very useful since "high" doesn't handle wind well when I'm outside, while "low" does.
And I consider all of those buttons to be pretty important - I use all of them regularly, including when I'm not right next to my phone.
I just hope the 700's are an aberration, and that Bose goes back to a more practical design next time.
Anyone who puts non-tactile touch controls on _headphones_ shouldn't be allowed to design electronics interfaces ever again.
The QC35 had it right with physical controls.
I've lost track of how many times helm has misrepresented the result of upgrade operations, even returning success when it actually failed, and what should be routine upgrades often break in ways that require detailed knowledge of both kubernetes and helm to recover from.
Yes, conflicts and failures do sometimes happen with package managers, but with helm we've seen it happen with nearly every Chart at some point or another, from the simplest single-resource pipelines to widely used community projects.
Helm 3 will help, but it's still built around the same messy string-templating system that ensures Charts are fragile and difficult to understand.
They're plenty intuitive, but they're obviously timed for the slowest possible user using them for the first time - so by the hundredth time you try to do something, you're getting really frustrated by having to make grand, exaggerated gestures to get the OS to understand what you want, and I frequently find myself having to repeat actions 2-3 times for them to "take".
Gmail doesn't have the automated bundling features that Inbox does, and like you, losing Inbox will be a pretty significant blow to my ability to manage email.
I've been slowly migrating away from Google's services for a long time now because they keep pulling stunts like this - it's like they're completely unable to keep their engineers focused on maintaining any kind of product consistency or long-term support.
Android Pie's awful UI/UX changes and discontinuing Inbox are very nearly the last straw for me. I can't avoid Gmail entirely as I'm too attached to the address, but worst case I can always just forward to a new one.
I like macOS, but Apple's making it incredibly difficult to take their product line seriously lately.
There's so many cases (arguably including the problem this PEP was designed to solve!) where having a real inline closure is just far more readable than having to arbitrarily break every single thing that happens to need 2+ expressions out into named blocks out of sequence.
Other things in Python are either simply a result of the language's age and history, or have real technical pros and cons, but that one irks me because it's an artificial limitation chosen for no reason except aesthetics.
Unless you're paying close attention, it's not obvious to the average consumer that so many products are being sold by independent resellers vs Amazon themselves, so people aren't as careful as they might be on, say, eBay.
Instead, they chose to rub the user's face in it as a marketing ploy.
But GOPATH was a mistake in the same way Go's hitherto lack of versioning was: it deliberately breaks easy isolation between projects / dependency management.
This mindset only works if you control most of the ecosystem (such as with a monorepo), but it's a irritating mess otherwise.
Always run your builds with maximal version selection in CI (unlocked), and lock the new versions in if it passes all tests, otherwise leave the previous locked versions and flag it for review.