There was a scene I always liked on The West Wing where Josh waxes lyrical about Johnson being on the disc (It's about 1:50 into This clip)
Or an interstitial ad could have triggered their ADHD and move on to the next planet.
You don't seem to understand how slashdice works...
as well as solar, wind, geothermal, whatever.
You forgot nuclear. Never forget the nukes.
All words are made up.
...so I doubt this update will make things any worse.
My Number One problem with Chromecast was the dumb setup procedure - the bloody thing is forever losing it's connection with my WiFi, with the only recourse being to do a hard reset and then wade through the interminable setup process again and again...
Of course, Google provides no customer support for the thing - they just send you to a web forums full of raving fanbois who get offensive when you suggest that it's possible for any google product could be anything other than perfect.
Of course I mind - your judgement should also be based on grammar.
Yes. And it turns out that it *is* possible to write readable Perl. It's just that if you do so, all the Perlista look at you as if you were something they'd trodden in.
C++ is often unreadable
That's not a problem with the language, it's a problem with whoever wrote the code.
I've been writing software for about 40 years - and one of the things I've observed in that time is that it's possible to write unreadable code in pretty much any language. I've also observed that it's possible to write readable code in pretty much any language.
The main reasons I have for this are the needs to manage memory usage and disk access at a very granular level
And why, exactly, do you imagine you need these things?
(You may well do - but you don't give a reason for it, so it's entirely possible that you don't need to manage those things on a granular level)
Which is *exactly* the point I'm making... You very rarely (if ever) need to write 'new'.
17 years? Talk about a newbie - I've been a member of WG21 for longer than that.
I have explained; I'm not wrong.
And I certainly wasn't suggesting you need to "look into the implementation of make_unique in your compiler's version of the STL".
But hey, apart from the small detail of everything you wrote, you're completely right.
You should almost never see a new
That is complete nonsense.
At some point you have to allocate the objects/memory. And for that you need a "new".
To demonstrate that you're wrong, I mention make_shared as an example of allocating objects without your having to see new.
Was that really so hard to figure out?