stormbeta

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.

Yeah - as a user, I specifically _don't_ like Apple's approach of breaking things all the time.

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.

The US is at no serious risk of hyperinflation in the foreseeable future, barring unknowable events / disasters.

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.

Speaking personally:

* 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.

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.

Exactly.

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 own an iPad Pro 11.

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.

While this is great news for my QC 35's, the newer Bose 700's have me extremely worried for the future of their devices.

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.

RIP Inbox. Still a drastically better UI for a lot of users than Gmail is.

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.

Not to mention the inability to split the keyboard - on iPad sized devices, trying to thumb type without a split keyboard is a huge pain in the ass.

The navigation gestures and movements on iOS are a prime example.

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".

Yeah, I thought Inbox would actually be safe to use since it was tied to email, but nope.

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.

Agreed. It's not even the cost I take issue with, it's the design compromises. I want a professional device Apple, not a toy fashion product.

I like macOS, but Apple's making it incredibly difficult to take their product line seriously lately.

The big one I want to see, because it's one of my biggest frustrations with Python, is to finally make lambdas work like every other contemporary language instead of being inexplicably limited to a single expression simply because Guido couldn't come up with a syntax that agreed with him.

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.

I don't know, I've seen a lot of trust erosion in the last few years even just among people I know (many of whom don't even work in tech), largely driven by them getting burned by problems with sketchy third-party re-sellers.

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.

I wouldn't have been so annoyed if it was actually treated as the engineering concession that it is. From a user experience POV, the obvious thing to do with an OLED screen would have been to make the notch the same height as the status bar, and have the status bar white-on-black.

Instead, they chose to rub the user's face in it as a marketing ploy.

gofmt, sure. Consistency in style is great.

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.

Not only that, but locking allows for what is IMO the best way to handle this through CI:

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.

And yet my Android apps have often stayed working long past when they stopped being supported, and rarely seem to suffer from the quantity of layout problems iOS does since Android has always had to deal with devices of variable sizes and ratios.

I'll grant the low end of Android apps is probably much worse than the low end of iOS apps, but I generally don't use those apps in the first place.