I was using triple display back in 1990 on Mac II 68040 machines.
I can't believe it took so long to get to 2 monitors, and 3 well, only bother if you're a graphic artist and need loads of screen real estate, plus a TV output so you can drag media across to do a quick preview to get colours, etc looking right.
One comment was surround "flight sims". I think a high res VR headset with direction tracking would be much nicer for the application. That way you could look behind you better.
Anyway, it's been around for years, just another example of the fact that no new technology is really new anymore.
I'm a little stunned at the fact that you think C++ is inherently less stable and crashable than other languages.
True in C++ there's generally more you need to do than in other languages, but frankly, my first C# application (with garbage collection, etc) had a major memory leak. I only picked it up because I happened to be looking at the task manager and noticed the memory usage going up, not because things were unstable.
I was calling.Dispose on an object and just assigning null didn't help for some reason.
I also get errors popping up all the time and need to wrap code in try catch blocks.
C++ also has this construct so my advice to you is make as many mistakes as possible and get used to spotting where code is likely to be vulnerable and take action to avoid crashing.
Employing patterns and decoupling can prevent individual modules from stopping entirely, but it's not going to stop the individual modules from being unstable.
You still need to do explicit error checking whenever you write code, regardless of the language or patterns you decide to use.
If you want to write platform independent code the use an API which has the same goal.
For GUI apps use Qt or GTK, and for 3d games use Ogre3d.
But using these won't eliminate the need to follow sound error handling practices.
A programming language will always give YOU the option of how things should be handled in the event of an exception.
"Given that the MPAA's intent isn't financial gain..."
Well, you know, I find it strange that then that even doing a copy for backup purposes is considered bad.
How about dvd rips I might do to post via usenet or whatever (hypothectically speaking of course). That wouldn't be for for financial gain, yet it's illegal.
That quote would basically condone all file shared movies as long as you make no money from their distribution.
Re:No language that I like better
on
What is Perl 6?
·
· Score: 1
Excellent point. I'm just finishing off a uni degree and was always gobsmacked as to how everyone thought OOP was the bees knees. "It promotes REUSE fo code, encapsulation and data hiding". As with yourself I could never understand why students were taught that C was defficient in this area. A.o is called an "object" file after all.
Yeah it's not discrete classes which can be inherited, but you can supply a.h and a.o (or.a) library to a customer and they can reuse the code in whatever projects they wish. But admittedly it does become a little messy if you want to override a function, and overloading rocks my socks.
Frankly use whatever get the job done in the best way.
Slashdot Mirror
I was using triple display back in 1990 on Mac II 68040 machines.
I can't believe it took so long to get to 2 monitors, and 3 well, only bother if you're a graphic artist and need loads of screen real estate, plus a TV output so you can drag media across to do a quick preview to get colours, etc looking right.
One comment was surround "flight sims". I think a high res VR headset with direction tracking would be much nicer for the application. That way you could look behind you better.
Anyway, it's been around for years, just another example of the fact that no new technology is really new anymore.
I'm a little stunned at the fact that you think C++ is inherently less stable and crashable than other languages. True in C++ there's generally more you need to do than in other languages, but frankly, my first C# application (with garbage collection, etc) had a major memory leak. I only picked it up because I happened to be looking at the task manager and noticed the memory usage going up, not because things were unstable. I was calling .Dispose on an object and just assigning null didn't help for some reason.
I also get errors popping up all the time and need to wrap code in try catch blocks.
C++ also has this construct so my advice to you is make as many mistakes as possible and get used to spotting where code is likely to be vulnerable and take action to avoid crashing.
Employing patterns and decoupling can prevent individual modules from stopping entirely, but it's not going to stop the individual modules from being unstable.
You still need to do explicit error checking whenever you write code, regardless of the language or patterns you decide to use.
If you want to write platform independent code the use an API which has the same goal.
For GUI apps use Qt or GTK, and for 3d games use Ogre3d.
But using these won't eliminate the need to follow sound error handling practices.
A programming language will always give YOU the option of how things should be handled in the event of an exception.
"Given that the MPAA's intent isn't financial gain..." Well, you know, I find it strange that then that even doing a copy for backup purposes is considered bad. How about dvd rips I might do to post via usenet or whatever (hypothectically speaking of course). That wouldn't be for for financial gain, yet it's illegal. That quote would basically condone all file shared movies as long as you make no money from their distribution.
Excellent point. .o is called an "object" file after all.
.h and a .o (or .a) library to a customer and they can reuse the code in whatever projects they wish.
I'm just finishing off a uni degree and was always gobsmacked as to how everyone thought OOP was the bees knees.
"It promotes REUSE fo code, encapsulation and data hiding".
As with yourself I could never understand why students were taught that C was defficient in this area. A
Yeah it's not discrete classes which can be inherited, but you can supply a
But admittedly it does become a little messy if you want to override a function, and overloading rocks my socks.
Frankly use whatever get the job done in the best way.