Printable View
This is a good little debate.
I think using ' is much better than ". But depending on what you wanna do really. I can't think of a situation where I use " over '.
Also when i want to do echo I usually strip the string into each individual letters as they get put into an array and I echo them out individually to improve performance.
BTW I WS JKING
Well there is an advantage to useing ", as you can just have a line like "hello {$username}, whats up?"; as opposed to 'hello '.$username.', whats up?';Quote:
Originally Posted by BoyBetterKnow
Which does add to readability and can speed up coding. All really depends on what your doing and when, both have there place :)
Yes a database with 10s of millions of records isn't going to have write access when it's handling huge amounts of data, well done.Quote:
Originally Posted by Mentor
Your mind understands it faster (less than 0.0000000000000001 of a second faster! but that obviously still matters when your brain can process trillions of signals a second, just like a computer) because it's part of your mother tongue, just like and and und, your brain will always recognise and faster (if you're english, or und if you're german) because it's part of your "base programming" if you will it doesn't matter which, and as i said it's a matter of preference.Quote:
Originally Posted by Mentor
it doesn't make the difference at all, i've never seen any application that prints/echos something over 100 timesQuote:
Originally Posted by Mentor
see above, nobody cares about the differences any more, it's not real unless you're messing with several hundred thousand strings in 1 script, which never happens.Quote:
Originally Posted by Mentor
print is never faster than echo because it always returns 1, i will continue to drill this into your head until you understand RETURNING IS SLOWER THAN NOT RETURNINGQuote:
Originally Posted by Mentor
storing objects in a session is stupid, why would you ever do that? i can understand integers, booleans, arrays and strings, but not objectsQuote:
Originally Posted by Mentor
"usually, its preferable to use str_replace, but when you want to replace many characters for many others characters (and not only a value) strtr is better." note i didn't say always in my post, nor did i say anything about a speed differenceQuote:
Originally Posted by Mentor
my situations are logical, easy to understand and easy to comprehend, you're going on about differences that only happen in the poorest of code, i do believe my situations are far more real-world than yoursQuote:
Originally Posted by Mentor
I have no idea if your being sarcastic or not, but yea, thats pretty danm common? whats your point?Quote:
Originally Posted by Jewish Bear
You may wana go look at some German programming... (tip: it aint in german)Quote:
Your mind understands it faster (less than 0.0000000000000001 of a second faster! but that obviously still matters when your brain can process trillions of signals a second, just like a computer) because it's part of your mother tongue, just like and and und, your brain will always recognise and faster (if you're english, or und if you're german) because it's part of your "base programming" if you will it doesn't matter which, and as i said it's a matter of preference.
Yup, what script ever has ever output more than a 100 things... You don't believe in objects so i'm gonna guess in your code every time you show the top 100 members you get that?Quote:
It doesn't make the difference at all, i've never seen any application that prints/echos something over 100 times
[quote] see above, nobody cares about the differences any more, it's not real unless you're messing with several hundred thousand strings in 1 script, which never happens.
700,000 string? Thats a lot less than i often find myself messing with. You know what i was saying about those databases. Some companies have alot of transactions... Generating live stats reads alot of data and takes a while, those milliseconds start to count
They handle buffering differently, so not entirely true :)Quote:
print is never faster than echo because it always returns 1, i will continue to drill this into your head until you understand RETURNING IS SLOWER THAN NOT RETURNING
If you don't understand oop i have trouble considering you as a programmer..Quote:
storing objects in a session is stupid, why would you ever do that? i can understand integers, booleans, arrays and strings, but not objects
What makes this better?Quote:
"usually, its preferable to use str_replace, but when you want to replace many characters for many others characters (and not only a value) strtr is better." note i didn't say always in my post, nor did i say anything about a speed difference
I really, really doubt that. You see, my situations happen in the real world, with real data, for real people, under real deadlines, on machines with real specs and need to work in real time. Duno how you get much more real o.0Quote:
my situations are logical, easy to understand and easy to comprehend, you're going on about differences that only happen in the poorest of code, i do believe my situations are far more real-world than yours
I'm starting to follow Iszak's thinking as this is getting dull...
yes this is getting dull because you are making complex points about simple thingsQuote:
Originally Posted by Mentor
to put it simply:
returning is always slower than not
i use objects in everything that needs it (storing objects in sessions is not needed)
i am going to leave you to your fantasy world situations where every server is a pentium 3 with less than 1gb of ram and every database does 10 quintillion queries a nanosecond to listen to some brian eno and get some coding done and chat to people about things
using latin and such isn't smart nor impressive, using simple language that everyone can understand and get to grips with even though you can use such language is
uh and scalability is more important than speed anyway bye
Ha... if you only knew what the corporate world was like... are staging server has less than those specs :p Efficiency is key, fortunatly the db runs on a much faster cluster in the main data center so we just uses views to perform all the querying and main statistical processing sql side :)Quote:
Originally Posted by Jewish Bear
If your systems slow and inefficient, it wont scale o.0Quote:
using latin and such isn't smart nor impressive, using simple language that everyone can understand and get to grips with even though you can use such language is
uh and scalability is more important than speed anyway bye
Who was using Latin? I got lost on that point.
you need a better business if your staging server is that poorQuote:
Originally Posted by Mentor
you did, "ad hominem"Quote:
Originally Posted by Mentor
Playing my work place is bigger than yours seems kinda stupid... Then again, i kinda suspect your work only includes some mates giving you a few quid to bash out a crappy site every now and then "/Quote:
Originally Posted by Jewish Bear
Ah... Sorry to tell you thats English, it just comes from Latin. You start banning words that we imported from other countries and your dictionaries gonna be very very small.Quote:
you did, "ad hominem"
i don't do php for funds or profit, i find it's better to be open source with open source languagesQuote:
Originally Posted by Mentor
it's latinQuote:
Originally Posted by Mentor
Is that your way of saying you flip burgers for a living?Quote:
Originally Posted by Jewish Bear
Yea.. so's octopus :rolleyes:Quote:
it's latin