Hmm no, that's not really it... that's more so that you don't pass URLs starting with /app1/ onwards to the application, which would not be aware of that subpath.
I think I need something that intercepts the content being served to the client, and inserts /app1/ into all hardcoded absolute paths.
For example, let's say on app1's root I have an index.html that contains:
...
src="/static/image.jpg"
...
It should be dynamically served as:
...
src="/app1/static/image.jpg"
...
But the point is, for the cost of a single CD per month I was able to listen to any CD from any band whenever I wanted. It was an extremely easy decision to sign up.
Yeah but my point is, you pay but you don't actually get those albums. So if after some years Spotify turns to shit you don't have anything to show for when you cancel the service, and even though you have paid the equivalent of dozens of albums your music collection is gone.
Also, I don't buy anyting near an album per month, so even on that level it doesn't make sense to me. I do have a large collection, but I'm not really digging much current music anymore so if I buy two albums per year, it's a lot.
This has nothing to do with WEI. Google can do more than one shitty thing at once you know.
Never understood why anyone would want to rent their music in the first place. As good as the service may be when you sign up for it, you know it will eventually turn to shit as they're trying to monetize every last cent out of it, and then your only choices are to endure the shit or to quit the service and be left with nothing.
I honestly don't think there's much of a market for high speed trains between Brussels and a small boring provincial city of merely 115.000 people.
Meaningless poll because the popular vote doesn't determine who becomes president. What matters is what percentage of the votes he gets in swing states.
Ok, so you don't know what FUD means.
You can disagree with the comment above, but it's not "FUD", it's just criticism.
That's just a meme. If you can follow some basic instructions, you can setup arch.
Yeah, I evaluated both when I chose this solution several years ago. Don't ask me why I chose one over the other though, I don't remember.
Desktop usage is almost always going to feel laggy in a VM because you don't have a real GPU inside the VM and it will fallback to some non-accelerated framebuffer mode. There are some GPU virtualization solutions, for example QEMU has virgl that offers 3D acceleration, but in my experience it's buggy/not ready and doesn't offer near bare metal performance.
The only way to get near bare metal graphical performance in a VM is by using PCI pass through of an entire GPU, but that requires an extra GPU, is non-trivial to setup and comes with a lot of caveats.
WEI is a proposed modification to Chrome/Chromium that doesn't even exist yet, and that would have the side effect of blocking adblockers on every site that implements WEI.
This here is an already existing change to the YouTube service that blocks adblockers on YouTube, across all browsers, Firefox included. It does not use or need WEI to do this.