Heinlein's books are not politically correct. Just look at the PR trouble they're having with Ender's Game just because the author is against gay marriage.
Hollywood doesn't want any controversy in their movies. The latest Star Trek even used a white man instead of the older Star Trek material to avoid associating evil with a man of color.
Why are you talking about the 3rd world? The majority of Hollywood's money comes from the first world: North America, Europe, Australia and the civilized parts of Asia.
If there is no contract, then there is no warranty of any sort nor any guarantee that the work done will conform to what was desired. Which means that you'd have to be extremely naive to use this sort of service as you could end up in serious trouble. If there is a contract, then there is nothing special about this. It's just regular work.
A gun is a device that is pretty much guaranteed to maim or kill--with a single use--a selected target, at a distance and almost instantly. It requires almost no real physical effort on the part of the user.
Surely you realize this is also true of a lot of other devices, and that for some of those devices neither purchase nor ownership is restricted by law? Pretty much any tool running on gasoline or electricity is capable of seriously maiming people without effort.
Some objects are responsible for the lifetime management of resources. It's called ownership. You don't really need shared ownership. Most of the time it's just used as an excuse for sloppy design.
If your resource is not copyable, then copying is not an operation that is available. Copying is also costly, so If you don't need to copy, then don't copy.
Those people saying that don't make it a very good idea. Stepanov, the inventor of the STL, clearly recommends a non-aliasing non-sharing approach to scope-based resource management.
And I found him to be a more interesting guy than Bjarne or Herb when it comes to C++ programming.
shared_ptr is a distortion of the RAII principle. RAII says that you acquire a resource in a constructor and free it in the destructor. shared_ptr does not free the resource in the destructor, it decrements a reference count, and if it reaches zero it frees the resource.
Proper RAII is exclusive ownership. shared_ptr is for lazy GC-style coding.
shared_ptr is reference counting, which is pretty much garbage collection. Just manage your memory without relying on this but by designing your application taking into account which objects are responsible for the lifetime of other objects (ownership).
Slashdot Mirror
Heinlein's books are not politically correct.
Just look at the PR trouble they're having with Ender's Game just because the author is against gay marriage.
Hollywood doesn't want any controversy in their movies. The latest Star Trek even used a white man instead of the older Star Trek material to avoid associating evil with a man of color.
Skyfall wasn't that good.
You'll have forgotten it in a few years.
Clearly you haven't forgotten Moonraker though.
Why are you talking about the 3rd world? The majority of Hollywood's money comes from the first world: North America, Europe, Australia and the civilized parts of Asia.
If there is no contract, then there is no warranty of any sort nor any guarantee that the work done will conform to what was desired. Which means that you'd have to be extremely naive to use this sort of service as you could end up in serious trouble.
If there is a contract, then there is nothing special about this. It's just regular work.
Reddit and insightful open-minded discussion in the same sentence?
Surely you must joking.
The next generation of social marketing maybe.
Surely you realize this is also true of a lot of other devices, and that for some of those devices neither purchase nor ownership is restricted by law?
Pretty much any tool running on gasoline or electricity is capable of seriously maiming people without effort.
Isn't Colorado supposed to have decent beer?
Some objects are responsible for the lifetime management of resources. It's called ownership.
You don't really need shared ownership. Most of the time it's just used as an excuse for sloppy design.
Most resources are not shared.
That's because you're still thinking with references.
If your resource is not copyable, then copying is not an operation that is available. Copying is also costly, so If you don't need to copy, then don't copy.
A complex application in Javascript? Come on, be serious. Web applications are hardly complex. The very few that are are written in C or C++.
Those people saying that don't make it a very good idea.
Stepanov, the inventor of the STL, clearly recommends a non-aliasing non-sharing approach to scope-based resource management.
And I found him to be a more interesting guy than Bjarne or Herb when it comes to C++ programming.
Just read wikipedia.
The principle of RAII is that you acquire a resource in a constructor and release it in the destructor.
When you copy, you copy the resource.
shared_ptr does not do that. The destructor does not release the resource, and copying just aliases the resource.
shared_ptr is a distortion of the RAII principle.
RAII says that you acquire a resource in a constructor and free it in the destructor. shared_ptr does not free the resource in the destructor, it decrements a reference count, and if it reaches zero it frees the resource.
Proper RAII is exclusive ownership. shared_ptr is for lazy GC-style coding.
All shared_ptr does is allow for lazy GC-style memory management in C++.
ownership usually does not need to be shared.
Wait, are you seriously comparing a full-featured GNOME program with a trivial Python script?
The C standard library is extremely lightweight, that's the point.
But I do that everyday. There aren't many at all.
There are essentially two garbage collection algorithms: mark-and-sweep and stop-and-copy. Both can be generational, incremental, concurrent, etc.
shared_ptr is reference counting, which is pretty much garbage collection.
Just manage your memory without relying on this but by designing your application taking into account which objects are responsible for the lifetime of other objects (ownership).
You simply code what you need instead of depending on framework that do everything for you.
You realize you have thousands of packages installed, right? That's not a couple of Javascript apps.