tired_man

What a load of fluff. I'm glad wired hasn't endangered it's preeminent position as the tech equivalent of the National Enquirer.

Mick Resnick's "Feelies" is based around future society where this has happened.

Cruise missiles that aren't supersonic aren't of much use. As long as they're in the air, they're targets.

The author painted a very gloomy picture for the carrier. But it isn't all one-sided. In a wartime situation, the carrier would have a much deeper defense. Several hundred miles or more. The E-2 EAWS aircraft easily provide coverage over a 500 mile bubble. Paired with other maritime surveillance aircraft and satellite imagery, they'd have a handle on the nearest aggressors and plan accordingly. Even supersonic missiles need time to travel 2-300 miles.

You know the funny thing? When I was in, the idea was that we'd get off that one big Alpha strike. After that, well.. No one expected to be around long enough to ever recover aircraft if it came down to cases, and the aircraft probably wouldn't be coming back anyway.

War sucks, people die. But the side with better weapons loses fewer people and the best probable chance of surviving. No sane person wants a war, especially the military. That's the sole purview of insane politicians.

Sure, the CVNs are big and their expensive. No argument. But they also have better manning and logistics requirements when compared to multiple smaller decks. Most people fail to realize that the avionics systems in those planes require dedicated test systems that in themselves costs many millions of dollars each and require very, very, well trained technicians to maintain and repair them. That is in addition to the technicians who actually repair the avionics systems.

Then there are the jet's engines. They also require a substantial capital expense for the maintenance systems.

Everything that is found on a big deck is also required on a smaller deck. And you don't get much of a break, either. If a big deck needs four expensive avionics test systems, then the smaller carrier may only need two. In some cases, there might only be on of a particular test bench on the CVN. But that one needs to exist on each smaller carrier. By the time you have three smaller carriers, the capital costs are already higher than for a CVN.

Don't get me started on trained personnel. The shop supplies the basic cadre for the intermediate maintenance shops and each squadron kicks in some technicians to support their systems. Those shops ran two 12 hours shifts (someone jump in if this has changed). Want to take a guess at many more maintenance people it would take to man three smaller ships vs one larger ship?

Aircraft maintenance is more than poking around with a multimeter, swapping tubes to get the radios working, or swapping out a cylinder on a recip engine. Systems are more computerized and require intelligent people to operate them.

You can't stuff 40-50 aircraft onto something with a cat and arresting gear without also providing all of the very expensive ancillary repair systems to support them.

The days of the jeep carrier are long gone.

Author apparently doesn't know that carrier task groups typically travel with their own attack sub. If there is a possibility of hostile submarines, someone will be more than willing to stuff mk48 up their tail.

But that was half the fun of doing learning to hack on a C64. Adding coder tools typed in from MLX code from Compute! or Compute!'s Gazette and learning assembly by taking apart programs in Monitor was a deep learning experience for many beginning 6502 coders.

It's sad that they didn't last, but the chip was simply an evolutionary dead end. I've recently thought about finding one to give my grandson in an attempt to pry away from a tablet his parents gave him.

The crop of tablet/cell-addicted kids is a sad state of affairs.

For most things, my C720 Chromebook runs Ubuntu and handle any tasks I need. Don't equate price with utility ;-)

TIFF. It might have been handy in certain instances, but IMHO, it was never been a big deal except in the page-layout world. And even then, having an eps was better.

I missed that cluster of madness for firefox, I guess. Had I known that Mozilla would turn out this way, I would never have donated money. My name is on their full-page NYT ad and poster.

I wonder if they'd give me a refund?

> Mozilla was driven into the ground by better competition

I thought it was Microsoft's anti-competitive strategy? (bundling IE, changing the API's to break netscape, etc.)

I thought it was Mozilla's utter lack of regard for the their userbase.

That is their prerogative, though, and I don't begrudge them the opportunity to try. But short of setting up in-store cell systems that cut out those of the individual carriers, I don't see how they'll manage it.

I never use in-store wifi and only turn on data if _I_ need data. I'm always amazed by people who complain about battery life, yet wander around with wifi,data, and bluetooth running 24/7. :-)

The more you know.

Like most sheep, they're marching to slaughter and don't care. I have friends who have plain, old dumb cells that can't even text. But they are reaching retirement age and it doesn't matter for them. Persons who take an interest in their environment and safety will find out and take measures to safeguard their privacy, but the others, like sheep, will blithely ignore everything and continue to broadcast every facet of their lives to anyone who will listen. There's no hope for them.

I can't even be bothered explaining it to them any longer.

Turn off location services. I don't think many people actually need to walk around with GPS active.

All the more reason to use a custom ROM.

