Re:Deskop app more richer than web app? How?
on
The Future of HTML
·
· Score: 1
i agree with you. as web developer (LAMP,CSS,XHTML), creating a browser-based web app is much easier then a desktop app.
1. deployment is much simplier. Just post the latest code to the production server.
2. maintenance is much simplier as well. again, just post the code.
3. there is basically no such thing as pirating as you have complete control over the code of the app.
4. the cost of developing a web app is much cheaper then a desktop app.
5. compatibility is much easier. it just has to work with a small group of browsers. and the more simple your output code (html,css,javascript) the more compatible you are.
6. accessability... section 508.
IMO, one major thing i have an issue with is restricting your app to a particular browser (IE). Especially when the point behind the application doesnt require a particular browser.
There's a javascript hack available that gets called as a behavior in css which wil display png files' opacity correctly and it doesnt require the need to give each png a unique id. see a previous client of mine. I used this technique on that site.
speaking of talking tits....
... if he keeps failing at jobs like that! I wonder if it was his attitude or 'just being lazy' that got him fired from nasa?
you mean how the racing stripe on my 92 civic gives me an ubber HP boost?
i wonder if that would get sent to nigeria.
i agree with you. as web developer (LAMP,CSS,XHTML), creating a browser-based web app is much easier then a desktop app. 1. deployment is much simplier. Just post the latest code to the production server. 2. maintenance is much simplier as well. again, just post the code. 3. there is basically no such thing as pirating as you have complete control over the code of the app. 4. the cost of developing a web app is much cheaper then a desktop app. 5. compatibility is much easier. it just has to work with a small group of browsers. and the more simple your output code (html,css,javascript) the more compatible you are. 6. accessability... section 508. IMO, one major thing i have an issue with is restricting your app to a particular browser (IE). Especially when the point behind the application doesnt require a particular browser.
cd /Internet; rm -rf Level3
already happened .... Bush
apperantly my real dad is in kansas too
Go there and Zoom all of the way in.... it makes me hungry!
Now they have an excuse to screw up even more.
There's a javascript hack available that gets called as a behavior in css which wil display png files' opacity correctly and it doesnt require the need to give each png a unique id. see a previous client of mine. I used this technique on that site.
Even IE7 cant really handle pngs that well.
Hey Microsoft meet W3C.