ethermal

I'm throwing my 2 cents in, although I haven't built a large scale app with either, I did do a full evaluation of both before my latest large app and I decided on neither one. There were many reasons but every time I wanted to do anything that was remotely non-trivial both fell apart. Although most of that had to do with the MVC pattern more than the actual framework (but the two are tied intricately) In the process of evaluating these two frameworks I found KnockoutJS and I chose it for my large project that is one year into development. After one year with it I love it more now then when I first started. It's not perfect but it is a really well thought out framework, it does lack some documentation, ko.utils I'm looking at you. But it's documentation is vastly superior to the other two frameworks, at least it was a year ago. It's very stable and I prefer the team's approach. The two binding and subscription model is great for solving some intricate problems. It's easily extensible with custom bindings and unlike angular doesn't favour bad coding habits that lock you in to the framework, I forget the name now but their custom HTML tags (I think they call them directives) is nothing but bad news and vendor lock in.

I don't get this line of thinking. Do you know there are programs written on system/36 machines from the early eighties still in production today on ibm iSeries machines? And even older software/systems in place that are older then that. Business requirements don't change hourly/weekly/monthly. If the business requirement that existed at that point in time, that the software solution put in place at that time met those requirements why would a business be compelled to change if those requirements have not changed and the solution met those needs? I've been a developer a really long time, 25+ years professionally. Businesses demand stability, this absolutely absurd idea that software that is only a few years old must be thrown out and some new flashy unproven shit put in its place is mind boggling. The last job I put a bid on, one of the requirements was that the software in initial form be supported for a minimum of 10 years. And in my experience that is a short life span.

it isn't, it's all political.

just wanted to say that if alcohol is related to 31% of the deaths in driving crashes. Then being sober accounts for 69% of the deaths therefore it is safer to be drunk then to be sober. Woohoo!

I agree and perhaps handing a coder some code and asking the coder what's going is maybe a better test of their skills then asking them to code on the spot.

That's true, however asking someone on the spot to write a function that requires domain specific knowledge isn't a good solution. What are you in fact testing, do they know how to code or do they know how to calculate the area of a circle. I can code but I'd fail horribly on the area of the circle thing simply because I haven't done anything like that since grade school math class probably 30 years ago.

So his comment is valid in that coders should code but his example of how to tell if someone can code I think is flawed.

But you could make possession of stolen property (the bike) a major crime with prison and financial punishment and you weaken the demand side of things.

Then using RFID or similar technology, you could embed a RFID tag somewhere in the frame. Then allow someone to report a stolen bike with a police report, very similar to a stolen vehicle report and then using remote scanners you could scan for stolen bikes very easily. All it takes is fear of a stolen bike to scare away potential buyers.

Well said.

indeed. I can't stand when setting width:100% can actually extend past the bounds of the parent.

But having to use the app to manage files, is a whole new paradigm that someone has to learn which is exactly what people are trying to avoid in the first place. So either teach one paradigm to a new user and stick to it (aka using the file system) or application specific paradigm (aka use iphoto to manage photos, itunes for music files, etc). So depending on how good you are at controlling the application usage from one app to another you end up having to learn each applications way of doing things instead of learning one way of doing things and using that throughout.

As a developer and previous life as IT support I fully support the teaching the file system paradigm because it works better overall.

All of the tag resorting you are doing within iphoto can and is done rather easily within the file system as well so what has that added other then more complexity?

Very true, I've been in IT for over 20 years and have worked at sites ranging from 10 users to over 13000 users. I can attest to the flat filing system as the exception not the rule. At my current employer, looking at public folders on network shares the average folder depth is 5 deep. Many have a main repository and then secondary and Tertiary hierarchies using symbolic links to the same contents to help people find what they are looking for.

not true in the least, the healthiest of my friends from outward appearances eat no fruit or veggies what so ever. Observations on small samples sizes are useless.

IE9 can easily handle your quick example. Check out http://jsfiddle.net/c8rN3/ then hit f12 bring up the developer tools. In the HTML tab click the tiny refresh button then hit the select element by click and select an element within the iframe.

wha? Hit the tiny html refresh button ctrl-b select away.

IE9's debug tools are hands down the best at this point in time. Although Chrome's is cacthing up, pound for pound you will be far more productive in IE9s debug tools then firebug, dragon fly or any other at the moment. I think there is just too much bias at play here.

VMs run all of them crazy easily. And using unity you can have all versions on your desktop at once and open. I do it every day. My default browser is IE 9, so when i launch I always launch in IE 9 do all of my testing debugging there, almost never even look at another browser until it works 100% there. Then my browser for surfing is Opera, all others for testing.

So why would you sort it in FF then open IE why wouldn't you start with IE then go to FF. I really think you are starting in the wrong spot.

almost all of my spinning disks in the last 20+ years have failed. Some right away, some in a few months, some in a few years but they all have failed.