Put an asteroid in geosync orbit and attach the elevator to that. Which means that first we need to fly asteroid-capture missions, not only as counter-weight but for the raw materials they provide. This is where the money is. The nation or company that gets the first asteroid in orbit will have more than enough money from raw materials to build their own space elevator.
And I guess we need a shuttle-type transport to get asteroids in Earth orbit somehow.
Furthermore, an algorithm is inherently non-technical and therefore cannot constitute a technical invention. Nonetheless, a method involving the use of an algorithm might be patentable provided that the method is used to solve a technical problem. However, any patent granted for such a method would not monopolise the algorithm itself or its use in contexts not foreseen in the patent.
Which, frankly, isn't worth all the money we spent on the shuttle, much less fourteen lives.
Well those fourteen astronautes themselves thought it was worth it! They sure knew the risks. Who the hell are you to say they died for no good reason? Give these people the respect they deserve.. Jeez...
Here's another hint: with arch (and some others), revision control is distributed. So you're probably comitting in your own repository, where you only need to agree with yourself. Upstream then fetches those patches that they want from you repository. And you'd better make sure all patches related to feature/fix X are present.
Regardless of this, atomic commits are a must because it is very possible to share an archive with N developers, and you don't want to have two commits referring to one revision (or other freakyness).
Distributed revision control also means you can continue to work even if the "master upstream" is down. (The master server is probably the one from the lead developer, or whatever. It is in no way different to any other repository.)
There's much more good stuff this way, come check it out. Me, I gotta work now.;)
I mix techno on two Technics MK1210 MK2's for about a year now. Really fun, but also really expensive, since you have to keep buying vinyl to keep with the times.:)
For an MVC architecture in PHP you should give Phrame a try. Quite cool, but there's a bug in the 2.0 release.
Easy enough to fix yourself, but I can send you an updated version if you don't like to bother with redo-ing work.. Just reply to this if you're interested.
Or asking the gcc folk to have a particular compile option on ia64 actually work -- their response -- either do it yourselves or pay us to do it. ???
Erm? Your reasoning is seriously twisted. It's free software as in freedom, not as in beer. Of course the gcc team asks for money.
You are, of course, totally justified in using something else, if that suits your needs better.
Well if it is not patented nobody will make serious bucks selling invisibility cloaks and this means noone will produce them.
The inventor also wouldn't see a penny (no, the author of some sci-fi story dit not invent it, he had the idea.. FTL drive prior art, anyone?), which would be a shame.
That't what I think, anyway. Maybe I'm just blatantly wrong.
Slashdot Mirror
This is interesting to me. If you would find that article, I'd greatly appreciate you posting the link in this thread.
:)
Cheers.
-- Alexander
Oops. You were right and I was wrong.
The asteroid would need to be past geosync orbit, I read on http://en.wikipedia.org/wiki/Space_elevator. I apologise.
No, it doesn't.
Put an asteroid in geosync orbit and attach the elevator to that. Which means that first we need to fly asteroid-capture missions, not only as counter-weight but for the raw materials they provide. This is where the money is. The nation or company that gets the first asteroid in orbit will have more than enough money from raw materials to build their own space elevator.
And I guess we need a shuttle-type transport to get asteroids in Earth orbit somehow.
Hah. Train accident galore! You might want to read this and this.
60 fps is just fine. If it isn't, you're just not good enough at the game.
Bah. The right solution to this problem is having the cameras encrypt their signal. Switching to a fascist society will not do the trick.
Hehehe :)
One word... Jabber.
I'd say 13c is pretty important, as well:
Furthermore, an algorithm is inherently non-technical and therefore cannot constitute a technical invention. Nonetheless, a method involving the use of an algorithm might be patentable provided that the method is used to solve a technical problem. However, any patent granted for such a method would not monopolise the algorithm itself or its use in contexts not foreseen in the patent.
Can't win the lawsuits? Let's just see how many suckers will pay up if we just send out invoices.
3. Profit!
I guess we should be poking the Abiword developers now to do the same.
Well those fourteen astronautes themselves thought it was worth it! They sure knew the risks. Who the hell are you to say they died for no good reason? Give these people the respect they deserve.. Jeez...
Here's another hint: with arch (and some others), revision control is distributed. So you're probably comitting in your own repository, where you only need to agree with yourself. Upstream then fetches those patches that they want from you repository. And you'd better make sure all patches related to feature/fix X are present.
;)
Regardless of this, atomic commits are a must because it is very possible to share an archive with N developers, and you don't want to have two commits referring to one revision (or other freakyness).
Distributed revision control also means you can continue to work even if the "master upstream" is down. (The master server is probably the one from the lead developer, or whatever. It is in no way different to any other repository.)
There's much more good stuff this way, come check it out. Me, I gotta work now.
You're missing Control-Tab for tab-switching, and Control-W for closing tabs.
;)
There, all your gripes eradicated.
I mix techno on two Technics MK1210 MK2's for about a year now. Really fun, but also really expensive, since you have to keep buying vinyl to keep with the times. :)
For an MVC architecture in PHP you should give Phrame a try. Quite cool, but there's a bug in the 2.0 release.
Easy enough to fix yourself, but I can send you an updated version if you don't like to bother with redo-ing work.. Just reply to this if you're interested.
Use a Wiki, it should do all you need.
You are, of course, totally justified in using something else, if that suits your needs better.
The original author must be attributed, is what licenses usually say. Please do correct me if I'm wrong...
Does anyone know of some real-world applications that use this framework?
Heh, that last link even has some funny source code I didn't notice at first glance. ;)
http://identd.sourceforge.net/
http://freeware.teledanmark.no/identd/
http://sourceforge.net/projects/winidentd/
http://identd.dyndns.org/identd/
But on the other hand, here are some reasons why your question is valid...
You were right, weather was great. ;) The Dali museum in Figueres is magnificent, visit it if you haven't yet.
Well if it is not patented nobody will make serious bucks selling invisibility cloaks and this means noone will produce them.
The inventor also wouldn't see a penny (no, the author of some sci-fi story dit not invent it, he had the idea.. FTL drive prior art, anyone?), which would be a shame.
That't what I think, anyway. Maybe I'm just blatantly wrong.