That is nice. I a saw a review linked in a different post where they complained about the shiny 1366x768 screen.
I tried to buy a ThinkPad Edge last year, and had to give up because the latest models only came with extremely reflective 1366x768 screens. Let us hope Lenovo has learned the lesson then.
You can have multiple versions of KDE installed. Not Gnome.
No, unfortunately KDE is not that good out box either. It takes a bit of work to run multiple versions of KDE-runtime, but of course it is possible, that is how you develop for it and test it while still running the latest stable KDE on your desktop.
Bottom line is, for a AAA game, there's a good 2 months at the very least before launch when nothing much goes on with the game. DLC is worked on in that period, and if it doesn't hit the mark and needs 2-3 weeks more, it's not a big deal. Risk management.
That doesn't explain the "DLC" that is now commonly shipped with the games to minimize the downloading process.
The comment is not necessarily about you specifically. You have already answered for yourself elsewhere, and explained what you do about information warfare is not about propaganda but encryption (though after I wrote my comment), but I stand by my assessment of the general competence of misinformation mercenaries, though that apparently doesn't relate to you.
There are other types of synchronization than just Mutexes, as I said, except Mutexes it is not trivially to do exception safe coding for synchronization. What the 'revert' or 'safe' state is, can vary from function to function, and you need to handle the cases explicitly, which is the opposite of what exceptions does. Exceptions makes the assumption that the code-path doesn't matter, and everything has a trivial way to unstack the state, this is rarely the case, and you are just adding more and more increasingly complex workarounds (unstacking pointers, transactions, mutexes) to make an obviously broken feature, almost work.
Point allocation is only one problem, other much bigger issues are database transactions, data safety and especially thread synchronization. You can do smart-pointer like stuff to make sure the database transactions are rolled back or commited when the function is exited on irregular codepaths, but with the exception of very simply mutexes, the same can not be done for thread synchronization.
It is much simpler to just disable exceptions, and deal with your errors the right way, by handling them.
Well, in 12 years of C++ programming, I have never seen a project where exceptions were NOT disabled. Of course 10 years ago, they were generally too poorly supported and slow, but still all projects I have encountered since have stayed clear of them.
I guess this means it depend on the field of programming then. In some fields they are used, in others they are never used.
Sweden also has a legal extradition agreement with the US
Nyyaah, depends on the crime. In general European countries do not extradite to the US, because they US openly conducts torture and has the death sentence. Specifically people are only extradited to the US under terms that they will not be submitted to either of those -- Not unlike the kind of agreement that was attempted to be made with Sweden (And which I expect will be actually made now, because Sweden needs to internally demonstrate they are were not going to extradite him in the first place)
More likely you're not actually Dave Schroeder, or you're being honest and stupid. Real information warfare wouldn't have links to a sight claiming to do so.
If the guys that attacked Anonymous are any guide, this level of incompetence is exactly what I would expect of anyone involved in official information warfare. Nothing anywhere near the level of sophistication of something as simple as Fox News has, and they are pretty honest and stupid about it.
Ignoring RTTI is fine, but forbidding exceptions requires a dangerous sort of doublethink. The language itself, as well as the STL, is defined to generate and use exceptions. By ignoring their existence, you banish yourself to a nonstandard purgatory.
No you don't. Forbidding exception is de-facto standard for C++ programmers, exceptions are an unsafe feature that integrates extremely poorly with most programming paradigms C++ is used for, every good C++ programmers disable them. If you enable exceptions, then you are using C++ in a way no one but programming students does, and could end up in all kind of bugs by doing untested things.
GCC as a compiler and a community seems to really be moving, it is probably due to the competition from LLVM, but atleast for now, GCC is still the better compiler, and I wish them the best of luck.
Yeah, that always freaks me out. GCC backends atleast are configured using LISP wrapped in C. I hope this is one of the things they clean-up, though, it won't be straight forward. LISP is quite powerful and fast as a machine language, it just happens to be unparsable by humans.
Re:too bad GCC is not relevant anymore thanks to L
on
GCC Switches From C to C++
·
· Score: 4, Informative
This is the first I've heard of anything like this. Did I miss something? Is GCC now GPLv3, and does that mean you can't use it to build non-GPL programs?
No, it means when you go in and add extra functions to GCC that those would have to be GPLv3 as well, at least if you want to distribute them.
It has NO effect on what the use of the application. In fact that is has no effect on the end user is one of the topmost clause of the GPLs.
LOL. Well there were a few improvements by making the suite into active x objects, so that you could place one item into another. (for example an excel table in a word document and still have it editable in the excel style.)
Koffice has been using Kparts for a decade, I can only assume calligra hasn't reverted that.
It's a myth that the US still has the highest social mobility. It used to, but it stalled. Europe is now the better place to make your ambitions come true, unless you are already rich and you want to become a millionaire. The US is still the millionaire's paradise.
I am not sure if it was ever true. The highest social mobility in world is btw in the Scandinavian countries by a wide margin. The US is only good if your already is rich and want to stay rich, places like Scandinavia are places you can make a career for yourself, and end up better than where you started.
You might have to double-check on that, it is Googles primary source of income. Of course they only sell aggregated information, to protect your privacy, but selling what they can out of your information is their business, they are just doing it as nicely as they can.
What's funny they announced they would give feature updates to WP7 at the same time they announced they couldn't update WP7-hardware to WP8, somehow you end parsing 'will receive updates that will work on their hardware' as 'will not receive updates'. Now, is that a fault of MS, or a fault of your reading comprehension?
Well, I think the potential negative impact definitely has to be taken into consideration. What will the companies in question do with the data that could cause harm to me?
As the summary meantions: Sell it?
Seriously there is nothing about the free market that protects you from having your data end up in the hands of the very same people you think somehow magicaly doesn't have access to it rigth now. NOTHING!
holding hands?
happy happy
That is nice. I a saw a review linked in a different post where they complained about the shiny 1366x768 screen.
I tried to buy a ThinkPad Edge last year, and had to give up because the latest models only came with extremely reflective 1366x768 screens. Let us hope Lenovo has learned the lesson then.
No, unfortunately KDE is not that good out box either. It takes a bit of work to run multiple versions of KDE-runtime, but of course it is possible, that is how you develop for it and test it while still running the latest stable KDE on your desktop.
That doesn't explain the "DLC" that is now commonly shipped with the games to minimize the downloading process.
Neither is a 1366x768 glare screen. It is outright offensive.
It is TOO shiny, please for the love of god, make one with a proper matte screen.
The comment is not necessarily about you specifically. You have already answered for yourself elsewhere, and explained what you do about information warfare is not about propaganda but encryption (though after I wrote my comment), but I stand by my assessment of the general competence of misinformation mercenaries, though that apparently doesn't relate to you.
There are other types of synchronization than just Mutexes, as I said, except Mutexes it is not trivially to do exception safe coding for synchronization. What the 'revert' or 'safe' state is, can vary from function to function, and you need to handle the cases explicitly, which is the opposite of what exceptions does. Exceptions makes the assumption that the code-path doesn't matter, and everything has a trivial way to unstack the state, this is rarely the case, and you are just adding more and more increasingly complex workarounds (unstacking pointers, transactions, mutexes) to make an obviously broken feature, almost work.
Point allocation is only one problem, other much bigger issues are database transactions, data safety and especially thread synchronization. You can do smart-pointer like stuff to make sure the database transactions are rolled back or commited when the function is exited on irregular codepaths, but with the exception of very simply mutexes, the same can not be done for thread synchronization.
It is much simpler to just disable exceptions, and deal with your errors the right way, by handling them.
Well, in 12 years of C++ programming, I have never seen a project where exceptions were NOT disabled. Of course 10 years ago, they were generally too poorly supported and slow, but still all projects I have encountered since have stayed clear of them.
I guess this means it depend on the field of programming then. In some fields they are used, in others they are never used.
Nyyaah, depends on the crime. In general European countries do not extradite to the US, because they US openly conducts torture and has the death sentence. Specifically people are only extradited to the US under terms that they will not be submitted to either of those -- Not unlike the kind of agreement that was attempted to be made with Sweden (And which I expect will be actually made now, because Sweden needs to internally demonstrate they are were not going to extradite him in the first place)
If the guys that attacked Anonymous are any guide, this level of incompetence is exactly what I would expect of anyone involved in official information warfare. Nothing anywhere near the level of sophistication of something as simple as Fox News has, and they are pretty honest and stupid about it.
It was outside the US.
Okay okay, you deserve it:
You were right.
Congratulations! (Too bad I can't mod it any more.)
No you don't. Forbidding exception is de-facto standard for C++ programmers, exceptions are an unsafe feature that integrates extremely poorly with most programming paradigms C++ is used for, every good C++ programmers disable them. If you enable exceptions, then you are using C++ in a way no one but programming students does, and could end up in all kind of bugs by doing untested things.
GCC as a compiler and a community seems to really be moving, it is probably due to the competition from LLVM, but atleast for now, GCC is still the better compiler, and I wish them the best of luck.
Good compilers benefits everybody!
Yeah, that always freaks me out. GCC backends atleast are configured using LISP wrapped in C. I hope this is one of the things they clean-up, though, it won't be straight forward. LISP is quite powerful and fast as a machine language, it just happens to be unparsable by humans.
No, it means when you go in and add extra functions to GCC that those would have to be GPLv3 as well, at least if you want to distribute them.
It has NO effect on what the use of the application. In fact that is has no effect on the end user is one of the topmost clause of the GPLs.
For a compiler? What does a distribution license have to do with a compiler?
You seem to be treating the GPL like cuties.. Who does believes in GPL cuties? Apple, FreeBSD, 6 year olds, anybody else?
Koffice has been using Kparts for a decade, I can only assume calligra hasn't reverted that.
I am broadcasting my thoughts right now. I own them forever, read them and you shall be a criminal!
It doesn't just seem like it, it IS not only unsupportable to point of insanity, in further yet, it is well in the area of insanity.
I am not sure if it was ever true. The highest social mobility in world is btw in the Scandinavian countries by a wide margin. The US is only good if your already is rich and want to stay rich, places like Scandinavia are places you can make a career for yourself, and end up better than where you started.
You might have to double-check on that, it is Googles primary source of income. Of course they only sell aggregated information, to protect your privacy, but selling what they can out of your information is their business, they are just doing it as nicely as they can.
What's funny they announced they would give feature updates to WP7 at the same time they announced they couldn't update WP7-hardware to WP8, somehow you end parsing 'will receive updates that will work on their hardware' as 'will not receive updates'. Now, is that a fault of MS, or a fault of your reading comprehension?
As the summary meantions: Sell it?
Seriously there is nothing about the free market that protects you from having your data end up in the hands of the very same people you think somehow magicaly doesn't have access to it rigth now. NOTHING!