Please create an account to participate in the Slashdot moderation system


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re:Why doubt something better would exist? (Score 1) 154

by darkHanzz (#45925669) Attached to: Oracle Promises Patches Next Week For 36 Exploits In Latest Java

WHERE did you get the idea that C++ is more immune to memory leaks or buffer overflows than C? C++ adds to the basic C memory management services and memory organization, but it still retains the original C ones. And adds an additional way to leak memory - undisposed objects.

Probably from experience: Consistent use of stl memory classes (shared_ptr and unique_ptr) and containers (mostly std::vector) make it very hard to shoot yourself in the foot. Adhere to "Raw pointers don't transfer livetime from function to function" if you use raw pointers. These things are really easily spotted by code-review.

Comment: Re:Backwardness of KDE continues (Score 2) 51

by darkHanzz (#45899809) Attached to: KDE Releases Frameworks 5 Tech Preview

and then provide native code layer to provide an interface for computational demanding stuff.

Well, they are moving in that direction with QML. For many apps, a native UI makes perfect sense. Not only if the UI is very demanding, but also when the UI is very simple: staying in one programming language keeps things simple.

Comment: Re:"So who needs native code now?" (Score 1) 289

by darkHanzz (#45781063) Attached to: Asm.js Gets Faster

Indeed he didn't. The whole thread was about native vs. non-native code, where C is just an example of native code.

C++ is another example, closely related to C, with all the relevant properties. for example, you don't pay (performance) for abstractions/features you don't use. (exceptions, garbage collection, virtual function calls/inheritance)

Comment: Re:The mess at the bottom (Score 1) 214

by darkHanzz (#44528971) Attached to: Back To 'The Future of Programming'

The best bet might be if China decides they need to be fully independant from the 'Capitalist West' and design their own architecture

I'm not so sure if you have ever seen the Chinese way of designing; fiddle with it until it seems to work. Search for Huawei's security problems and you'll get the drift. Hardware design is really not done better.

Comment: Re:Huh? (Score 4, Informative) 371

by darkHanzz (#44456693) Attached to: Using Java In Low Latency Environments
Use RAII consistently, and use containers (from stl or otherwise) which have asserts() on bounds-checking. Bonus points for a tiny unit-test (which can therefore run at the end of every compilation). You'll be amazed at how stable, maintainable, easy to debug and performant your code will be.
Do the hardcore pointer handling only where the profiler tells you that it matters and there's no way java even gets close in performance

If you think nobody cares if you're alive, try missing a couple of car payments. -- Earl Wilson