Re: maybe a QuantumBoolean or Qlean
Presumably pronounced "clone".
7284 publicly visible posts • joined 12 Jun 2008
Wind and solar are not "endless" of course, otherwise Britain would already be roofed in solar panels and every house would have a windmill and the electricity Board would have taken a well-deserved hike yonks ago.
Solar works when the sun is out bright enough and long enough, and even then it works only kindasorta otherwise Walt Disney World wouldn't need to be on the grid despite acres of solar panels all over the Orlando/Kissimmee area and baking hot sun most of the year.
Why would you put them in Earth's orbit?
Inverse square law means that somewhere closer to the sun would be ideal.
Not sure what CO2 or Water have to do with anything.
One is talking about clean power, not CO2 fracking.
Power is sent back using high power maser which is converted nearby into usable electricity.
That can be cleanly used on Earth, at very low cost once the infrastructure is established.
Once can do all sorts of things with large amounts of clean electricity.
One could, for example, cook CO2 into syngas - just to get rid of the atmospheric carbon, since we'd have all the electricity for traveling that we could use.
Nonononono, you fail to understand how private company owned electricity grids drive prices down because of competition in the free market and power companies absolutely do not use the lobby and political donations to form a monopoly or collude with each other like what did NOT happen in California to drive prices so high they can be clearly seen by astros in the ISS without recourse to binoculars.
Why would someone put their humongous, red-hot data center in Texas of all places rather than, say, Iceland, where it gets nice and cold (at least for the time being)?
This outfit is missing a trick. They should contract soonest with The Finns to commission a sand battery* in which to dump all their bitcoinheat, then sell *that* to the consumers in Winter the next time the governor decides to decamp for warmer climes.
Given the truly silly amounts of heat thrown off by bitcointronics they might need two or more sand batteries.
And the costs of the Finnish Sand Batteries of Heat Storage could be leveraged using Texas’ liberal corporation-tax-avoidance rules.
Huzzah! Everyone wins!
* A “Sand Battery” is what was known in the UK years ago as a Block Storage Radiator, except those were made of concrete and the Finns don’t waste time dicking about with cement mixers and have scaled the idea up to match the stupid levels of heat data centers produce in places already too hot for most people.
Heh.
Our SAs who Must Not Be Questioned set up all the trad Unix versioning tools as "SA permission required", for reasons that passeth all understanding.
I asked my Boss - who was hot to trot on getting rid of blah.old, blah.<date> files littering our servers for a copy of the git software (I had no download or install privs). Refused.
I explained it was in use around the world *and* by all our vendors. Refused. He told me we had a "Microsoft product" that would do nicely.
"What's it called?" Dunno.
"Is there any training to be had for it?" No.
"Where's the documentation for it?" Dunno.
"Who's the admin?" Dunno.
So I went away and in a rage wrote a perl script that would make copies of any file into a .old version. You typed notgit myprog.sql and would get notgit.sql.old but - and here is the !clever bit - it would first look for all .old files and move them to .old versions.
So if this was your fourth "version" of myprog.sql there would be myprog.sql.old, myprog.sql.old.old and myprog.sql.old.old.old too.
I showed my boss when he came round to nag me. He was livid. I explained with my best "keen innocence" look that one could keep track of changes and fork from old versions by simply counting the "old"s and subtracting one, but he was unimpressed and shouted at me for not using the Microsoft product.
I did my "hurts borne manfully" face and explained that I would have done so but that I did not know what it was called, how to use it, where to find the documentation for it and could not contact the admin for guidance because I was unaware of his name, at which point my boss started to make wheezing noises and stomped off.
Later, we were in a meeting and he announced our dotnet devs had a new version of Toad that had a versioning engine in it. He said he did not know what the underlying technology it was. I told him I did. He asked me for the name.
"Git".
Ah, but you forget that as soon as the Clever Young Things are hired they fall under the powerful illusion that companies buy, maintain and replace computers for a living.
Ollie White had a radical suggestion in his course on Material Requirements Planning: Take your software staff onto the shop floor and show them what the company does and who does it. That way, that bill of materials breakout is no longer a report that can be delivered just so good, a bit late if necessary, but a vital cog in the wheel that grinds the grain to make the bread for the table of the programmer.
I did a contract a large concern that manufactured postage machines where they turned this on its head and had manufacturing bods as IT team managers. Unfortunately, they forgot to do the walk-through for the team members too, so there was still a basic disconnect with what the IT team hunchbacks thought they did for a living.
It is truly depressing the number of System Administrators in my current workplace who believe they are the top of the heap - and therefore must not be questioned when they make decisions - rather than plumbers needed to unblock the too-small pipes they installed for the real job we do.
Time for a snack and a cuppa.
"the rest of a ships crew are (as the article already indicated) always busy with maintenance tasks"
That would be just as true with the crashed aircraft finding sonar drone ship though.
Once the ship is shown to be capable of making the atlantic crossing those maintenance jobs become redefined, possibly as in-port jobs.
Not that I disagree that this idea is nuts. Saltwater and electronics do not mix well.
Because side scan sonar is so economic with the electricity.
Considering the actual business involved in doing a deep water undersea wreck search rather than simply lading and unlading cargo containers this idea simply does not stack up agains the cargo boat idea.
Amazing how many people don't believe that tungsten filament lightbulbs pop on being turned on.
I had a floodlight bulb in a bathroom that lasted for 30+ years because the switch had a dimmer built in and no rocker on/off like modern dimmer switches do.
Just like in a theatre, fading up - even really quickly - saves the bulbs.
Had a car that ate headlights and tried to get my EE Dad to help me design an in-line fader (he was fading fast himself and I hoped to revive his spirits with a nice little project) but he had no interest even when I expleined that I wasn't worried about overvolting in my own car (which he obsessed on) as much as economy in all the cars I'd ever own.
"Fortunately" a mechanic overfilled the engine oil on that car and killed it.
1) Easy to design a train that can break at random points along its length without the - unpowered remember - rest of the train rolling to a halt in the freeway?
Don't think so.
2) Real electric trains don't work to the powered tractor unpowered train model. Why would road-based versions work that way?
3) The streamlining issue is a bum steer. At 55-70 mph there is no need to worry overmuch about super-streamlining.
My vision simply reurposes the car. The road stays the same.
I imagine a future when my drive from NY to Florida down I95 could be done with me sitting in the equivalent of a 6-person railway carriage, wrap-around sofas, entertainments on tap, and not a steering wheel in sight. Basically, a train in which the carriages can go where the passengers need when they need to go.
A leisurely trip to Florida, overnighting in the car as it tootles along if I don’t want to break my journey, no need to face forward, watch the traffic (and traffic jams - those will be a thing of rarity when everyone is doing it my way) and no steering wheel needed.
The car would stop to service itself (swapping out batts maybe to cut down on wait time) and let me use facilities not included inside the cabin. I could tell it I want to shop for something on the way, or I want to stop and eat at a restaurant of such-and-such a type, and it would find the nearest place in which to do those things.
The idea of the car needing to still be a “car” once it can self-drive properly is risible. As is the idea I would need to own (and maintain) the thing.
One for the old Univac/Sperry Univac/Unisys crowd:
I was once asked to bundle up an application and send it and all the (empty except for configuration data) files it needed to another site across the country (never underestimate the bandwidth of a truck full of tapes barreling down the interstate: Tannenbaum), where "Univac experts" would install the same application and re-configure it to their needs.
I got a phone call a week later from an irate on-site expert: "You forgot to send SYS$DLOC$ ..."
Once had the pleasure of having a colleague from what they considered to be the most important office screeching at me that I "had configured <software> with a bunch of resources specified" - which was a problem in their office because they had rolled-their-own when it came to allocating shared resource pointers instead of using the computer manufacturer's automatic configurationatorizer like everyone else in the world, and those "specified" resources were "KNOWN to be reserved in the head office".
(I had the job of configuring this software in my office because I took a brief break from the madhouse to work for the manufacturer and knew how it all worked. Would that I had stayed there.)
I listened to the rant and then said I had no idea what the person was talking about as I had simply allowed the software installation to take defaults.
More ranting, until it transpired the person (who was sneakily trying to steal my job wrt this software and - because they couldn't bring themselves to speak to me rather than at me - was unaware I would happily give the job away) was looking at the configuration report file and *not* the configuration itself.
My sweetly delivered "Why on earth didn't you just ask me where to look?" must've been like drinking battery acid to that twit.
In my days as a Unisys DBA supporting a CODASYL database the following conversation happened at least once a month.
"The database broken!"
Not as far as I know, it isn't. Why do you think it is?
"Well I know I stored such-and-such a record on the database yesterday, and now it says the record is not on file!"
Did you delete the record?
"Of course not!"
Did someone else do that?"
"No-one would touch my test data!"
Lucky you. What did you change in the program?
"Nothing!"
So if I do an @PRT,S of all the library elements, the dates will all be at least a week old?
"Well, I DID change something in a subroutine, but it wouldn't effect the program!"
Let me guess. You added a few columns to your subroutine's DATA DIVISION.
"er ..."
You have displaced your calc keys by however many characters in your LINKAGE SECTION. You are chopping the front of the calc key off. That is why your record is not found, assuming your "no-one would touch" assertion is valid.
"So ..."
So you need to go fix your program so all the bits match the one bit you changed.
It got so bad at one point that when someone offered me a listing of their botch job and insisted the database was broken I offered a wager, that if I went through their code and found no cause for concern I would give them a crisp ten dollar bill, but for every protential problem I found they would give me one dollar. I pointed out that before they took the bet I could see I was five dollars up on the deal from what I could see on the first two pages.
That and the old "Your record counts say there are 66 thousand records on the database, but I can only find 60" thing. How many times did I have to tell them to re-establish currency when switching from "in set" to "in area" semantics? Well, I quit before an answer to that was available.
Not phone-related.
I transferred into a new department and was asked to replace their "expert scripter" who was retiring. One of the jobs he had written was represented to me as "vital, if this doesn't run we are in big trouble".
Said script ran at regular intervals and sent an email if there was a problem of a certain type. The problem was detected by examining the output of a "ps" command and using "cut" on the output to extract the pid, which was typically 3-4 digits on that hardware.
We had deployed a new Unix infrastructure from another manufacturer and the expert had ported this script to the new hardware, but had never checked it was working.
The expert had also usefully redirected stderr to the bit bucket because he never figured out how to make his dot profiles work for logon shells *and* batch shells and the script would fill the server mailbox with "can't do stty keyboard configuration stuff in batch mode" error messages. Said dot profile had a truly staggering amount of code that I think was trying to find out if it was running in a logon script or not. It certainly had no other purpose, but didn't work anyway. I surmised it was the work of several people. I digress.
As part of another project I sorted out the problem with the dot profile so that it *would* work in both use cases (if tty -s etc of course), and that is when I discovered that:
When the expert had deployed the script on the new servers, he forgot to also deploy the mailing list file with the addresses for that "vital" email, and the script was failing on line 2 as a result.
Smiling to myself I fixed that, and discovered that:
The new hardware was super virtualized. One side-effect was that pids were now 6-8 digits long rather than three or four. The "cut" command presented only the most significant of those digits to the rest of the "logic" and so was not working. At all. The "vital" email would never go out.
So I replaced the "cut" part of a massive pipeline with "awk" and the script started doing what it was supposed to.
And that afternoon the condition it was built to detect came about and fifty bajillion emails went out to the man who had told me how important it was he get said emails.
And BOY was he pissed. "Stop these G_D_ emails!"
So I descheduled the "vital" script.
All-in-all, an avalanche of suck.
Non-luminous object 3 and a third miles away?
Nope. Having ridden the slowly exploding bomb into LEO and having sat in a thin-walled tin can for x days awaiting the arrival of powdered Soviet satelite, the threat of something I won't see coming speeding past (well, not so much, orbital mechanics being what they are) a few miles away is not going to consume much nightmare time in the Steviehead.
Get a grip, man.