For human-maintained config, TOML is only "better" when the structure is so flat that it's almost indistinguishable from an INI file.
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).
That aspect at least is easy to solve by drawing a stronger line between public content and stuff seen by people you actually know. This would be more of a social change than technical of course.
The harder part is figuring out how to handle public content, because there are still innocuous or positive uses for it as well.
> Anyone who understands what Bitcoin enables and still doesn’t agree that Bitcoin is valuable and good for the world has a wildly different set of values that I can’t understand.
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.
> Also, like regular graphics cards, newer versions are highly prized so one might say that graphics cards as an industry is already all about e-waste. Unless you’d like to buy my Radeon 9800 or my GTX 1070? They’re still perfectly good for gaming… except everybody wants the new RTX ray tracing etc.
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.
I don't mind 16:9 so much as the incredibly poor choices for resolution and panel quality I'm faced with on most Windows laptops lately. It feels like TV salespeople took over and completely ignored what actually makes sense for a laptop.
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.
And this is exactly why I'm so skeptical of cryptocurrencies in general. There doesn't appear any viable way to make them work as currencies that doesn't either have horrendous externalities, simply replicate what existing currencies already do (often poorly and with many downsides), or often both.
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.
Couldn't disagree more. I've always had false positive issues with Apple's trackpads. The newer ones are slightly better in terms of accuracy, but they're so absurdly large that it still happens more often than it used to - and this is across 4+ macbooks and multiple generations, so it's not just a faulty model, and I'm not the only person I know with this issue.
* 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.
That and the energy cost, both direct as well environmental.
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.
Consider that for many of us, our phones are now quite literally painful to use one-handed, and we have no alternatives - for devices that most of us use for at least an hour or two a day and is often our primary tech device when not actually at a desk.
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.
I have the QC35's, and the voice assistant integration is, as expected, gimmicky and not very useful.
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.
Capacitive controls have zero place on any headphones, let alone ones as expensive as these. The fact that you're willing to live with it doesn't mean it's not still a terrible design.
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.
The fact that we _still_ can't disable the drafts "feature" says a lot about how little they listen to user feedback. I've not found a single person who likes that behavior, the behavior doesn't make any sense. There is a good reason almost literally every other chat app with a similar feature simply uses color/icons to indicate the same thing.
That might have been the intent of helm, but it does not at all reflect the reality of using it in the experience of most people I've spoken with, especially pre-3.0.
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.
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).