vvvvtt340

Let's say I'm upgrading a large software enterprise application. I start the upgrade process. After 5 minutes, the process determines that the upgrade will require an extra 1.5GB of storage and asks me if I would like to continue with the upgrade. After 15 minutes, I'm presented with a username / password prompt to enter credentials to retrieve a package from an external resource needed for the upgrade. After another 5 minutes, the upgrade process has detected that there are a number of derelict files detected and asks for permission to remove these files.

I switched from Android to iOS a few years ago. I used to be deep into Android customization - custom ROMs, custom icon packs, etc. But today, I feel that iOS and Android offer pretty all the features that I could ever want. My deciding factors when I switched:

- iOS UI animations are significantly better

- access to iMessage

- Apple got around to adding their version of "always on display"

- I turn the vast majority of notifications off, so Android's better notification management stopped mattering to me

- It felt like Google kept bending Android towards iOS anyway (camera app, moving away from the 3 button navigation)

One example I can think of is the "immer" package / the "produce" function:

https://immerjs.github.io/immer/

https://immerjs.github.io/immer/api

The API page lists numerous functions, but the bottom of the page says "In most cases, the only thing you need to import from Immer is produce".

My thought is, immer does something novel, but the vast majority of functionality can be covered in one function.

I think another problem with the "left-pad" situation is the lacking "JavaScript standard library", but that situation is improving over time, especially now that IE11 is deprecated so it's a reasonable expectation to develop against Chrome / Firefox / Safari which are actively maintained and continue to implement new JavaScript features.

I love svelte too, but I would argue that the way svelte extends JavaScript by making reactivity a language primitive pushes svelte beyond "the old web, just better".

https://gist.github.com/Rich-Harris/0f910048478c2a6505d1c321...

https://svelte.dev/docs/svelte-components#script-3-$-marks-a...

https://svelte.dev/docs/svelte-components#script-4-prefix-st...

I think this is a fair point. Taking a look at the product page for the $300 HomePod (https://www.apple.com/homepod-2nd-generation/), I would argue that the HomePod is marketed more as a speaker with Siri integration rather than a Siri device with a really good speaker.

The bullet points I see on the above page, in order, are - really good speaker - Siri integration - integrates with Apple ecosystem for playing music - smart home integration - "private and secure" whatever that means

So, it's not clear to me that "a better Siri" would necessarily result in selling X amount more speakers to make Siri a worthy investment while investing in better audio technology does because it's the main selling point for HomePods.

I don't think Siri's quality is a good indication of Apple's ability to come out with a successful LLM product in the future.

One thing I think about is how Alexa is apparently considered a failure at Amazon (https://arstechnica.com/gadgets/2022/11/amazon-alexa-is-a-co...). Alexa devices sell well but people only use them for trivial use cases that are hard to monetize.

I speculate that Apple doesn't see a need to invest in Siri because the market has shown that digital assistants don't synergize with "services" that well.

Additionally, I don't think that Apple will need to leverage the "Siri codebase" as a starting point for releasing a compelling LLM codebase - maybe voice recognition, but who knows.

Apple has shown through other product launches that they will take a "wait and see" approach and release something when its ready.

I really enjoyed this article. I would recommend others check out "Advice That Actually Worked For Me" by the same author. This same topic is mentioned in #6. https://nabeelqu.substack.com/p/advice