and a lever-arm on the parachute rig to angle the capsule on the descent (not sure why, I guess for a better landing).
Wild guess: to make splashdown less impactful by avoiding a "belly flop" and hitting the water edge-first.
As always, troubleshooting capacity comes, primarily, from personality type, not from training. Training can help, but it can't substitute.
When I said "If you were doing the same thing in C/C++" I meant hanging onto a pointer after freeing the memory. Which you can do in both languages and which will cause you no end of problems later on.
Whoosh - he was talking about how you could allocate objects on the stack and have them be released automatically as you exit the scope. Java always allocates objects from the heap, but the reference can be on the stack and when you exit the scope the reference disappears and the object is now eligible for garbage collection.
Greyfox doesn't understand how garbage collection works in Java is what it comes down to.
Yeah, it only took him 20 years to figure out that he needed source code management.
You just create objects on the stack, let them handle their memory management internally and automatically clean up when they go out of scope.
You mean like this in Java?
public void myfunc()
{
MyObject localObj = new MyObject();
}
When you exit the scope it's eligible for garbage collection. Unless you hang onto a reference it's not going to hang around. If you're leaking memory or resources in Java you're hanging on to them somewhere. If you were doing the same thing in C/C++ and you free the object while keeping the pointer around you're just creating a Heisenbug.
The fact that *EVERY* line of kernel code has to deal with those kind of issues is a byproduct of the monolithic kernel design, not what the code itself is doing.
I started off as a Unix kernel programmer in the late-80's, did a lot of stuff on supercomputers and went to Apple to work on Copland (micro-kernel). I/O subsystems can make good use of OO abstractions. OS X's IO subsystem is written in C++.
It's really time to look at microkernels again. There are some performance issues, but many of those will get smoothed out as they're hit and engineered around.
the next giant leap in ubiquitous mass surveillance.
I just can't wait for all the devices that surround me to snitch on me and report all my life habits to their corporate or state masters 24/7...
A surprising number of sites use CloudFlare. The trouble with CloudFlare is, if you want to stay anonymous on the internet using Tor, you're SOL, as they serve you captchas every 3 pages when they see a connection coming from a Tor exit node.
So essentially, if you're a Tor user, CloudFlare:
- Renders a sizeable portion of the internet unusuable for you
- Makes money on your back by making you solve captcha, and turning you into a human OCR.
CloudFlare and Google (which also serve captchas to Tor users, only fewer exit nodes are concerned) are quickly making Tor unusable, which must make the NSA wet their pants.
And btw, I notice that, with 99 comments in, nobody else has bothered to actually provide you with the links to the official Apple iOS developers or Android developers docs, api, tools, etc. I at least showed enough respect for you to expect you to benefit from them. Was I wrong? Only time will tell.
You know, if he can't use Google he's really bad off.
Back in 1990 if you were an experienced C developer and hadn't looked seriously at OO languages it was understandable. In 2014, if you haven't at least dabbled with C++, Java or C# I think it shows a definite unwillingness to learn. So that's why the OP is getting "condescending" answers like "just hire someone"
HA HA HA HA HA HA HA
You don't know Apple, or iOS developers. Dominant over ObjC within two years (and by the end of next year that prediction will probably seem ridiculously conservative).
Oh really? Drink some more koolaid. Remember how long it took to lay Carbon to rest. And the Cocoa APIs are still incomplete in many areas. Then take a look back at all the new programming languages and frameworks Apple has introduced over the years and then shot in the head. Dylan? OpenDoc?
I'd say it's 50/50 whether or not Swift will get enough traction to continue on.
If you've spent this long avoiding modern languages why start now? If you're not interested in object oriented design you're just going to spend your whole time cussing at the frameworks. Just hire a contractor.
That's my question. I've wound up with it installed plenty of times because it's the default on too many distributions but use?
At least with terminals you could arrange them how you like. Ah, the joys of 3 VT100s on your desk.
I'm sure your neighbors appreciate the fact that you're a self absorbed twat.
Any circuit design must contain at least one part which is obsolete, two parts which are unobtainable, and three parts which are still under development.
