why do we need a massive installed base? no one had a web browser before they were invented and people went out of there way to track one down. if it easy to code for and easy to install people will download and use it. and yes I have a better idea - a standard event driven web model - its that simple. define the widgets, define the events they can generate, and provide an open source implementation of the whole thing.
don't get me wrong, i wholeheartedly AGREE! this would have been a lot easier before the web became so ubiquitous. now, you'll have to somehow coerce MS into embracing (and not extending) the standard, or hope that a real migration away from IE to something we have more control over occurs.
i read a comment somewhere today that mentioned boycotting IE browsers by redirecting them to some page when they're detected and not allowing access to the site. i think this idea is half-baked, and by that i mean one part is viable - i'd like to temporarily redirect users coming to my site to warn them about IE, and then allow them to continue on, hopefully after installing firefox. a standardized message without the usual kiddie shit would do just fine. of course, you'd never get this out to any real corporate site, but bloggers however...
Such a heavy book must contain lots and lots of usefull information!!!!
thick glossy paper...
Re:take a look in the book
on
Web Design Garage
·
· Score: 1, Insightful
yay, more "less knowledgable" people making web sites - just what we needed. be sure to check out the publisher's php nuke book for the less knowledgable too...
Sometimes it doesn't feel right to replace a 3-page PHP program with a 3-line Ruby script (hello Rails!) that does more. But then the feeling passes.
i agree. and at risk for going OT, i'll add that i'm only doing PHP at work, and in other for profit ventures. this is where i have to deal with other PHP developers and their associated skills (or lack of, sorry). don't get me wrong, i've work with some really great programmers.
my personal stuff, which is to me where i really soak up new things and experience, is in something else. lately i'm down with using fastcgi+python for web apps.
And yes I wish there was some kind of "programmer license" so there was at least *some* barrier to entry.
i've run across the people you're talking about. they're employed where i work. sometimes i really don't know how they got hired...
my job has offered to pay for employee's Zend certification, for whatever that's worth. i think that a real problem solving programming test and good response interpretation isn't a bad idea, for a company hiring developers. not something overly difficult, but looking for the very basics (and progressing).
Thanks for playing the role of "Angry, Anti-social, Elitist Perl Snob."
actually, i don't use perl cuz it sucks (compared to another p language that isn't the topic of this story).
i am merely suggesting that there are a sufficent quantity of PHP books on the market, and more do nothing to help the glut of "learn $language in 24 hours" programmers.
does the world really need another php book? what does this one cover that others don't? how many times can you rehash the real manual? i work in a place where 99% of development is in php, and you won't believe the idiots who read books like this one and are suddenly a "programmer".
In your own words, if someone gets spammed, it's their own fault.
no, i said that people shouldn't expect to spread their email all over the place and not get some spam, and that they should filter a little. go get rid of your bias, and reread.
You say that spammers shouldn't be in jail.
i don't think that drug addicts should be in jail either, does that make me one?
you posted that your company ocassionally sends spam.
not spam - *unsolicited* bulk email. just opt-in offers, that's not spam.
you're gonna say that about any multi-billion dollar company that incorporates open source into their products, regardless. face it, apple has contributed more.
Slashdot Mirror
why do we need a massive installed base? no one had a web browser before they were invented and people went out of there way to track one down. if it easy to code for and easy to install people will download and use it. and yes I have a better idea - a standard event driven web model - its that simple. define the widgets, define the events they can generate, and provide an open source implementation of the whole thing.
don't get me wrong, i wholeheartedly AGREE! this would have been a lot easier before the web became so ubiquitous. now, you'll have to somehow coerce MS into embracing (and not extending) the standard, or hope that a real migration away from IE to something we have more control over occurs.
i read a comment somewhere today that mentioned boycotting IE browsers by redirecting them to some page when they're detected and not allowing access to the site. i think this idea is half-baked, and by that i mean one part is viable - i'd like to temporarily redirect users coming to my site to warn them about IE, and then allow them to continue on, hopefully after installing firefox. a standardized message without the usual kiddie shit would do just fine. of course, you'd never get this out to any real corporate site, but bloggers however...
This technology is horrible for developers, we need a standardize event driven model for the web not this hacked together javascript nonsense.
:)
that's true, but do you have a better idea and implementation (with a massive installed base)?
this was in my bookmarks. you can use the HTTP request to call a script (in turn accessing a database), or whatever else you want to do...
ignore the troll, it's server independent.
way to go slashcode...
google this:
XML httprequest object site:developer.apple.com
http://developer.apple.com/internet/webcontent/xml httpreq.html
Such a heavy book must contain lots and lots of usefull information!!!!
thick glossy paper...
yay, more "less knowledgable" people making web sites - just what we needed. be sure to check out the publisher's php nuke book for the less knowledgable too...
did something change? i thought the troll was supposed to post first, not the other way around.
pc gripe 1: macs are too expensive.
answer: mac mini
pc gripe 2: one button mouse sucks
answer: apple two button mouse (hopefully with wheel)
Sometimes it doesn't feel right to replace a 3-page PHP program with a 3-line Ruby script (hello Rails!) that does more. But then the feeling passes.
i agree. and at risk for going OT, i'll add that i'm only doing PHP at work, and in other for profit ventures. this is where i have to deal with other PHP developers and their associated skills (or lack of, sorry). don't get me wrong, i've work with some really great programmers.
my personal stuff, which is to me where i really soak up new things and experience, is in something else. lately i'm down with using fastcgi+python for web apps.
And yes I wish there was some kind of "programmer license" so there was at least *some* barrier to entry.
i've run across the people you're talking about. they're employed where i work. sometimes i really don't know how they got hired...
my job has offered to pay for employee's Zend certification, for whatever that's worth. i think that a real problem solving programming test and good response interpretation isn't a bad idea, for a company hiring developers. not something overly difficult, but looking for the very basics (and progressing).
yes, i read it - same old same old. i'm sure it's a wonderful book and all, but how many "leading developers of PHP" have to suddenly become authors?
Thanks for playing the role of "Angry, Anti-social, Elitist Perl Snob."
actually, i don't use perl cuz it sucks (compared to another p language that isn't the topic of this story).
i am merely suggesting that there are a sufficent quantity of PHP books on the market, and more do nothing to help the glut of "learn $language in 24 hours" programmers.
the wheat must be seperated from the chaff.
my point exactly.
does the world really need another php book? what does this one cover that others don't? how many times can you rehash the real manual? i work in a place where 99% of development is in php, and you won't believe the idiots who read books like this one and are suddenly a "programmer".
can i see those pics? i mean that in the most "not a perv" kinda way...
ooh, i wanna put a mini in my rabbit.
:)
no, i like it here on my kitchen table
i agree. also, if i have a sql statement:
$some_q = " SELECT *
FROM x.table
JOIN y.table USING(a)
WHERE b = 0";
so that the statements (most much larger than this) are more readable. tabs only please, set to 4 spaces.
you wouldnt happen to know who came up with the x ? y : z syntax would you? I have a baseball bat who would like to meet him. or should i say
why? i use that all the time. if someone else comes along to change it and doesn't know what that means, they shouldn't be there.
In your own words, if someone gets spammed, it's their own fault.
no, i said that people shouldn't expect to spread their email all over the place and not get some spam, and that they should filter a little. go get rid of your bias, and reread.
You say that spammers shouldn't be in jail.
i don't think that drug addicts should be in jail either, does that make me one?
you posted that your company ocassionally sends spam.
not spam - *unsolicited* bulk email. just opt-in offers, that's not spam.
you're gonna say that about any multi-billion dollar company that incorporates open source into their products, regardless. face it, apple has contributed more.
somehow a headshot of jobs with the borg gear doesn't quite grab me...
alright, alright, for dogs sake i stand corrected! bad day, i swear.
it makes you look like unscientific amateurs.