rubbish, there are all sorts of database queries that might be repeated, and the whole point of caching is that it takes advantage of the fact that recently accessed data is likely to be accessed again soon. not all 10 million users are going to be logged in at the same time...
Re:Author seems to live in a vacuum
on
On PHP and Scaling
·
· Score: 2, Informative
Quite. The advantage of Java when combined with a database (and as you rightly point out how often is a webapp *not* combined with a database?), is that you can take advantage of in memory caching, improving scaling up to a point by reducing load on the database, which is typically the slowest part of a web app transaction.
Personally I use and love both Java and PHP for web apps, horses for courses certainly, but I would be far more comfortable with Java for a large webapp any day.
Superb! Thanks for that, I promised my friend I'd find some hamster pr0n for his new hamster's boudoir. So far she (the hamster) has a framed Keanu Reeves picture, and a zebra skin rug. I made her a bottle of poppers, but daddy wasn't too pleased, so it was removed. I think the porn will go down well though. Perhaps we can make it into a magazine...
'Game' and Tetris have been on Ericsson phones for a while, they were first released on the T29. I was chuffed, defender is one of my favourite classic arcade games..
Well if the GPL released code is only part of a system then what use is it without the non-GPL parts? In that case, why bother GPL-ing them at all? Unless you expect someone to finish off the missing bits...
This way they can have the core of their system updated, bug fixed etc by an OSS community, while still selling their value-add version.
Well you could say the same about the Jakarta project, but that would clearly be stupid, because all you have to do is go and look at the website and read about the sub-projects.
Eclipse has grown from being an open-source IDE framework, with an 'example' IDE for Java, into a general application framework, still with an 'example' application, being a Java IDE.
The fact that the Java IDE is superb helps matters.
That's fine if you're dealing with well documented code, but suppose you're using a 3rd party library which doesn't have very good API documentation. In practice being able to look inside the code lets you work out *how* you're meant to use the interface.
I would consider it a failure on my part if someone had to look inside my code to write client code for it, but that doesn't mean I'm not going to look inside someone else's if it's poorly documented.
1. Images don't scale, clients often want nice big branding 2. Clients will often override the designers wishes. Fixed width sites are still pretty popular.
Having said that, I'm happy with the minimum target res being 800*600. I don't like browsing full screen and I often nearly have to do that already. The vast majority of users still browse on a PC, handheld devices can force reorganisation of the layout, like Opera for Symbian does.
Slashdot Mirror
rubbish, there are all sorts of database queries that might be repeated, and the whole point of caching is that it takes advantage of the fact that recently accessed data is likely to be accessed again soon. not all 10 million users are going to be logged in at the same time...
the 150 was a reference to the copies linked from their hacked site, not suprnova, as far as i can tell.
They can't cache database accesses? Why not?
Quite. The advantage of Java when combined with a database (and as you rightly point out how often is a webapp *not* combined with a database?), is that you can take advantage of in memory caching, improving scaling up to a point by reducing load on the database, which is typically the slowest part of a web app transaction.
Personally I use and love both Java and PHP for web apps, horses for courses certainly, but I would be far more comfortable with Java for a large webapp any day.
Superb! Thanks for that, I promised my friend I'd find some hamster pr0n for his new hamster's boudoir. So far she (the hamster) has a framed Keanu Reeves picture, and a zebra skin rug. I made her a bottle of poppers, but daddy wasn't too pleased, so it was removed. I think the porn will go down well though. Perhaps we can make it into a magazine...
overpriced.
'Game' and Tetris have been on Ericsson phones for a while, they were first released on the T29. I was chuffed, defender is one of my favourite classic arcade games..
biometric encryption eh?
what was the last count of undefeated biometric id systems? somewhere around zero wasn't it?
"Closed source can ahdere to standards
;)
just as well as open-source."
Yet it's remarkable how often it doesn't.
There's far less motivation for an open-source project to break standards.
By the way, you probably shouldn't write your replies in OE with text wrap on and c/p them
Once bitten, twice shy?
Well if the GPL released code is only part of a system then what use is it without the non-GPL parts? In that case, why bother GPL-ing them at all? Unless you expect someone to finish off the missing bits...
This way they can have the core of their system updated, bug fixed etc by an OSS community, while still selling their value-add version.
Jobs runs Linux?
goodness!
I... oh I can barely be bothered....
Slashdot and the Internet maybe. Not spaceflight or computers, sorry...
"Why? How come you are offended by this? Why do you care so much?"
I don't know about him/her, but I dislike it because it makes us look like shouty skiddies..
Well you could say the same about the Jakarta project, but that would clearly be stupid, because all you have to do is go and look at the website and read about the sub-projects.
Eclipse has grown from being an open-source IDE framework, with an 'example' IDE for Java, into a general application framework, still with an 'example' application, being a Java IDE.
The fact that the Java IDE is superb helps matters.
except it's not. anywhere near :)
Surely being able to see a surfer's eye view on a big screen during competitions would be good?
what about Quake?
That's fine if you're dealing with well documented code, but suppose you're using a 3rd party library which doesn't have very good API documentation. In practice being able to look inside the code lets you work out *how* you're meant to use the interface.
I would consider it a failure on my part if someone had to look inside my code to write client code for it, but that doesn't mean I'm not going to look inside someone else's if it's poorly documented.
That's all very well but 2 things..
1. Images don't scale, clients often want nice big branding
2. Clients will often override the designers wishes. Fixed width sites are still pretty popular.
Having said that, I'm happy with the minimum target res being 800*600. I don't like browsing full screen and I often nearly have to do that already. The vast majority of users still browse on a PC, handheld devices can force reorganisation of the layout, like Opera for Symbian does.
RTFPatent ;)
to be fair I haven't read the patent either, but both of the articles imply that this is limited to automatic updates / patches.
mod parent up!
*burns karma*
I frequently look into (non Sun) APIs when I'm working in Java. If the documentation is unclear then what better way than to just have a look?
RTFP
It's about automatic updates. The headline is misleading.
Have you tried apt / apt-rpm / yum? They all work fine in my experience. The only time you're likely to get problems is if you mix repositories.