Earlier quoted context omitted.
So if you have problem that goes away with another user, the problem commonly lies in a corrupted preference related to the app, so you start hunting out the .plists for the application and moving them to the desktop before relaunching and seeing if the problem is fixed. If not, then you start poking about in Application Support for the app.
After 9 years of Apple use, I have successfully made this method work one time (iMessages), and even then, it took a full system reboot after each file move to validate whether or not that had made a difference. The whole process took the better part of a day. It was long, it was tedious, but at least I got there in the end. There was no paid-support story that would have done this for me, but hey ho, it all worked o…
Apple Music Web Client
181–190 of 213 posts
Re: Apple Music Web Client
#182Earlier quoted context omitted.
I only remember Ember because it was so much more popular at the time (2013? Early 2014?) than Backbone, which I had just completed an application using, and Angular, which was relatively new to the scene. Ember looked like it was the next big thing. And then, I guess, React came around and everybody was hot on the heels of the next big thing.
Well, I tried Ember back in the day for one project and remember it being pretty hard to learn and quite fat in terms of file size. It was quite powerful when you were using it the way it was supposed to be used, but made your life pretty hard when you wanted to do things a bit simpler and the initial load times were horrible at the time. I heard, that things got a lot better over the years, but I never tried it agai…
Re: Apple Music Web Client
#183seems they're using Ember.js . Reason I love spotify so much is that it's available on the web, no need to be downloading native apps everywhere. Always bet on the web. also good to see, another web property using Ember. As a react dev, competition is healthy
I’m surprised. I haven’t heard anything about Ember in years. Not since 2013 or so.
What some see as constraints, others see as consistency. It's more typically seen in "dashboard apps" but it's also great when you need to quickly spin up a new site and don't want to have to configure anything. I know movie studios in LA that use it for those kinds of promo websites, because of the fast turn around time.
Another thing that is cool about Ember is the community-driven process- if you have a good idea for Ember and the energy to make it happen, it typically will happen. Makes you feel like you can make a difference if that's your thing.
Re: Apple Music Web Client
#184I’m curious what framework Apple uses for web now. Last I checked (a week ago) icloud.com is still implemented with SproutCore.
Ember, jQuery, Moment, and RequireJS. https://imgur.com/DioXtwe
Re: Apple Music Web Client
#185Earlier quoted context omitted.
If you have a big collection of obscure/foreign music (video game music is a great example), then nothing beats Apple Music + iCloud Music Library and iTunes match. You can use iTunes match to provide cloud-based high quality versions for music ripped from your CDs (or collected during your teenage Napster years). Even better, being able to mix content from your iCloud Music Library and streamable content from Apple…
Does it touch my original files in any way? I have a huge selection of rare and obscure music not available via iTunes or any streaming service. Obviously I don't want any service to touch, modify or replace these or any of my more popular release. I'm wary about auto matching. Should I be?
Re: Apple Music Web Client
#186Earlier quoted context omitted.
Not surprising as they are using Ember (one of the slowest front end frameworks), Moment (super heavy date library), and they don't even minify their code... https://js-cdn.music.apple.com/musickit/v2/components/musick...
> one of the slowest front end frameworks What metric are you referring to here?
Here are the latest results: https://krausest.github.io/js-framework-benchmark/current.ht...
As you can see Ember 3.11.1 doesn't fare too well in either performance, startup metrics, or memory consumption. Glimmer does a bit better but that not much.
Re: Apple Music Web Client
#187Earlier quoted context omitted.
Wappalyzer [1] is much better in my opinion. And is available for both Chrome [2] and Firefox [3] as well as a Bookmarklet [4]. The extension that @pier25 is using seems to be available only on Google Chrome [5]. [1] https://www.wappalyzer.com/ [2] https://chrome.google.com/webstore/detail/wappalyzer/gppongm... [3] https://addons.mozilla.org/firefox/addon/wappalyzer/ [4] https://www.wappalyzer.com/download [5] https:…
Wappalyzer's results for example.com, a 1.3 KB static page with no JS or sub-requests, include eight JS frameworks and two web font providers. Its results for facebook.com include a web framework made by Yahoo and deprecated in 2014. It says Youtube is built on WordPress, and HN is a React app with custom fonts.
I only see that HN runs on NGinx.
Re: Apple Music Web Client
#188It appears even Apple themselves do not bother with using the overflow scrolling CSS that iOS needs.
Re: Apple Music Web Client
#189Requires DRM to be turned on for it to work. No thanks.
The fact that Apple is using third-party DRM in a web app is news. Apple TV / iTunes videos never had a web app, and presumably DRM was a big factor.
Re: Apple Music Web Client
#190This was the reason I chose Spotify over Apple music all those years ago. Any reason to prefer Apple Music over Spotify? Spotify's recommendations have been absolutely stellar for me over the years and I have a lot of playlists and stuff "locking" me in.
For my use, all the major streaming platforms are broadly equivalent in functionality, so I go with the cheapest one. That was Amazon Music when I had Prime, which I haven't renewed. Spotify is about 50% more expensive than Apple Music in my location, so I'll likely be going with Apple Music when my Amazon subscription expires.