Most open-source "foundations" have been operating in a "give away the razor, sell the blades" mentality.

Give away the razor (base software), sell the blades (support contracts / phone support / specific pay-for-implementation requests / etc).

I can see why the IRS is having a hard time taking claims of being a nonprofit or public-benefit company seriously when that's examined. It's kind of taking the "how to make money off FOSS" instructions constantly published in the community at face value.

Unfortunately, it's a fairly standard business tactic.

Corp X has assets and debts. They sell the assets to Corp Y, which includes products, staff, equipment, etc. Corp X holds the debts. Wen they declare bankruptcy, there's no way to recover the debt, so it's gone.

Corp Y may be operating in the same office, with the same people at the same desks, doing the same jobs. The only real difference is that employee paychecks now say the new name, as does all new marketing materials and letterhead.

So what about the people owed money from Corp X? They get nothing. Or if they're lucky there's something left and they'll get pennies on the dollar.

Sometimes it's done for the right reasons, and they will work out deals with those owed. For examine (if I read the article right), 2600 is owed $100K. That may be broken up to $10K/mo over 10 months, or $1K/mo over 100 months. In the end, they get their money. Unfortunately when they already have high dollar events scheduled, it hurts.

Of course, because of ... Betteridge's law of headlines.

I guess I'm weird. I use text editors.

On the server(s) or dev boxes, I use vim for anything.

When I'm on a Windows desktop, I use UltraEdit. I don't use most of the extra functionality, but the brace matching lines are nice. I could almost do just as well with notepad.

I have to pay more attention to what I'm doing, but I end up writing better code than I see churned out by a lot of people with overly helpful IDEs.

A while back, I was thinking about how to to make an ultra-long range drone. Like something I could send off on a mission, and expect it to come back on it's own later on. One of the ideas, if it were battery powered, was to instruct it to land on or near power lines. That would have been a nightmare to figure out though.

To be stealthy, it would need to fly around 5K to 10K feet. It wouldn't be able to approach ground level, except in uninhabited areas. There's no way you'd get a map of all the high tension power lines in the world, and I don't know of any method of detecting them miles away. Well, other than Hollywood magic methods, which unfortunately don't translate well to the real world. :)

To land on power lines or on the connecting towers, it would have to hover, which is battery expensive. Automatically picking an arbitrary landing spot isn't exactly easy. Once you're parked close to the power lines (like on them, or on the towers) inductive loops could handle farming electricity without human intervention or needing to deploy charging mats.

In the end, I gave up on the idea. I don't really have a reason to make one. If I did, and it worked, I'd have all the lovely three-letter-agencies knocking on my door to have a chat over a nice cup of tea.

Maybe "nice" would be optional in their opinion, and cup of tea would be room temp water in an interrogation room. Either way.

A bus is a lot bigger than a car, with a lot less margin for error. I have a city bus that's converted to be a RV. All that extra space beside a car becomes pretty much non-existent. According to the FHWA, lanes are 9 to 12 feet wide. My bus is 8.5 feet wide, so on a narrow road, that gives me 3 inches on either side on a local road, along the 40 foot length of it.

The last drive I took it for a drive, I cruised down a 6 lane "local" road, with 9' lanes. It was like threading a needle with giant steel elephant, and people get stupid around large vehicles. Sure, it can stop on a dime, as long as that dime is the size of a Buick.

Bus passengers tend to be more annoying too. They tend to argue, just because they can.

The "don't talk to the driver" rule is mostly there so the driver can say "Go away, I'm driving." I've had plenty of bus drivers that like some idle conversation. I'm not asking how to get to some obscure place, or demand that they take the bus off-route to drop them off, so they like talking to me. :)

Passengers scream a lot more about perceived threats too. :) They may see something out of the corner of their eyes (or directly in their line of sight). The person on the other end of a phone call rarely sees your driving hazards.

It sounds like the formula for an urban legend.

Take a little bit of truth. Just enough to be believable. Build up that truth with whatever lies you can tie to it, get enough suckers to believe it, and you'll have the next Snopes entry.

I could build an inductive receiver. Given enough time, it could charge a small battery. Believers will see "enough time" as being minutes or hours. People analyzing it will see it's really centuries. The whole time, I never lied. I just let their misconceptions carry it along.

In the last several years, things have happened. Someone very close to me died with no notice. Quite literally, I saw him alive and normal at home. I went outside. A few minutes later I went back inside and he was dead. Natural causes.

I went in for spine surgery a few weeks ago. I could have walked away from it, or have been rolled away to the cemetery.

I always make sure someone knows how to do what I do. That person usually knows where everything is. They don't necessarily have all my passwords, but they know where the "key" is, which guides them to the vaults (one logical, one physical). I double checked the key, and the instructions for the vaults before surgery, and reminded them where the "key" is hidden. My "key" has another more colorful name, so I'm not even giving away secrets here. :) Your "key" could be something like an envelope marked "1997 expense reimbursements", with just a piece of paper containing a few important passwords and instructions for the rest.

It doesn't have to be a life changing (or ending) event, or even an employment terminating event. It could be something as dumb as you're stuck in a remote airport during a blizzard, with no data service, and something major happened. Sure, everything *could* wait a week for the storm to pass. Or you could say "Call X. Tell them to go get the key. They will understand and can take care of everything." The instruction to "Call X" is kind of redundant, as the primary people should already know who the "oh shit" person is to contact. It's just reaffirming, "I'm stuck, and can't do anything from here."

Just be very sure you can trust the people holding your secrets.