Calling ObjC via your language of choice is like the easiest thing possible, solved multiple times over. Signing and notarizing outside of Xcode is also a solved problem.
IME people bitch about this but when push comes to shove just don’t want to do the required work, typically on flimsy grounds. It’s just not that hard.
The increase in Swift-only frameworks will eventually be a problem but it’s typically not a blocker right now.
> Everyone complains and then everyone lines up and buys Macs again.
Yeah, because the rest of the laptop industry seems to be eternally asleep at the wheel, unable to build anything remotely as efficient and premium feeling.
Most developers I know "use" macOS the same way they "use" Linux: you have a browser with a million tabs open, a terminal (or several), and a chat application or two. It's effectively the same experience whether you're using macOS or Linux, but with the former you at least don't feel like you're typing away on some plastic shell that overheats at the drop of a hat.
I help out with an emulation community. Any time anyone with a 2019 MBP comes in with issues, I stop them from giving any more details and just have them check this first.
“Upgradable hardware on a laptop” is a loud minority.
I want open hardware. I want to know what’s running on my machine. I don’t really give two shits if the RAM is soldered because I will probably upgrade when (if) it becomes a problem.
Half the articles about Japanese culture are "off topic" yet rocket to the front page without issue.
i.e, on or off topic hasn't been the deciding factor on that for some time now. Pretty sure the rules even state that it's about "what people find interesting".
I think the politics of the USA becoming so entangled with the tech scene to be quite interesting, it's definitely not a phenomenon I expected to see given the ethos of the industry when I started my career in the early 2000s.
Seeing the support from the previous SV "rebels" for the demolition of US's institutions is interesting.
A lot of people in tech today think politics is something “other” to tech. It’s the same kind of “we just make the thing, how it’s used, by whom, for what, and why is someone else’s problem” that pervades the likes of Meta Platforms Inc. With today’s technology industry, thinking like that is naive at best.
The worst of the worst tech bros and their earlier investors (like Marc A) created and have tried hard to spread that idea around. The goal is to keep politics out of the tech workforce so that they can meddle in politics without fighting multiple fronts.
You’re not supposed to say that though, for that’s saying the quiet part out loud. The sad thing is how many people buy it hook line and sinker.
Which isn’t to say you’re somehow wrong for wanting a safe space away from political discourse. It’s important not to forget how empowering silence and ignorance are to causes that typically undermine the rights of the populace.
> Which isn’t to say you’re somehow wrong for wanting a safe space away from political discourse. It’s important not to forget how empowering silence and ignorance are to causes that typically undermine the rights of the populace.
I feel like these two statements nearly contradict each other. Maybe the second sentence should have begun with "However,..."
Either way, I totally agree that apathy is enemy #1 and policies that enable censorship for any reason are enemy #2.
You shouldn't use reqwest on mobile devices, you should be using the built-in platform-specific HTTP libraries.
On Android this appears to be less of an issue, but on iOS there's documentation floating around that you really want to use e.g NSURLSession for battery/radio reasons. Spotify even went so far as to write a cross-platform lib for this kind of thing some years back.
Dioxus has this idea stuck that it's webview only. They're actively working on (and ship at least in some form of alpha or beta) a native-renderer backend.
Calling ObjC via your language of choice is like the easiest thing possible, solved multiple times over. Signing and notarizing outside of Xcode is also a solved problem.
IME people bitch about this but when push comes to shove just don’t want to do the required work, typically on flimsy grounds. It’s just not that hard.
The increase in Swift-only frameworks will eventually be a problem but it’s typically not a blocker right now.
reply