* Posts by Das Schaf

4 posts • joined 30 Oct 2017

Fairytale for 2019: GNOME to battle a patent troll in court

Das Schaf

Re: I have said it before

Unfortunately that scheme disadvantages small patent holders against large corporation seeking to exploit their technology. The large corp can make billions infringing, then pay back thousands to the patent holder when they are held to account.

Don't make us pay compensation for employee data breach, Morrisons begs UK court

Das Schaf

Re: English Idio.....

In my 50 years of speaking and listening to British English in various parts of the country, I have never heard the word Compo used in any other context but as an abbreviation for Compensation.

Amazon: Intel Meltdown patch will slow down your AWS EC2 server

Das Schaf

Re: maybe it's time to re-consider server-side inefficiency

@Destroy All Monsters

Maybe he is performing dynamic memory allocation in C++11 using smart pointers, preferably unique_ptr<>, so that explicit calls to "free" are not required and object lifetime management is achieved. C++ isn't Java and the class designs may well be very different depending on idioms used e.g. PIMPL idiom is sometimes useful in C++ where binary compatibility between versions is a requirement, not applicable in a Java implementation.

You're designing an internet fridge. Should you go for fat HTML or a Qt-pie for your UI?

Das Schaf

Re: Rip the Q key off their keyboards

Not a fan of Qt here.

Use it once and it starts to spreads its cancerous tendrils everywhere. Smart pointers which aren't (no exception guarantees and no unique_ptr implementation). You can't use proper STL smart pointers like unique_ptr<> because the Qt container classes require anything in them to have an accessible copy constructor (due to copy-on-write "optimisation"). Copy-on-write optimisation is an anti-pattern in multi-threaded environments, in fact the standard library string class is forbidden from being implemented using C-O-W. Guess what QString uses .....

Other GUI frameworks don't restrict your use of proper smart pointers and container classes, using optimisations which aren't in most circumstances.

If you keep your GUI code well separated from the rest of your system, using a MVC or similar architecture, using Qt in the View part is OK I suppose. Don't let it near any critical processing though!


Biting the hand that feeds IT © 1998–2019