Also the iOS SDK isn’t freely available, so you’d have to copy that out of an Xcode installation… but given enough time and effort, you could almost certainly hack together a cross-compilation config for Clang that compiles an unsigned iOS app on Linux. Signing it might in fact be the bigger issue, since I’m not aware of any tools that sign Mach-O binaries on Linux.
Should also be noted that macOS does support Bluetooth File Transfer natively, so they did already implement it elsewhere.
JS is fine, it’s more that people overdo it and bundle their heavy, deeply layered frameworks with thousands of npm dependencies for the web. Often times analytics/tracking/ad libraries are a major contributor of bloat, I once shrunk down a package-lock from thousands of lines to a few hundred just by stripping the telemetry libraries from an open-source app.
Use the right tool for the job. Sometimes it’s a static page, sometimes a server-rendered dynamic page and sometimes a single-page application, all of those can be made performant.
Having the ability to overload functions or constructors without a million Stuff::with_x variants is something I consider more ergonomic and not unsafe. I know the Rust community prefers explicitness in many places, but explicitness and safety are somewhat orthogonal in language design. I consider e.g. Swift to be a safe and ergonomic/sugared language, that borrows, no pun intended, a lot of ideas from Rust
As long as you limit yourself to a subset of modern C++, it’s actually a decent language. Less guardrails than Rust, but more syntactic sugar (think overloading, default parameters, implicit this, implicit reference-taking, implicit conversions). You could argue those are anti-features, but even as someone who really likes Rust, I gotta admit C++ is occasionally more ergonomic.
Seriously. There are a lot of parallels between GPUs (or NPUs for ML inference) and quantum processors in terms of being architected towards a more specialized form of computation and I could totally see QPUs being a thing in the future, probably mostly for number cruncing (see Grover/Shor’s algorithms). Though if Grover search suddenly becomes the way of quickly searching for files or something, who knows, maybe this might be more useful for general computing than we think.
In the 80s no one thought computers would be something normal people would use at home, they were seen as a tool for mathematicians and nerds. Now look at the world today. Who knows what the future will hold.
When case insensitivity is the default I always wonder how many apps unknowingly rely on that due to typos somewhere. I encountered this once while porting a Windows/macOS app to Linux that someone imported a module with the wrong case and nobody noticed
It took them a few years, if I remember right, though they did add the unlock-with-watch pretty early.
CMake can also emit its own errors during the configure step though, particularly if you have complicated build logic and/or lots of external packages.
Projects for Apple platforms usually also use .h, where it could mean anything from C/C++ to Objective-C/C++.
In practice, Clang handles mixed C/C++/Obj-C codebases pretty well and determining the language for a header never really felt like an issue since the API would usually already imply it (declaring a C++ class and/or Obj-C class would require the corresponding language to consume it).
If a C++ header is intended to be consumed from C, adding the usual should alleviate the name mangling issues.
A nice example of this is Ardour: A DAW that’s free in the sense that the source code is GPL, but the prebuilt official binaries have to be paid for.
How so? It’s a polished Unix desktop that runs most open-source and a bunch of proprietary apps, including Final Cut and Logic. It’s natively POSIX and has a proper shell.
deleted by creator
This is all fun and games until you try moving a backup to a file system that’s case-insensitive
In principle you can, the Mach-O format is openly documented and implemented in the major compilers. The issue is that you need a sysroot (aka SDK) of the frameworks and headers for your target OS, which in Apple’s case are proprietary and cannot be redistributed legally (you could probably rip them out of a macOS installation yourself though). For iOS apps you’d also need to sign the binaries and install the app to the device which is non-trivial to impossible to do on other platforms.
Arguably mapping out cities to this degree across the globe is a ginormous effort, on an order of magnitude more so than what Google Maps etc. currently provide. Thus I don’t think it’s entirely unreasonable to try designing something that operates purely in terms of sensory input (and of course map data where available, those approaches don’t have to be mutually exclusive).