10,734 karma · joined October 1, 2007
@tolmasky
1. The Monsters are Due on Maple Street: https://en.wikipedia.org/wiki/The_Monsters_Are_Due_on_Maple_...
Like, I get the potential scale is different. But this is some joke video, not someone trying to actually replace David Attenborough or something.
This article is a good example of this. For starters, the "one shell component" thing is kind of a red herring. There's plenty of React components that interact with children, and you can clearly make web components that also "hide all the details". So this seems to be more of a "general" good practice they want to encourage, than anything specifically tied to React or Web Components in particular.
Critically however, the whole idea of "hey, web components still look good before JavaScript!" is either intentionally obtuse or really misses the point of React -- React can have a better non-JavaScript initial render, thanks to SSR, which is significantly harder to do with Web Components. I don't really care if <user-avatar><img></user-avatar> "falls back" to some lame Web 1.0 rendering if my SSR-ed UserAvatar looks identical to the fully "active" component on first paint before any JavaScript runs. That is one of the main selling points of React and React-like systems today. You can't just ignore that completely and expect to convince anyone who's currently using that sort of system. But I understand why they don't address it, since the only real answers involve using some sort of build system with Web Components, which they've also decided to say are the worst thing ever. So their only choice is to compare non-SSR Web Components to non-SSR React Components. And, I dunno, maybe they're better than the way we did things 8 years ago when that was the case? I'd have to think hard about that purely academic question.
The funny thing is that these are often the same people that would push for as little JavaScript as possible, and yet Web Components are fundamentally tied to JavaScript. Whereas React-style components can actually generate fully static JavaScript-free pages if you want to. This sort of situation springs up a lot: Web Components go on and on about not being "shells single components", and yet React-style components make it so much easier to deal with children. You aren't forced into the ugly slot system which immediately removes the "illusion" of it being a "real" HTML component, and is easier to deal with in the catch-all case too. Not to get into another huge differentiation, but I also personally prefer a more "functional" approach of writing a single render function vs. dealing with a bunch of lifetime callbacks to track the changing states of attributes and children.
1. It’s not functionality people were already used to getting for free, so they wouldn't feel like something was being taken away.
2. It's something people have been, quite vocally, asking for for a very long time, so you know that they, well, actually want it.
3. It doesn't lend itself to complaints because typos feel like they're “your fault,” and so it feels more understandable to pay to "fix your mistake."
4. And it can be billed as a pure convenience: "you can always just delete the post and repost it". Even though this misses the point that you lose your retweets, it just adds to point (3) that it feels like a hack they're allowing you to do to fix your mistake.
5. It doesn't negatively affect any existing user dynamics. When you charge a subscription, it's natural to feel like you shouldn't see ads anymore. "What am I paying for if I still see ads?!" This feature is completely orthogonal to every other existing revenue stream.
If they would have just done this at the beginning, I think people would have actually cheered it on, and it doesn't affect any existing user dynamics. No devaluing of blue checkmarks, no risking losing tons of users by making it a for-pay service, and again, there's no hard ceiling on how much revenue you can generate from a single user.
And guess what... a year later, they can still also offer a subscription that gives you 20 edits a month, or 300 edits a year if you pay all year up front, or something like that. So you can still get your subscription payments. And critically, unlike previously, you know what you're paying for. The messaging is simple and you can spin it as a user-friendly move: "Oh wow, the new edits feature is so popular, we decided it made sense to give people a way to get edits cheaper. Our new subscription pricing saves you money!"
Yes, if my non-Apple email service "locks me out", then the same would happen as here. The point however is that:
1. Usually this would only happen if something weird specifically happens on that account. For example, if I am paying for an email provider and my card is declined. Notice that with the Apple case, a problem in something completely unrelated to email can cause this (including apparently the card being flagged for a fraudulent charge on some unrelated service).
2. Even then, usually the next step is I am told that that happened. Notice that in the Apple case they won't even tell you what the situation is to give you a chance to remedy it.
3. Finally, you then almost always have a way to remedy the problem. For example, by giving them a new credit card. Notice in the Apple case they insist that the account is disabled forever.
Do you see the difference? It's not in the "what happens if your email stops working" part, it's in the "what leads to your email not working anymore" and "how do you fix your email" parts.
Additionally, you can't send email. That's also a pretty important part of the whole "email" thing. Any ongoing discussions will just be cut off.
Seems pretty walled garden-y to me, considering the entire framing of this is that nothing bad was done with said email. It was because Apple has a unilateral switch that turns everything off if anything bad happens to an associated credit card. That is to say, if your credit card number is stolen, completely outside of your control, this could happen to your email. I'm not aware of any other email service where that is the case.
1. All your emails if you use iCloud for your email, and thus potentially locking you out of any other sites that use email as a 2-factor-auth.
2. All your backups on iCloud.
3. All your data on iCloud.
4. Every single login you have where you used sign-in-with-Apple.
5. Every app on your phone that you have a paid subscription for.
6. The fallback login mechanism on any of your Macs where you used iCloud as the login fallback.
The list goes on. They ask you to tie your life to iCloud. They tell you to make backups on iCloud. According to the reddit thread, this can happen if there was a fraudulent charge made with a credit card associated with the account... Not even done on the account. So then all of your data disappears?
1. All your emails if you use iCloud for your email, and thus potentially locking you out of any other sites that use email as a 2-factor-auth.
2. All your backups on iCloud.
3. All your data on iCloud.
4. Every single login you have where you used sign-in-with-Apple.
5. Every app on your phone that you have a paid subscription for.
6. The fallback login mechanism on any of your Macs where you used iCloud as the login fallback.
The list goes on. They ask you to tie your life to iCloud. They tell you to make backups on iCloud. According to the reddit thread, this can happen if there was a fraudulent charge made with a credit card associated with the account... Not even done on the account. So then all of your data disappears? Is that enough wrong here?
NOW would be different because, again, this system is worse than Apple's, and because Chrome has a larger influence on the web than Safari (on Desktop, on mobile its a foregone conclusion since you're not allowed a different engine other than Safari anyways, so the real fight there is allowing third party engines).
Does this answer your concerns? I can't tell if you are defending Apple and Google, or are against both but are using this what-about-ist accusation as a way to vent general frustration.
It is unbelievable that over the course of 3 days, the potential future of the web has been put in such dire straits. There's already an existing, far less troubling (while still bad), proposal in the form of Private Access Tokens going through a standards committee that Google chose to ignore. They presented this proposal in the shadiest way possible through a personal GitHub account. They immediately shut down outside contribution and comments. And despite the blowback they are already shoving a full implementation into Chromium.
What we need is real action, and this is the role Mozilla has always presented itself as serving. A "true" disinterested defender of the ideals of the web. Now is the time to prove it. Simply opposing this proposal isn't enough. This is about as clear and basic an attack on what fundamentally differentiates the web from every walled garden as possible. If someone drafted a proposal to the W3C that stated that only existing browsers should be allowed to render web pages, the correct response would not be to "take the stance that you oppose that proposal," it would be to seriously question whether the submitting party should even participate in the group. Make no mistake, that is what is happening now.
Depends on your definition of "ideal", and whether you even want to strive for such an "ideal". To me this sounds more like a "sterile" web. If we temporarily assume that humans won't do what they're experts at (finding ways around that system too), and take at face value that this will lead to this "cleanest" web space, we are still assuming that that's what consumers want. I would argue that the very existence, and success, of the web in the face of approximations to this "ideal" space in the native-app-world disproves this theory. We have the App Store, we have lock-down control and identifiability for apps, and yet the web still manages dominate commerce in the face of this. Consumers still end up going to the web, and arguably increasingly so with things like Figma. So where are the cries for this "sanitized" web? The demand certainly doesn't appear to be on the consumer end, that's for sure.
I think it's weird to compare failed products within a company (and minor products at that) to failed companies. I think you may have not even listed some of the more notable ones (The Apple LISA, the iPod HiFi). But he wasn't betting the company on the Cube, or MobileMe, or even Ping. These were low-stakes (and arguably low effort) bets taken within a company that was simultaneously having insane success in other departments. The G4 Cube came out between the iMac and the iPod (2 years after the iMac, 1 year before the iPod). That seems like a damn good product-line, and if you could choose any one to miss on, it'd be the niche prosumer device, not the two consumer devices.
> Remember NeXT? > Remember he got kicked out of Apple?
These could be interpreted either way. It seems all part of the larger "Apple story arc", and more comparable to Tesla's shaky middle period, than as binary successes and failures void of any surrounding context. However, I do mean that it could go either way. I wouldn't fault someone as judging them as true failures separate from the later Apple success.