Good, please let it die. OpenID is as if someone sat down and said to themselves "username/password is too damn quick and easy to use. lets replace authentication with a URL for a website no-one can remember (that still requires a username/password) and make it fragile and hard to implement! oh, and let's make it slow. sometimes. yeah, that's the ticket."
avgas is 110 octane and full of lead. even though it's "low lead" it has more lead than leaded automotive gas had. it will destroy your catalytic converter and oxygen sensor(s). don't use it if you have a car made since 1975.
Ahh, you are correct. I'd never run into it before since I generally consider it bad form to modify parameters.
Leave it up to PHP to introduce nuances in every aspect of the language. After 8 years of PHP, issues like this are why I'm trying my best to move on to other languages.
I'm a general aviation pilot and would LOVE to have a fuel-injected engine. More power, better reliability, better fuel economy, smoother running, and one less control to monitor.
One big problem with EFI is how to handle total loss of the electrical system. As it stands now, you can lose the alternator, the battery, and one magneto and still fly. Same with mechanical (Bendix systems) injection. However, with the mechanical systems, you don't gain a whole lot. There is still a mixture control- they basically act as a glorified carburetor.
With EFI, if you lose the alternator and the battery goes dead, the engine stops. An additional alternator and battery could be installed to mitigate most of the risk. Same for the coils. You could even keep a magneto as a fallback if the coil dies.
Really, the biggest opposition to modernizing GA is the government and all the red tape involved. It would fairly easily cost millions of dollars to just get an EFI system certified on ONE make/model. Even if you targeted the Cessna 172 with the Lycoming O320, the cost would be prohibitive. As just a guess, it would cost $30-45 thousand per installation- close to the cost of a complete new engine with mechanical fuel injection. Not really a viable option.
There was a program a few years ago call the General Aviation Propulsion engine (GAP). It was supposed to reduce the cost and increase the reliability of GA propulsion. Last I read the project was "considered a success" and disappeared. Seems like a shame, really.
In PHP4 objects are passed by value. In PHP5 they're passed by reference.
This is probably one of the most misunderstood features of PHP5. They are passed by reference, but they're also copy-on-write references. As soon as the variables value is changed, a copy is made, and the function/method then uses the local copy (as if a copy were made in the first place like in php4).
Nothing has changed for the programmer except a reduction in memory usage.
In PHP5 you also have public, private, and protected variables.
Yes, optional. The old var keyword works the same as using public.
In PHP4 class constructors were the same name as the class. In PHP5 it's __construct.
Again, optional. There is also a __destruct() method in php5.
I could go on about the difference, but I won't. There's a lot of differences between the two.
There are a lot of differences, but backwards compatibility is pretty good. A coworker and I converted a 130k loc mess of a php4 codebase (originally php3) from 4.3 to 5.1 with only a handful of changes. It just took a bit of research and a bit of planning.
And yes, good riddance to php4. It will not be missed.
I work for a real estate service company that lets agents, buyers, and sellers do their respective thing online. Pretty large slice of the demographic pie.
From one of our webservers (Month-To-Date):
IE 13992090 92.5% Unknown 700841 4.6% (half of which are the server checker) Netscape/Moz (63% firefox) 407199 2.6%
ZFS, the dynamic new file system in Sun's Solaris 10 Operating System (Solaris OS), will make you forget everything you thought you knew about file systems.
Don't forget, everything is possible with the Zombo File System!
Fiberglass is fairly popular as the primary component in aircraft construction for general aviation and experimental aircraft.
See: - Glasair/Glastar - Cozy Mk IV - Vari-EZ and Long-EZ (couple of Rutan's designs; he has several others that all use composite fiberglass construction.) - Quickie - Cirrus SR20
Those are just a few that I can think of right now. There are dozens of others.
I would imagine that the spacecraft is built with mostly carbon though. It's stronger than fiberglass and can be built lighter.
Not really. He's talking from personal experience. In the previous article he notes that he knows one good programmer who chooses java.
I think the point Graham is trying to make is that if a programmer knows only one language, and it's java, that person is probably not a good programmer. They're someone who was taught some idioms in college and can squeak out the par-level code required to bring in the paycheck.
A good programmer seeks out a good language. And a surprisingly high number of good programmers choose python or lisp.
If you want to fill a seat, choose java. There are a million and one code monkeys out there that will take the job. If you want to fill a position with good programmers, choose a language that good programmers use. Java is not that language.
I think you missed the analogy. It's more like "Fords suck because all the good mechanics I know drive Chevy's." While the mechanic may need to work on a Ford (Java) now and then to pay his bills, or he has to drive a Ford as a work truck because they won't supply any other brand, he chooses to drive (and work on) a Chevy (Python).
Does anyone know what the Traffic Rank means? My company's site is listed as a 2, slashdot is a 1. Lowest I can find is a 4. Lots of sites have a Not Available rank.
A manual's greatest advantage (direct link from input to output) is it's greatest disadvantage when towing. If you rev up an automatic transmission trying to get a weight moving, it'll just overrun the torque converter and heat the fluid. If you do the same thing to a manual, fry the clutch and/or break things like gears and input shafts.
I've seen some trucks rated at ~2x the towing capacity (or more) with an auto vs. manual tranny.
18 wheelers can use a manual because they're HUGE transmissions, they've got LOTS of gears, and the savings in diesel is worth it in the long run.
As for parts count, there might be 100 more moving parts in an automatic transmission vs. that of a stick shift, not 10,000 more.
That said, I've never owned any vehicle with an automatic transmission. Even my gas-guzzling SUV has a manual.
The CVT is a weird transmission to get used to. It just isn't natural to have the same engine RPMs at 70mph as at 25mph and at 35 and, 45 and..
The problem with 2-stroke engines is that they're dirty. They aren't illegal because they're 2-stroke, they're illegal because they can't pass modern emissions.
Modern engines under 50cc don't have to pass emissions tests, so you see them in mopeds. The pre-ban 2-strokes were grandfathered in.
If you look really hard, you can sometimes find grey-market 2-strokes. I knew a guy with a suzuki 250 (I forget the model) with street tags, and I've heard of a few street-legal aprilia RS-250s.
L1,L2,L3 caches relate to caches either on the CPU or very close to it. Only when a bit of code isn't found in the L1,L2[,L3] cache, does the processer go all the way out to the system memory to fetch the next set of instructions.
Now, a database generally runs a fixed set of instructions during a query, though those instructions may not fit in the smaller L1 and L2 caches (the L2 on the dual Xeon we just bought was 512k, but 1mb is also available). Having the larger L3 cache can help keep those instructions for doing queries closer to the CPU, which can significantly speed things up.
As for database design, good database will use available index(es) when possible during a query since they shortcut looking for data. This is why having proper indices is important to maximize database performance.
The database will use as much memory as you allow it to cache data. Only when the data isn't resident in memory does it go out to the HDDs to find it, regardless of whether the query was able to make use of index(es).
Both databases and CPU caches make use of MRU/LRU (Most/Least Recently Used) to determine what to keep and what to throw away. The MRU stuff stays, and the LRU stuff is flushed out when something new is stored in the cache/database memory.
A complex SELECT statement that returns millions of rows, but makes use of 2mb of instructions would significantly improve performance with the addition of a 3mb L3 cache since the CPU wouldn't have to go to system memory to find the next set of instructions, per row. Save a few ms here and there fetching instructions, and it adds up over time.
Going on the instrument example, this is exactly why sport bikes have analog tachometers even though most have a digital speedometer. I'm able to tell, without even looking, that I'm above 8000 RPM, and that redline (14,500) is coming up real soon now -- about 1/4th of a second WOT in 1st. If I didn't have that hand sweeping through my peripheral vision, I would hit the revlimiter.
I couln't imagine flying with digital gauges. Most of the stuff I look at while flying doesn't need to be quantified in hard numbers, but more or less whether or not something is changing: if i'm climbing or descending, if i'm deviating from my course, the direction to the next ADF beacon, things like that.
It'll be interesting to see how many people turn Hyper Threading OFF when doing some tests. I found that my database was 212% FASTER for read operations after I turned Hyper Threading off on the 2650.
We've got two 2450s (RAID5 and RAID1) and a 2650 (RAID1) all running that PERC 3 RAID controller with no problems at all. The 2650 acts as a database server, and is fairly heavily used. The 2450s are web servers. The 2450s have been running for about 2 years, and the 2650 for about 1 year without a single hiccup from the hardware, even with the FD dumped a few hundred gallons of water on the office above, causing it to rain on the servers.
Maybe it is a problem with newer distros? We run RedHat 7.3.
CSS is great, when used correctly, especially for professionals and large sites.
Some advantages of css:
- sitewide changes by changing 1 file - ability to play with changes, in real-time, by using one of the several css-switching/editing plugins, without affecting other users - complete control over fonts, colors, spacing, etc - seperation of data from presentation, which leads to: - ability to change the presentation based on the output device (browser, printer, tele-type, etc) - (MUCH) smaller pages which leads to: - faster loading pages
Not every site should use CSS, but it is a nice technology to have, quirks and all.
Slashdot Mirror
Good, please let it die. OpenID is as if someone sat down and said to themselves "username/password is too damn quick and easy to use. lets replace authentication with a URL for a website no-one can remember (that still requires a username/password) and make it fragile and hard to implement! oh, and let's make it slow. sometimes. yeah, that's the ticket."
avgas is 110 octane and full of lead. even though it's "low lead" it has more lead than leaded automotive gas had. it will destroy your catalytic converter and oxygen sensor(s). don't use it if you have a car made since 1975.
Ahh, you are correct. I'd never run into it before since I generally consider it bad form to modify parameters.
Leave it up to PHP to introduce nuances in every aspect of the language. After 8 years of PHP, issues like this are why I'm trying my best to move on to other languages.
I'm a general aviation pilot and would LOVE to have a fuel-injected engine. More power, better reliability, better fuel economy, smoother running, and one less control to monitor.
One big problem with EFI is how to handle total loss of the electrical system. As it stands now, you can lose the alternator, the battery, and one magneto and still fly. Same with mechanical (Bendix systems) injection. However, with the mechanical systems, you don't gain a whole lot. There is still a mixture control- they basically act as a glorified carburetor.
With EFI, if you lose the alternator and the battery goes dead, the engine stops. An additional alternator and battery could be installed to mitigate most of the risk. Same for the coils. You could even keep a magneto as a fallback if the coil dies.
Really, the biggest opposition to modernizing GA is the government and all the red tape involved. It would fairly easily cost millions of dollars to just get an EFI system certified on ONE make/model. Even if you targeted the Cessna 172 with the Lycoming O320, the cost would be prohibitive. As just a guess, it would cost $30-45 thousand per installation- close to the cost of a complete new engine with mechanical fuel injection. Not really a viable option.
There was a program a few years ago call the General Aviation Propulsion engine (GAP). It was supposed to reduce the cost and increase the reliability of GA propulsion. Last I read the project was "considered a success" and disappeared. Seems like a shame, really.
In PHP4 objects are passed by value. In PHP5 they're passed by reference.
This is probably one of the most misunderstood features of PHP5. They are passed by reference, but they're also copy-on-write references. As soon as the variables value is changed, a copy is made, and the function/method then uses the local copy (as if a copy were made in the first place like in php4).
Nothing has changed for the programmer except a reduction in memory usage.
In PHP5 you also have public, private, and protected variables.
Yes, optional. The old var keyword works the same as using public.
In PHP4 class constructors were the same name as the class. In PHP5 it's __construct.
Again, optional. There is also a __destruct() method in php5.
I could go on about the difference, but I won't. There's a lot of differences between the two.
There are a lot of differences, but backwards compatibility is pretty good. A coworker and I converted a 130k loc mess of a php4 codebase (originally php3) from 4.3 to 5.1 with only a handful of changes. It just took a bit of research and a bit of planning.
And yes, good riddance to php4. It will not be missed.
cmd-down
in the finder, cmd-up goes up a level, and cmd-down goes down into the folder/app.
I work for a real estate service company that lets agents, buyers, and sellers do their respective thing online. Pretty large slice of the demographic pie.
From one of our webservers (Month-To-Date):
IE 13992090 92.5%
Unknown 700841 4.6% (half of which are the server checker)
Netscape/Moz (63% firefox) 407199 2.6%
And to for the KDE vs Gnome argument:
Konqueror 12 0%
Galeon 4 0%
Last month looked about the same.
In May, IE had a 96% share and Netscape had 1.5%.
What a useless writeup.
ZFS, the dynamic new file system in Sun's Solaris 10 Operating System (Solaris OS), will make you forget everything you thought you knew about file systems.
Don't forget, everything is possible with the Zombo File System!
Fiberglass is fairly popular as the primary component in aircraft construction for general aviation and experimental aircraft.
See:
- Glasair/Glastar
- Cozy Mk IV
- Vari-EZ and Long-EZ (couple of Rutan's designs; he has several others that all use composite fiberglass construction.)
- Quickie
- Cirrus SR20
Those are just a few that I can think of right now. There are dozens of others.
I would imagine that the spacecraft is built with mostly carbon though. It's stronger than fiberglass and can be built lighter.
Not really. He's talking from personal experience. In the previous article he notes that he knows one good programmer who chooses java.
I think the point Graham is trying to make is that if a programmer knows only one language, and it's java, that person is probably not a good programmer. They're someone who was taught some idioms in college and can squeak out the par-level code required to bring in the paycheck.
A good programmer seeks out a good language. And a surprisingly high number of good programmers choose python or lisp.
If you want to fill a seat, choose java. There are a million and one code monkeys out there that will take the job. If you want to fill a position with good programmers, choose a language that good programmers use. Java is not that language.
I think you missed the analogy. It's more like "Fords suck because all the good mechanics I know drive Chevy's." While the mechanic may need to work on a Ford (Java) now and then to pay his bills, or he has to drive a Ford as a work truck because they won't supply any other brand, he chooses to drive (and work on) a Chevy (Python).
Does anyone know what the Traffic Rank means? My company's site is listed as a 2, slashdot is a 1. Lowest I can find is a 4. Lots of sites have a Not Available rank.
yeah, I just searched for:
- ecu limp
- ecu limp home
- ecu limp mode
- ecu open loop
- limp +sportage
- limp home +sportage
They all came back with useful results. The key is that "ecu" - Electronic Control Unit -- your car's brain.
I pretty much felt the same way.
;)
It's a great transmission if you need to show clients around. The complete lack of shifting makes for a very comfortable ride. Perfect for women
It's a really bad transmission if you enjoy driving and feeling/controlling what the car is doing.
limp mode, as i understand it:
- revert to the a overly-rich fuel map
- ignore some/all sensors ("open-loop" mode)
- retard the timing
- limit RPMs and/or speed
All of that serves to help prevent the engine from blowing up.
rich mixture + retarded timing would cause it to idle very rough. Most engines need a bit of timing advance at idle to idle smoothly.
A manual's greatest advantage (direct link from input to output) is it's greatest disadvantage when towing. If you rev up an automatic transmission trying to get a weight moving, it'll just overrun the torque converter and heat the fluid. If you do the same thing to a manual, fry the clutch and/or break things like gears and input shafts.
I've seen some trucks rated at ~2x the towing capacity (or more) with an auto vs. manual tranny.
18 wheelers can use a manual because they're HUGE transmissions, they've got LOTS of gears, and the savings in diesel is worth it in the long run.
As for parts count, there might be 100 more moving parts in an automatic transmission vs. that of a stick shift, not 10,000 more.
That said, I've never owned any vehicle with an automatic transmission. Even my gas-guzzling SUV has a manual.
The CVT is a weird transmission to get used to. It just isn't natural to have the same engine RPMs at 70mph as at 25mph and at 35 and, 45 and..
The problem with 2-stroke engines is that they're dirty. They aren't illegal because they're 2-stroke, they're illegal because they can't pass modern emissions.
Modern engines under 50cc don't have to pass emissions tests, so you see them in mopeds. The pre-ban 2-strokes were grandfathered in.
If you look really hard, you can sometimes find grey-market 2-strokes. I knew a guy with a suzuki 250 (I forget the model) with street tags, and I've heard of a few street-legal aprilia RS-250s.
Apt for Fedora Core 1.90 is available here.
It's all I use, and it works great (much better than yum or up2date did).
From the article:
"A RamSan 320 unit holds up to 64GB of RAM in a 3U rack unit. The US government order is housed in three full height rack units."
So, about 7' tall, 10' wide.
L1,L2,L3 caches relate to caches either on the CPU or very close to it. Only when a bit of code isn't found in the L1,L2[,L3] cache, does the processer go all the way out to the system memory to fetch the next set of instructions.
Now, a database generally runs a fixed set of instructions during a query, though those instructions may not fit in the smaller L1 and L2 caches (the L2 on the dual Xeon we just bought was 512k, but 1mb is also available). Having the larger L3 cache can help keep those instructions for doing queries closer to the CPU, which can significantly speed things up.
As for database design, good database will use available index(es) when possible during a query since they shortcut looking for data. This is why having proper indices is important to maximize database performance.
The database will use as much memory as you allow it to cache data. Only when the data isn't resident in memory does it go out to the HDDs to find it, regardless of whether the query was able to make use of index(es).
Both databases and CPU caches make use of MRU/LRU (Most/Least Recently Used) to determine what to keep and what to throw away. The MRU stuff stays, and the LRU stuff is flushed out when something new is stored in the cache/database memory.
A complex SELECT statement that returns millions of rows, but makes use of 2mb of instructions would significantly improve performance with the addition of a 3mb L3 cache since the CPU wouldn't have to go to system memory to find the next set of instructions, per row. Save a few ms here and there fetching instructions, and it adds up over time.
Going on the instrument example, this is exactly why sport bikes have analog tachometers even though most have a digital speedometer. I'm able to tell, without even looking, that I'm above 8000 RPM, and that redline (14,500) is coming up real soon now -- about 1/4th of a second WOT in 1st. If I didn't have that hand sweeping through my peripheral vision, I would hit the revlimiter.
I couln't imagine flying with digital gauges. Most of the stuff I look at while flying doesn't need to be quantified in hard numbers, but more or less whether or not something is changing: if i'm climbing or descending, if i'm deviating from my course, the direction to the next ADF beacon, things like that.
Will they let you tweak Hyper Threading?
It'll be interesting to see how many people turn Hyper Threading OFF when doing some tests. I found that my database was 212% FASTER for read operations after I turned Hyper Threading off on the 2650.
We've got two 2450s (RAID5 and RAID1) and a 2650 (RAID1) all running that PERC 3 RAID controller with no problems at all. The 2650 acts as a database server, and is fairly heavily used. The 2450s are web servers. The 2450s have been running for about 2 years, and the 2650 for about 1 year without a single hiccup from the hardware, even with the FD dumped a few hundred gallons of water on the office above, causing it to rain on the servers.
Maybe it is a problem with newer distros? We run RedHat 7.3.
CSS is great, when used correctly, especially for professionals and large sites.
Some advantages of css:
- sitewide changes by changing 1 file
- ability to play with changes, in real-time, by using one of the several css-switching/editing plugins, without affecting other users
- complete control over fonts, colors, spacing, etc
- seperation of data from presentation, which leads to:
- ability to change the presentation based on the output device (browser, printer, tele-type, etc)
- (MUCH) smaller pages which leads to:
- faster loading pages
Not every site should use CSS, but it is a nice technology to have, quirks and all.
it means to add the -y or the -ies suffix when appropriate: community or communities.