Progressive enhancement is generally a waste of time. Users with JavaScript disabled account for an exceptionally low portion of users and it doesn’t make sense to spend time or money on it. Not to mention, your users should not be expected to have reduced functionality because less than 1 out of every 100 people make the conscious decision to disable JavaScript. Why stop there? Why not support for IE6/7/8? There are at least 4-5 times as many users on that.
Cause supporting IE6 is a silly waste of time and resources. So is worrying about people with JavaScript disabled. Most of the reasons people disabled JavaScript are outdated and wrong, anyway. The whole argument about “what is JavaScript doesn’t load” is equally silly. What if the HTML doesn’t load? What if the CSS doesn’t load? The user refreshes, that’s what.
In the case of TIDAL, one should not expect to go to a live streaming music service and expect it to work without JavaScript enabled. However, rendering nothing but a grey screen on the front page of a website that is well funded and expected to reach the widest audience possible, it probably also not a good idea. Even disregarding progressive enhancement entirely, it should at least have a description of what TIDAL is and why you need to have JS enabled. That would take what? About twice as much time as it took me to write this post? Where as I think Meteor.com rendering a blank screen without JavaScript is perfectly acceptable, given that’s it’s specifically a site for a JavaScript framework geared towards developers.