I'm unfamiliar with ISP scale networks - where is the actual bottleneck for them? One of the large ISPs in the UK is Virgin, and they have their own fibre network. They also throttle Youtube.
Is there only so much data that can go down a fibre line? Is it the routers (I'm not sure if calling them routers is correct?) that lie between the main backbone and the network connecting a street/apartment? Is it the hardware in a handful of large data-centers?
Usually it's the peering between google/youtube and the ISP that is the bottleneck, internal ISP network and google CDN are usually fine there's just an unwillingness to upgrade the connection between them (usually because parties can't agree on terms, some ISP would like to be paid when peering).
Traffic inside your network come free of cost of course except for your own bandwidth constraints, but once you need to communicate with other networks that's where you start to pay.
Google offers free interconnections, but sometimes you can't just connect directly to Google and have to go through backbones that are owned by private companies.
So ISPs need to create as many interconnections as possible with other networks to decrease their costs, invest in their own infrastructure and pay for everything their network can't reach directly.
I live in Scotland, and the weather is mostly wet and damp (rain on ~2 out of 3 days of the year). This year we had a glorious summer. I got productive work done in a single month in June than the entire first 5 months of the year.
There exists at least one UK university which uses Haskell as a teaching language in its CS department. Not quite 7 year olds, but certainly a good percentage of fresh programmers.
Does it result in better programmers? Perhaps. It certainly forces you to understand recursion.
My university used Haskell as the intro language for the math department. People who where already good at programming and people who had never programmed before picked it up quite quickly, but people in the middle who knew a bit of programming coming in had a terrible time with it.
However people who'd never programmed before the Haskell course had a very hard time transitioning that knowledge to Java and similar languages, which was used in some other courses.
I remember learning Haskell at Imperial College London - a very nice language. I had never tried a functional language before and just loved how "natural" if felt after getting familiar with it.
I would love to re-learn it but I am thinking that from a career point of view I am better off learning Scala/Clojure than Haskell.
Is there only so much data that can go down a fibre line? Is it the routers (I'm not sure if calling them routers is correct?) that lie between the main backbone and the network connecting a street/apartment? Is it the hardware in a handful of large data-centers?