cornfutes
The problem was that it had a resistive touch screen. Samsung already had touchscreen MP3 players that you can install apps on, but it was the capacitive touch at that price point that gave Apple a good 3+ year head start on software. At the time, being able to dial phone numbers with IPhone was mind blowing versus a resistive touch
That’s what was revolutionary about IPhone. They didn’t invent capacitive but they brought it to the $1k range.
Nokia was developing their own OS and App Store, too, but it was the iPhone’s cohesive experience that made everything else fit together
Has anyone done the cost + risk assessment of building a for-profit product on top of this? Would love to know, as I am working on a web IDE with collaboration. There’s also the matter of obscuring client data from 3rd and even 1st party.
Money to go do something else.
You must be American.
You used to be able to login with IRS credentials, but now it's a hard requirement to use ID.me credentials. So I created an account and had to verify my identity. The automated verification failed, so I waited 20 minutes on the phone to talk to one of the representatives. There was a checkbox to consent to having the meeting recorded. I opted out but the submit was disabled. Even before this, they took a 3d scan of my face. None of this seems like choice and options.
By the way, ID.me is a private company. They're even squatting on HackerNews: https://news.ycombinator.com/item?id=13831921&
How is this not a web service?
> Would anyone suggest replacing TeX with a "modern" alternative simply because it's newer?
No, “modern” implies that the existing solutions have some shortcomings which are perceived to be due to old age or legacy/tech debt.
That’s why no one is proposing an alternative to TeX.
Whether that perception of old age therefore bad is valid or not is a different question. Chances are that the “modern” solution will end up reinventing the wheel and rediscovering why the old tools did things a particular way.
Other times modern means the new tool cherry-pick the best part of its predecessors and omit the bad parts.
And also a tendency to not have experiencing working on large web apps (I’m talking 100k+ cloc) where issues arise, and why those React engineers made the decisions that they did
Actually, it was Svelte who coined the term and sold us on the idea of reactivity by default. I don’t think anybody asked for “Reactivity by default”. Svelte advanced this idea, and it helped the framework gain traction. It was easy to get started, and gave Svelte this sense of better ergonomics than other frameworks. I was always skeptical about the performance claims, amortized, and the real selling point of Svelte was ergonomics and the dev experience.
The problem with the Node.js ecosystem is the devs are borderline marketing and sales type. They’ll justify, rationalize and make things sound good after the fact. Previously, Svelte was persuading us that Svelte was better than the rest because of reactivity by default. Now they did a literal 180. It’s probably in the right direction, and maybe how things should have been. A related symptom of the Node.js ecosystem is reinventing and rediscovering the wheel. The problem here is a lost of trust. Anything else which Svelte purports it’s got figured out or is more enlightened about should be taken with a grain of salt.
So it seems those boring FANG engineers with React has it right all along. They had experiencing building sufficiently complex apps where verbose but explicit code was necessary.
> Because the compiler can 'see' where count is referenced, the generated code is highly efficient
Yeah, I don’t believe such claims anymore. Sure, in cherry picked and constrained settings, the performance benchmarks might seem good. As much as I hate to admit, I will reach for the production ready and battle tested React, as boring as it is.
Then why do you need bloated web UI that's not performant as React, Vue, Angular, Svelte? You can also just add 1 line of css classes to HTML elements to have transitions if you use a library like Animate.css.
It feels like there is a lot of brigading and shilling of Astro throughout this thread, as typical with web frontend frameworks.
Or you can have a webpage that serves useful information to 100,000 people.
My motivation is that there seems to be some consistency issues with the backend. I save a spot, and then it gets reverted. Given that I have over 6,000 spots saved, it’s impossible to keep track of when Google didn’t commit or, worst, reverted a past pin.
I’m pretty OCD about n%-completion of my travels.
Being a war criminal