I don't see how it qualifies as a legitimate download or ownership. You cannot save the file to a disk you control and you have no way to ensure you have continued access to it. Apple or the IP holder can cause this "download" to dissapear from your device/account without prior warning. Its actually written in the terms.
Afaic, people designing circuits still do care about that.
> Good Assembly
The thing with the current state of coding is that we are not replacing "Coding Java" with something else. We are replacing it with "Coding Java via discussion". And that can be fine at times but it still is a game of diminishing returns.
LLMs still make surprising mistakes, they too often forget specifics, make naive assumptions and happily follow along local minima.
All of the above lead to inflated codebases in the long run which leads to bogged down projects and detached devs.
In case you weren't aware, MacOS uses zsh as the default installed shell. The bash version that comes with MacOS is some ancient 3.x version, from 2005.
Just that it would be `.zshrc` since zsh is already the default shell in the context of this post unless you enjoy a mid-2000s existence and none of the nice bash features of this generation (in which whatever `.bashrc` you've crafted is likely broken by time passing).
Maybe I'm underinformed, but I don't personally know any Linux users who convert to zsh, instead opting for fish or something else (oilsh? nushell?).
Yes, I'll throw my hat into this group too. Bash is fine.
YMMV but I have found using zsh too frictitious to be helpful. Sure, theoretically zsh living in a bash world (lets face it, all scripts are bash) is completely fine but reality seems to differ. Copied a one liner from shell history into your script? Crash. Use arrays? Weird bugs. Use shell builtins? Whoa unexpected interactivity!!! Etc...
Bash is absolutely fine as a default shell. As an added benefit, you don't feel like an invalid once logged in to a container or server.
I also think that it sends the right signal in terms of "Hey, this really doesn't need to be an app". I don't need an app for my newspaper, I need a shortcut/bookmark to its web page.
And once you start thinking about it, the same thing goes for a surprisingly large amount of apps.
I feel like in the coming years the facade big A and big G put up in order to push everyone into their distinctive walled garden of apps will crumble in public opinion.
It never was "yeah, it needs to be an app because the web platform doesn't have an API standard for it", geez, apple even forced a single web engine. They could have easily allowed access to their APIs on the browser. It just never was in their corporate interest to do so.
Okay, this devolved into an anti corporate rant without it being my intention to... So, go web!
I don't really know how to articulate exactly how I'd classify into one bucket or the other but I think there are two types of "app" and I tend to have differing preferences on whether they should be native apps or web apps as a result.
One is where relatively-static content is the priority, deep-linking is important or essential and the web platform is pretty ideal for those. News articles or blogs or Wikipedia pages or those sorts of things. Things where I might want to be switching between tabs or forgetting about for a while and coming back to later.
The other is where the app is primarily interactive or where the content is a lot more likely to be real-time or ephemeral. Not least because if you're on a low-bandwidth or high-RTT connection, navigating between web pages or having interactivity blocked behind a backlog of XHRs (particularly where caching isn't permitted) is utterly miserable. My experience is that native apps usually continue feeling responsive to input even when the network itself is not responsive but that is often not true with many clickable elements in many web pages.
PWAs might be the middle-ground here but they feel a lot like Electron apps to me: still foreign to all platforms, not responsive in the way that native UI controls are, weird/missing "back" behaviours and still no better support for deep-linking than the average app would have.
PWA was an awesome idea and should have been the way forward.
Unfortunately both Google and Apple very early on identified that it was in their best interest to keep the concept around in a half-dead state and ensure nobody really built on it...
You get notification. You can autoplay video/audio. You get whaterver video or element full screen with all necessary UI. You get rotation lock. You have a fullscreen to do what ever you want for any purpose. You probably can't touch hardware APIs(for example: bluetooth/nfc) like native app. But that isn't really needed for most apps either.
On the other side. Apple seems sabotage the PWA as much as possible. You can't autoplay video/audio. You can't even fullscreen anything other than video, and when fullscreen video, UI is ignored. Also there is no way to disable gesture so your app will misfire system gesture. And you can't lock the rotation either. There is no way to auto rotate the video player or whatever when maximized either.
It's really a golden example for pretend to do something while actually not. It seems you can do pretty much everything with ios pwa. And when you try to do it. You will figured out it will have a worse experience than native app because all sort of issues.
To be fair, Android also sabotages PWAs, it's just done behind your back. You see, in order to get a PWA to properly install, you'll have to use Chrome, and you'll have to have a Google Play account and Chrome will submit the PWA manifest for validation to a Google server, which in turn will decide whether the PWA is worthy, and if it is, it will generate a so called WebAPK, which is then installed on your device. If it's not worthy however, then it will become a bookmark instead, and many of the features that can be described in the manifest will not work at all.
So if you wanted to use a different browser or install a PWA without a connection to the internet, or without Google Play, all you get is a bookmark.
In my personal experience, it only validate whether manifest is malformatted though. Although it's still up to google if they want to do something wonky.
I saw someone claim on SO that they were not able to get a PWA to install properly until they changed their IP address, supposedly because they were from Iran, a sanctioned country.
To my knowledge, every PWA installed from Firefox on Android will become a bookmark. For Firefox I believe that means for example that if you try to open a link elsewhere that is within the manifest scope, it will not open in the PWA. That's because it's not possible to deep link to the PWA without it having an AndroidManifest with a corresponding intent filter, which is what the Chrome WebAPK achieves and why they can support for example custom protocol handlers or share targets or launch handling options.
AS I said, YMMV. PWA install has seen many a regression. Last Android release it didn't work for me, this one it does. I presume a lot of it is due to ecosystem variations and API changes.
Google invented PWAs and broke their back trying to make them a thing. I'm not a fan of Google but credit where credit is due.
They were also highly incentivized to develop the APIs that make it all work as Chromebooks are basically hosts for browser apps. Apple, as well as the other tech giants involved in the W3C had no such incentives and were dragging their feet.
Admittedly I am not up to date on the latest developments but as far as a couple years ago the PWA runtime on both ecosystems was significantly stymied in comparison to the APP runtime. No access to real storage functionality, significantly less platform APIs, yada yada.
Sure, you could build "better (installable) websites" but even to get standardized stuff like background execution or notifications working was either impossible or a long series of jumping through hoops. Even installation prompts bugged out way too often.
But to be clear, if that isn't the case any more I will be positively surprized by either platform provider.
As others have mentioned it might even get too spot on on occasion.
reply