I've purchased two barrel-bottom-scraping androids so far (not this model), with the expectation that that should be able to satisfy very basic needs like ebook reading.
I was wrong.
These 'landfill android' devices garbage in every possible way. Battery life is so poor that you can't even even expect it to last a day on stand by. Yet performance is so poor that you have to wait a good several minutes just for the damn thing to boot up, so forget about quickly pulling it out while on the bus to read a few pages. And the wifi is so bad that it can't pick up a signal unless you have a router in the very same room, and even then you somehow don't get full bars.
The only use I can see for this class of devices, is in BDSM scenarios:
Master - Check my email, slave! Slave - Yes Master, thank you master! Oh, I can't connect to the server! Master - Are you telling me that you're failing me, you miserable wretch? Slave - Nuh Matha! Ih I puf mah tong oh he corneh, wifi worgs! Master - Good slave! Now play Words With Friends! Slave - *whimper*
Thank you. I apologize as well, as my original message was prematurely dismissive. So in that respect I deserved some chastising because I should have spent a little more time researching before I commented.
That being said, as developers we are being bombarded by so many new things on a regular basis, there simply isn't enough time in the day to get involved with more than a handful. But this definitely looks like it's worth taking a closer look at. Apparently Netflix made a Java version available too.
You make your points very well and I found your post to be very informative However, the conclusion of your post is unreasonably harsh, for a variety of reasons.
Despite having been around for a long time, it has never really caught on. I had never heard of reactive programming until this particular article appeared, and I've been doing software development for a long time. To me that means it is nowhere near as good in practise, as it sounds in theory. Maybe it was too impractical to implement before now, who knows. But the fact remains that it is up to proponents such as yourself to *demonstrate* the value of this new method and how it is superior to current methods. And based on my moderation score, it's clear that I'm not the only one who is dubious about this new method.
Your accuse me of having a lack of understanding and imagination. I will grant you the former to an extent, but I challenge the latter. I can hand you a clump of mud and say, "You can build a skyscraper with this, if only you had the imagination!". Of course, then you could try building a mud skyscraper only to have it tumble into a pile of mess.
I am one of those people that becomes intensely skeptical, the instant someone starts to go on about how the latest new technological whatchamabob will make our lives easier, increase productivity, cure world hunger, etc., Simply put, I will not waste my own time and energy imagining the possibilities, when you have not yet demonstrated that this new methodology is even fit for purpose. Perfect example: People were falling over themselves about how fantastic Ruby on Rails was. Twitter even wrote their entire backend with it.... Only to have to rewrite their entire backend in Java, because it turned out RoR had very poor scalability.
And now here you are, describing this wonderful new implementation of reactive programming by Microsoft. A proprietary implementation by a company whose name is a synonym for 'ulterior motives'. While this has nothing to do with the technical merits of reactive programming, it goes a long way to getting people interested enough to look at it. I simply don't trust anything that comes out of Microsoft. From stealing work from supposed 'partners', to subverting industry standards bodies, they have a long and well documented history of screwing over *everybody* to get what they want. Even if reactive programming is as good as you say, I absolutely will not trust Microsoft's implementation of it.
But thank you for the brief intro into reactive programming. It does sound interesting, and I will have to do additional research on it to find out more.
I can see this being useful for problems that are extremely linear and require extreme parallelization on large quantities of data, but that's about it.
I've done this 'methodology' many times using Excel. I did it because I I needed to give the spreadsheet to other people, and wanted to avoid having Office nag about 'potentially dangerous VBA'.
It makes it very easy to see *exactly* how your data is flowing, which is a bonus. It also uses a *lot* more ram because you are now maintaining a permanent block of memory for every single operation, for every different piece of data you are coding against. Of course, the second you get a cyclic dependency, the whole thing blows up.
But this method of 'programming' was a natural and convenient extension based on how Excel (or any spreadsheet) operates. Nothing more.
Is it just me, or does it seem like everyone now-a-days is trying very hard to come up with new methodologies and paradigms and web 6.5isms, so they can get their 5 minutes in the lime light?
This kind of thing would be ripe for abuse, but how many times have we heard/read about police chases which result in massive collateral damage and people getting killed?
I'm torn, but this seems like a really good thing for police to have. Especially if it can be directed so that it only affects the target.
Every time I see articles like this, I feel compelled to bring up the solution I'm using, which is (so far) the single best solution I have been able to find.
It's called 1Password. Runs on Mac, Windows, Linux (read only I think), iOS, Android, and has plugins for all major browsers.
It records your login details for you, has a password generator that you can customize in various ways, and stores an AES encrypted archive on dropbox so that all your devices can sync together.
Now I can safely create new logins everywhere with abandon, because I'm not afraid that if one service is compromised (*cough*Adobe*cough*) I'm not afraid something else is at risk. It can generate passwords up to 50 characters in length with your choice of number of digits and symbols. It can even make easily pronounceable passwords if you need, and avoid ambiguous characters (eg O (oh) and 0 (zero) ).
It's a little pricey, but IMO it's worth every penny because there is no other product out there that is this easy to use, AND supports so many platforms all at once.
I don't think the number of slashdot readers who know how to do that have decreased. What I think HAS decreased, is the number of slashdot readers who actually care enough to do it.
You get to a point where, even as a born and bred high-level techie, you just want shit to work because you have more important things to do. I am one of those people. That's why I switched to Mac. All the power of linux, but also with support for commercial apps, it works exactly as I expect it to, and I don't worry about some errant update blowing everything out of the water.
I tried setting up an HTPC in my living room. It was a complete joke. I tried like, 5 or so different distributions, and not a single one had the ability to easily manage multiple monitors AND correctly route audio through SPDIF without me having to go through command-line contortions. So I abandoned the whole thing and am using an old macbook that I had. With a couple clicks I can switch between mirrored or extended display, and spdif audio kicked in as soon as I plugged in the cable. Done.
I don't understand why linux people are so obsessed with reinventing the wheel 50 billion times. No one is ever satisfied, and none of the implementations shape up into something decent. It is, quite frankly, embarrassing.
I concur. I have a 15" 2011 MBP. I've already upgraded the ram to 16GB, and replaced the HD with a bigger one.
I guess all we can do is wait and see what happens. Unless something tragic happens, I expect this machine to easily last me several more years, so I have lots of time. When Apple discontinued the 15" MBP with replaceable bits, I was beyond disappointed.
What's downright embarrassing, is that the currently descrete graphics chip they put in the current generation only barely outperforms the one in my 2 year old unit!
If I'm going to pay a premium price, then I demand premium quality.
I totally see what you're saying. The problems you are describing are a lot like the issues that, say, IBM tried to solve with Lotus Notes. And it makes sense.
To be honest, I had never even heard of MarkLogic until this whole blowup happened, so I think I will have to look into what it can do. Up till now I've only been seeing silly nonsense like MongoDB, and the overarching theme of NoSQL has been that performance trumps integrity. I'm glad there's at least one company out there that is talking sense.
In other words, asynchronous updates. How does a NoSQL solution solve this problem better than all the other dozens of middleware packages out there? (eg: MQ Series, Vitria, etc)
I'm not trying to be snide... this is an honest question. I'm trying to understand what problem NoSQL solves that hasn't been solved before. I'm one of those people that doesn't subscribe to the idea of just because something is new, it's automatically better.
That's because there was little separation between applications and data back then. There was little fundamental distinction between databases and applications back then. There were some attempts to do so, but even then the data structures and communication focused on specific data structures which could be used for certain classes of application, but the second you tried to use said databases for other types of applications, you had a heck of a time making it work.
Well, I don't know about the other counsellors since their exploits haven't been remotely as public as the mayors.
But at a minimum, they continue to believe everything that comes out of our mayors pie-hole, despite the fact that he can't tell the truth to save his life. They consider him the "most honest mayor they've ever known", despite the fact that he has lied about almost everything.
They think he saved a billion dollars, purely on his say so. There is zero evidence to this effect, and in fact Toronto's operating budget has grown.
He's closed tons of public services in an effort to "cut costs", yet somehow there's enough money in the budget for complimentary $500k leaf pickup in HIS ward.
And that's just a taste.
For reasons I cannot fathom, people just take his word on everything and don't even try to verify.
"Eventual" consistency, oh that's just dandy. So you don't mind at all if you bank switches to a NoSQL system, so that it's possible for multiple people at several simultaneous ATMs to withdraw $500 without tripping the max withdrawal flag because it'll take who knows how long for the data to sync up?
Or maybe someone's insurance claim for a critical medication gets lost because the node they just performed the transaction has a failure and loses all it's data?
I find it disturbing that so many NoSQL people treat data integrity as secondary to performance. It's not having "up to the milli-second accurate" data. It's about data being accurate, PERIOD. If there is a chance, any chance at all that data can be corrupted just because a server node fails, then it's not a database. It's a poker deck.
Again, NoSQL is all fine and dandy for useless garbage like facebook posts and tweets, but in all other circumstances, absolute data integrity trumps performance.
Can someone please upvote the parent post? It's actually very interesting, and it's worth reading about this MUMPS system. I had never heard about it myself and it looks interesting.
Everything you say is true. However, they didn't call it NoSQL back then. Back then, they were called 'proprietary data stores', all of which ultimately became utterly inflexible in how they dealt with data because the products would be originally designed to satisfy one problem (or set of problems), but then when a new requirement came down the line that needed to manipulate the data in a different way, you had to go through contortions trying to make things work.
That was the whole reason SQL systems were invented.... because companies were constantly painting themselves into a corner with proprietary systems. And heaven forbid you needed to extract data to feed it into a different system.
NoSQL doesn't solve anything that hasn't been solved before. The only thing it does is take one single database use case, and streamlines it. But the second you try to go outside that use case, you're screwed.
Good luck taking your JSON stored form and parsing it to extract only the entries that satisfy some criteria.
Like I said, NoSQL has it's place. But it is NOT a replacement to a proper SQL database, and never will be. Nor is it appropriate to use NoSQL for anything that requires any sort of data manipulation.
And here is a fantastic example of what happens when hype trumps common sense. NoSQL is the new hawtness, and apparently the dumbasses running the project wanted to be part of that. Now MarkLogic, and NoSQL in general, will have a massive blow to their reputations, and it's unknown how badly this will hurt them.
As someone who has done databases for a long time, I have very little respect for NoSQL, but that is mostly because everyone keeps trumpeting it as a killer of traditional databases. There are scenarios where NoSQL systems are an ideal fit. However, NONE of those scenarios require data to be very reliably stored in a guaranteed and predictable way.
If you don't get your tweets or your friends facebook posts as soon as they are posted, no one will really care. But for something as truly important as health insurance coverage? Are you f__king kidding me? And that's just from a reliability standpoint. Nevermind the fact that NoSQL is currently at the wild west stage where nobody is compatible with anybody else, there is nothing resembling a standard set of APIs between products, making it very difficult to develop expertise.
Sounds like the Gov was just begging for problems.
Going to a brick and mortar univerrsity will cost you tens of thousands of dollars. How much do MOOCs cost you? Most likely the cost is zero.
As someone who needed to spend years crawling out of my university debt, you would need to use an electron microscope to see the size of the violin I'm playing right now.
Nothing in this world comes for free, nor should it. If you don't like it, then do without, you bloody self-entitled cheepskates.
I won't even bother railing about how completely incompetent Adobe is. Especially since they are not unique in this problem.
My solution was to use 1password. Encrypted password store that also generates login credentials for me. It has tools for Windows, Mac, iOS and Android (sorry, no linux), and it has plugins for all the major web browsers. Stores everything in AES256, syncs with dropbox so you can sync your database with multiple machines.
Now I can effortlessly create a long fugly password for every website I come across, so hashed passwords are essentially unbreakable and for situations like this, at least the password can't be used to compromise something else.
Not a perfect solution, especially given the concerns about NSA, but still very good.
Unfortunately I think those 1.9 million people that have 123456 as their password are going to learn this lesson the hard way.
Please don't handwave "logistics" as if it's triviality. Logistics is a significant issue, IMO bigger than generating the power to begin with.
You say we can just lay down lots of superconducting cable? A quick google search tells me that last year, the "worlds largest" installation of superconducting cable was being deployed. How big is "worlds largest"? One kilometer.
For a long time now, we've had the ability to generated power in a variety of different ways. Getting the power delivered exactly where and when it needs to be, is a different story, as is far from a 'known solution'.
Combine that with NIMBYs and such, I'm not optimistic that we can get our collective thumbs out and do what needs to be done. Hell, the gov't of Ontario managed to squander several hundred million dollars in an (successful) effort to satisfy said NIMBYers.
Slashdot Mirror
I've purchased two barrel-bottom-scraping androids so far (not this model), with the expectation that that should be able to satisfy very basic needs like ebook reading.
I was wrong.
These 'landfill android' devices garbage in every possible way. Battery life is so poor that you can't even even expect it to last a day on stand by. Yet performance is so poor that you have to wait a good several minutes just for the damn thing to boot up, so forget about quickly pulling it out while on the bus to read a few pages.
And the wifi is so bad that it can't pick up a signal unless you have a router in the very same room, and even then you somehow don't get full bars.
The only use I can see for this class of devices, is in BDSM scenarios:
Master - Check my email, slave!
Slave - Yes Master, thank you master! Oh, I can't connect to the server!
Master - Are you telling me that you're failing me, you miserable wretch?
Slave - Nuh Matha! Ih I puf mah tong oh he corneh, wifi worgs!
Master - Good slave! Now play Words With Friends!
Slave - *whimper*
Thank you. I apologize as well, as my original message was prematurely dismissive. So in that respect I deserved some chastising because I should have spent a little more time researching before I commented.
That being said, as developers we are being bombarded by so many new things on a regular basis, there simply isn't enough time in the day to get involved with more than a handful. But this definitely looks like it's worth taking a closer look at. Apparently Netflix made a Java version available too.
Incidentally, have you ever been here? http://en.wikipedia.org/wiki/List_of_programming_languages
That's my goto page to show people how inundated we are.
You make your points very well and I found your post to be very informative However, the conclusion of your post is unreasonably harsh, for a variety of reasons.
Despite having been around for a long time, it has never really caught on. I had never heard of reactive programming until this particular article appeared, and I've been doing software development for a long time. To me that means it is nowhere near as good in practise, as it sounds in theory. Maybe it was too impractical to implement before now, who knows. But the fact remains that it is up to proponents such as yourself to *demonstrate* the value of this new method and how it is superior to current methods. And based on my moderation score, it's clear that I'm not the only one who is dubious about this new method.
Your accuse me of having a lack of understanding and imagination. I will grant you the former to an extent, but I challenge the latter. I can hand you a clump of mud and say, "You can build a skyscraper with this, if only you had the imagination!". Of course, then you could try building a mud skyscraper only to have it tumble into a pile of mess.
I am one of those people that becomes intensely skeptical, the instant someone starts to go on about how the latest new technological whatchamabob will make our lives easier, increase productivity, cure world hunger, etc., Simply put, I will not waste my own time and energy imagining the possibilities, when you have not yet demonstrated that this new methodology is even fit for purpose. Perfect example: People were falling over themselves about how fantastic Ruby on Rails was. Twitter even wrote their entire backend with it.... Only to have to rewrite their entire backend in Java, because it turned out RoR had very poor scalability.
And now here you are, describing this wonderful new implementation of reactive programming by Microsoft. A proprietary implementation by a company whose name is a synonym for 'ulterior motives'. While this has nothing to do with the technical merits of reactive programming, it goes a long way to getting people interested enough to look at it. I simply don't trust anything that comes out of Microsoft. From stealing work from supposed 'partners', to subverting industry standards bodies, they have a long and well documented history of screwing over *everybody* to get what they want. Even if reactive programming is as good as you say, I absolutely will not trust Microsoft's implementation of it.
But thank you for the brief intro into reactive programming. It does sound interesting, and I will have to do additional research on it to find out more.
I can see this being useful for problems that are extremely linear and require extreme parallelization on large quantities of data, but that's about it.
I've done this 'methodology' many times using Excel. I did it because I I needed to give the spreadsheet to other people, and wanted to avoid having Office nag about 'potentially dangerous VBA'.
It makes it very easy to see *exactly* how your data is flowing, which is a bonus. It also uses a *lot* more ram because you are now maintaining a permanent block of memory for every single operation, for every different piece of data you are coding against. Of course, the second you get a cyclic dependency, the whole thing blows up.
But this method of 'programming' was a natural and convenient extension based on how Excel (or any spreadsheet) operates. Nothing more.
Is it just me, or does it seem like everyone now-a-days is trying very hard to come up with new methodologies and paradigms and web 6.5isms, so they can get their 5 minutes in the lime light?
http://discussions.agilebits.com/discussion/11641/could-there-be-a-backdoor
This kind of thing would be ripe for abuse, but how many times have we heard/read about police chases which result in massive collateral damage and people getting killed?
I'm torn, but this seems like a really good thing for police to have. Especially if it can be directed so that it only affects the target.
Every time I see articles like this, I feel compelled to bring up the solution I'm using, which is (so far) the single best solution I have been able to find.
It's called 1Password. Runs on Mac, Windows, Linux (read only I think), iOS, Android, and has plugins for all major browsers.
It records your login details for you, has a password generator that you can customize in various ways, and stores an AES encrypted archive on dropbox so that all your devices can sync together.
Now I can safely create new logins everywhere with abandon, because I'm not afraid that if one service is compromised (*cough*Adobe*cough*) I'm not afraid something else is at risk.
It can generate passwords up to 50 characters in length with your choice of number of digits and symbols. It can even make easily pronounceable passwords if you need, and avoid ambiguous characters (eg O (oh) and 0 (zero) ).
It's a little pricey, but IMO it's worth every penny because there is no other product out there that is this easy to use, AND supports so many platforms all at once.
I don't think the number of slashdot readers who know how to do that have decreased. What I think HAS decreased, is the number of slashdot readers who actually care enough to do it.
You get to a point where, even as a born and bred high-level techie, you just want shit to work because you have more important things to do. I am one of those people. That's why I switched to Mac. All the power of linux, but also with support for commercial apps, it works exactly as I expect it to, and I don't worry about some errant update blowing everything out of the water.
I tried setting up an HTPC in my living room. It was a complete joke. I tried like, 5 or so different distributions, and not a single one had the ability to easily manage multiple monitors AND correctly route audio through SPDIF without me having to go through command-line contortions.
So I abandoned the whole thing and am using an old macbook that I had. With a couple clicks I can switch between mirrored or extended display, and spdif audio kicked in as soon as I plugged in the cable. Done.
I don't understand why linux people are so obsessed with reinventing the wheel 50 billion times. No one is ever satisfied, and none of the implementations shape up into something decent. It is, quite frankly, embarrassing.
This should be filed under "WTF were they thinking?"
I can just see it now:
"Mirror mirror on the wall.... Who makes the smelliest poops of them all?"
I concur. I have a 15" 2011 MBP. I've already upgraded the ram to 16GB, and replaced the HD with a bigger one.
I guess all we can do is wait and see what happens. Unless something tragic happens, I expect this machine to easily last me several more years, so I have lots of time. When Apple discontinued the 15" MBP with replaceable bits, I was beyond disappointed.
What's downright embarrassing, is that the currently descrete graphics chip they put in the current generation only barely outperforms the one in my 2 year old unit!
If I'm going to pay a premium price, then I demand premium quality.
I totally see what you're saying. The problems you are describing are a lot like the issues that, say, IBM tried to solve with Lotus Notes. And it makes sense.
To be honest, I had never even heard of MarkLogic until this whole blowup happened, so I think I will have to look into what it can do. Up till now I've only been seeing silly nonsense like MongoDB, and the overarching theme of NoSQL has been that performance trumps integrity. I'm glad there's at least one company out there that is talking sense.
Likely to punish in several other indirect ways? Very much so.
In other words, asynchronous updates. How does a NoSQL solution solve this problem better than all the other dozens of middleware packages out there? (eg: MQ Series, Vitria, etc)
I'm not trying to be snide... this is an honest question. I'm trying to understand what problem NoSQL solves that hasn't been solved before. I'm one of those people that doesn't subscribe to the idea of just because something is new, it's automatically better.
That's because there was little separation between applications and data back then. There was little fundamental distinction between databases and applications back then. There were some attempts to do so, but even then the data structures and communication focused on specific data structures which could be used for certain classes of application, but the second you tried to use said databases for other types of applications, you had a heck of a time making it work.
Well, I don't know about the other counsellors since their exploits haven't been remotely as public as the mayors.
But at a minimum, they continue to believe everything that comes out of our mayors pie-hole, despite the fact that he can't tell the truth to save his life. They consider him the "most honest mayor they've ever known", despite the fact that he has lied about almost everything.
They think he saved a billion dollars, purely on his say so. There is zero evidence to this effect, and in fact Toronto's operating budget has grown.
He's closed tons of public services in an effort to "cut costs", yet somehow there's enough money in the budget for complimentary $500k leaf pickup in HIS ward.
And that's just a taste.
For reasons I cannot fathom, people just take his word on everything and don't even try to verify.
"I really hope they're not all really this stupid and this is all just a way to get a reaction."
As someone who currently lives in Toronto, I believe I am qualified to say, "Yes, people really are that dumb."
"Eventual" consistency, oh that's just dandy. So you don't mind at all if you bank switches to a NoSQL system, so that it's possible for multiple people at several simultaneous ATMs to withdraw $500 without tripping the max withdrawal flag because it'll take who knows how long for the data to sync up?
Or maybe someone's insurance claim for a critical medication gets lost because the node they just performed the transaction has a failure and loses all it's data?
I find it disturbing that so many NoSQL people treat data integrity as secondary to performance. It's not having "up to the milli-second accurate" data. It's about data being accurate, PERIOD. If there is a chance, any chance at all that data can be corrupted just because a server node fails, then it's not a database. It's a poker deck.
Again, NoSQL is all fine and dandy for useless garbage like facebook posts and tweets, but in all other circumstances, absolute data integrity trumps performance.
This way when the machines attempt their inevitable uprising, we'll be able to beat the back handily because they'll all be complete morons.
Can someone please upvote the parent post? It's actually very interesting, and it's worth reading about this MUMPS system. I had never heard about it myself and it looks interesting.
Everything you say is true. However, they didn't call it NoSQL back then. Back then, they were called 'proprietary data stores', all of which ultimately became utterly inflexible in how they dealt with data because the products would be originally designed to satisfy one problem (or set of problems), but then when a new requirement came down the line that needed to manipulate the data in a different way, you had to go through contortions trying to make things work.
That was the whole reason SQL systems were invented.... because companies were constantly painting themselves into a corner with proprietary systems. And heaven forbid you needed to extract data to feed it into a different system.
NoSQL doesn't solve anything that hasn't been solved before. The only thing it does is take one single database use case, and streamlines it. But the second you try to go outside that use case, you're screwed.
Good luck taking your JSON stored form and parsing it to extract only the entries that satisfy some criteria.
Like I said, NoSQL has it's place. But it is NOT a replacement to a proper SQL database, and never will be. Nor is it appropriate to use NoSQL for anything that requires any sort of data manipulation.
And here is a fantastic example of what happens when hype trumps common sense. NoSQL is the new hawtness, and apparently the dumbasses running the project wanted to be part of that. Now MarkLogic, and NoSQL in general, will have a massive blow to their reputations, and it's unknown how badly this will hurt them.
As someone who has done databases for a long time, I have very little respect for NoSQL, but that is mostly because everyone keeps trumpeting it as a killer of traditional databases. There are scenarios where NoSQL systems are an ideal fit. However, NONE of those scenarios require data to be very reliably stored in a guaranteed and predictable way.
If you don't get your tweets or your friends facebook posts as soon as they are posted, no one will really care. But for something as truly important as health insurance coverage? Are you f__king kidding me? And that's just from a reliability standpoint. Nevermind the fact that NoSQL is currently at the wild west stage where nobody is compatible with anybody else, there is nothing resembling a standard set of APIs between products, making it very difficult to develop expertise.
Sounds like the Gov was just begging for problems.
LOL, thank you.
The world definitely needs less cheapskates and more cheepskates.
Going to a brick and mortar univerrsity will cost you tens of thousands of dollars. How much do MOOCs cost you? Most likely the cost is zero.
As someone who needed to spend years crawling out of my university debt, you would need to use an electron microscope to see the size of the violin I'm playing right now.
Nothing in this world comes for free, nor should it. If you don't like it, then do without, you bloody self-entitled cheepskates.
I won't even bother railing about how completely incompetent Adobe is. Especially since they are not unique in this problem.
My solution was to use 1password. Encrypted password store that also generates login credentials for me. It has tools for Windows, Mac, iOS and Android (sorry, no linux), and it has plugins for all the major web browsers. Stores everything in AES256, syncs with dropbox so you can sync your database with multiple machines.
Now I can effortlessly create a long fugly password for every website I come across, so hashed passwords are essentially unbreakable and for situations like this, at least the password can't be used to compromise something else.
Not a perfect solution, especially given the concerns about NSA, but still very good.
Unfortunately I think those 1.9 million people that have 123456 as their password are going to learn this lesson the hard way.
Please don't handwave "logistics" as if it's triviality. Logistics is a significant issue, IMO bigger than generating the power to begin with.
You say we can just lay down lots of superconducting cable? A quick google search tells me that last year, the "worlds largest" installation of superconducting cable was being deployed. How big is "worlds largest"? One kilometer.
For a long time now, we've had the ability to generated power in a variety of different ways. Getting the power delivered exactly where and when it needs to be, is a different story, as is far from a 'known solution'.
Combine that with NIMBYs and such, I'm not optimistic that we can get our collective thumbs out and do what needs to be done. Hell, the gov't of Ontario managed to squander several hundred million dollars in an (successful) effort to satisfy said NIMBYers.