I do realtime embedded. I made a kernel that had C++ support and it would crash on boot. The watchdog timer would fire before all the C++ support initialization routines would finish. I had to disable the watch dog timer temporarily. I think it was the exception and io streams initialization code that was the culprit. The whole exceptions thing can be bloated depending on implementation to varying degrees. But in the end what is more bloat (checking return values all the time or exception frames handling all the time) I do not know.

Somebody mod this up, that's exactly what's done on ARM.

True, but that's not the case with ARM though since thumb mode. Most instructions are then two bytes. ARM also has some neato features in it's instruction set, like you can shift for free almost every time you do anything else with a register like arithmetic. Also condition codes only change when you want them too. And almost every instruction can be conditional. This makes it so that the little cache there tends to be is utilized pretty well and you don't really need the branch prediction logic as much. I think unlike the other RISC chips, in the case of ARM, IA32 keeps up only since they are made in more modern efficient process to a greater extent.

I agree and unless there's something in CPAN pretty much already solving my problem (which happens a lot actually), I almost always choose python so I'm being honest unlike that person that somehow thinks the python makes more sense. I think that with perl, it depends how much shell scripting someone did first. Somehow a person needs to have experience with some syntax that's not like C/java/pascal and has reached the limits of shell scripts plus tools like sed and awk first before perl clicks or they can see the value in it.

You answered the real reason why maybe, it was a couple of instructions. In SWEET-16 it was one. Storage was expensive then. I think that must have been the real reason.

Exactly, also BMW and FIAT have engines with throttle bodies where the butterfly valve is open under most conditions. They all have spark plugs though, which is what I think the fellow you replied to was thinking about.

What? Like there is a carry flag, there is an adjust flag, it's set every time (unlike needing to use adc say). You just do the normal add, sub, or mul. Then daa, das, or aam respectively to adjust the values to BCD.

Now that's a proper car analogy!

No Bob sets AL = 0, does int 13h, and writes down the values of the registers. Then he does AL = 1 .... After that he hands that document to Fred, who writes the code that acts the same.

Sorry if I caused any offense. I don't know them, I'm sure they are great. I was just replying in regards to the list of reasons, which I thought was weak in my opinion. Sometimes I get cynical and snarky, again I apologize. I should have stopped at before all that you quoted, it was a reasonable response the words I wrote before that. Basically that not much has kept-up with visualization, especially in a browser. I worked (wow now more than fifteen years ago) on that as my first job after graduation, it sort of depresses me the state of scientific visualization to this day, hence why I got so grumpy in my reply. Cheers

Wow that's pretty bad, the only reason in that list that makes any sense is the rails one. But there have been lots of visualization packages for science for decades. It's just that it's a brand new group of people, not familiar with what is there, only familiar with what they know already or what there is buzz about, and they want to use that. These are ruby coders after all.

I've bought a new car and one for my wife, I took the cash back once and once the 0% precisely for the sort of calculation you did. There was a big trade in one case that made the financed amount small and the relative percentage of the rebate big enough (and I still had a big enough cushion of savings afterward). It's just not as simple as you initially made out as it's free money - take the 0%.

That principle allows you to have line noise that parses in other languages, make is harder to do that in python, so I don't know really if it should be followed to such dogmatic ends. There still is a lot of freedom in presentation in python after all. The cstyle and later astyle commands are a taste thing, some C coders liked it, others didn't. I always like to use whitespace to help me and others understand code and have it in a consistent style from the get go, not have a script or program munge it for me. I can have my editor auto indent python code too though, I use that a lot like when moving a block of code into a function, its moves over to the left on paste. Also about the new coders and pasting from examples on the web, having your editor change tabs to spaces always including (especially?) on paste seems to do the trick pretty well for those that do not want to deal with that headache.

1. vim s///g
2. vim folding
3. vim >, <, or =

I guess vim isn't an ide though, thankfully.

Really? There wasn't an option like 0% financing or $2500 cash back? If you had say $17.5k in a savings account it would not have been a $20K car.