Our third major release in 18 months is going out in two weeks. We have not yet sunk into the quicksand.

I'm beginning to like Agile. I don't have to wait 2 months to find out my next release is being delayed another 2 months. In Agile I get disappointed every two weeks.

This is not sarcasm. My users now get told their fix will be in weeks, not months, and no finding out 2 months later that's another 2 months. Yes, they still wait 2 months, but it feels better. To them.

0. Netflix will charge the end ISP (Comcast, for instance) with throttling or pay-to-play.Lawsuit.

1. ISP (Comcast for instance) will claim this is the fault of the lousy Netflix connection (through Cogent, for instance), and maybe even sue the connection provider.

2. Netflix's provider (Congent, for instance) will disclaim any responsibility, maybe even sue Comcast (for instance), you know, slander.

3. After a few years, customers will buy the higher tiers of service from Comcast (for instance).

4. Before that, customers will buy the higher tier of service from Netflix, the one that has such better speed and performance, the one that is connected directly to their ISP (Comcast, for instance).

5. Profit!

And little has changed.

They may be wrong, but they are working for the Left in America.

Owning the majority of the media is wording.
Winning elections is working.
The courts are working.
And they are now beginning on usurping local police.

Only opposition can still them, obviously.

Any of the Sennheiser or Shure wireless packs.

Countryman E6 type headset. Best every

For $700-$800+ you've solved the microphone problem. Look for used, maybe save half.

Maybe a Shure BLX14, $300

An Audio-Technica System 8 might satisfy your needs, $200 +/-

Then go fix your speaker placement and EQ the room. The Countryman likes a slight cut at 600Hz for vocals, choose the capsule cover carefully. The A-T mic I don't know well.

Are we going to permit 'inadvertently shed" fingerprints also?

Oh, wait...

Actually, there is no technical reason to limit .TLDs to a single registrar. Oh, wait...

I got to pile on about this.

".dev, .lol, .app, .blog, .cloud and .search." .dev certainly has usefulness well beyond Google. ICANN should refuse this outright. .app? After the fight with Apple, let ICANN deny both of them. .cloud? See .dev for the explanation. .lol? More of the same. .search? Ask Yahoo, Microsoft, and Steve Wolfram about this. .blog? Remarkably tone deaf.

ICANN should specifically refuse not only Google, but any Google-related applicant.

Unimaginable. I'll be looking to file comments on these with the relevant parties.

I used a DUN connectoid, but. Wildcat! was fun.

Trumpet Winsock.

Next question.

It's the return fire your want to suppress, as well as those last few outgoing rounds.

And the possibility that they move just a little bit and continue to fire. Your underestimate the resiliency and determination of good snipers. You had best kill them first shot.

You obviously are neither a commander nor a soldier.

Soldiers want to kill as easily as possible, lest they be killed.

Commanders want killing to be as easy as possible for their troops, to both win and get troops back.

From the movie 'Patton': "I want you to remember that no bastard ever won a war by dying for his country. He won it by making the other poor, dumb bastard die for his country."

If only Patton had said that.

"If you wound someone, one of their comrades has to drag them back to cover."

This is not universally true. Sometimes killing is an excellent outcome.

And then there is the problem of roles. You can wound a MRAP driver and cause problems, but you'll want to kill the sniper with the first shot, lest they continue shooting.

Ditto. My phone is handier than my wallet, and I can pull up Softcard, PIN in, and tap faster than you say 'oh, please....'. And you're gonna be fishing for another penny to save time with exact change.

Disclaimer - I work for a Softcard partner, and am sort of sad to see it go to Google. But hopefully it will become the main competitor to Apple Pay, which is for us an interesting problem. All is not bliss in Apple Pay land.

"There is at least a 5 second processing time. Closer to 10 seconds in most cases"

The acquirer takes 2 seconds tops. 60-200 millisecond round trip.

The rest are POS issues, and even small stores have systems that don't take 7 seconds to give the operator the thumbs up...