(c) The.NET runtime is a moving target. I know developers who have had to basically trash all of their work to target the latest.NET Runtime. 1.0 -> 1.1 -> 1.3 -> 2.0 all required major rewrites, lots of refactoring, and lots of work. This is not just to get the new features, this is just to make it compile. Heck, even going from 3.5 to 4.0 will cost MAJOR development time and money because they changed everything around AGAIN.
Rubbish. Version 1.3? Where did you get that? 3.5 to 4.0 is a MAJOR development effort? You don't know what you're talking about.
I thought it was a pretty cheap shot. One has to be a prolific achiever now to even criticize Steve Jobs? Sorry that doesn't sound so smart to me. I could've imagined that coming from Steve Ballmer, but I imagined Jobs to be better.
I'm disappointed in this industry in general. With the advent of internet and open communications/standards, I thought the era of odious restrictions placed by software companies would go away. Looks like nothing will change; only the players change. We need more Stallmen.
i don't know what you're talking about. The replies have been pretty good so far. It's a sort of inane question, and the submitter isn't participating. What do you expect? Ask the submitter to post the actual requirements or atleast hint at them.
However, I think I see a glimmer of hope (for the not-more-blinking-MS-stuff view) in scripting languages..
Powershell is pervasive now. Every MS product now has powershell hooks. Most command-line utilities are being folded into Powershell extensions. While the language itself is not to my taste(I much prefer the *nix shells still), it's a big improvement alright.
Why not use the DB features? Most enterprise-y databases have PITR(Point-in-time Recovery features).. Although it's not designed for that sort of thing, it could be used in such a fashion. Most DBs do the same thing you guys do, i.e, use a transaction log. The transaction log could be replayed to get into a Point-in-time state. The one disadvantage is it's all or nothing i.e, you can't do it for specific transactions(although I'm sure some DBA will wander in correct me on this;)
Yes, but it's useless if you want to get at it remotely - like getting data for an ASP.Net app. Which means, you end up writing your own web services using the OM, and wrestle with your SharePoint IT management to get it deployed on the SP server. And if you're doing any non-trivial queries, it's back to CAML again. It can all be done, doesn't mean it's good though.
Is it that hard to come up with a coherent, usable API that can be remoted? I don't know; I'm hoping the next version does better.
Yeah, blindingly trivial; if you like munging through some hideous CAML fragments to extract meaningful metadata.. (CAML is SharePoint's XML schema nightmare). Getting the documents is the easy part; metadata, authorization info, and all those nifty bits is the tricky part.
Don't get me wrong - there's little standardization around this subject, and every CMS vendor fucks up quite a bit. They all have proprietary APIs; at least SharePoint spits XML. It still feels like pulling teeth. Next version is supposed to have a LINQ interface; hopefully that's better.
Well, please read the article. He was suffering from Stage 4 lung cancer, diabetes and high BP. I'm no doctor, but that looks fairly terminal to me. Why the fuck should I hang around as a vegetable?
Suicide is devastating to those who care, yes; but in this case at least, there's no selfishness. He saw that he was beyond extended support; and decided to go. Committing suicide takes a phenomenal amount of courage, and/or some mental instability. In this case, it seems to be mostly the former. Rest in Peace.
Can't that "non-fossil-fuel-based electric power" alone propel the car? Why do we need to make more fuel, resulting in more emissions, and poor energy conversion efficiency?
Classic case of a company not knowing what their product is used for.
Opera != Work Browser. Opera == Bestest P0rn Browser ! Swift image resizing, superior mouse gestures, and remaining responsive even after a gazillion tabs are opened.
It's like turning up with your purpose-built race car at the city center, and whining about speed humps.
Well SharePoint doesn't do any of those things, and the Office integration part sucks. Have you seen system requirements for SharePoint for a large organization? Have you administered a non-trivial sized Sharepoint instance? Have you managed a SharePoint version to version migration? It's a PITA, and completely overkill for most applications. The OP was right, most people don't need SharePoint.
It's the new generation nightmare - almost like MS Access and Lotus Notes rolled into one - easy for some tasks, ridiculously painful for others. And don't get me started on the whole song & dance people go through to build custom applications on top of it...
You can use Database Resource Management to control maximum execution time for queries in Oracle; it's designed to protect such scenarios.
However, the "pessimizer" as you call it is not a magic wand - it's just decent heuristics for selecting the optimal path for data retrieval. It's pretty complex; and has taken decades to come to this level. It's damn good if you understand it and configure your instance correctly. Where it doesnt work, you always have had other options.
I think GP's comment is quite valid. His comment was on the popularity of the framework on the Linux side of the fence, which is pretty much true. Outside of Suse, I'm not sure there's a lot of traction for Mono.
To be fair, Outlook/Exchange isnt a Groupware platform anymore. SharePoint is, and you could do the same things that you mentioned, in SharePoint. Office+SharePoint+Exchange+Outlook+.Net is the MSFT story. And I cringe whenever I hear "groupware" or "collaborative" applications. Yes sir, we dont need no steenkin design, data model, modularity, unit tests, anything!
A groupware platform is for groups; end-users, non-technical folks to collaborate on. When somebody decides to write a full-blown application on top of it, it's as useful as an Excel macro or Access application. Maybe useful at the start, but becomes a maintenance nightmare.
Slashdot Mirror
See subject. Please do not fuck these up - revert at least these two to the original. I don't wanna waste my time with user styles for now.
Dude, you made me RTFA - that's unfair :/
How many self-replicators would a self-replicator replicate if a self-replicator could replicate self-replicators?
Rubbish. Version 1.3? Where did you get that? 3.5 to 4.0 is a MAJOR development effort? You don't know what you're talking about.
Nice hack. And that's $24 large, as in millions. Heals the world, and somebody makes money out of it - win/win.
I thought it was a pretty cheap shot. One has to be a prolific achiever now to even criticize Steve Jobs? Sorry that doesn't sound so smart to me. I could've imagined that coming from Steve Ballmer, but I imagined Jobs to be better.
I'm disappointed in this industry in general. With the advent of internet and open communications/standards, I thought the era of odious restrictions placed by software companies would go away. Looks like nothing will change; only the players change. We need more Stallmen.
More like MicroGoogle(TM) Content Search Services 8th series 5th Edition...
i don't know what you're talking about. The replies have been pretty good so far. It's a sort of inane question, and the submitter isn't participating. What do you expect? Ask the submitter to post the actual requirements or atleast hint at them.
Yeah, why can't they just put ABS on it?
Powershell is pervasive now. Every MS product now has powershell hooks. Most command-line utilities are being folded into Powershell extensions. While the language itself is not to my taste(I much prefer the *nix shells still), it's a big improvement alright.
My guess - it'd be 50 dollars. With a service plan. 100 dollars per year. 200GB cloud storage, 10GB/month bandwidth, and pay more as you go.
Sweet enough? Of course you can hack and get onto local storage. But will you want to? Have you backed up your gmail mails lately?
Why not use the DB features? Most enterprise-y databases have PITR(Point-in-time Recovery features).. Although it's not designed for that sort of thing, it could be used in such a fashion. ;)
Most DBs do the same thing you guys do, i.e, use a transaction log. The transaction log could be replayed to get into a Point-in-time state. The one disadvantage is it's all or nothing i.e, you can't do it for specific transactions(although I'm sure some DBA will wander in correct me on this
Yes, but it's useless if you want to get at it remotely - like getting data for an ASP.Net app. Which means, you end up writing your own web services using the OM, and wrestle with your SharePoint IT management to get it deployed on the SP server. And if you're doing any non-trivial queries, it's back to CAML again. It can all be done, doesn't mean it's good though.
Is it that hard to come up with a coherent, usable API that can be remoted? I don't know; I'm hoping the next version does better.
Yeah, blindingly trivial; if you like munging through some hideous CAML fragments to extract meaningful metadata.. (CAML is SharePoint's XML schema nightmare). Getting the documents is the easy part; metadata, authorization info, and all those nifty bits is the tricky part.
Don't get me wrong - there's little standardization around this subject, and every CMS vendor fucks up quite a bit. They all have proprietary APIs; at least SharePoint spits XML.
It still feels like pulling teeth. Next version is supposed to have a LINQ interface; hopefully that's better.
Well, please read the article. He was suffering from Stage 4 lung cancer, diabetes and high BP. I'm no doctor, but that looks fairly terminal to me. Why the fuck should I hang around as a vegetable?
Suicide is devastating to those who care, yes; but in this case at least, there's no selfishness. He saw that he was beyond extended support; and decided to go. Committing suicide takes a phenomenal amount of courage, and/or some mental instability. In this case, it seems to be mostly the former. Rest in Peace.
Can't that "non-fossil-fuel-based electric power" alone propel the car? Why do we need to make more fuel, resulting in more emissions, and poor energy conversion efficiency?
I bet your VCR has 12:00:00 on it too :P
Classic case of a company not knowing what their product is used for.
Opera != Work Browser.
Opera == Bestest P0rn Browser ! Swift image resizing, superior mouse gestures, and remaining responsive even after a gazillion tabs are opened.
It's like turning up with your purpose-built race car at the city center, and whining about speed humps.
Well SharePoint doesn't do any of those things, and the Office integration part sucks. Have you seen system requirements for SharePoint for a large organization? Have you administered a non-trivial sized Sharepoint instance? Have you managed a SharePoint version to version migration? It's a PITA, and completely overkill for most applications. The OP was right, most people don't need SharePoint.
It's the new generation nightmare - almost like MS Access and Lotus Notes rolled into one - easy for some tasks, ridiculously painful for others. And don't get me started on the whole song & dance people go through to build custom applications on top of it...
Dunning-Kruger indeed.
make phone calls? :P
Interestingly, Opera's new ECMAscript engine has a register-based byte-code instruction set.
http://my.opera.com/core/blog/2009/02/04/carakan
You can use Database Resource Management to control maximum execution time for queries in Oracle; it's designed to protect such scenarios.
However, the "pessimizer" as you call it is not a magic wand - it's just decent heuristics for selecting the optimal path for data retrieval. It's pretty complex; and has taken decades to come to this level. It's damn good if you understand it and configure your instance correctly. Where it doesnt work, you always have had other options.
And no, I dont work for Oracle.
If you really wanted to know what happened to WinFS tech, read this interview by Quentin Clark.
I think GP's comment is quite valid. His comment was on the popularity of the framework on the Linux side of the fence, which is pretty much true. Outside of Suse, I'm not sure there's a lot of traction for Mono.
To be fair, Outlook/Exchange isnt a Groupware platform anymore. SharePoint is, and you could do the same things that you mentioned, in SharePoint. Office+SharePoint+Exchange+Outlook+.Net is the MSFT story.
And I cringe whenever I hear "groupware" or "collaborative" applications. Yes sir, we dont need no steenkin design, data model, modularity, unit tests, anything!
A groupware platform is for groups; end-users, non-technical folks to collaborate on. When somebody decides to write a full-blown application on top of it, it's as useful as an Excel macro or Access application. Maybe useful at the start, but becomes a maintenance nightmare.