> although at 15%, it's half the normal 30% rate for the app store
15% is the normal rate for the App Store. Only developers earning above $1MM/yr through the App Store have to pay 30%, the vast majority of developers only pay 15%.
It's not "normal", you have to "apply" (and get auto-accepted) but won't get the rate if you don't know to do that. You'll also get permanently booted from it if you do some things like transfer ownership of an account (if you want to sell an app you made, IIRC you lose access to this program, even if the app makes under a million).
Screenshot this when the iPhone Pocket is the hot new product everyone must buy, but somehow I don't think these are even remotely in the same category. I don't think Ballmer laughing at the iPhone's price is in the same category as this or the wheels, somehow. Maybe I'm just not enough of a thought leader.
I’m not saying it’s going to be a hot new product that everyone must buy, I’m pointing out that “Apple product ridiculed online” is a completely meaningless non-event that it makes no sense to report on. It’s going to happen for excellent, incredibly successful products; it’s going to happen for bad products; and it’s going to happen to all the products in-between.
Except for all the young, fit people that want to track their workouts and health. Maybe the time of watches that just tell time has passed - I would argue even against that with the continuing existence of Swiss luxury brands - but watch as a small health monitor is still in full force.
To be honest I usually wear a cheap Timex even though I have an Apple Watch because charging is a task. Wear for hiking. Care less about regular fitness tracking.
People that care about battery life probably use something more sporty like the new Suunto's (I get about 2weeks+ of batter life). However the smart watch health features are nowhere near as good.
Cloudflare Stream isn’t just for live-streaming, it’s for generic video hosting too. It does transcoding, adaptive bitrate, HLS, etc. It’s terrible and you shouldn’t use it, but it does a lot more than just serve static video files like R2.
Just to add, you should never serve video straight from R2 unless you pre-render all your videos for all major devices. Otherwise you get very, very subpar device buffering performance. Generally use R2 as a cache layer over your stream processor (CF Stream).
If you have small payments that can be made by bots easily, then your service can be used by thieves as an oracle to determine which of their stolen credit card numbers still work. Then you get lots of chargebacks to deal with.
> Full of security issues is similarly overly dramatic
It doesn’t seem dramatic at all:
> Finding and exploiting 20-year-old bugs in web browsers
> Although XSLT in web browsers has been a known attack surface for some time, there are still plenty of bugs to be found in it, when viewing it through the lens of modern vulnerability discovery techniques. In this presentation, we will talk about how we found multiple vulnerabilities in XSLT implementations across all major web browsers. We will showcase vulnerabilities that remained undiscovered for 20+ years, difficult to fix bug classes with many variants as well as instances of less well-known bug classes that break memory safety in unexpected ways. We will show a working exploit against at least one web browser using these bugs.
Server-side XSLT tools have existed for 25 years or so. The people complaining about this want existing websites using XSLT on the client to continue to work without changes.
It's actually possible to support it by re-implement it by js or compile to wasm and running on client side. There are extensions to support pdf(pdf.js), flash(Ruffle), mht(UnMHT). So it should be possible to do the same thing for XSLT. The real question is "Who want to"? Does xslt have a large user base like pdf, flash, mht?
But made by a corp in the “Extend” phase of embrace-extend-extinguish. No thanks. Fanboys love a new tool but let’s for once look ahead a bit before jumping in.
This is something that really grates with me, but it’s made so much worse with the AI-generated image of him. If you want to say that you don’t think Apple should do that, then fine. But stop using Jobs to fight your battles, and especially don’t generate images of him with that attention-seeking YouTube thumbnail face.
> It’s WWDC week. Every time this rolls around, I see people saying the same sort of thing. “Steve Jobs wouldn’t have done this”.
> Firstly, Jobs wasn’t perfect. He got a lot of things right and a lot of things wrong. His opinion wasn’t the end of the argument when he was alive, and it’s certainly not now that he’s been dead 14 years.
> But more importantly: Stop putting your opinion in a dead man’s mouth to give it more credibility. It’s ghoulish. Let your opinion stand on its own two feet.
You’re right. It’s explicitly about not caring about the code:
> There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. It's possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper so I barely even touch the keyboard. I ask for the dumbest things like "decrease the padding on the sidebar by half" because I'm too lazy to find it. I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I'd have to really read through it for a while. Sometimes the LLMs can't fix a bug so I just work around it or ask for random changes until it goes away. It's not too bad for throwaway weekend projects, but still quite amusing. I'm building a project or webapp, but it's not really coding - I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.
https://www.grab.com/sg/press/others/grab-launches-third-par...
reply