Funnily enough a lot of the time I'm talking about Ruby on Rails and Ruby's Active Record. They're a very good example of a project that says "Oh look how easy it is to build a web page with our thing!" with a trivial example. Last time I looked at it, I started having to look at implementation-level details of the packages almost immediately. I also remember it being an awful lot of code for what I needed. I really only needed about 10% of the functionality Rails provided, and had no way to scale down to just that.

Funnily enough I went through that phase where liked ruby, but am now back to the point where I'd rather just use perl with "use strict;". If I'm going to do OO development, I'm going to do it in C++ or Java.

Be sure to let us know if you ever go on tour with Steve Martin - I'd love to see that!

I set up UUCP to uunet once. Does that count? I think I still have a box of bangs around somewhere, I guess I could do it again.

But with ACTUAL GUITAR! We have the technology! Rocksmith tries to go i in that direction, though I don't know how well it does.

Yeah, the quality of the open source programs that I look at is usually far superior than anything I've ever seen inside a corporation. Although... at one company I worked for, I had to audit the source code for the original AT&T C standard library. That was obviously done by people who knew what they were doing. I also recently submitted a pull request to the gnu flex maintainer on github. Flex seems to generate some pretty decent code, but the code it uses to do it is a maze of global variables. I did manage to tweak it to generate a C++ class that works for me without the #include fuckery that flex typically requires, but I don't know if the maintainer is going to actually like that change. Doesn't matter to me, I can just use my version from now on.

I'd be happy to just go into a company and write unit tests for their code, but in most cases that would require dictating huge design changes to a lot of their code. If I take over a code base, I like to start writing unit tests for new development and bug fixes (Write the test prior to fixing the bug.) Last project I worked on was an old C code base with hundreds or possibly thousands of global variables. In some cases there were multiple global variables for the same value, and they got used in different places and often had to be set to different values in order for the code to work correctly. It might not have been too bad to go through and make sure it was just passing everything it used, but it was a lot of code and it kind of all needed to be changed at the same time. Much too much of an effort for the team that was working on it.

Or is just complex and unfamiliar. The problem with these frameworks is they work great when they work, but you only ever see them working because they've been published with the most trivial example. When you actually start trying to do things with them, you have to know implementation-level details of the framework in order to make it work for you. By the time you've invested all that time, you may as well have written something less generic that actually does what you want.

Oh and when I say they work great, I was kind of lying. I have a favorite example. A while back a developer I was working with wrote some Spring/Hibernate code to pull records in from the database and print a billing report. Soon as he handed it off to me, I thought "What happens if I throw 100000 records at this?" Well what happened is that it crashed. So I cut the number in half and it still crashed. Down around 30000 records, it started taking about half an hour and THEN crashing.

Turns out he was using the framework to pull all the records from a couple of different tables and doing the join in Java. The SQL join I wrote to test the code took a couple of minutes to run on a million records and returned the correct output. On a hundred thousand it was neighborhood of 10 seconds.

Now the Spring/Hibernate people will be quick to point out that you can edit some XML file or something and make the framework do a join for you, thus solving that problem. And that is true, if you know a fair bit about the framework. And you'd have to know a fair bit about all the other frameworks they used on that project, too. By the time you got done learning all the frameworks they were using to the level of detail where you could actually be that effective with them, you could have written the application they'd built 10 times over.

Fortunately this story has a happy ending. The team ended up deciding to run the original developer's code against the billing database several times a day so that it would never have so many records to process that it would crash, thus solving the problem once and for all!

Remember: The needs of the many outweigh the needs of the few!

Short sighted leadership making cars no one wanted had nothing to do with it.

Heh heh. Now current workstation has the Monkey Virus!

Oh, I thought someone just took a shit on my Slashdot today. So... It's going to stay that way, huh? Huh...

I don't understand why people are expected to buy more software on their phone then on their PC

But they DO! For a majority of PC users software is scary, many worry about installing *anything* as it could "break" their computer. They lack the savvy to recognize fake vendors and malware apps. Also plain software incompatibility is a huge problem for them to understand. Even if they do buy something, many cant even find where their downloads go.

Now compare this to a smartphone App Store. Your CC goes to one place, Apple or Google who they already trust more than random developers. Installs are single click, generally can't mess up th system and are easily removed if you didn't like it.

All stores are MUCH safer and comfortable for general computer users. This is WHY there are millions of apps, finally non-technical folks are empowered to try out and explore software largely without fear. It's been a huge experience for them and finally showing them the potential of computers that WE have been claiming for decades.

So yes, people most definitely do pay more for apps on their phones than their computers, and they like it that way.

Meanwhile in Europe where one party's politicians don't spend as much effort trying to use global warming as a bludgeon against their political enemies (and an excuse to funnel public money to their friends) popular acceptance of "climate change is a real thing to worry about" seems to be higher. How about that, hmm?

It sounds like I haven't reached you. Insurance companies share some of the blame, but insurance is simply one way of paying for healthcare. The insurance will always be stratospherically expensive as long as the health care that it must pay for is expensive. In a way, the insurance companies enable the charging of high prices by not pushing back harder against unscrupulous providers who charge high prices.

I'm curious to see how often they have random people tell them they're their father, or ask them if they can lend a hand. It might not be that many, if they can also crush bone with their bionic hands.