I second this idea.
On the servers I manage, the usage is fairly stable so we have alerting set at various levels for each file system. Some are set above 95% and others as low as 60%. I want to know when disk usage changes abnormally, no matter what the absolute level is.
Some disks are less important than others so they just send email alerts. The file systems that are critical send text messages since we're a 24x7 shop.
How does performance change as the big disks approach full? That was always one reason for the rule of thumb about keeping at least 10% free space on UNIX.
I agree. Show info on known bugs in release versions, but keep development track stuff limited to those actually working the problems.
Just start small with hybrid motors in the buses, enough to get them rolling again from their frequent stops (and red lights of course). If you just improved the fuel mileage a couple of miles per gallon, it would make a huge impact overall.
It's even worse than you think!
Having said that, I love programming in this language (well, Intersystems Caché actually). The database and language are fully integrated with a very powerful standard library.
In MUMPS, now mostly used in Intersystems Caché, white space is significant in a strange way. There are places where one space is required and other places where two spaces are required.
You said: "as web apps using PHP"
How about just using PHP from the command line? It's dead simple and just extends all of the things you already know how to do: sed, grep, shell scripts and C. Just read from stdin and write to stdout and you have access to a lot of capability with very little new learning. You don't need web pages to write PHP. It can be used like any other scripting language (Perl, awk, etc.)
:-) Wasn't trying to be virtuous. Merely sticking up for the first poster.
I think it could be true. I wrote over 200,000 lines of C in one three year burst in the early 90s. A multi-tier client server thing, everything from user interface to SCSI control code. It is running still in production 20 years later. So a million lines in a decade is at least feasible.
8 m of thermal expansion/contraction would make that the biggest bridge in the universe!
Point: there are quite a few Columbia River dams downstream of Wanapum, not just one. There is only one below Wanapum and above the free-flowing stretch of the Columbia, but that is only about 60 miles or so. Then there are a few hundred more miles of river with several more dams.
Point: there are many buried reactor cores at Hanford. Hanford is large though, over 500 square miles, and they are not subject to flooding even if the dam was gone.
Biggest concern at the moment is the potential fluctuations in the cost of electricity.
although radix is a close second. Depends on the mess I'm dealing with at the time.
:-) Almost happened once. Some sensors got wired wrong. Somehow the QA failed. When the temps started going up it got noticed instantly. We fixed it in software in an hour and continued.