3 ms·
And they know they're using NoScript. If the website doesn't work, they can decide if they want to enable or not. It's their burden, not mine. Unless, of cours
by slig 13y ago
And they know they're using NoScript. If the website doesn't work, they can decide if they want to enable or not. It's their burden, not mine.
Unless, of course, my client wants a 100% working no-script webapp/site. Then I'll happily charge for the extra time building it.
- prodigal_erik 13y agoYou may want to use a pseudonym for work where you cut corners and failed to do work you're actually prepared to do properly. I browse without javascript enabled to judge the quality of the tools I'm considering; I wouldn't hire anyone with a portfolio full of broken non-semantic documents.
- slig 13y agoIt's not "cutting corners". It does take more time to build an webapp that works without any JS. If it takes more time, the final product costs more. The client should be aware of that and make the decision. Why should he/she always pay for something that will only be useful for a very small % of his/hers clients?