moleperson

Daily charging for normal use isn't so much an issue once it becomes a habit, but battery life during extremely long (24+ hour) activities is pretty much a make-or-break feature for me.

I've done some 50ks and while truthfully I may never do an ultra that requires that much battery life, choosing a device that can't almost feels like admitting defeat. It's kind of stupid but I know I'm not alone in that thought process.

I recently worked for a company with a large C++ codebase. For many years they relied entirely on asserts in QA builds to catch errors, no unit testing or production asserts. When I joined about three years ago they had just started to pick up unit testing, and would be enabling asserts in production “soon” (once all the most common ones had been fixed).

I left a little over a month ago, and the status on that was still “soon”. Some bad practices early on are just really hard to dig yourself out of.

Out of curiosity, what's the portable keyboard you like?

Right next to my apartment building is a crosswalk that crosses a fairly busy street. The crosswalk is well-marked, and it has a sign in the median specifically stating that stopping for pedestrians is required by law. In the time I've lived here I've nearly been hit by cars several times on this crosswalk, and I've witnessed countless people almost get hit here as well. Once I saw a pedestrian yell at the driver, and the driver yelled back that they didn't have to stop because "I don't have a stop sign".

I noticed recently that the city installed a flock camera pointed directly at this crosswalk, and while I'm generally opposed to this kind of surveillance, and I wish they would implement other measures to make this safer, I really would love nothing more than for drivers speeding through here and not stopping for pedestrians to get ticketed. It's unclear still whether that's actually happening (and not that it matters once you're dead), but I'm finding myself empathizing with the argument for more surveillance for the first time in my life.

> For instance, the fact that the laws of physics are the same today as they were yesterday and will be tomorrow — a symmetry known as time translation symmetry, represented by the Lie group consisting of the real numbers — implies that the universe’s energy must be conserved, and vice versa. “I think, even now, it’s a very surprising result,” Alekseev said.

Maybe I’m misunderstanding the implication here but wouldn’t it be much more surprising if that weren’t the case?

I'm not at all advocating for treating life like a lottery. I've had overall a successful career due in large part to my own effort, but the best opportunities have come to me simply by being in the right place at the right time, so it would be arrogant to discount luck entirely. I've also had periods of repeated failure, and if I had counted each and every one of those as a score against my own value then I wouldn't have made it this far. Put more simply, the healthy mindset I have is to do what you can, and accept what you can't. Sometimes things work out, sometimes they don't. Easier said than done.

It seems like you're misinterpreting my words through the lens of your own frustrations right now, so I don't think there's anything else I can say to help you. I just hope you find what you're looking for eventually.

Again, I think you've completely misinterpreted the post as well as what I'm trying to say. A "healthy mindset" is simply one that gives you a framework to navigate the world without falling into despair when things don't go your way. Learning to accept that things won't always go your way, and that in some cases they might not go your way the majority of the time, but that they don't have to, is one component of that.

I'm not making any recommendations on how people should actually go about finding wealth, or success, or happiness, or whatever it is you're looking for in life; only how to deal with it when they don't get those things immediately.

> Applying in the hope they mess up and admit you when they're really better off rejecting you is so antisocial.

What? That's not what I'm suggesting at all. I just found the post to be a helpful reminder of how to have a healthy mindset towards some uncertainties in life, but it seems like you took away something completely different.

The way I read this is that there are many "games" in life (applying for schools, jobs, dating, etc) where the odds of "winning" each instance are not in your favor, but you only need to win once to win overall. If you treat every absence of a positive outcome as a failure, then you're inevitably going to lose hope and give up.

This is in contrast to gambling where you actually do need to win more often than not to win overall.

Right, I didn’t think about the shebang case being different. Thanks!

Why is the ‘-S’ argument to ‘env’ needed? Based on the man page it doesn’t appear to be doing anything useful here, and in practice it doesn’t either.

This actually looks perfect for me. I travel often with my steam deck, and sometimes pack an xbox controller or two to play local multiplayer with friends but this is a much less bulky alternative.

What's wrong with Bitwig engineering?

Even if Python used the anonymous function syntax proposed, people would still call them "lambdas". If you want to have aa keyword for this, you might as well name it after what most people are going to type into Google when searching for it.

I really despise the idea that we should let the manufacturer decide what's best for us with no out based on the premise of protecting people who don't know any better. As technology becomes an increasingly integral part of our lives, people need to be able to think for themselves and understand the consequences of how they interact with software.

Also as someone who's grandmother started her own software company and was a programmer since the days of punchcards, I find these "what about grandma" appeals very repetitive and kind of insulting.

It sounded like the underlying issue was the OS reusing the same int value for the file descriptor (2), rather than a dangling FILE*, which AFIK is not something rust could prevent. The only way you could really prevent this is if the OS generated GUIDs for newly opened files.

I’ve spent countless hours playing insta-team on Venice. Any Linux distro which doesn’t include Sauerbraten in its package repo isn’t one worth using, IMO