CapeWearingAeroplane

@CapeWearingAeroplane@sopuli.xyz

This profile is from a federated server and may be incomplete. Browse more on the original instance.

CapeWearingAeroplane,

Vsauce for me as well, I like veritasium, because I feel like the questions being asked/answered are legitimately interesting questions/answers. With Vsauce I feel like the whole thing is just about him constructing unnecessarily “out of the box” answers in order to look smart.

CapeWearingAeroplane,

I don’t know if this is done in practice, but if you have a nuclear powered sub, implementing a water electrolyzer that makes oxygen is fairly trivial. Then you have air as long as you have power, so they could in principle stay submerged for ≈ 20 years, or however long the nuclear reactors can go without refill.

CapeWearingAeroplane, (edited )

If you’re “tired of fighting” it still costs you little to nothing to support those fighting, or at least not speak condescendingly about the fight they are fighting. Something about your comment tells me you weren’t fighting much in the first place.

CapeWearingAeroplane,

Honestly, this makes me feel good about my habit for peeling off / throwing away those little ad stickers and cards whenever I see them somewhere and people aren’t looking.

It ain’t much, but it’s honest work.

CapeWearingAeroplane,

Came here to say this, I use DD.MM.YY in day-to-day stuff, but for files it’s either YYYY_MM_DD or YY_MM_DD, the automatic ordering is beautiful

CapeWearingAeroplane, (edited )

“I can reuse this old function if I just monkey-patch this other class to work with it, no one will have any issues understanding what’s going on”

Edit: Thought this was the programmerhumor community. For context: A monkey-patch is when you write code that changes the behaviour of some completely different code when it is running, thus making its inner workings completely incomprehensible to the poor programmer using or reading your code.

CapeWearingAeroplane,

I was starting to get issues with a macbook from 2012 (specifically homebrew / xcode) when I upgraded. I’m going to be honest: Having a powerhouse of a machine for 10 years before it becomes obsolete, I’m not going to complain for one second. Got myself a new macbook, and it runs like the wind. Works seamlessly with all the tools I need in an environment where we rely on gfortran / gcc, and a lot of my coworkers use Linux.

To be fair: Part of the reason I waited for so long before upgrading was that I was waiting for them to ditch the butterfly keyboard / touchbar, and get some ports back into the machine. Once they did that I was sold. My only issue with macbooks would be the absurd price for an adequate amount of RAM, but as far as having a good computer, once it’s paid for it’s fantastic.

CapeWearingAeroplane,

Ok, it’s true that you have to spend 15 mins after setting up to “install developer tools”, and remove some safety rails. However, the mac doesn’t prevent you from doing that, and doesn’t really even try to make it hard (if you’ve ever touched a terminal before). Once it’s set up, you’re good to go…

CapeWearingAeroplane,

I honestly don’t see why, when I’m looking for help on some problem on a mac, I’ll happily open a Linux forum, and throw whatever commands I need into the terminal. Works like a charm every time. Just replace apt with brew or some other reasonable package manager (idk if macports or whatever is actually any decent, never tried it)

CapeWearingAeroplane,

I can agree that fighting apples UI’s can get frustrating (i.e. playing the “try to find the right button” game). What makes me think macs are great is that you get all the freedom you could wish for in a terminal that is unix-compliant, while also getting the reliability of a hugely widespread OS that a bunch of good developers are paid to maintain. With the new macs you also get the apple silicon hardware, which is great.

I think most people that use macs indeed do need the safety rails, but at the same time they bother me. I know how to disable them within 15 mins of setting up my computer, but if I’m helping someone with an issue, I sometimes first need to spend some time disabling safety nets and installing the tools I need. Also: Shoving iCloud storage down my throat is shit. They should stop that.

CapeWearingAeroplane,

Easy: Nothing beats the simplicity of brew install whatever or apt install whatever, and then having whatever just work, in my experience, pretty much every single time.

CapeWearingAeroplane, (edited )

cd ~/ && open .

idk how hard or unintuitive that is?

CapeWearingAeroplane,

wat? You have the whole gcc suite on macOS. What kind of black magic are you trying to compile? I’ve cross-compiled a bunch of libraries for mac on intel and arm chips without much issues…?

CapeWearingAeroplane,

what do you mean? clang is a command line tool, can’t you write some cmake and a bash script to automate the build process? That’s what I always do when I writing any C++ that needs to be compiled/updated fairly regularly.

CapeWearingAeroplane, (edited )

I have to admit, I’ve never touched the kind of issue where I need to load a bunch of binaries I can’t automatically trust as part of a build process, so I won’t speak on that.

On the part about OS updates being a PITA, yes: I’ll admit that I offset updating the macOS major version for as long as possible. As long as my major version is maintained/get’s security updates, and the newer versions are backwards compatible enough that I can compile stuff for them without any hassle, I’ll stay on macOS 13. Judging by historical data, that means I have about two more years before I might need to spend an hour or two fixing up stuff that bugs out with the eventual major update.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #