735 karma · joined April 21, 2011
is this true ? is it legal..
2) You don't see a change of cursor when hovering over editable properties. People who never used firebug might have gotten used to this but for me it feels clunky.
3) No single click edit. On firebug you can start editing a property with a single click. Not so on chrome. This is even worse when editing styles. When single clicking a style you don't even see a visual indication that something happened... again feels clunky..
4)Too many tabs that are not bunched according to how often they are used.. I don't think people use Resources, Timeline, Profiles, Audits as often as they use the other tabs.
5) The information is presented in more readable way. When a break point is hit, chrome displays a bunch of tabs on right which are vertical (often empty - because they aren't relevant to this break point) and wasting precious vertical space..
6) Clutter, clutter and more clutter.. just too many sub windows cramped into one another affecting readability...
I know that most of these reasons are subjective and vary across developers but wanted make a list of my own reasons as I found my self trying to use chrome dev tools and always jumping back to firebug.
Though one problem I see with above approaches is that you may not control what project proposals you get... that's okay as long as a portion of your projects are of tangible output type...
It's many things to many people. To beginners, its a friendly cub to play with. To enterprise coders its the beast of burden to carry things. To newbie web developers/existing c++ programmers its familiar face on a new road. It won't devour you unless you have a death wish.
Exploits like this are worth a lot on black market. They are worth even more if you provide a precious and vulnerable target to go along (github).
It was actually a common misconception. Nearly all the engineering work for Apple 1,2 was done by Woz alone (as per his book). And Apple 1 was completely done in isolation in his apartment. His book is such an awesome read.
It's very interesting. They straight out say P3P is a dead protocol. And from the explanation of how it works, it does seem to be a joke - trusting third party websites to honor user privacy ? seriously ? I think Microsoft is simply trying to raise a shit storm over nothing... at least Safari one is a real screw-up on Google's part...