To elaborate on your comment, if you just ship sourcemaps in production, that means you can ship minified code and track down what _actual_ source that you _aren't_ shipping to users is getting called, is in stack traces, etc.
Unsurprisingly there are many frameworks/initiatives that end up falling by the wayside over the years, e.g. MacRuby was being lined up to supersede Objective-C for app development at one point.
Didn’t SproutCore become Ember [1]? Just my vague recollection, not sure if that was the case though. Anyway, Ember is still used and maintained, despite not being very well known.
Dumb question but Apple’s apps are buttery smooth. I just assumed they were using swift and not a web stack to render their UI. Am I completely wrong?!
Apple Music is not buttery smooth and was just a web view for a long time. I feel like I read that this changed a few years ago. This didn’t change the fact that it’s very slow.
In case you want to save sources with the ability to fetch all possible lazy chunks, last year I made a tool to do exactly that:
https://github.com/zb3/getfrontend
(note it won't work on apps.apple.com because apple has removed these sourcemaps)
Honestly the site[1] is very basic and pretty damn slow. When I click into a different category there is a noticeable delay of 1-2 seconds before the new page loads. I don't want to replicate this in any of my own projects.
I wanted to write, 'They have to load the entire catalogue for a category, including all the images. What did you expect?' However, having looked into it a bit more, it seems that they didn't particularly care about optimising load times.
Is there any reason sourcemaps are a genuine problem? I'm out of touch with the JS world, but I wonder if code is shared between server and client and server code may show in sourcemaps.
A DMCA takedown is inappropriate, as no copyright was circumvented. It was freely distributed (albeit briefly) on Apple's own website. A DMCA takedown at this point is entrapment: https://en.wikipedia.org/wiki/Entrapment.
39 comments
[ 4.9 ms ] story [ 97.8 ms ] threadCurious if it was done intentionally or simply due to hurrying.
a lot of people learned to code on the web via viewsource - now we are obfuscating the code
To elaborate on your comment, if you just ship sourcemaps in production, that means you can ship minified code and track down what _actual_ source that you _aren't_ shipping to users is getting called, is in stack traces, etc.
I'm not aware of a point of sourcemaps otherwise.
1. https://emberjs.com/
The pattern itself is a little bit different, has some conceptual overhead, but it's also fairly clean and scaleable.
(note it won't work on apps.apple.com because apple has removed these sourcemaps)
Here's the original post by the author of the repo himself: https://old.reddit.com/r/webdev/comments/1onnzlj/app_store_w...
Was it, HTML, CSS & Javascript?
1: https://apps.apple.com/
Have you tried visiting the site on a worse machine?
https://en.wikipedia.org/wiki/WebObjects
This issue is very wide-spread.