Unless Google Play Services can somehow turn on GPS without it registering as a battery usage item, I doubt they are successful in tracking me.

I happy she was able to check out on her own terms rather than being forced into a miserable existence.

You're right! This is a welcome addition.

Dear FBI,

Perhaps using some real investigative techniques rather than fishing expeditions would engender some trust towards the FBI.

Oh, and about those malware apps you push into people's computers? You might want to knock that shit off. That practice is no more acceptable when the FBI does it than when hackers do it to steal financial information.

No one trusts you to abide by the Bill of Rights.

This is a tired, old line those opposed to marijuana legalization trot out whenever the polls concerning legalization show an uptick.

The fact is, that people who tend to be lazy will stay lazy and those who are motivated stay motivated.

A cursory web search for successful marijuana smokers wil return people such as Carl Sagan, Steve, Jobs, and many more.

Smoking pot doesn't turn one into the a Cheech and Chong stereotype. If you weren't already a lazy slacker, then smoking marijuana will certainly not cause you to become one.

I thought having the poor taste to plunk one down into a neighborhood where it was a sore thumb was enough.

I'm happy to see there are other aesthetic reasons, too.

It's a cool idea, but I think it's very unrealistic to label this vehicle as a bus. It is more along the lines of a streetcar, especially since it will only be traveling along fixed paths and isn't able to turn down a side street to detour or make an ad hoc route change.

The Prince - Machiavelli

I remember Fido. I briefly operated a dial-up BBS in the early 90's. Fido was a great way to have globe spanning discussions with other having similar interests.

There are some FidoNet archives floating around as torrents or as websites, too. There isn't an all inclusive repository, though.

I'd add a drain in a bottom corner to allow drainage as it melts. I think the temp in the dry ice container would remain lower if there were enough thermal mass, too.

Have you ever played with dry ice? I just read of someone using it to remove old tile and mastic from a concrete floor. There was also an article on another site describing a city dropping chunks into rat holes to kill rat nests.

It would be interesting to see this repeated, but allowing the melted water to drain. I think that this might be why the wet ice seemed to keep cooling for so long.

What? Do you mean using AGILE techniques?

I think I'd rather they take the time to actually come up with the right answer first. I don't think submitting a JIRA is very effective after you're dead from something they thought they could push to the next sprint.

Pinnacle Group - https://www.pinnacle1.com/Home

They've been straight with me and got me my current gig.

The Air Force wants the cash to help make up for the abysmal F-35 program. The USMC and Navy should have control of ground attack resources. Let the Air Force play with their missiles and laser death rays.

If the Air Force is so bent on getting rid of these wonderfully useful, tough machines, then perhaps they should entirely leave the ground support role to the US Marine Corps and the US Navy, both of which have a long history of providing ground attack support to troops.

The A-10 is the best damned aircraft at this role since the AD-1 Spad's were retired.

All the Air Force wants is glitter and fame, they aren't really interested in life on the ground. Give them their wish, take the A-10s and give them to someone who will use them to their fullest potential.

That's the traditional method of developing.

Requirements doc -> Functional Spec doc -> Technical Spec doc -> User Docs.

Or,

What you need -> How you'd like to do it -> How you will do it -> How it works

You're doing it just right.

Of course, to keep up with the times, you have to toss together any sort of code and then write some half-assed docs that may or may not represent how the app works (The Agile method: Wonder at the agility of developers dodging any sort of spec-writing).

Perhaps not, but I'm willing to help support their efforts, I just don't want any more dusty hardware on the shelf than I have. I think that adding a couple GB to the package or a second slot would boost demand and drive down unit cost.

I'm not looking for something powerful, just a small, low-power box to run daemons, but 2GB is limiting it's usefulness.

Even when they are distributed exactly to their demographic, that 2GB will be a wall they hit as they become adept at computer use. Then they'll have hardware that is not quite big enough.

I want it to succeed, but I can see it becoming obsolete in a couple of years.

I love the idea of mini-pcs, but the specs are always dismal.

To me is teems like a single-purpose machine deisgned for web-surfing. People do more than surf and so I see less utility in this that I do in a ChromeBook.

Maybe with 4GB with root access and allowing me to change the distro and operate a lightweight server. Say SABnzbd, or plex media server(but not for transcoding, of course).

I bought a Zonbu when they appeared and ran mine until it died a few years back. It was handy for quick local network admin tasks and ran a few low priority cron jobs. Very cheap to operate, too.

It's the marketing buzzword flavor for this period. Remember when everything was robust? Or resilient?

I don't know what people think they're doing as they write this stuff. If technical documentation was written like, just imagine how long and flaky their docs would be.