How many self-replicators would a self-replicator replicate if a self-replicator could replicate self-replicators?
.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.
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'd like to learn more arts or crafts.
Things like :
- Driving a race car
- Play a musical instrument expertly
- Do some carpentry
- Develop a garden
- Play more with kids.
I'm bored with science/math. Maybe I'm getting too old...
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.
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.
The primary function of the design engineer is to make things difficult for the fabricator and impossible for the serviceman.