Remember when IE6 was so incredibly easy to work with? Remember how much effort has been dedicated to port those internal "web applications" that worked on one specific browser?
That's an interesting idea. Allow me not to take part on it.
At least my master gives me a 'created-date' field on every file. Gosh, that makes sense. I'd have to write my own file-system or use some outdated, unsupported crap to have that on 'nix.
I see you are unfamiliar with modern *nix OSs. Mine gives me both creation time and access time:
rbanffy@computer:~$ ls -l --time=atime a.out
-rwxrwxr-x 1 rbanffy rbanffy 8378 2011-11-10 15:24 a.out
rbanffy@computer:~$ ls -l --time=ctime a.out
-rwxrwxr-x 1 rbanffy rbanffy 8378 2011-10-22 19:31 a.outhttp://unix.stackexchange.com/questions/20460/how-do-i-do-a-... "Note that the ctime (ls -lc) is not the file creation time, it's the inode change time."
So, like I said...yes you do have to roll your own to get it. Enjoy that.
I see where you are going. I guess I'll have to move to FreeBSD to get file "birth time" support (or look into POSIX extended attributes). It's more or less a painless change. FreeBSD also has ZFS support, which is the filesystem to rule'em all. Either way, I don't expect Silverlight or WPF to run on FreeBSD.
The takeaway is this: don't build your mission critical internal apps on a Microsoft browser plugin. This has never worked out well.
OTOH, you may be tied to IE6 and unable to see all this.
Can you even get a data grid that is half as powerful or has as robust an API as something like this? http://www.telerik.com/products/wpf/gridview.aspx
Which is the whole point. Gmail runs on my Mac, on my Linux machines, on my OpenSolaris server (actually, it runs OpenIndiana these days) and on my tablet. It would probably run just fine on my AIX boxes if I compiled Firefox or Chromium for them. If Google abandons it (but keep the servers running) it will continue to operate on newer computers and newer browsers until Google pulls the plug.
I'm sure the Gmail team could do a bunch of hacks to fix this, but that's the problem. You have to hack-up everything to make HTML work well as an application platform.
If you think that's a good grid, I don't expect you to see anything remarkable about the grid I posted.
Looking around my office, I gather it would run on about four or five computers out of the about 50 here.
[1] http://www.microsoft.com/getsilverlight/Get-Started/Install/...
People who only do web dev just don't know what quality is.
I don't understand why everyone is so hung up on HTML though. The internet is not HTML, the internet is TCP/IP and all the protocols that ride on it like HTTP.
Why can't we just leave HTML the way it is, use it primarily for making nice documents and come up with something new for apps? You know, instead of trying to shoe-horn everything into a spec that has to cover both apps and documents or anything in-between?
Why isn't there a standards committee for a kit like Silverlight or Flash? The runtime would have to be built once for each platform, but that's no different than HTML.
every discussion i've ever seen about advancing the state of the web, the sticking point has always been "what about intranet/corporate networks?". well, if you run an intranet, fuck you. stop using the idea that you control the endpoint as an excuse to write crappy apps. you shouldn't be controlling that end point, you should be giving your users freedom to access your services in as many ways as possible rather than limiting their productivity by restricting their usage to your approved endpoints.
security policies like those are stupid, and an artifact of a time before networks. we shouldn't have to build our networks around outdated policies, security policy should be built to accommodate the technologies of the time.
Nobody should ever invent a competing technology because HTML is good enough for you? Is that it?
As long as this technology is easy and free for everyone to implement in compatible ways, yes, you can.
I think that I understand why someone would wish to exclude all proprietary technology. No advocacy is the best advocacy though. If the product is so great, it sells itself. It does. People use 'nix all the time for the things it's good at and then they go use other stuff too. Hostility towards that "other stuff" really works against the cause IMO. Why not spend the same time an energy to make the product better? Then people will just use it and nobody will have to argue about it.
I really hope this isn't true.