People normally thing they want to handle tons of people at the same time, but handling 10x more client requests simultaneously typically means each one takes 10x longer to process; there's no performance advantage, and all you've managed to do is burn RAM.
Hoo-raay! So many just plainly fail to understand that. For one web site I'm running, we have an event-driven web server that talks to an app backend. It's maybe 50-150 active users on it, but a lot of dynamic stuff happening. The server have 2 cpu's. For two cpu's I figured 4 threads (some overhead with network connections, pushing data around, and occasional upload) were okay for the app backend. The other admin involved asked "Why only 4? Couldn't we bump it up to at least 100?" - What would be the point? If a request hits the app backend then that's almost by definition cpu bound (db server is on same hardware), and allowing more requests in than spare cpu resources would just make every request go slower, use more server ram, and kill the cpu with thread switches. In addition to work up a nice request queue that will make sure the server is overworked for the forseeable future.
And it's not the first time I've seen that attitude either. And I bet, not the last. Honestly, I don't see what use apache have now. If you serve static files, there's advantage event-driven servers. Talk to app backends, advantage event-driven. Long standing poll requests? Advantage definitely event-driven. Want to run php inside the web server?.. Okay, you got me there. But in most cases, that's not necessary. Run php as separate user, or even on a separate server. Gain security and scalability. Let web server do the web thingys, let app servers do the app thingys. Keep it clean and separated.
if you need 1500 concurrent connections, then you REALLY should look at event driven web servers.
BTW, for comparison, with cherokee and a uwsgi python uGreen app (used for ajax long-poll comet events) I've successfully tested 1500 connections on a 256mb vserver. It started to go a bit slowly then (1-2 seconds delivering to all clients), but it worked. In normal use I see maybe 150-200 connections to that daemon, and that works splendidly.
It's the difference between a restaurant having a waiter (and in some cases cook) for every customer (and always enough standby to handle peak), and having a few waiters and cooks that instead handle multiple customers.
Actually, the merger might end up saving the company.
There's no doubt that AMD's engineers made some significant improvements to the ATI cards, and now you see the results. AMD gfx cards beat nvidia in performance, performance / price, and are starting to get better drivers and linux support than nvidia.
And they are slowly winning the gamer mindshare, too. A few years ago ati cards were the "special" cards that required a lot of tweaking, had terrible drivers, and never could reach nvidia's top models. Now they're starting to get the reputation for being top, solid quality.
So even if their CPU department takes a dive, they're winning the gamer gfx market, which probably have just as much money in it.
And they might be able to get a comeback on the bulldozer cpu's too after some tweaking. Some overclocking benchmarks hinted to bulldozer scaling better when clock rate went up than intel's sandy bridge.
People are, of course, required to provide evidence when they are under investigation.
"The person refuse to give the location of the gun used in the murder, and is therefore held in contempt of the court. Put him in jail until he informs law enforcement of the location of said gun."
Let's say defendant had that (or a very similar) gun some time ago, but honestly have no clue what have happened to it the last years (maybe it got stolen, he lost it, woke up after a party without it, and so on).
Would that be similar? Would that decision be right?
Over a six-to-eight month period, a small team under Tim Schafer's supervision will develop Double Fine's next game, a classic point-and-click adventure.
They're funding the game, not the whole company. As least as far as I've understood. The company itself was started ~12 years ago, in 2000.
I found it rather readable, but then I'm used to jQuery. I would have formatted the code a bit differently to make it even easier to read, tho.
$(".hideable").before( function () {
var hideableElement = $(this);// "this" is a raw element, we want a jQuery wrapped one
var newToggleElement = $("#showhidecontrol").clone();
newToggleElement.click( function () {
hideableElement.toggleClass("hidden");
});
return newToggleElement; });
Whenever I look at java code it's all that gooblygook structure with a morsel of actual logic hidden deep inside it.
It's like those restaurant meals where your order comes on a large plate, the sauce is in sophisticated patterns, plenty of green and red and other colors, and so on. But the actual real food itself is barely a mouthful. The rest is just chaff to make it look good (or in Java, to make it look yummy to the preprocessor).
This whole page seems a bit like deja vu. Had the same basic discussion just a few days ago, here.
I won't re-post most of it, but there is one link there that I think you might find interesting.. Python for Java people
If you look at the solution they first present there, that looks VERY java'y. If you scroll down to the "final" python version (honed by a lot of people commenting on it) it looks very different, at least from my viewpoint. The first code looks java'esque. The second looks pythonic.
"A language that doesn't affect the way you think about programming, is not worth knowing"
Are you saying that no new language you learn affect the way you think about programming? In that case, you're either a programming god, or you're the exact problem people are talking about.
I learn something new in every language, and notice that I have to work with a language for months (or even years) before I really start to understand it. And in the process, I also get a bit better in the other languages I know.
The language I feel I've learned the most from, and which I've worked with for years (and *cough* still learn new things and concepts from) is python. In python, you have a word, pythonic, which more or less means doing a thing in the preferred way of that language.
I wouldn't say that you've learned that language until you not only do things the "pythonic" way, but understands why it's done that way. Sure, you *can* move the exact code from C to python, with little changes, but then you're still programming C, it just happen to use python syntax. That is my point.
Modern, dynamic languages are pretty neat. They allows you to easily do things that would have been impossible or extremely hard in more traditional languages.
But you do need the right mindset for it. Sadly, most of the python/ruby code I see from java / C programmers are.. well... Java/C programming with different words and syntax. That way you got both the disadvantages of the old languages AND the disadvantages of the new languages.
It can take a while to get fully used to the new, hip languages. For many, it's a hard time, as they feel like they're just writing $old_language in a slower, more stupid system.
Actually, my phone (SGS2) have built-in wireless tether from the manufacturer. Phone sets up an access point and functions like a normal internet router.
And it works. I've used it several times, in fact. And that is with default firmware, no rooting or anything.
And why not just set up a temp "auth server" that just OK's everything that comes in, for the movement period?
Some people might be able to pirate it for a copule of days? People are already able to pirate their games, nothing new there.
For me, if it was the choice of either cutting off all valid customers for a time, or let people play for free for a time, the choice would be obvious. Paying customers first, then paying customers second. Pirated games that only work a week's time? That's called a "DEMO", stop worrying. You might even gain some sales on it.
..a more fine-grained security model and a firewall to android?
Well, it is rather fine-grained. Especially when compared to the other smartphone market leader. But yeah, there are some things that could be done better.
And regarding firewall: 1. Google release firewall 2. Users start blocking ad servers 3. World goes under
"Using a metaphor in front of a man as unimaginative as Ridcully was like a red flag to a bu-- was like putting something very annoying in front of someone who was annoyed by it."
Actually, that's not entirely true. Pirating games looks shitty compared to Steam in my opinion.
* No need to find new crack every time the game updates (or even check for new version.. it auto-updates) * In-game chat system, with one-click multiplayer join function (for those games that support it) * Savegames are stored on Steam's servers and synced between machines (for those games that support it) * Consistent screenshot / gallery system across games, with upload support to Steam servers. * Game statistics and achievements, displayed online on your profile. * Direct access to high-speed download of games, no virus risk, minimal game install process. * No need to search around, try different downloads, find one that downloads fast, then find out if it has virus, then find out if it works... Just click-click-click-click-click, and it downloads, full speed.
Yes.. Steam can fail (server down, can not start single player game), and it's offline modus can really do with some improvement (you have to be online to play offline? What?), but overall it does give some value over pirating games.
The irony is that NRK (the Norwegian government-owned radio and television public broadcasting company) is the nation-wide media doing (imho) the best job, being critical and covering a wide variety of cases from different angles.
For an example, look at DLD (norwegian DRD) coverage, NRK was just about the only media discussing it. Others media either ignored it, or uncritically posted statements from politicians arguing for it.
It seems everyone's forgotten how different things were before the iPhone. All this "obvious" shit wasn't obvious at all back then, and it was only a few years ago.
Well, you got LG Prada (came out before iPhone, had virtual touch buttons), Samsung F700 (slightly after iPhone), and then you of course got IBM Simon... Launched in 1993, had touch screen controls, a calendar, address book, world clock, calculator, note pad, e-mail, and games. And it had less physical buttons than the iPhone.
So... I'd say that all that obvious shit was pretty obvious back then, but the hardware was lacking a bit. Being the first in a race doesn't mean you invented running:)
Slashdot Mirror
Apache is the Slackware/Gentoo of the web server world.
That's probably very true. Thanks for pointing that out :)
People normally thing they want to handle tons of people at the same time, but handling 10x more client requests simultaneously typically means each one takes 10x longer to process; there's no performance advantage, and all you've managed to do is burn RAM.
Hoo-raay! So many just plainly fail to understand that. For one web site I'm running, we have an event-driven web server that talks to an app backend. It's maybe 50-150 active users on it, but a lot of dynamic stuff happening. The server have 2 cpu's. For two cpu's I figured 4 threads (some overhead with network connections, pushing data around, and occasional upload) were okay for the app backend. The other admin involved asked "Why only 4? Couldn't we bump it up to at least 100?" - What would be the point? If a request hits the app backend then that's almost by definition cpu bound (db server is on same hardware), and allowing more requests in than spare cpu resources would just make every request go slower, use more server ram, and kill the cpu with thread switches. In addition to work up a nice request queue that will make sure the server is overworked for the forseeable future.
And it's not the first time I've seen that attitude either. And I bet, not the last. Honestly, I don't see what use apache have now. If you serve static files, there's advantage event-driven servers. Talk to app backends, advantage event-driven. Long standing poll requests? Advantage definitely event-driven. Want to run php inside the web server? .. Okay, you got me there. But in most cases, that's not necessary. Run php as separate user, or even on a separate server. Gain security and scalability. Let web server do the web thingys, let app servers do the app thingys. Keep it clean and separated.
if you need 1500 concurrent connections, then you REALLY should look at event driven web servers.
BTW, for comparison, with cherokee and a uwsgi python uGreen app (used for ajax long-poll comet events) I've successfully tested 1500 connections on a 256mb vserver. It started to go a bit slowly then (1-2 seconds delivering to all clients), but it worked. In normal use I see maybe 150-200 connections to that daemon, and that works splendidly.
It's the difference between a restaurant having a waiter (and in some cases cook) for every customer (and always enough standby to handle peak), and having a few waiters and cooks that instead handle multiple customers.
Actually, the merger might end up saving the company.
There's no doubt that AMD's engineers made some significant improvements to the ATI cards, and now you see the results. AMD gfx cards beat nvidia in performance, performance / price, and are starting to get better drivers and linux support than nvidia.
And they are slowly winning the gamer mindshare, too. A few years ago ati cards were the "special" cards that required a lot of tweaking, had terrible drivers, and never could reach nvidia's top models. Now they're starting to get the reputation for being top, solid quality.
So even if their CPU department takes a dive, they're winning the gamer gfx market, which probably have just as much money in it.
And they might be able to get a comeback on the bulldozer cpu's too after some tweaking. Some overclocking benchmarks hinted to bulldozer scaling better when clock rate went up than intel's sandy bridge.
Here's an actual example:
http://code.google.com/p/django-tagging/issues/detail?id=160
Basically, the subquery was run all the time, leading to an amplification of biblical proportions. The solution there was to put that subquery in another subquery (yo dawg), as shown in http://www.xaprb.com/blog/2006/04/30/how-to-optimize-subqueries-and-joins-in-mysql/
We also tried with a temp table, but this solution was cleaner :) The performance difference was around 1/100th of the time for a sample query.
We also confirmed that the problem still existed in MySQL 5.5
I think there is a line and that Vostu crossed it.
IMHO Zynga have already tiptoed over the line. Vostu just seems to have cheerily flown past it with a jet engine.
People are, of course, required to provide evidence when they are under investigation.
"The person refuse to give the location of the gun used in the murder, and is therefore held in contempt of the court. Put him in jail until he informs law enforcement of the location of said gun."
Let's say defendant had that (or a very similar) gun some time ago, but honestly have no clue what have happened to it the last years (maybe it got stolen, he lost it, woke up after a party without it, and so on).
Would that be similar? Would that decision be right?
And if the speakers sound broken, it's dubstep.
Over a six-to-eight month period, a small team under Tim Schafer's supervision will develop Double Fine's next game, a classic point-and-click adventure.
They're funding the game, not the whole company. As least as far as I've understood. The company itself was started ~12 years ago, in 2000.
I found it rather readable, but then I'm used to jQuery. I would have formatted the code a bit differently to make it even easier to read, tho.
$(".hideable").before( function () {
var hideableElement = $(this);
var newToggleElement = $("#showhidecontrol").clone();
newToggleElement.click( function () {
hideableElement.toggleClass("hidden");
});
return newToggleElement;
});
Facebook. They likely have the best JavaScript guys using the best tools
*almost dies laughing*
Phjeww, you haven't tried to use their api's or actually looked at their code, I take it?
Hah, +5 Funny truth
Whenever I look at java code it's all that gooblygook structure with a morsel of actual logic hidden deep inside it.
It's like those restaurant meals where your order comes on a large plate, the sauce is in sophisticated patterns, plenty of green and red and other colors, and so on. But the actual real food itself is barely a mouthful. The rest is just chaff to make it look good (or in Java, to make it look yummy to the preprocessor).
This whole page seems a bit like deja vu. Had the same basic discussion just a few days ago, here.
I won't re-post most of it, but there is one link there that I think you might find interesting.. Python for Java people
If you look at the solution they first present there, that looks VERY java'y. If you scroll down to the "final" python version (honed by a lot of people commenting on it) it looks very different, at least from my viewpoint. The first code looks java'esque. The second looks pythonic.
What makes you think they want software patents?
return get_software_patents_income() > get_software_patents_expenses();
"A language that doesn't affect the way you think about programming, is not worth knowing"
Are you saying that no new language you learn affect the way you think about programming?
In that case, you're either a programming god, or you're the exact problem people are talking about.
I learn something new in every language, and notice that I have to work with a language for months (or even years) before I really start to understand it. And in the process, I also get a bit better in the other languages I know.
The language I feel I've learned the most from, and which I've worked with for years (and *cough* still learn new things and concepts from) is python. In python, you have a word, pythonic, which more or less means doing a thing in the preferred way of that language.
I wouldn't say that you've learned that language until you not only do things the "pythonic" way, but understands why it's done that way. Sure, you *can* move the exact code from C to python, with little changes, but then you're still programming C, it just happen to use python syntax. That is my point.
That 45 year old developer that cut his teeth on C/C++ can pick up Ruby in a short time
Sadly, this is not always true - example 2
Modern, dynamic languages are pretty neat. They allows you to easily do things that would have been impossible or extremely hard in more traditional languages.
But you do need the right mindset for it. Sadly, most of the python/ruby code I see from java / C programmers are .. well... Java/C programming with different words and syntax. That way you got both the disadvantages of the old languages AND the disadvantages of the new languages.
It can take a while to get fully used to the new, hip languages. For many, it's a hard time, as they feel like they're just writing $old_language in a slower, more stupid system.
Actually, my phone (SGS2) have built-in wireless tether from the manufacturer. Phone sets up an access point and functions like a normal internet router.
And it works. I've used it several times, in fact. And that is with default firmware, no rooting or anything.
http://www.youtube.com/watch?v=GGsG239_hbA
And why not just set up a temp "auth server" that just OK's everything that comes in, for the movement period?
Some people might be able to pirate it for a copule of days? People are already able to pirate their games, nothing new there.
For me, if it was the choice of either cutting off all valid customers for a time, or let people play for free for a time, the choice would be obvious. Paying customers first, then paying customers second. Pirated games that only work a week's time? That's called a "DEMO", stop worrying. You might even gain some sales on it.
*shakes head*
..a more fine-grained security model and a firewall to android?
Well, it is rather fine-grained. Especially when compared to the other smartphone market leader. But yeah, there are some things that could be done better.
And regarding firewall:
1. Google release firewall
2. Users start blocking ad servers
3. World goes under
1. Create ArrayList
2. Add ALL THE THINGS
3. Forget to remove old entries when not used anymore
Reference still exist, not considered garbage.
This one explains it pretty well, I think.
"Using a metaphor in front of a man as unimaginative as Ridcully was like a red flag to a bu-- was like putting something very annoying in front of someone who was annoyed by it."
--Terry Pratchett, Lords and Ladies
Actually, that's not entirely true. Pirating games looks shitty compared to Steam in my opinion.
* No need to find new crack every time the game updates (or even check for new version.. it auto-updates)
* In-game chat system, with one-click multiplayer join function (for those games that support it)
* Savegames are stored on Steam's servers and synced between machines (for those games that support it)
* Consistent screenshot / gallery system across games, with upload support to Steam servers.
* Game statistics and achievements, displayed online on your profile.
* Direct access to high-speed download of games, no virus risk, minimal game install process.
* No need to search around, try different downloads, find one that downloads fast, then find out if it has virus, then find out if it works... Just click-click-click-click-click, and it downloads, full speed.
Yes.. Steam can fail (server down, can not start single player game), and it's offline modus can really do with some improvement (you have to be online to play offline? What?), but overall it does give some value over pirating games.
The irony is that NRK (the Norwegian government-owned radio and television public broadcasting company) is the nation-wide media doing (imho) the best job, being critical and covering a wide variety of cases from different angles.
For an example, look at DLD (norwegian DRD) coverage, NRK was just about the only media discussing it. Others media either ignored it, or uncritically posted statements from politicians arguing for it.
It seems everyone's forgotten how different things were before the iPhone. All this "obvious" shit wasn't obvious at all back then, and it was only a few years ago.
Well, you got LG Prada (came out before iPhone, had virtual touch buttons), Samsung F700 (slightly after iPhone), and then you of course got IBM Simon... Launched in 1993, had touch screen controls, a calendar, address book, world clock, calculator, note pad, e-mail, and games. And it had less physical buttons than the iPhone.
So... I'd say that all that obvious shit was pretty obvious back then, but the hardware was lacking a bit. Being the first in a race doesn't mean you invented running :)