Sounds to me like we have the following folks:

1. "Owner" of server... meaning, he thinks he owns it.
2. He doesn't own the hardware said software sits on.
3. The company met their SLA, and this guy is not being accomodating. Prob 'cause he doesn't want said ISP knowing what is on his box... ergo, materials and/or services that break said ISP's SLA.
4. Or, everybody's favorite option: he is a lying twit making up the whole story.


Considering not that long ago I found a former client's "server" (read: a tower PC that used to sit in a rack chassis) that was pulled from production for running an open SMTP relay (and the owner wouldn't provide root access nor fix his illegal broken shit) on top of the dumpster... I vote number 4.

Prove me wrong, OP. Prove me wrong.

Chrome OS is a Ubuntu shell replacement.

• I'll join the Red Cross/St. John Ambulance when my doctor start providing free treatments.
• I'll volunteer at the soup kitchen when restaurants start giving free food.
• You hopefully get my point

Lawyers, doctors, builders, pilots, general people, regularly do volunteer work for the good of the public. The point of doing volunteer work is that by definition, you are not fully compensated for your time and effort but hopefully, it makes you feel good that you have made a difference.

Use it, submit bug reports, and participate on forums. When you can, push for more open-source to be used in your organisation.

The modems are layer 2 and below devices. They don't know or care.

Routers are the real problem as far as customer premise equipment goes; however, the relevant functionality is typically in software on most consumer routers. Ostensibly this means that manufacturers can release a firmware upgrade.

I find that the turnover on those router boxes is rather high, so I suspect that newer routers will ship with it and the problem will slowly go away.

Buy support. Pay for your Linux licenses. Just because it's open source doesn't mean that you should pay $0.

By buying from a legitimate open source company, you help reinforce the open source eco-system.

And it's all legitimate: it's not a donation, so your boss shouldn't object. You are still saving a lot of money compared to buying a proprietary solution, but you are helping people who code full-time sustain themselves. Let's face it, developers are the critical resource for most open source projects.

PS: some cool startups are looking for extra developers/founders: help people go solar, build a better bug collector tool, or help build a music community that supports its bands.

Everybody says that, few, if any, buy like that.

To clarify, I was groping for examples where the sequel was "better". As the years went by, I actually started liking the Dylan versions better. Less production, more passion... if you can get by the timbre of his voice. I didn't offer any examples where the sequel was worse, since I figured they were plentiful enough.

There. Fixed that for you.

There's nothing cooler than money. When "cool geeks" in the USA no longer have to compete with "cool geeks" in India making $5/hr, you'll see many more "cool geeks" in the USA.

Believe anything else and you're either delusional or trying to sell something.

I hear ya bro, you've got 2 gigs, you might as well fill 350 megs with bytes to display about:blank.

Hang on though, which bytes are actually needed to display an EMPTY PAGE ?

Even considering he's storing the DOM which is basically a set of empty containers for js, document head, document body, css objects etc., why in fucks name does it take 350 meg ???

The indexes only work on MyISAM. Who needed transactions anyway? Every feature MySQL lays claim to is always full of gotchas like this.

If you have invested a lot of money in a language and it's dumped, it certainly is an issue. Things may not stop running completely, but you get issues and those issues will no longer be patched. More than this, if you were selling commercial VB apps (as we were), customers tend to be quite concerned about buying an application written in a defunct language. Our main application was in VB. It was big and a lot of money had gone into it. You can't just ignore that and hope things will keep working. What happens when you want to write some new module for your large system? Throw money at writing it in defunct VB6? Or go down the hellish path of writing new modules in C# and use interop?

If you just had some little in-house tools in VB6, its dumping by Microsoft may not have been so much of an issue. For companies whose main product was in VB6, I can't understand it not being a major issue.