If you open more than one draw at a time you would unbalance the drawer and it would tip over, falling on you and possibly injuring your feet and damaging your stuff and the floor.
This safety mechanism is not there if the drawer is embedded in a larger frame where tipping over is not possible.
Sometimes it's not bad UX, it's just the thing trying to protect you from your stupidity.
Think about that: children have died from 𝘥𝘳𝘦𝘴𝘴𝘦𝘳𝘴. It's easy to be smug power user complaining about design when you only consider how you interact with things.
This very thing happened to me decades ago: I walked into parents' bedroom to find my fearless younger brother, ignoring my yells, climbing up the handles on the front of my father's dresser. I yelled for my parents but I couldn't stop him fast enough. As the dresser began to tip I got between him and it and pushed upward, both removing him from the dresser and tipping it back to rest.
I was truly shaken and astonished that this child might have killed himself, since I knew that the top drawer was filled with my father's most valuable (and heaviest) WWII memorabilia and that the entire dresser, about 5 feet tall, was hardwood with decorative protrusions on the front.
Makes you wonder how we as humans haven't evolved the ability to innately perceive being crushed by large objects.
I know I become hyper aware of any small black specks in my peripheral vision since they resemble spiders that could have posed a threat to our ancestors so we evolved these heightened senses to avoid them.
And in nature you do not really have much big objects that could fall on you if you climb them.
Maybe a large boulder loose ... but they are very rare in my experience. So I guess it makes sense we are not prepared for it. What is much more likely, a loose rock which breakes off at climbing .. we are prepared for. Instinct reflexes are pretty fast in that case, I noticed ..
A cabinet being wobbly and starting to tip over towards you should feel pretty dangerous I'd imagine, we have various biological mechanisms that detect balance [1].
I would hope the ability to sense loss of balance equilibrium would innately result in having the strong urge to bail from that activity to sturdier ground, given you knew you could safely land on the ground without a worse outcome.
A tipping cabinet takes much longer to fall unlike a rock dislodging when you are climbing the side of a cliff in nature. Maybe it is simply a blind spot in our evolution like you suggest, evolution never optimized us for this edge case scenario not experienced in the wild.
As a parent, this is one of the silent killers that haunts me. We only have one dresser and I have it tilted back... but I should also strap it to the wall.
I was a PICU nurse before I started writing software for a living. A surprising number of kids also get seriously injured by pulling TV sets/cabinets over onto themselves. Affixing things to walls definitely a good plan.
Also PSA for the holidays: fence pools, use your reversing camera and know where your kids are before backing out of the driveway, and that dishwasher detergent does horrible things to kids (airway/oesophagus) and people tend to keep it down low for some reason.
Just the other day my toddler fell out of a shopping cart. I never paid much attention to the warning signs because I'm always right there pushing the cart, this time though I'd moved a few feet away to wrangle his older sister and he stood up in the cart. I immediately moved back towards him but I was too late. Normally he has great balance but as he reached out to me his weight shifted causing the cart to roll forward and he toppled right out. He landed right on his face in the most horrifying moment of my life. Thankfully he's all right (giant bump and a black eye) but it easily could have been fatal. I'll never leave him unrestrained in a cart again.
That was the first thing to jump out at me, too. I love crotchety blogs ranting about (whatever screwups), but this one takes a serious credibility hit right off the bat. Ranting about something you don’t understand and being blatantly wrong about it isn’t a great look.
> That was the first thing to jump out at me, too. I love crotchety blogs ranting about (whatever screwups), but this one takes a serious credibility hit right off the bat. Ranting about something you don’t understand and being blatantly wrong about it isn’t a great look.
Cunningham's Law states "the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer."
I thought that was to say "X can't do Y but Z can so X is stupid". You will then get a list of solutions from fans of X.
The most common sighting of this in action is OSs (ask "how do I do Y with Linux" and you'll be pointed at documentation, say "Linux can't do Y but Windows can" and you are more likely to get a couple of pre-baked solutions sent your way, and the same works the other way around and with other OSs) but I've seen it work for scripting languages/environments (powershell, bash, ...), databases (postgres, SQL Server, Oracle, ...) and other tools.
>Cunningham's Law states "the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer."
I am amazed there is a law describe this. This is so accurate. I couldn't be bothered to answer questions even if I knew the answer, but I would be bothered to correct it if the answer were wrong.
The one about the update and upgrade commands in brew too. I've never used brew but I assume they operate the same as update and upgrade in apt related tools and are not really synonymous if you have a vague idea what is going on: update acts on the package catalogue and upgrade upgrades packages. Maybe update should be update-catalogue, but then people would moan about the extra typing.
Update could legitimately mean upgrade of course and you could have it essentially auto-correct, but I'm generally wary of software trying to do what it thinks I mean rather than what I explicitly say (and not doing anything if what I explicitly say doesn't match up with its language). At some point it will mis-guess and do something I really didn't want.
Thing is, "update" to me doesn't mean "update self to have newest content". Especially in the context of what Brew does: version manager for packages. By definition alone I expect it to be taking an action to update a package.
Now suppose instead of "update" they used called the functionality "sync". I don't think I would have the same problem, since linguistically and contextually, I wouldn't use Brew to _sync_ packages. But it does make sense to use "sync" when talking about getting updated information about which packages are available--we're syncing the local catalogue with the remote catalogue.
So I agree with grumpy blog that their use of "update" here is suboptimal. There are better fitting words that both better describe the functionality and avoid the confusion.
Yeah, I think the existing UI is absolutely correct for that one.
I'm not a heavy brew user, but if it works like other package managers then the "update" command is a fairly casual, frequently used, and typically reversible kind of action. If you pull in too high a version of something, oops, remove and redo. Whereas "upgrade" is something you probably only do when you have a specific reason.
I mean, it's sometimes sensible for apps to auto-correct on inputs, but a frequently used "muscle-memory" kind of action should never auto-correct into something heavy and non-reversible. I imagine that's the thinking there.
While “brew update foo” may be difficult to handle technically, it does have a meaning that makes sense: you want to fetch the latest information about just that one package so you can install it, without updating the entire package database (which may obsolete some of your other software).
It works pretty much like apt. When you do update it also shows you which packages can be upgraded. It seems pretty obvious how and why that is (maybe you dont want to upgrade everything). Seems like solid ux to me.
Yep. Quite a few times I've had cabinets start to tip on me because I opened multiple drawers at the same time.
It's not something very intuitive since we generally expect furniture to be stable in normal usage. To make it worse, when it starts tipping all drawers slide open and bang into you, compounding the effect and accelerating the move.
That makes sense for a 4 drawer, 5' tall filing cabinet -- which generally all have the interlock, and little to none for a 3 drawer under desk unit with drawers half the length or less of a filing cabinet. Even if you wanted to load them as heavily as a file cabinet, the drawers are generally far less substantial or well made. Doubly pointless considering the drawer unit shown has no filing drawer. Most of those solve the possible tip with a castor or slide under the front of the sole bottom filing drawer.
It just depends on what you load into the drawers. Since essentially the contents of only one drawer at a time is accessible in any case, it's the right UX decision.
Anyway, you need to close those drawers eventually, right? Why not before opening the next drawer?
Put another way, the alternative is to support the general use-case of disorganization: "I'm not sure where the thing I'm looking for is, but I need it in a hurry!" Do you really want to categorically assume in such situations that people have mitigated the tip-over risk in some external way? Just to allow for high-speed riffling?
Your castor idea only really helps if the search happened to start with the bottom drawer first. That's sorta logical, at least in some cases, but I don't think you can come anywhere close to assuming it's going to happen all the time.
That would be a 12" deep file drawer, which either do have an interlock, or in a desk side with single file drawer the castor or slide underneath, as mentioned.
The one illustrated isn't deep enough for hanging files -- maybe the odd ream of A4, pens and pencils. Will need an awful lot of carefully placed paperclips and pencils to tip. Which is why you rarely see those locking each other out. If you use it for storing your collection of lead weights you bring it on yourself (the base of the drawer would probably fall through anyway)... :)
That set of drawers is not sizeable enough to warrant tipping protection that is so unfriendly to the user. If it were a 2m high filing cabinet, I would agree, but it isn't.
Dressers made of thin, light wood, filled with drawers full of clothes and/or toys never have this safety feature, and those are the things which need it most; they all require (or recommend) that you instead strap the top of the dresser to the drywall, assuming that it is both against a wall and that the wall is finished with drywall, and not some other wall material, such as brick, which is common in certain geographies.
Too many people commenting here completely missed the point of the linked website entirely, immediately homed in on some minutia, commented with some variant of "uh, actually...", and even got that wrong, arguably.
I think people are stupid, it's our right to be and things should be designed with this in mind.
I agree that using the world "stupid" could be ill-receive and other words could avoid this problem, but with the right audience this shouldn't be a problem.
> Sometimes it's not bad UX, it's just the thing trying to protect you from your stupidity.
In my opinion, it is bad UX, but for a reason. There might be better solutions.
How about a pulley system which does not require locking the drawers but instead pulls the other drawers shut when i open a new one. No locking, no tipping, better UX.
This is like saying a gun with a safety catch is "bad UX." The best UX is the one that enables the user to use an object like it's supposed to be used while not allowing them to literally or figuratively shoot themselves in the foot.
But we already have a solution for the problem: Anchor the dresser to the wall.
But people don't, so these companies introduce measures "for safety" by compromising the UX for all their users (can't open multiple drawers at once even if you wanted to) in order to prevent a dangerous scenario that the operator failed to address (leaving the dresser unanchored and ready to topple over).
And what do we think is the goal of the manufacturer? Is their goal to provide a public service and preventing people from injuring themselves? Unlikely, as it's still entirely possible to overload the drawers, or put something on top, that will still provide a dangerous result. No, their goal isn't safety because the safety is out of their hands. Their real goal twofold: First, to prevent situations where their products can be associated with dangerous or fatal situations, even if the fault has nothing to do with them (operator error, not product error). Second, in events where dangerous or fatal scenarios do happen, be able to say "we've taken measures for safety, so don't look at us".
This "feature" isn't for their users' benefits, it's to protect themselves, and they do so at the expense of all the users that _do_ use their products safely and as intended.
It fails the first condition - using like it's supposed to be used. It would be like a gun that refuses to shoot when pointed too low because sometimes people shoot their own feet.
What's your solution? You could give it a super wide base so it has trouble fitting in places people normally put filing cabinets, or make the body so heavy that having all the drawers full and pulled out won't tip it over?
> If you open more than one draw at a time you would unbalance the drawer
This is my filing cabinet. I put a bunch of papers in it. It's not going to tip over. Your assumption of a worst-case scenario is getting in the way of how I actually use the cabinet that I own.
"Sometimes it's not bad UX, it's just the thing trying to protect you from your stupidity. "
It is still bad UX, when the result is frustrating.
And some people do not need nor want to be protected from all forms of stupidy. I mean if you would accidentally blow up something by pressing the wrong button, then yes, safety first. But some people actually can use drawers without letting them fall. And if the worst case happens .. it probably won't be catastrophic either. I mean you can break a leg or ancle falling down on any road anyway, if you don't pay attention.
When trying to find more about the website on mobile, I scroll down and I only see a few links at the bottom, but within less than a second new content loads and the links are gone, I will probably need to load all the content before being able to see the credits / about links.
I have JS default to off (saves big on load times, bypasses some "please buy a subscription" things), and thought this was just a weirdly short list of eccentric things until I saw this comment.
So, add "JS is required for crucial, rather than merely useful, features."
> Five other people are reading this doc, right? Wrong! The user with a white avatar is actually a button to start a chat! Why does it look like a user and is placed where all other users are, we’ll never know.
> But wait, isn’t there a chat button next to Share? No, that’s comments! What’s the difference? Comments are square, while chat bubbles are oval!
> Also, if you ever wanted to check how your stocks are doing, there’s a button for that too.
My all-time anti-favorite UI thing like this is Mac dialogs where two different buttons are focused.
E.g. when closing a file with unsaved edits, you typically get a dialog with three buttons:
[Don't save] Cancel [Save]
"Don't save" and "Save" are both highlighted, but in two different ways - and for added excitement, spacebar activates one of them and Enter activates the other. Feeling lucky?
There’s a system behind it, which the same one that underlies all of “Full keyboard access” (which is of by default because it takes a bit of background information to master). When you press space, the item under the focus ring is selected; not only this, you can shift focus to other elements by pressing tab. So the ring acts as a visual indication of the item you will select. The filled-in blue button is there regardless of whether “Full keyboard access” is enabled and is intended for a sensible default so that pressing enter will do something useful. The “Cancel” action is usually mapped to escape. The focus ring, then, is usually set to the third option if there is any because that one wouldn’t be accessible via a keyboard key otherwise.
I know the reason for it! But the fact remains that it's two actions that are superficially the same (press an affirmative sort of key to trigger a highlighted button), and users who choose wrong lose data. That's... pretty much a one-sentence definition of bad UX :D
The same system would make perfect sense if it only had one focus target. Dialog comes up, the "main" action is focused, tab cycles the focus, space/enter select it, and escape cancels the dialog. There'd be nothing to learn and nothing to remember.
Using tab/space to navigate dialog buttons (like you're describing in your comment) is not a default setting in macOS. You have to explicitly enable it.
This is why it's complicated: it's not aimed at regular users, only at people who need it for accessibility reasons, or power users.
I love this feature. Regular users use mouse anyway, and power users have a shortcut instead of pressing tab several tabs to pick an option.
Never made a mistake with it.
Outlined button is activated by space and the filled button is activated by enter.
Anyway, I thought this only happens when you opt-in by enabling tabbing between all types of controls (the default is that only edit controls can get focus). What you're describing here, I think, is that the "Don't Save" button has focus, which is why spacebar activates it.
I hope this doesn't get nerffed. "Space => don't save, Enter => save" is part of my muscle memory now. Why would you enable focus on any control and then bang randomly on the keyboard anyway? If you aren't sure, leave the defaults as-is.
Fully highlighted button responds to Enter, the most powerful action. The button with a border only is associated with the secondary action, space bar. Makes perfect sense.
It makes sense because you’re already familiar with the platform convention. It’s not intuitive. Space bar is a larger key and easier to reach, why isn’t it associated with the more “powerful” action?
It’s not about “power”, it’s about the default key to perform an action being enter. So dialogs will run the default action, signified by the highlighted button, when you press enter. Space is intended for selecting the retargetable focused item.
It's standard UI for keyboard focus across most operating systems. At some point, you're just going to have to know that space selects the item that the focus ring is around, just like you know that tab switches between fields. (By the way, this is off by default so you don't invoke it accidentally without knowing how it works.)
It’s off by default, presumably because it takes a bit of effort to use effectively and is thus only useful to power users and those who need it for accessibility reasons.
Sure, I know that's the reason. There's a behind every UX decision, always, even the most stupendously bad ones.
As such, the relevant question isn't "is it logical?", but rather "is having two UI focus targets so useful that it justifies cases where the user will lose data if they choose incorrectly between two superficially similar options?". And obviously that's down to opinion, but it seems like a pretty huge glaring no to me.
A Chrome UI idiocy: The new tab page in Chrome contains a text entry field that says to search Google or type a URL. But as soon as you start to type in it, it switches the focus to the URL bar. Why the heck do they put in the text field if they aren't going to let you use it!?
On a desktop that is mildly annoying. On a Windows tablet it is extremely annoying, because the onscreen keyboard closes when the focus leaves the text entry field.
For Chrome startup you can fix this by changing the startup page from the new tab page to a specific URL, and simply give the URL for the Google front page as that specific URL.
But Chrome doesn't seem to have a way to set the new tab page itself to start at a specific URL (without installing a third party extension) so you still have this focus changing idiocy on subsequent tabs.
A further Chrome annoyance on Windows tablets: if you tap the address bar to bring up the virtual keyboard and then try to paste something by typing CTRL and then V (CTRL on the virtual keyboard acts as a one-shot CTRL lock, so you can invoke control keys with one finger), Chrome somehow loses the CTRL part, and you get a "V" in the address bar. If you then backspace, and try CTRL V again it works.
The biggest problem with modern tech for me is that it almost never works as advertised. A lot of times it's just there to tick a box on the marketing material. The most recent example, got myself a new Fuji camera and it has bluetooth and wireless and a smartphone app and theoretically you can transfer your pictures wirelessly (but not over a physical usb cable). I'd rather it didn't have these features, because it's not reliable, sometimes it won't work at all, other times it takes too long to connect, it's a mess and I have no time in my life to deal with this crap anymore.
I totally agree. For file transfer on my Fuji camera, I just take out the SD card and grab the files on a SD card reader (+ usb-c adapter) on my phone.
(The Fuji wireless app won't let me transfer regular JPEGs or RAW files. Only compressed JPEGS less than 1MB large even though the original JPEGs are ~2.5 MB big.)
The biggest problem with tech is that the "smartphone app" is basically immediately on a (usually steep) decay curve of support.
Usually with no basic protocol backup, such as a basic web api, cli, or filesystem interface.
Of course that's a feature for hardware manufacturers. No one wants a device used for decades, even though that's exactly the level of support necessary to make IoT successful in consumerland.
That apple intentionally breaks things that aren't broken / forces upgrades within its walled garden is even more despicable
The "doesn't add up to 6.5gb" is because storage is shared with other services and doesn't pertain to just Google Drive.
I agree with Google, that it is more important to show how much overall storage you have left, than how much is being used in this particular service, but there needs to be an overview that can show where storage is used. And clicking around on Google Drive it appears there isn't such an overview.
So yes, bad UI, but for different reason than what grumpy website says.
Honestly Gmail storage should show up as an entry when you look at drive storage stats given that it's shared. They do that elsewhere in the account iirc.
Also when you try to dismiss a notification on the phone, and just as you're doing it a new one appears and you end up dismissing that instead. Boom! Now you don't know what it was.
This is on Android BTW, not sure how iOS does it. But instead of the newest notification appearing at the top of the list, maybe it should appear at the bottom. Problem solved.
The git status issue he lists (that it will say it’s up to date with origin/master) is really confusing to folks. Hard to wrap your head that your local “pointer” to that branch is potentially not up to date. Well that really it’s an out of date copy of a remote pointer, known as a reference... That when you “fetch” it’s really updating local copies of remote references.
In a world of devs that has to wrap their head around pointers or references, having copies of references, in a distributed system, doesn’t exactly come naturally to most, especially new, developers. This is pretty bad for what should be baseline dev tooling. It’s like having to learn regular expressions just to be able to edit your first hello world program!
That being said, git is complex, and trying to idiot proof a complex system with more abstractions only makes it more confusing when the abstraction leaks (which it will)...
Abstractions only leak if the system design doesn't match the abstractions properly. Other tools like Mercurial do a better (but not perfect) job because they get more right than git does.
This site makes me happy because it reminds me that other people are just as frustrated with stupid UI decisions everywhere. And that most apps are actually terrible by default. Including ones I've built. UX is hard.
UX is hard, but adding fashionable trends to UX just to arbitrarily kill off perfectly functioning and well-established interface paradigms really makes things hard.
The UX crowd embraces this for the same reason hardware people don't support their software long-term.... it keeps people buying their services at a higher premium.
Are they making their own decisions based on those documentation efforts? Scrolls to bottom of page, no prev/next buttons. Scrolls to top, "ah, there they are!" :(
Actually I really appreciate someone collecting collective stupidity in one place. I am constantly frustrated by terrible design and product decisions every day (both at work and in general) that I can't do anything about. Maybe shame will work.
The problem is that I'm not sure it's stupidity. I bet a lot of this BS is caused by "data driven" decisions that maybe improve ad engagement by 0.1% at the expense of everyone else's productivity, but the company considers the 0.1% increase a win.
What makes me sad is that it seems like us who appreciate & demand good quality, no-nonsense software seem to be a minority, and the masses don't seem to care. I've noticed most non-tech people just accept their fate, either they've already came to terms with the idea that "tech sucks and will always suck", or they legitimately don't know how the experience can be improved (a lot of things may look absurd to us as developers, but might not to someone not familiar with how those things are built) or that they think software is delivered by gods or equivalent superior entities and that they, the "peasants" have no way to call for change even though voicing discontent in feedback sometimes works and is at least worth a try.
I agree with everything, except with the part that tech people appreciate and demand non-nonsense software.
A lot of people in tech enjoy being the "ultimate power user" and are proud of using things that look or feel complicated.
You just have to look at HN itself to read trough rationalisations of why software is bloated and why bigger software is probably better. It's never driven by data or by facts, it's purely by anecdotal experience.
We, collectively as the software industry, have the power to fix this. The fact that awful software still exists demonstrates we don’t care or want to fix it. It’s not a popular opinion here, but software developers/designers are responsible for bad software.
It's just free advertising. After the public is sold on the fact that a certain NEW! feature represents a fix to the thing everyone hates, the manufacturers will have already embedded something new that will keep you idiots buying the next NEW! thing forever.
My new favorite default behavior annoyance was FF for Android deciding that everytime I clicked an open tab after some short time interval, it would reload the entire page making it extra annoying when you have the massive HN who is hiring thread open and want to scroll through it while on a subway with no connection.
Not being able to open all drawers at once is actually a safety feature preventing it from tipping over (see Ikea MALM fiasco). I suppose the UX could still be better.
I noticed that this site is missing the modern classic "giant modal covering the entire screen". Usually reserved for "log in pls", "subscribe to site/mailing list", etc. And then sometimes the modal doesn't render correctly and instead I just see the whole screen go white/gray. News sites, reddit, twitter, facebook, and tons of blogs are guilty of this.
The one about complaining about git status “Your branch is up to date with origin/master” Not hitting the network just belies a complete misunderstanding of both the message and distributed versioning systems in general. This message is telling you that your branch is up to date with your LOCAL tracking branch and is absolutely accurate and helpful in this regard. If you fetch and pull new diffs then it will tell you a different story. I wish people would stop complaining about git and just read the very easy to understand git book https://git-scm.com/book/en/v2 Learn your tools people!
If the naively obvious meaning of a message doesn't match the actual meaning of the message then that's a usability issue, even if it's technically correct.
This message is at odds with how most people use Git. When they talk about master, they mean remote master. Because local master is not useful in their workflow.
Saying that people should learn the concept is not helpful. I know what it means and I just disregard the message as noise. Wait, I think I often reflexively write "git pull" when I read that message. So you could say it does serve some purpose.
My point is the message is not at all confusing if have a fundamental understating of a distributed system as opposed to a centralized one. Just because most people want to use git just like you would have with SVN doesn’t mean it isn’t a completely different architecture that is (admittedly) a bit difficult to grok, but far more flexible and powerful
What's not obvious is if git status does a git fetch under the hood before presenting that message, so that the message can be trusted. A good tool wouldn't print such a message without fetching first and since i assume git is a good tool i assume it presents me useful and trustworthy information.
I know it doesn't, but the message IS misleading for the inexperienced. If i need to read a user manual first to understand it they might as well replace the message with some status-code written in hex.
I think you’re right when you say it’s a good idea to learn your tools, no matter if the tools provides good or bad UX.
In the case of git status, I think the UX is simply bad, as evidenced by the replies and my usage of git. A text update could improve the command substantially - and perhaps a suggestion to run a git pull to update the tracking branch. I don’t think it’s reasonable to read a 456 page book on git
Hehe at our new office in the kitchen there's a cupboard above the sink so that any person going to the sink will not be able to see what they're doing cause the cupboard is in the way unless you double yourself over so that you can stick your head under the cupboard or are a maximum of 140çm tall. Maybe the design was done by a person who has 2m long arms so that he/she can operate the sink from afar and thus avoid this problem.
Hm I was doing something similar, but in the end there was just too much stuff that's broken, all the time: https://twitter.com/everythingisbr2
In the same vein, I've been thinking of having some universal bug/annoyance reporting tool where you'd tag each annoyance with the software/hardware/website and optionally its version.
Assuming you collected those yourself and events happening close to upload. If you have such a high amount of breakages, it means an average user is experiencing several breakages per day. Comparing with my own anecdotal experience I'm not surprised but seeing it all in one place just makes one depressed.
Ah, ok, wasn't obvious to me, either. I always wonder, if it's legal in Germany, because you need to have an imprint easily accessible (from any page I think). Might not be relevant for here, but am just curious.
Is there an easy way out of it after? The first time I used that button I had to turn off my Wi-Fi so I could down to the "top" and click the button again without infinite scroll kicking in.
those are mostly minor annoyances that can be avoided by switching to a different product... What is wrong with tech is that proper regulations to protect customers have mainly not been written yet or are outdated (mainly for privacy issues).
Why don't you suggest alternate products that don't have these problems?
no, we are victims of how Google and other companies are allowed to design their systems because the regulations are nonexistent or outdated.... forget about the drawer this is just stupid to think that it is a big problem.
Claiming Reminders can be written in 600 lines of Ruby is pretty ignorant. That reminds me of those posts that claim they could have written <some famous app> in a single weekend. Reminders is far more powerful than a school Todo app programming assignment.
This safety mechanism is not there if the drawer is embedded in a larger frame where tipping over is not possible.
Sometimes it's not bad UX, it's just the thing trying to protect you from your stupidity.