An iOS question:
From what I can tell, the "Ringer and alerts" setting controls both notifications and my alarm. I need a loud alarm to wake up, so I set it to max, but that means my ears blow out every time I get a notification with earbuds in.
Is there some way to have a loud alarm without destroying my ears with every notification? If so, how? If not, how did anyone think the current system was a good idea?
It would be even worse if I used Chrome. There, I'm pretty sure that logging into my work Google Drive account would log into my work Chrome account for browser sync, and logging into my personal YouTube account would mean logging into my personal Chrome account for sync.
Google seems completely unable to understand the concept that one person might have multiple Google accounts. Weird, since they're pushing for everyone to have a work Google account plus a personal Google account.
I hate this consolidation of services. Streaming videos has nothing to do with downloading work files. But just because both services happen to be owned by Google, the two accounts are linked. It's literally impossible, from what I can tell, to be logged in to one YouTube account and a different Google Drive account in the same web browser.
I have a work profile of Firefox which is logged in to my work Google account for Google Drive.
I wish I could just keep it logged into my work Google Drive account, while also being logged into my personal YouTube account, because I sometimes want something on in the background while working, and I just don't want that associated with my work account.
But Google owns YouTube, so that's impossible. Can't use one YouTube account while using a different Google account for Drive.
To be clear, Rust will probably be mature _eventually_. I'm not inherently against the "rewrite it in rust" thing, but it currently presents challenges.
Seriously, this isn't some "oh, that service is probably just some employee's side project" thing. This is one of their most important products, and file downloads is one of two central features. To me, this indicates that literally nobody in power inside Google cares about software quality - and that anyone who may care don't have the power to fix things.
Google is worth over a TRILLION dollars. Googles has over a hundred thousand employees. Google is the world's largest web-focused corporation.
Google Drive is one of their flagship products. The main feature of Google Drive is the ability to upload and download files.
WHY IS GOOGLE UNABLE TO IMPLEMENT CORRECT HTTP FILE DOWNLOADS? They're not sending a Content-Length header! This is literally web programming 101!
To support GCC and Clang, I need `#if defined(__SSE2__) && (defined(__clang__) || (!defined(__GNUC__) || __GNUC__ >= 9))`.
This would always enable the vectorized code on Clang versions which claim to support SSE2, and on GCC versions >=9 which claim to support SSE2. It would disable vectorization on all non-Clang compilers which claim to be GCC <= 8 (which means at least the Intel compiler I think).
Programming is terrible.
I vectorized some code with SSE instructions, protected by an `#ifdef __SSE2__`. However, GCC 8 defines `__SSE2__` even though there are some intrinsics not supported until GCC 9.
I could do `#if defined(__SSE2__) && (!defined(__GNUC__) || __GNUC__ >= 9)` to enable SSE only on GCC >=9, but that would exclude Clang because Clang (even Clang 11.0.2) pretends to be GCC 4 (i.e defines __GNUC__ to be 4).
inb4 "Apple sucks, should've bought Android": Yes, Apple sucks. Android also sucks. The lesser evil for me is generally Apple, but I won't defend their practices.
Technology in 2020:
My bluetooth earbuds ran out of battery. Luckily, I have wired earbuds!
Oh, but my Apple gadget doesn't have mini-jack. Luckily, I have Apple earbuds!
Oh, but my Apple earbuds with the Apple connector don't work with my Apple product with the other Apple connector.
Brought to you by the removal of standard audio interfaces and insistence of keeping half the products on Lightning while moving the other half to USB-C.
The absolute worst thing about #golang: You can't just comment something out to try something out while debugging.
Oh, that line was the only line which used a particular variable? Fuck you.
Oh, that line was the only line which used a particular import? Fuck you.
Tau is a cool circle constant. However, wouldn't it be nicer to keep pi, but switch to an angle unit based on the diameter? Pi diameters around the circle is the full rotation, just like tau diameters.
The fundamental problem with pi and radians is that pi is based on the diameter while radians are based on the radius. We don't _have_ to throw out pi to get nice angles, we just have to either base both on the diameter or base both on the radius.
The downside: This idea would never appeal to people who dislike the over-engineered nature of snaps, and people who don't mind the over-engineered nature of snaps wouldn't see a benefit.