So true. If this takes off, I can see it as a way to achieve microtransactions, but if a few billion people suddenly start using it to send 1p to each other every time they read a newspaper article or whatnot, then I can see that blockchain becoming as large as all the computer storage in the entire world in short order.

It has to be trimmed in order to be practical, and I'm not sure how practical it would be without the blockchain. I wouldn't worry too much about the transaction speed, visa and mastercard happily handle a lot of transactions so this can be handled too (even if they need a better system than the current one).

people new to torrenting and need a client might look at old links (there are many on the internet) and go and install the very pretty looking uTorrent, and of course they'll want the latest version.

Frankly, I ditched it when they started getting shitty with the adware, I moved to qbitorrent which doesn't look too dissimilar from uTorrent and all is good now.

creating code that doesn't need to be refactored is the key to maintainable code.

C++ is a language that is very good for generic programming. It doesn't really meet Alan Kay's definition of OO

To be fair, there aren't very many that do!

Did they come to that conclusion from looking at their own tax returns or Amazon's?

Ah, but the principle is that the lagoon is filled by the moon (spinning those turbines as it floods in) and then they put down gates to keep the water in, releasing it when the tide has turned. The tides are every 6 hours, so you get a lot of generation during that time - it may not be continuous 24/7 but you get it between 4pm and 10pm, so we would get a lot during the evening when the sun has set and solar is no longer producing. They say generation will be 14 hours a day,

Sure, we still need storage though - efficient storage would fix all our energy problems! I think if we could pump water uphill during peak generation times, it would store a lot of energy. I vote to re-use all the old gas meters we have kicking around for the task!

http://xkcd.com/1492/

It is blue and black, but if you up the lighting, and/or display it against a white background the black lace part looks golden.

Some programmes on TV over here (including the excellent Last Leg - see it on C4 player) had it on the show, it really is blue and black.

thanks.,

"Doctor, doctor, when I raise my arm I shit myself."

"Ah, that'll be because we got a couple of the nerves mixed up in your head transplant. What happens when you wiggle your toes?"

I do think they could practice on paralysed people first - after all, if they can't reconnect severed spinal cord nerves in someone whose spinal cord is roughly still in place, what hope do they have for merging 2 different spinal cords?

Scaling will matter when you have a 4K display, and half your dialogs appear a quarter of the size you're used to. Take one of your dialogs and think how small that is. More pixels means better looking dialogs, and most of the time you still want them to be the same physical size.

Look up Flywheel.com. It is the defacto Taxi dispatch app in San Francisco now.

Ah but that was then. I imagine these are more vector graphics than bitmaps. When you get your new 4k monitor, you'll understand why they have to change.

Not necessarily - Wilko Johnson, a famous guitarist,was diagnosed with terminal and apparently inoperable, pancreatic cancer and decided to basically go out with a show - he refused chemo and organised a farewell tour.. and then a doctor got in touch to say he could cure it, and he now is. Which is good news, apart from the farewell tour not being a farewell any more.

http://www.independent.co.uk/n...

Addenbrookes hospital in Cambridge, UK. Give them a call, you never know.

I agree, I tweaked a few settings on my work FF (as work laptop is 4GB) and it shows 245MB private bytes used with 6 tabs open and doesn't show nay signs of slowness compared to the default 'cache up loads of stuff' settings.

I think the most important is the sessionhistory stuff as that can multiply how much back button pages are stored, per tab!

browser.cache.memory.enable;false
browser.sessionhistory.max_total_viewers; 2
browser.sessionstore.max_serialize_back;5
browser.sessionstore.max_tabs_undo;5
browser.sessionstore.max_windows_undo;2

I think those are the only settings that I've changed WRT memory. Maybe they could do a pre-defined setting set that optimises FF for low-memory PCs.

not if its a walled garden that all the browsers (and W3C) specify and support. Then its a club that you can join if you like.... or go back to sitting on the steps outside whining at passersby, who don't really care.

I think you can generally blame Google for this, and I think one day they will wall off their part (in a Microsoft-eque de-facto standard) and then we'll be really unhappy with the internet.