As a Linux gamer, I run just about everything in wine since proton uses wine.
I moved to a cardinal area from an area that didn't have them, and it blew my mind to see one for the first time. They are gorgeous birds. They are also annoying as fuck. But they are so pretty while they are annoying.
Sort of like my cat.
Maybe Google can work with Google on implementing a user-level API for Android so manufacturers don't have a monopoly on RCS apps.
I'm the opposite. I am so bad at coming up with ideas, but writing code for a new project with no tech debt is exhilarating.
I wonder if McAfee changing their name to Trellix to escape how much the general public hates them will work better than Comcast rebranding as Xfinity.
Jar-Jar warned us. "The suns doin' murder to meesa skin"
I love that Disney's portrayal of him is that he's an absolute unstoppable force and no one stands a chance against him. All they can really hope to do is run away.
When I was in college and learning programming, I believed that anything could be programmed. Anything was possible if you were good enough at programming. Then I joined the industry and learned just how stupid requests from product managers are.
My favorite, and I have told this story dozens of times on the internet: we just got our first test board back from the manufacturer. It was our first product with a 64 bit processor. We get called into a meeting because the product manager read an article on the internet about how 64 bit processors can reduce battery life. Without any further info about under what conditions, if our use case meets those conditions, and by how much battery life could be reduced, the product manager asked me to write some code to emulate a 32 bit CPU on the 64 bit CPU so we aren't affected by this battery life issue. Ignoring the fact that I am a Java developer that writes appcode and have no fucking clue about anything this close to the hardware, even if we did successfully emulate a 32 bit processor, there's absolutely no guarantee that it would actually fix the issue, because at the end of the day, the hardware is physically a 64 bit processor, and since I didn't read the article he was talking about, I have no clue what about the 64 bit processor might cause what was described. It could be something inherently about the hardware, I have no clue. I wouldn't even be surprised if it was just a clickbait article and only in very specific situations your battery life could be reduced by 0.1%. Anyway, I told him I was pretty sure that was impossible, but I'm far from an expert in this field. He told me to do some research on it. So I played with my phone for the rest of the day and in the follow up meeting the next day, I told him I did a ton of research and that it was impossible.
I'd like to think the Japanese government wouldn't approve that.
I use command line a lot. I hate needing to add backslashes before spaces or put quotes around file names. It's easier to just use underscores.
Just FYI, we have recently had a huge influx of electronic systems asking for tips in places that tips didn't exist before. I only tip when I sit down to eat at a restaurant and they serve me. If you walk up to the counter to order, you don't tip. If you are ordering takeout (even at a sit-down restaurant), you don't tip.
It's a really fucking stupid system that most of us hate, but if you don't participate, you are the asshole according to our culture (even though we know it's really the businesses not paying their employees enough that are really the assholes)
Edit: oh, and then "suggested tip" went up around the same time that these electronic systems popped up. My whole life, a 10% tip was bad, a 15% tip was average. A 20% tip was good. Now it seems the "suggested tip" says you should tip 20% minimum. I think this is bullshit, and I ignore it. The people who are suggesting the tip are the ones that benefit from it going higher. They are always going to try to increase it as long as they can get away with it. I stick to the 10/15/20% rule.
I was the lead engineer on an Openwrt router for 2 years at my old job. Their documentation is complete and utter shit, but their design is extremely intuitive. Whenever I said to myself, "hell, let's just try this and see if it works," it had an insanely high success rate.
I didn't know Lua going into this project, but when I left the company, it made me really wonder why more people don't use Lua. It's a really nice language.
I really enjoyed having my own open source router that I could just drop new features into by adding packages and recompiling. I was sad when I had to send all my dev units back.