I like my Macs precisely because they are boring and almost never surprise me.
TBH, the only reason my Linux boxes surprise me is because I try stupid things such as mounting /var/log as a tmpfs to reduce write loads (mostly on RPis SD cards and eMMC devices).
I don't know about that — macs have enough weird behaviours that it wouldn't totally surprise me if, soon, they required a network connection, or the lack of one would at least make things awkward. For example, the inability to use clamshell mode without AC power.
Amphetamine[0] lets you prevent sleep on lid close. I presume it lets you do so without AC power (but I might be wrong on that), but one of the techniques they use to do that (setting the IOKit key that indicates the system is currently in clamshell mode) definitely does work without AC power. I made a command line utility[1] for myself a while back that does that if you're interested. It works fairly well, but the clamshell state tends to reset upon gaining/losing AC power. That's fine if the lid is open at the time (as the utility just applies the change again), but if the lid is closed, the system sleeps until the lid is opened again (at which point, it reapplies the change and you can close the lid again).
Q. a local mac repair shop installed "new OSX" on a laptop by request .. but it is version 10.12.6 (?) ..
Later, when downloading several common desktop applications, upon opening them.. it says "this software requires v10.13 or later" .. I assume this is completely on purpose to get the legions of happy Mac owners off of their stable OS and into the upgrade churn ? I assume (US here) you have to have to buy OSX 10.13, register an ID with Apple, to get new software (according to them) ?
macOS upgrades have been free since OS X Mavericks[0] (10.9, released in 2013). macOS 10.13 (High Sierra) came out in 2017, so is a 5 year old OS at this point[1]. It also supports all Macs that macOS 10.12 (Sierra) supports[1]. And you don't need an Apple ID for anything other than Apple services and the Mac App Store. OS Upgrades don't need an Apple ID (even on older versions of macOS where they're installed through the Mac App Store), and you can even network boot a recovery image and install the latest version over the network[2] (Intel Macs only).
I'm a bit confused by the question and might be misunderstanding but there is no need to buy OS X upgrades, they're free. But you do need to register with Apple to get them.
You’re not entirely wrong; you do need “Xcode Command Line Tools”. Thankfully, that’s a much smaller bundle than Xcode. It contains a bunch of tools for building code, such as llvm, ld, make, and git.
According to many commenters in the linked thread, it's fixed in MacOS 13.2.1. Not great that it happened at all, but good to see that it was a software issue.
And, if it's something that's worked around in software (meaning, it was a hardware issue), that might have issues for things like Asahi Linux, which probably won't have that workaround in place.
Arguably it would impact the support for other OSes, especially alternative ones who'd need to reverse engineer the workaround and/or write their own to get the network stack working.
It could also fall apart the day Apple decides this machine is not supported anymore, and their next OS won't have the correct drivers anymore. It's their prerogative, but will sure suck for the machine owners.
PING fritz.box (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=11.845 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=24.287 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=3.120 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.630 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.801 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.139 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.772 ms
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=0.784 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=0.674 ms
The above suggestion fixes it, hopefully permanently:
settings->network-><ethernet interface>->details->hardware "change anything, safe and undo"
T3 stack (Next.js, tRPC, Prisma with MySQL, NextAuth, either Tailwind or a component library depending on the project), deployed to Vercel. Maybe swap Prisma for Kysely if cold starts become an issue.
Disclaimer: I maintain an init tool for this stack so I'm somewhat biased
At age 31 I was was working as a part-time university lecturer in a non-stem field plus constantly struggling to find any additional freelance work, couldn't really see a realistic path forward in that career. Had also just become a father, so being broke felt even worse than before. I spent about 18 months learning web dev (just free resources online), and successfully made the career change. Required a lot of sacrifices in that time period though as well as a bit of luck, and I don't think my path is representative of the average person who tries this.
I got a bit frustrated at YouTube dev videos being aimed primarily at entry-level developers, so I tried to record some more mid-level content. There is definitely room for improvement on the production values, but hopefully the content itself makes up for it. Any feedback appreciated :)
I need to use PHP at work sometimes. After working in it for a while I still don't love the language and would never pick it for a project myself, but it's overall decent a few quirks aside, and I think a lot of people have built up a habit of disparaging it without actually knowing much about it.
That being said, one issue I've found is that while I can use VSCode for every other language, using PHP feels terrible if I'm not using a JetBrains IDE. I tried installing the PHP extension pack, but it was still leagues behind. Is there any guide someone can recommend for making PHP a first-class language in VSCode, or am I stuck in phpStorm?
> I think a lot of people have built up a habit of disparaging it without actually knowing much about it.
It's possible that PHP's ubiquity and the core language's poor architecture/design (for decades now) are the source, not the ignorance of those complaining. PHP was the very first programming language I learned, in 1997. If anything, I mostly stopped disparaging it because I simply moved on in my career enough to be able to choose languages that aren't constantly fighting me.
I'm a consultant so I get asked about unfucking PHP codebases every few years, and I check in on the ecosystem and language. It's better but (unsurprisingly) still not great. Meanwhile, languages a decade+ younger avoided PHP's mistakes.
Thinkpad-style? Sure! Ortholinear? Why not!