This was the book that opened my eyes to reading novels in the language they were written in.
"The sky above the port was the color of television, tuned to a dead channel" just doesn't translate that well...
Why would you do that? Angular is based on the concept on binding form controls to a model and (a)synchronously posting that model to an API endpoint. That's the way you submit forms.
If you need the old style submit with form-data instead of json-data that can be done as well using a properly configured call to $http. You need to set a header and transform the model using $param.
Simple example: Ever try to submit a from from an AngularJS controller? Yeah, not doable. Add 2 lines of jQuery? Done! So yes, learn it, and use it where it fits.
If you're not able to submit a form in Angular you're not using the framework correctly.
This is exactly the way I do it too. Except I explicitly tell all clients that "IE6 support will cost you XX hours extra". At $120+ an hour they think twice about IE6
The largest bank in Denmark has all its employees running IE6 on Windows XP. The reason? It will cost $XX million to modernize all the legacy mission critical only-running-on-IE6 software.
On the other hand, if you're setting up a web server and you don't make the first component of the name www then I would have to say that you are dense and you're not really doing your job properly.
I can accept "www" for the "main" site. Just. But for subdomains? No way I'm going to name a site www.subdomain.example.com.
I'm so glad you're not running my DNS / Apache. I would have to fire you on the grounds of idiotic incompetance.
I'm a web developer paid by the hour. When estimating a project for a client I say to them that I will make their site work in all modern browsers (that is IE7+, FF2+ and Safari 3+). It will render in IE6 but will most likely not be pixel perfect. I will also say that I absolutely can make their site render pixel perfect in IE6 but it will be time consuming.
At $200+ an hour they always choose to let IE6 go.
We appreciate having/. optimized for FireFox, but would also like such consideration for the more-used IE6 browser.
Actually that's exactly what NOT to do. IE6 users need to be constantly made aware that they are using an obsolete browser. The sites being visited by the bosses need to break in IE6. That might turn things around.
Slashdot Mirror
I'm just looking forward to "Android Quiche"
That quote is the opening sentence of Neuromancer, not Burning Chrome.
This was the book that opened my eyes to reading novels in the language they were written in. "The sky above the port was the color of television, tuned to a dead channel" just doesn't translate that well...
The twit-in-chief is still twitting away..
Good point. Thank you.
I bet you've never once ridden a bicycle to work, have you?
Oh, but I'm not an american. I regularly bike to work.
What does it matter to cut down on carbon emissions if all you are doing is replacing them with methane?
Aaron Swartz lost this battle. Hopefully others will prevail.
The European Union is not a country. It's actually 28 countries.
Photographic memory is a myth. http://www.medicaldaily.com/ph...
It's a marketing stunt: http://vonhughes.getrumblr.com...
And the above is of course using jQuery ($.param)...
It is trivial to construct a function doing the same as $.param. There is no reason to pull in jQuery for this.
Why would you do that? Angular is based on the concept on binding form controls to a model and (a)synchronously posting that model to an API endpoint. That's the way you submit forms.
If you need the old style submit with form-data instead of json-data that can be done as well using a properly configured call to $http. You need to set a header and transform the model using $param.
This tutorial has more: https://scotch.io/tutorials/su...
Simple example: Ever try to submit a from from an AngularJS controller? Yeah, not doable. Add 2 lines of jQuery? Done! So yes, learn it, and use it where it fits.
If you're not able to submit a form in Angular you're not using the framework correctly.
Each time some government official says something like this I double the strength of the next keypair I need.
http://en.wikipedia.org/wiki/F...
Not at all.
This is exactly the way I do it too. Except I explicitly tell all clients that "IE6 support will cost you XX hours extra". At $120+ an hour they think twice about IE6
The largest bank in Denmark has all its employees running IE6 on Windows XP. The reason? It will cost $XX million to modernize all the legacy mission critical only-running-on-IE6 software.
Just apply for the JREF Million Dollar Challenge. With your ability it should be childs play.
*SWOOSH* Did you hear that? That's the sound the pus-joke made when it passed over your head.
+1 truth
Hmm..
Unless my math fails me then the average price would never drop below $10 if you only present the three options $20, $average and $10
I can accept "www" for the "main" site. Just. But for subdomains? No way I'm going to name a site www.subdomain.example.com.
I'm so glad you're not running my DNS / Apache. I would have to fire you on the grounds of idiotic incompetance.
I'm a web developer paid by the hour. When estimating a project for a client I say to them that I will make their site work in all modern browsers (that is IE7+, FF2+ and Safari 3+). It will render in IE6 but will most likely not be pixel perfect. I will also say that I absolutely can make their site render pixel perfect in IE6 but it will be time consuming.
At $200+ an hour they always choose to let IE6 go.
We appreciate having /. optimized for FireFox, but would also like such consideration for the more-used IE6 browser.
Actually that's exactly what NOT to do. IE6 users need to be constantly made aware that they are using an obsolete browser. The sites being visited by the bosses need to break in IE6. That might turn things around.