Apple’s first online store played a crucial role in the company’s resurgence
appleinsider.com
appleinsider.com
Also interesting that Jobs had Apple pay to use Amazon's one click ordering patent at a time when other online retailers didn't see the point of removing sales friction.
> Why Amazon’s ‘1-Click’ Ordering Was a Game Changer
https://knowledge.wharton.upenn.edu/podcast/knowledge-at-wha...
I thought gateway 2000 was a big online retailer around that time. In fact I thought it was them more than Dell that lead the online push.
I guess I’m misremembering as it was 25 years ago.
Thus when Apple opened its own store it was seen as a desperate gamble (perhaps it was? I no longer remember) and destined to fail.
The longer I stay in this industry, and the more I learn about compliance, customer surprise, and the difficulty in balancing usability/simplicity with flexibility/customizability, the more I realize it absolutely was.
Edit: maybe not O'Reilly, since he penned this [1]. Maybe it was Kevin Kelly?
Not sure what the OP had in mind, but my current favorite example is Expedia. I have used Expedia consistently for over 15 years. Have bought many flights for the family etc. over the years. They know who I travel with. Yet if I open Expedia now to book a flight, I will have to enter the ages of my kids again, as if Expedia didn't know their birthdays. Apparently it is difficult to get the balance correct.
I'm sure everyone on this site knows that it would not be difficult at all to implement this.
Perhaps there is some valid legal concern over remembering minors' data, but if so, you can pretty easily come up with another dozen examples of sites elsewhere having similar issues with non-sensitive data.
The problem is that you usually have to have someone who is actually passionate about the product to drive all these little things home. Maybe this was a bug that was the next item on their backlog, but then someone in the chain of command said "it's good enough now, ship it.", and then everyone got moved on to the next thing.
Almost everyone at most companies, at all levels, is just doing a job. Very few people actually care about the product.
I never heard of anything nonobvious at the time either.
For technical difficulty, it's certainly no less difficult than storing credit card details for reuse, and that passed muster at the PTO.
All that said, I am excited to see what's (hopefully?) coming. A travel site should be able to intuit what kind of trip I'm planning, or ask me if it's not obvious. If I do a search for a city that I fly to every other week, perhaps it's okay to just go ahead and sort to the top the same flights and hotel I used last time. If the flight is in the summer and to a popular vacation area, perhaps guess that my family will also be traveling.
These things have all been technically possible for decades, but we don't see them in the wild. Maybe they are less obvious or more difficult than they appear from the outside (I have never built a travel agent).
I think that's true about a lot of innovation.
So yes, the elevator pitch is just "remember the shipping and billing details, and use it by default".
But the question is the edge cases:
First, you have to remember that this came at a time when people were still nervous about even giving your credit card to a website. Cross-web identity wasn't a thing, password managers weren't a thing.
Second, you need intelligence for what are the default options to select? It's easy for iTunes when the delivery is digital, or for a Prime member when 99% of the time the shipping is free.
But what about for everyone else - should 1 click choose the fastest shipping or the cheapest? Is there a 3rd option? OK, you might say the customer should be able to customize that in the profile. But A) what if they don't, and B) what are the extreme edge cases? If someone wants it the fastest, is it worth it if it costs 100$? Or is it a % of the cost of the good? Is faster shipping by 1 day worth it if the shipping costs twice as much?
And so on.
Even though this article was published today, the video link is dead due to the posting account ("SteveJobsArchive") being terminated. I found a mirror here, though, and the audio seems fine: https://vimeo.com/30998833
I didn’t realize SteveJobsArchive was dead though. Dammit all.
Try using headphones or stereo speakers, or download the video and play it back in a program like VLC that lets you select just one of the audio channels to play.
This is pretty precious.
Uhh...
12,000,000 / 30 = 400,000
If I wanted to be charitable, I could guess that they might have gotten their numbers mixed up talking about net and gross revenue, but... This feels like a pretty big oversight.
It did the MVC-ORM-Persistance-Templates so early, and so well.
It's pretty widely recognized that Apple was circling the drain in the '90s, and things didn't turn around until they bought NeXT and put Steve in the CEO chair. Since that point, they haven't needed "saving". All these different stories you see are about the changes Steve made to the company that probably contributed to the turnaround.
If Steve hadn’t made drastic (successful!) changes fast, there would be no Apple. They really were right on the edge.
(Sculley worked for Pepsi at the time.)
Seems silly to take their website down for new products.
I assume that in ye olde days they were actually switching the website over with new products, or had some other reasonable technical explanation. These days I have to believe it's just for nostalgia or something.
> Apple’s multi-terabit, $100M CDN is live
https://arstechnica.com/information-technology/2014/07/apple...
I agree with another comment here that it’s more of a showmanship thing/making it more of an event these days.
And the white cabling with the silhouettes
MacOS became big because of the included Unix. Developers flocked. And al ballman once said... developers, developers, developers!
The iPod (which was not at all developer friendly) saved Apple commercially for several years. Yes, the Mac business had turned around a few years before, but e.g. the year before the iPod, Apple had the disastrous Power Mac G4 cube launch, which led to some unprofitable quarters. The iPod ensured that Apple's fortunes were no longer tied to new Macs (even though there were no G4 cube repeats).
And the big influx of developers came with iPhone. Not sure that Unix was that important a selling argument in that segment — it's certainly there behind the scenes, but does not play much of a role in developing.
iTunes on Windows was also key, as that let the iPod blow up with Windows users (using Rhapsody before that was awful). Those iPod sales really allowed them to build up their cash hoard.
Basically a very expensive PC built together with custom OS, without any possibility to extend or modify it, very un-hacker if I may say so. If you used it as Windows machine it was much smarter to go to similarly-priced enterprise laptops, which offered things like NBD on-site warranty repairs (I had whole keyboard block replaced once on Dell, from manifestation to fix it took maybe 1 hour and I just took a long coffee break), with which Apple simply couldn't compete in business segments.
iPod Linux: https://en.wikipedia.org/wiki/IPodLinux
Rockbox Firmware for an Archos and then an Nano w/ color and no WiFi: https://en.wikipedia.org/wiki/Rockbox
podman run --rm -it docker.io/busybox
xcode-select -p
# installing homebrew installs the xcode CLI tools:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
brew install podman
brew install --cask podman-desktop
https://mac.install.guide/commandlinetools/3.htmlHow to add a Software repository to an OS. Software repository; SLSA, Sigstore, DevSecOps: https://en.wikipedia.org/wiki/Software_repository
W/ Ansible:
osx_defaults_module: https://docs.ansible.com/ansible/latest/collections/communit...
honebrew_tap_module: https://docs.ansible.com/ansible/latest/collections/communit...
honebrew_module: https://docs.ansible.com/ansible/latest/collections/communit...
homebrew_cask_module https://docs.ansible.com/ansible/latest/collections/communit...
From my upgrade_mac.sh: https://github.com/westurner/dotfiles/blob/develop/scripts/u... :
upgrade_macos() {
softwareupdate --list
softwareupdate --download
softwareupdate --install --all --restart
}> GitHub Actions currently charges $0.16 *per minute* for the macOS M1 Runners. That comes out to $84,096 for 1 machine year
GitHub Runner is written in Go; it fetches tasks from GitHub Actions and posts the results back to the Pull Request that spawned the build.
nektos/act is how Gitea Actions builds GitHub Actions workflow YAML build definition documents. https://github.com/nektos/act
From https://twitter.com/MatthewCroughan/status/17200423527675700... :
> This is the macOS Ventura installer running in 30 VMs, in 30 #nix derivations at once. It gets the installer from Apple, automates the installation using Tesseract OCR and TCL Expect scripts. This is to test the repeatability. A single function call `makeDarwinImage`.
With a Multi-Stage Dockerfile/Containerfild, you can have a dev environment like xcode or gcc+make in the first stage that builds the package, and then the second stage the package is installed and tested, and then the package is signed and published to a package repo / app store / OCI container image repository.
Continuous integration: https://en.wikipedia.org/wiki/Continuous_integration
Is there a good way to do automated testing like pytest+Hypothesis+tox w/ e.g. the Swift programming language for computers? CloudFuzz is built upon OSS-Fuzz.
SLSA now specifies builders for signing things correctly in CI builds with keys in RAM on the build workers.
"Build your own SLSA 3+ provenance builder on GitHub Actions" https://slsa.dev/blog/2023/08/bring-your-own-builder-github