91–100 of 278 posts
Earlier quoted context omitted.
200 bytes for the business logic. 47MB for the UI & boilerplate around the business logic. I get that this may be the easiest way to develop and publish an application today, but it's sad that this is the direction we have taken in recent years.
Those who don't learn /usr/bin are destined to reinvent it, poorly.
Earlier quoted context omitted.
Well, if you COULD ship something across the world on a private 747 with extra features to protect your cargo, and it has nearly no environmental downside and has no meaningful downside vs a smaller airplane… you’d probably do it! There’s no incentive in software to get a smaller, more efficient plane, and plenty of incentive to use the big thing for free that has all the extra features
That analogy doesn’t really work here. Because there is a downside. It’s slow, takes up a ton of memory, lots of disk space… When you have so many processes on a modern machine competing for resources, when every app chooses to be bloated and slow it really adds up.
Earlier quoted context omitted.
Why does a Mac-only app that shows a menu bar icon and a notification popup need to be Electron…? That’s 30 lines of Swift, max.
[flagged]
I used to strap 20 virtual eths to my Linux box because my dorm gave only like 512kbps per account, and then aggregated the 20 interfaces.
Earlier quoted context omitted.
Well, if you COULD ship something across the world on a private 747 with extra features to protect your cargo, and it has nearly no environmental downside and has no meaningful downside vs a smaller airplane… you’d probably do it! There’s no incentive in software to get a smaller, more efficient plane, and plenty of incentive to use the big thing for free that has all the extra features
That analogy doesn’t really work here. Because there is a downside. It’s slow, takes up a ton of memory, lots of disk space… When you have so many processes on a modern machine competing for resources, when every app chooses to be bloated and slow it really adds up.
Earlier quoted context omitted.
Modern app bloat in one analogy: Business logic size: ~20 bytes Total app size: ~47 MB = 47,000,000 bytes Bloat factor: 47,000,000 / 20 = 2,350,000 Let’s scale this up and say the business logic is 1 pound. Then the whole app would weigh: 1 lb × 2,350,000 = 2,350,000 pounds What weighs ~2.35 million pounds? - A fully loaded Boeing 747-8: ~987,000 lbs - Another fully loaded 747-8: ~987,000 lbs - A blue whale: ~330,000…
Well, if you COULD ship something across the world on a private 747 with extra features to protect your cargo, and it has nearly no environmental downside and has no meaningful downside vs a smaller airplane… you’d probably do it! There’s no incentive in software to get a smaller, more efficient plane, and plenty of incentive to use the big thing for free that has all the extra features
I think this is not the case. E.g., we replace our computers every few years, but not because the new ones can do things that you can't do with your current computer. It's because the software you use to do the same things keeps getting more resource-hungry.
Earlier quoted context omitted.
That analogy doesn’t really work here. Because there is a downside. It’s slow, takes up a ton of memory, lots of disk space… When you have so many processes on a modern machine competing for resources, when every app chooses to be bloated and slow it really adds up.
That is more a tragedy of the commons thing. For each individual app the comparison holds true
Earlier quoted context omitted.
Nice, added it as a bash alias. alias randommac='sudo /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport en0 -z && sudo ifconfig en0 ether $(openssl rand -hex 6 | sed "s/../&:/g; s/:$//")'
So I tried this out on macOS 26 and the `airport` command is no longer there. There is a `airportd.sb` file, which appears to be some permissions based thing in s-expression/LISP. Weird. Edit: Spun up a macOS 15 VM and I got this: WARNING: The airport command line tool is deprecated and will be removed in a future release. For diagnosing Wi-Fi related issues, use the Wireless Diagnostics app or wdutil command line to…
`networksetup -setairportpower en0 on && [... set MAC ...] && networksetup -setairportpower en0 off`
I think it's pretty safe to assume that modern Macs will always have en0 as the WiFi adapter, but if you wanted, you could use `networksetup -listnetworkserviceorder` to find the associated device.
Earlier quoted context omitted.
Those who don't learn /usr/bin are destined to reinvent it, poorly.
What does this mean? I've always understood /usr/bin to be the storage dump for system binaries. Do you see or use it another way?