Images can remain fixed-size while text &c flows. Remember that the user controls font sizes, not you. Browsers will often scale your images to fit the screen if they are too big, so pixel-based layout will break horribly, often.
If you're a hacker, you can quickly pick up the other, but it makes sense to choose the first of the two on an informed basis, so kudos for the question.
Decide which language offers the most enjoyable job opportunities. For me it's Java hands down.
KMail is lean and clean, and it's integrated support for encryption is superior to the plugins and extensions for Thunderbird. I used and loved KMail, but I had to give it up because I use too many computers:
Thunderbird works essentially everywhere. You can share your mailbox over the LAN filesystem or globally via WebDAV, regardless of whether you are using Windows, OSX, Linux, Solaris, *BSD.
As far as I know Evolution is best for 1) People who need to interoperate with Exchange servers under Linux, 2) the mentally impaired, and 3) Gnome partisans. But then, I never saw a good reason to try it.
It is perfectly suitable logic for operating a system. It would be nice to have only good hackers on staff, so that trivialities such as choice of language are down in the noise, but if it may well become critical to the mission of your organization that person X perform maintenance on system Y, and person X does not and will not be able to deal with code in language Z at time T, then you shouldn't write system Y in language Z, or you will be SOL and run around crying "OMGWTFBBQ!"
I should mention that if you didn't code-in memcached, you probably don't want to retrofit it, just for performance tuning or capacity scaling. In that case, I should suggest C-JDBC. You don't need to use a Java AS node in order to use C-JBDC, either.
I haven't made a production deployment of C-JDBC, so I defer to the experience of others, but from my research, it looks like a hot ticket for scaling DB performance while simultaneously isolating you from the specificities of a given DB product.
In years past the Zeitgeist included far more information and far less fluff. Where's the low-down by country? Where's the scale that allows us to relate the various graphs?
You could do much, much more interesting stuff using the Alexa data. I hope someone does. There must be a mountain of dissertations to be mined in there, not to mention new business models.
Cheap scalability means load balancing over commodity components, which you can add quickly to a set for linear scaling. The first challenge is where the client traffic comes in the door. If you can't them in, you can't serve them. When you add commodity components, you reduce MTF, so your configuration needs to do dynamic-failover and rebalancing.
The best way I know to scale your front door is to start with two netfilter firewalls sharing a MAC, and getting load balance by MAC layer filtering rules. It's pretty easy to plug in additional firewall transit capacity and to script-in failover using a heartbeat daemon. You can do firewalls in failover pairs more quickly and easily than you can do odd-numbered rings, but both are quite doable by relatively straightforward scripting and configuration.
I strongly recommend against breaking your traffic into categories, like static pages, etc., and balancing load by moving different categories to different servers. If you do that, you end up with way too much hardware underloaded, and way to much hardware overloaded, and either no failover provisioning, or else a very complex failover configuration. Instead, make the individual servers identical, and cheap. Just add more clones to the pack as needed, and keep the traffic balanced.
By this time you're starting to see my basic approach to scalable commodity 'nix clusters. See this lame ASCII art for detail. It amounts to a series of independently scalable layers, Firewalling, app serving, db caching, db serving.
The memcached layer is indicated if you have a lot of read-only db traffic. These nodes are cheap, don't even really need hard drives. You could boot them off of CD or off the network, diskless. They hold as much RAM as possible. The number of MC servers required depends strongly on how much RAM each can hold but the amount of RAM required per DB node depends on the characteristics of your application DB traffic.
I'd rather install a memcached server and keep a hot DB spare than try to maintain transparent failover on a DB cluster. Coherence requirements complicate the performance curves when you have multiple DBs accepting write operations, which can lead to unpleasant surprises. Delay scaling your DB cluster as long as you can.
Of course the government regards its citizens as the enemy. Otherwise why would they kill so many millions of us? After all, if anyone were to remove them from power, it would almost certainly be the citizens.
It is incredibly esoteric. The sort of thing most programmers would only encounter in school. Because you see, when you need to sort in the real world, you just call the sort method. If you're using C++ it's quicksort, and you just don't care how fast it goes anyhow, because everything else takes a hell of a lot longer. Unless you're doing something fancy, in which case you're into esoterica again.
I'm not saying that knowing and recognizing the differences between log and exponential time is not practically important, but knowing the names of a variety of sorting algorithms and their runtime complexity is very much unimportant, unless you're doing specialized work, where sorting becomes a focus. That's very rare.
My bet would be that Holzman is describing his impressions of an environment in which experience programmers had to fix the complex bugs in code written by inexperienced programmers, which they were incapable of resolving.
I've spent years of my life fixing other people's code. Were it not for the money, I would have preferred death. Amazing what some coke and hookers will do for your motivation!
No, it's categorically false. One crappy senior engineer at twice the price will get less than half the work done that an average random tech-school graduate would, while one excellent senior engineer at the same price will get ten or twenty times as much done as an average masters from a hot university.
Seniority doesn't matter so much, intelligence doesn't matter so much. What matters are qualities of wisdom and motivation. Some people gain wisdom from past experience. Some people lose motivation with increasing experience. But not all, in either case.
The best discriminators for predicting success in working on a particular project are (1) enthusiasm for the project (the vision thing) and (2) a track record of success (preferrably relevant, but anything is good).
If you're living in Australia, I doubt you'll ever have trouble getting all the porn you can eat. Much more problematic is the sadistic torture and mass murder than you habitually partake of, by supporting brutal war crimes, and the incredible evil of crushing the souls of children in razor-wired desert concentration camps. But then, I suppose all that porn takes your mind off of it. Unless, of course, you happen to be a muslim, in which case it only works until you are sent to Egypt to be electrocuted and pierced with power drills.
Hopefully, one day, an Australian will atone for the crimes of the nation, and in so doing, turn your continent into a vast plain of radioactive glass. Then the souls of your victims can rest in peace, avenged.
Slashdot Mirror
Images can remain fixed-size while text &c flows. Remember that the user controls font sizes, not you. Browsers will often scale your images to fit the screen if they are too big, so pixel-based layout will break horribly, often.
If you're a hacker, you can quickly pick up the other, but it makes sense to choose the first of the two on an informed basis, so kudos for the question.
Decide which language offers the most enjoyable job opportunities. For me it's Java hands down.
KMail is lean and clean, and it's integrated support for encryption is superior to the plugins and extensions for Thunderbird. I used and loved KMail, but I had to give it up because I use too many computers:
Thunderbird works essentially everywhere. You can share your mailbox over the LAN filesystem or globally via WebDAV, regardless of whether you are using Windows, OSX, Linux, Solaris, *BSD.
As far as I know Evolution is best for 1) People who need to interoperate with Exchange servers under Linux, 2) the mentally impaired, and 3) Gnome partisans.
But then, I never saw a good reason to try it.
It is perfectly suitable logic for operating a system. It would be nice to have only good hackers on staff, so that trivialities such as choice of language are down in the noise, but if it may well become critical to the mission of your organization that person X perform maintenance on system Y, and person X does not and will not be able to deal with code in language Z at time T, then you shouldn't write system Y in language Z, or you will be SOL and run around crying "OMGWTFBBQ!"
Perl is plainly a very innovative language, and has been for 20 years.
Einstein's General Relativity was built on Newton's laws and Galilean Relativity, but that doesn't make it less innovative.
I should mention that if you didn't code-in memcached, you probably don't want to retrofit it, just for performance tuning or capacity scaling. In that case, I should suggest C-JDBC. You don't need to use a Java AS node in order to use C-JBDC, either.
I haven't made a production deployment of C-JDBC, so I defer to the experience of others, but from my research, it looks like a hot ticket for scaling DB performance while simultaneously isolating you from the specificities of a given DB product.
In years past the Zeitgeist included far more information and far less fluff.
Where's the low-down by country? Where's the scale that allows us to relate the
various graphs?
You could do much, much more interesting stuff using the Alexa data. I hope someone does. There must be a mountain of dissertations to be mined in there, not to mention new business models.
Cheap scalability means load balancing over commodity components, which you can add quickly to a set for linear scaling. The first challenge is where the client traffic comes in the door. If you can't them in, you can't serve them. When you add commodity components, you reduce MTF, so your configuration needs to
do dynamic-failover and rebalancing.
The best way I know to scale your front door is to start with two netfilter firewalls sharing a MAC, and getting load balance by MAC layer filtering rules. It's pretty easy to plug in additional firewall transit capacity and to script-in failover using a heartbeat daemon. You can do firewalls in failover pairs more quickly and easily than you can do odd-numbered rings, but both are quite doable by relatively straightforward scripting and configuration.
I strongly recommend against breaking your traffic into categories, like static pages, etc., and balancing load by moving different categories to different servers. If you do that, you end up with way too much hardware underloaded, and way to much hardware overloaded, and either no failover provisioning, or else a very complex failover configuration. Instead, make the individual servers identical, and cheap. Just add more clones to the pack as needed, and keep the traffic balanced.
By this time you're starting to see my basic approach to scalable commodity 'nix clusters. See this lame ASCII art for detail. It amounts to a series of independently scalable layers,
Firewalling, app serving, db caching, db serving.
The memcached layer is indicated if you have a lot of read-only db traffic.
These nodes are cheap, don't even really need hard drives. You could boot them
off of CD or off the network, diskless. They hold as much RAM as possible.
The number of MC servers required depends strongly on how much RAM each can hold
but the amount of RAM required per DB node depends on the characteristics of your
application DB traffic.
I'd rather install a memcached server and keep a hot DB spare than try to maintain
transparent failover on a DB cluster. Coherence requirements complicate the performance curves when you have multiple DBs accepting write operations, which can lead to unpleasant surprises. Delay scaling your DB cluster as long as you can.
Of course the government regards its citizens as the enemy. Otherwise why would they kill so many millions of us? After all, if anyone were to remove them from power, it would almost certainly be the citizens.
That depends on your oppressors having a conscience. Not applicable to the U.S.
It is incredibly esoteric. The sort of thing most programmers would only encounter in school.
Because you see, when you need to sort in the real world, you just call the sort method.
If you're using C++ it's quicksort, and you just don't care how fast it goes anyhow, because
everything else takes a hell of a lot longer. Unless you're doing something fancy, in which case you're into esoterica again.
I'm not saying that knowing and recognizing the differences between log and exponential time is not practically important, but knowing the names of a variety of sorting algorithms and their runtime complexity is very much unimportant, unless you're doing specialized work, where sorting becomes a focus. That's very rare.
My bet would be that Holzman is describing his impressions of an environment in which experience programmers had to fix the complex bugs in code written by inexperienced programmers, which they were incapable of resolving.
I've spent years of my life fixing other people's code. Were it not for the money, I would have preferred death. Amazing what some coke and hookers will do for your motivation!
No, it's categorically false. One crappy senior engineer at twice the price will get less than half the work done that an average random tech-school graduate would, while one excellent senior engineer at the same price will get ten or twenty times as much done as an average masters from a hot university.
Seniority doesn't matter so much, intelligence doesn't matter so much. What matters are qualities of wisdom and motivation. Some people gain wisdom from past experience. Some people lose motivation with increasing experience. But not all, in either case.
The best discriminators for predicting success in working on a particular project are (1) enthusiasm for the project (the vision thing) and (2) a track record of success (preferrably relevant, but anything is good).
> Intellectual property theft is not an inherent right of mankind.
that's right! it's actually a fiction told by statues enacted to line the pockets of the corrupt.
your pertinent inalienable right is to freely express yourself and your ideas, no matter where you got them. information is made of ideas.
I'm will to die fighting to protect my right to stay alive!
Oh, wait a minute....
> catching up with the 70s
You mean 1959 was part of the 70s? I guess McCarthy really was "ahead of his time".
But, yes, I understand that most of the interesting features of progamming language design
were pioneered in the 70s. Your point is taken.
But, no, programming language design features are not the sum of all art in software. Your
point is muted, albiet not mooted.
I take it you don't play well with others, but you play well with money.
You suffer too, because of all the sales ATI loses. When volume goes up, prices go down.
that would only result in mouse-whe.elc. and if you ever had to scrub barnacles off a boat, you'll know why I don't want whelks on my mouse.
If you take enough LDS, you can see it right now.
You seem to have confused atheism with agnosticism.
Not any more he isn't.
t icle_2121756.shtml
It seems unlikely that he was actually assaulted.
"Now, however, he is no longer taking phone calls or talking to the press about the incident. He has also just resigned..."
http://www.postchronicle.com/news/breakingnews/ar
> in China, they had it relatively easy, people liked to help them for nothing
They must have been avoiding the cities.
Spend 300 fucking billion dollars on it, like you do on bombing Iraqi families, and you'll damn sure cure 90% of all cancers.
If you're living in Australia, I doubt you'll ever have trouble getting all the porn you can eat. Much more problematic is the sadistic torture and mass murder than you habitually partake of, by supporting brutal war crimes, and the incredible evil of crushing the souls of children in razor-wired desert concentration camps. But then, I suppose all that porn takes your mind off of it. Unless, of course, you happen to be a muslim, in which case it only works until you are sent to Egypt to be electrocuted and pierced with power drills.
Hopefully, one day, an Australian will atone for the crimes of the nation, and in so doing, turn your continent into a vast plain of radioactive glass. Then the souls of your victims can rest in peace, avenged.