I had this exact issue. I spent some time experimenting with UTM, QEMU and Vagrant. This was a little over a year ago (March 2022 according to the timestamp on the Vagrantfile).

I was hoping that Parallels would eventually release something that would make this a lot more seamless, but apparently they're nervous about Apple bashing them overt the head for providing x86 on Arm compatibility and as such aren't going to release something that allows it.

I managed to get x86 vagrant images working fine, here's the relevant section of Vagrantfile

config.vm.box = "peru/ubuntu-20.04-server-amd64"
  config.vm.provider "qemu" do |qe|
    qe.arch = "x86_64"
    qe.machine = "q35"
    qe.cpu = "max"
    qe.smp = "cpus=4,sockets=2,cores=2,threads=1"
    qe.net_device = "virtio-net-pci"
  end

As for speed, I was pretty concerned it would be unusable, however whilst it wasn't blazingly fast, it was substantially faster than I thought it would be. A terminal was very responsive, essentially instant and if I didn't know better I'd have assumed I was using a virtual machine on a native CPU.

In the end I haven't actually had to use in anger it over the last year so I don't know how it would be compiling things, but I spun it up (had to update both Vagrant and all it's plugins) and here are some profiling comparisons from sysbench and a few random other experiments below.

Host CPU vs Virtual CPU for comparison:

Virtual CPU speed:
    events per second: 304.60
Host CPU speed:
    events per second: 12951889.44

File IO:

File operations:
    reads/s: 2686.80
    writes/s: 1791.20
    fsyncs/s: 5737.60
Throughput:
    read, MiB/s: 41.98
    written, MiB/s: 27.99

Memory:

Total operations: 2844369 (284335.43 per second)
 
2777.70 MiB transferred (277.67 MiB/sec)

Quick curl+gzip:

curl -s <large gzipped text file>|pigz -dc |cpipe -vt 2>&1 >/dev/null| perl -pe 's/\n/\r/g'
thru: 5.159ms at 24.2MB/s ( 26.5MB/s avg) 310.8MB

Compile hello world:

time g++ test.cpp
real 0m2.457s
user 0m2.133s
sys 0m0.325s

There are several places like that which are just as (if not more) confusing. Though spaghetti junction is the most famous.

Swindons Magic Roundabout for example

https://www.google.co.uk/maps/...

Then near where I grew up there is the A19 meeting the A66

https://www.google.co.uk/maps/...

What you can see if you follow that:

At the bottom (South of the river): Similar but not as bad as spaghetti junction
At the top (North of the river): The roundabout below has up to 6 lanes in places with 2 mini roundabouts
On the right hand side (just south of the river): This one isn't as bad when you're actually drivintg it, as it's a standard roundabout with a few shortcuts if you happen to be taking the first exit for you).

Actually this is due to a UK/EU law/requirement that all sites which require users to explicitly be notified (and agree to) any cookies which are not explicitly required for usage of the site (sites which require logins, shopping carts etc are therefore exempt), the site will just work as normal if you don't click on the "I agree" button (which ironically will set another cookie saying you have agreed).

I guess some sites just enabled it for world users rather than dealing with different countries seperately.

ICO link below for those who want to read up on it.

http://www.ico.org.uk/for_organisations/privacy_and_electronic_communications/the_guide/cookies

Which is what makes me suspect it's a joke site, and that there's a heavy touch of sarcasm.

"...., the brave pilots and operators of the U.S. drone program...."

Damn brave, risking their lives shooting someone down from their heavily fortified bunker located a completely different country to the actual battle.

The problem about this is that many of those types of flaws have been well known about and well publicised for many years now (and many high profile sites have had widely publicised exploits ecause of them).

However, there are now many standard practices which seasoned/experienced programmers/developers/system designers use to mitigate most of those issues (Hell, whilst I may have some issues with Ruby on Rails, with the current release I believe you'd have to explicitly allow unescaped HTML into your pages).

Anyone who has been developing any web applications for any decent length of time should be treating security (XSS, SQL Injection, Request Forgery etc) as a matter of principle, because it's much harder to retrofit security once you're finished. So that their source has so many holes in it does not bode well for any underlying protocol, they are not approaching the project with security in mind at all (and it may seem that they are not experienced enough yet to approach it so). This would be fine if it was just your average open source project, however it's not. They have been donated some $200,000 with which to develop it, and the benefit that could be gained from it is immeasurable. If the code they write is full of flaws, you can probably expect the protocol to have issues as well.

As has been suggested, the very first thing they should have done is come up with the protocol/data schema/api with which the sites would communicate . This would include allowing extensions/non base data as if there isn't a standard way of doing this then many of the various companies who run the servers will attempt to extend them (ala Microsoft) to get their own kind of vendor lock in (The best way would probably be something similar to the RSS v2.0 modules via namespaces, though I haven't spent too much time thinking about it).

For quoting the Simpsons in such style, I offer you my most enthusiastic contrafibularities.

In fact I'm anispeptic, frasmotic, even compunctuous that you seem to have caused the person who had to look up the words such pericombobulation.

http://www.imdb.com/title/tt0526724/quotes

You could resubmit the application with Shit load instead.

Get yourself (if you don't already have) a cheap colo/virtual host. Then just use SSH with the-D option, and set your browsers proxy to a socks proxy on localhost.

Thats what I always do at when there are network issues (firewall, throttling, shaping).

You seem to be a little touchy on the subject!

I'll be counting the time until some other programmer in a country Facebook can't touch (or who does it anonymously), scrapes the exact same data and pushes it up on a torrent, purely because of this story.

Although I'm not sure why Facebook are so concerned, the friend data is relatively fluid, whilst there will be long term friendships, people add new friends all the time (and I'd guess, to a lesser extent, remove people who are no longer friends.

Plus the data isn't THAT reliable, I have several friends who, purely as a game have 1000+ friends and counting, purely to see how many they can get.

There's an even easier way of noticing it's an output filter.

The switch when clicking between your current stream and the text stream, is instant. If you switch from low to high def streams it actually reloads the stream. You can click the TEXTp to normal links as many times as you like and it's instant. They probably did effectively convert aalib to flash in some form (at the very least use the conversion tables).

The official site is here http://ie6funeral.com/

Don't know why it wasn't included in the summary.

Yes, it was the episiode where they were satirising house. Apparently frmo a quick google it's been mentioned on House as well.

http://scrubs.wikia.com/wiki/My_House
http://www.tv.com/scrubs/my-house/episode/934864/summary.html

http://www.cucirca.com/2009/01/27/house-season-3-episode-11-words-and-deeds/

http://www.tv.com/scrubs/broken-heart-syndrome-in-andquotmy-houseandquot-and-this-weeks-episode-of-house/topic/2641-628341/msgs.html