boost_
and thank god they can't, at least not for now. i can still say any bullshit i want on the internet, as is my right.
from your own article:
>Non-discrimination on the basis of gender identity and expression may very well be interpreted by the courts in the future to include the right to be identified by a person’s self identified pronoun
nice precedent
>Policy on Preventing Discrimination Because of Gender Identity and Expression states that gender harassment should include “ Refusing to refer to a person by their self-identified name and proper personal pronoun”. In other words, pronoun misuse may become actionable, though the Human Rights Tribunals and courts. And the remedies? Monetary damages, non-financial remedies (for example, ceasing the discriminatory practice or reinstatement to job) and public interest remedies (for example, changing hiring practices or developing non-discriminatory policies and procedures). Jail time is not one of them.
oh ok, no jail time, but i'm forced to hire someone that identifies as an attack helicopter, great!
>So what does this mean for pronoun misuse? Well, refusing to use a person’s self identified pronoun is not going to be considered advocating genocide – unless the refusal to use the pronouns was accompanied by actually advocating genocide against trans and gender non-binary folks.
so its fine unless i promote genocide, kinda makes sense but its still a slippery slope imo
>Similarly, it’s hard to see the refusal to use the appropriate pronoun –without something else – rising to the threshold of hate speech. Hate speech laws in Canada have only been used- and only can be used – against extreme forms of speech – explicitly and extreme forms of homophobic, anti-Semitic or racist speech.
so pronoun misuse is still legal, unless it gets to "extreme", whatever that means. and who decides what "extreme" is?
>Moreover, prosecution needs the approval of the Attorney General.
so in the end the attorney general decides..
looks great btw!
is this reddit?
but i agree, for many people C++ is a no-no, even though Qt C++ is pretty straightforward with all the helpers they provide (like the parent-child memory management).
most people hear Qt and immediately think about heavy desktop applications. its a shame really, Qt is pretty awesome atm for mobile development.
just grow a skin, Linus can say and do whatever he wants about his project (linux). don’t like it? don’t help it then.
seriously kids these days get offended by everything..
this week is Indonesia fires, last week was china insane pollution from gadget manufacturing. next week will be something else. we wont ever be free while all the above exists..
and now they down vote me.. lol whatever guys go crazy!
i mean, we all saw the videos from the announcement, and the "live" demos. and that was just pure lies no matter how you want to paint them.
also even if they didn't lie, don't we need the dev kit to have the same full capabilities as the final product? would you acquire an early dev kit for some new console, only to find out that it has less ram, gpu and/or cpu than the final product? how can we actually test it fully?
nice one hackernews, downvoting the most important question in this thread...
i guess this is full of MS fanboys that don't mind being scammed out of 3k dollars..
they didn’t really "fix" it, instead they added a method called std::vector<T>::shrink_to_fit() which i'll admit its not the most elegant way, but it works.
what it does is, it resizes the capacity() to be the same as the size(), deallocating all the extra memory.
that’s probably because most of the AAA games you've seen used old in-house libraries that replaced the STL, since the earlier STL implementations weren't the best.
STL is not 100% the way to go every time, but i would say that nowadays unless there’s a really specific implementation need, it should be used at least 90% of the times, even if only for base for new data structures to be built on top of.
- "Stack allocations are discouraged because they can introduce non-deterministic bugs (stack overflow depending on the call sequence which can't be predicted in advance)."
i really don’t understand this problem, you can change the stack size on every compiler and every OS either on compile time or runtime. also, are you writing functions or methods with 10k LoC?
stack allocations are actually easier to follow than heap, its not even close..
- "Its nearly impossible to write a game without dynamic allocations. Most of the time they'll override the new/delete operators"
yes i agree, dynamic allocations are still really needed, and not only for games.
But, overriding new / delete operators in C++ when you can set custom allocators and deallocators for both unique_ptr and shared_ptr? once again i think that’s more of a legacy code update problem than an actually implementation need problem.
- "and on that level they work almost exclusively on void*."
only if they want to, that’s what templates (and again the STL) are here for.
I’m not saying pure C++11/14 features are the only way to go, i just think that at least in new code it should take priority, the cleanness and robustness it provides its just too good to ignore.
take for example a lot of C++ samples that that guy shows in the video, he calls it "C++11" and uses code like:
- void* data = NULL;
- no STL
- no stack allocations
- only dynamic memory allocation using new and delete
i mean come on..
not really complaining, since it runs out of the box in wine.
IMO its better than the Bjarne Stroustrup book (which i've read too), but any of the two is fine to learn modern C++ features.
#include <iostream>
class Int
{
private:
int _value;
public:
Int(int value) : _value(value) {}
Int operator + (const Int& b){ return Int(++_value + b._value); }
friend std::ostream& operator << (std::ostream& out, const Int& value){ out << value._value; return out; }
};
int main(int argc, char** argv)
{
std::cout << Int(2) + Int(2) << std::endl;
return 0;
}
output: 5so it's like saying "using our 3d game engine is easier to build games than pure opengl", which makes sense because it was made for it. now when they compare ATF with another toolset like it build in Qt then it will be a fair comparison.
the idea i got from the video is that mantle is a replacement for opengl and directx for "performance reasons".
i still agree with you though, this is just pure marketing to make people develop/buy AMD GPUs instead of something else.