The Fall of Intel

[Cmaier]

I don’t think you have to limit it to just electron apps. Most PWAs end up being sluggish & way more buggy. Whenever there’s an option I always prefer a native app. 1Password is a sad example of a company that moved from a solid native app to web based; I miss the v2/v3 days, never had as many crashes & needing to restart Safari as I’ve had to since the switch. Really unfortunate.

I had to abandon them after 7, due to security concerns. Luckily apple's own passwords app is slowly reaching feature parity.

 

[Nycturne]

One node once isn't good enough, sure - But if there's promising indications of being able to be one node ahead continuously for several years, that might be - Apple isn't leaving TSMC anytime soon and Apple is definitely not Intel's saviour on the fab business right now. But if Intel does make a viable fab business that remains a node ahead for a couple of years straight, it could be

I'd argue that if they are threatening to exit the business if customers don't show up, there's not much hope for getting folks to take the chance, IMO. Why would I get my designers to work on stuff for a fab that might pull the rug in the near future? Even if I get one node out of Intel, what's to say I'll get a second if they are already eyeing the exit?

I don’t think you have to limit it to just electron apps. Most PWAs end up being sluggish & way more buggy. Whenever there’s an option I always prefer a native app. 1Password is a sad example of a company that moved from a solid native app to web based; I miss the v2/v3 days, never had as many crashes & needing to restart Safari as I’ve had to since the switch. Really unfortunate.

I could have phrased it as "electron or similar", but the point is more that by spinning up a browser process, you get a couple more threads that do work async than you would with a native app. I wasn't trying to speak to the experience itself. Having had to work on React Native and Web the last couple years, I do miss native when it comes to work.

Despite being Electron and (I assume) React Native, I haven't had much in the way of issues with the 1Password apps on macOS/iOS/Linux... the browser extension on the other hand seems to be getting worse in Safari lately.

I had to abandon them after 7, due to security concerns. Luckily apple's own passwords app is slowly reaching feature parity.

The general CVE count, or something architectural about 8+? We still use 1Password as we have shared vaults in our household, but always curious if I'm missing something about what I'm reliant on.

 

[Cmaier]

The general CVE count, or something architectural about 8+? We still use 1Password as we have shared vaults in our household, but always curious if I'm missing something about what I'm reliant on.

Through 7 I was able to host the passwords on a server my employer considered safe. My understanding is this capability went away in 8.

 

[casperes1996]

I'd argue that if they are threatening to exit the business if customers don't show up, there's not much hope for getting folks to take the chance, IMO. Why would I get my designers to work on stuff for a fab that might pull the rug in the near future? Even if I get one node out of Intel, what's to say I'll get a second if they are already eyeing the exit?

Fully agree - I was purely arguing from a theoretical standpoint that it could be possible to get Apple off of TSMC - It doesn't seem like that's in the cards right now though.

I could have phrased it as "electron or similar", but the point is more that by spinning up a browser process, you get a couple more threads that do work async than you would with a native app. I wasn't trying to speak to the experience itself. Having had to work on React Native and Web the last couple years, I do miss native when it comes to work.

Despite being Electron and (I assume) React Native, I haven't had much in the way of issues with the 1Password apps on macOS/iOS/Linux... the browser extension on the other hand seems to be getting worse in Safari lately.

Experientially Electron apps and its elk have been decent enough for me for a while. No major complaints, really.
Philosophically I am opposed to them though. I find it such a shame that we waste computing resources to the degree we do parsing and interpreting web apps instead of running code made for our machines. Even if the machines I use are fast enough that it doesn't matter from a UX perspective, I still think it a shame. I don't mind abstracting away the machine; Abstraction is one of the beautiful things about computer science. A user process doesn't need to know if a file is on a USB flash drive or an internal HDD or a network drive, it can just call read and delegate the responsibility of giving it bytes in a buffer along. Fantastic. But with the Electron world, I must admit I see it as abstraction with no benefit. The "benefit" is that you get to write in JS I guess but that to me is a downside

----

As for the password manager conversation; I've always only really used Keychain/Apple Passwords and been happy with it - What has been reasons for you all to use anything else? Keychains have always served me pretty well. And have even allowed me to write automations such I can run a script, log into my keychain with fingerprint and then the script automatically finds and grabs my 2FA key for work's VPN and logs in with it.