I guess we can expect that source code repositories will be scanned and processed. And, for code written by multiple authors, the modified code (from commits) will be scanned and indexed as well.

But, I bet they will never figure out who writes the malware recently attributed to the three letter agencies. They should, however, be able to figure out which agency writes the stuff if they get a copy of the source code or maybe even from decompiling the binary.

Additionally, if written from .NET, the CLR code can be reflected back to VB, C# or any other .NET language to retrieve the source code.

Yup. Changing a bios required physically taking the old one out and popping in a new eprom. At 17, I doubt the NSA cared less about my original IBM PC that came with a cassette tape drive (I couldn't afford single sided floppy drives until a little later..let alone a hard drive until I was 18.

++i is not the same as 1++.

I have been working in Object Pascal, and C, and Obj-C and Java and numerous other languages for many years. I still prefer Object Pascal since I have been working with it since 1995. It's my preferred language for my own development. But, at work, I use what is most appropriate to meet our client's needs. Delphi has yet to be the correct choice. Our clients are either, PHP/Drupal, JAVA or C#/.net shops. Delphi doesn't have a place in web app development.

There was an argument earlier about why do we need another language, another tool chain etc. Hmmm. I seem to recall that Pascal and Object Pascal were around long before most of today's "modern" languages. I think we have the right to ask the same question of those languages.

The biggest argument I hear against PASCAL and Object Pascal is it's verboseness. While I would agree that all the begin/end blocks can seem annoying at times, nobody I know mistakes begin/end keywords for variables. And, single line statements don't need a begin/end block. I have heard arguments about the excessive use of white-space or the need for a semi-colon. Giving whitespace significance in code is an awful idea. Nothing could possible go wrong there could it?

The primary reason the language has suffered is because of what transpired at Borland/Inprise/Embarcadero after Delphi 7 was released. Quality suffered at the expense of making profit and developers migrated to cheaper or free solutions. I can't say I necessarily blame them - the product IS expensive. The migration of developers away resulted in a significant downsizing of the tool and component vendor community as well. At the same time, OSS became very popular. Still, Delphi continues to evolve. The tool permits rapid development of Windows/Mac and, on the mobile side, iOS/Android is a true cross-platform manner. While some might bitch about the FireMonkey framework, it does get the job done for cross-platform UXs. There will always be things that it can't readily do such as accessing certain frameworks out of the box. But, many frameworks have been translated. You can still access Java code on Android once you run the bridging tool and then adding the bridge units. Or, you could still write native iOS apps. But, if I am going that route, I would use the native tool chain rather than translate the headers (that's the vendor's job). That's just me.

I don't know if Delphi will survive. But, to speak against it without knowing what it can do is ignorant. Ignoring other languages and tools just because is just as ignorant as well.

I grew up knowing RadioShack in its glory. It was one of the few places where I could run out and buy parts to build some new gadget or circuit. And, it was one of the few places where you could not only test tubes from your TV, but replace them...yeah...when YOU could repair your own TV. And, it was fun.

I also had my first, unofficial job demonstrating the TRS-80 computer. They would let me come in and write software for it. I managed my paper route on their computers. The selling point, customers would come in and see me working. They'd ask what I was doing and I would tell them. Seeing how it ran my business contributed to quite a few sales for the local RS.

Yup....first HeathKit disappeared, RadioShack lost their way. Now, they too, will soon be gone....just like me.

But, if the business is subject to regulation and you fail to let the regulators in....well, be prepared for heavy fines and possible jail sentences.

As a company, their valuation is based entirely on speculation as they have little capital assets. Hindering those that hold legislative and regulatory powers over you is liable to result in your valuation disappearing overnight.

Mod poster up! Of course, that's the Holy Grail of mobile apps.

What ever happened to the "we'll release when it's ready" approach to product development?

Oh...that's right...stockholders and their never ending quest for higher stock prices and profits and using customers as their QA department to cut costs.

But, it's not limited to just public companies. My favorite development environment (which I won't name as it's not relevant), went down the tubes for the longest time. It took a near-death experience for them to realize that they needed to get back to the "ship it when it's ready" mentality. They still have issues, but they are improving. Just wish the cost of the next major "upgrade" wouldn't cost me another vital organ donation.

As a mobile developer and architect (primarily iOS now), I hate to say that there is much truth in that statement. In 2010, I started developing apps for both myself and corporate. The trend, which became very apparent in the early days, is that even if you have a great idea, you are up against several roadblocks. At the very least, an app/applet/program on a mobile device is supposed to do one thing and do it really well.

In the private, consumer world:
1) You have to set a price point that people will pay. That's typically either free, $0.99 or $1.99. And, it's why some developers people incorporate ads into their apps in the hopes of eeking out a living.

2) Then, you have to get it noticed. For some reason, insanely stupid or novel apps make it on the chart. The apps that provide utility never rank high so they become to find.

3) Then, you have have the copy-cats. They say copying is the finest form of flattery. Great - if it gets one a date with a really hot member of your preferred sexual preference. But, don't cut into my profits with that bullshit because you can't come up with an original idea of your own and then resell mine at a lower cost or give it away.

4) Lastly, there is the app lifecycle and planned obsolesce. You app has a limited lifetime. Any slowness during loading or awkwardness in its UI and it will, likely, meet the squiggly icon of doom rather quickly.

Platform of choice? Android and iOS.

The Commercial world is where the money is to be made. Large corporations have products they want to sell and marketing/sales folks who keep coming up with ways to get their products out there. They also have the money to fund development of limited purpose apps. Most still prefer to use web-based apps as well as they understand the web platform and how it can get their message across and it tends to be cheaper. Done with it? Just turn it off. Users aren't out any money. Typically, doing so is no harm no foul. Their platform of choice? iOS. Android is not making a dent in our industry (Pharma and Health) BECAUSE it is so open.

So, where does that leave us developers? Well, the market keeps evolving. First we had the older BREW and SYMBIAN phones (what a PITA). Then, we got smartphones followed by tablets. Now, through emerging tech, we have wearable devices. That will be the next market - finding the best ways to marry wearable tech with mobile, tablet and desktop technology to give the user something they find useful and affords the chance of making money. People might not like the ApplePhone or Pebble or whatever. But, it's coming.

Case in point - My youngest son, now 15, said he wanted an AppleWatch. Why? He finds reaching into his pocket to see the time (he doesn't walk around with it in his hand all the time, oblivious to the world around him as many teenagers do). Still, he wants something that does more than just tell the time (he's a competitive swimmer...not that the AppleWatch will help him there as it's not, supposedly, waterproof).

I still think a good online service providing utility via the web AND offering a useful web-service API is the way to go. I can build a mobile, tablet or tethered device to it when I am ready and think the market is ready and willing to pay for it.

WTF? Railroad Super Conductors get preferential treatment over less than stellar ones? What lobbying group managed to get Congress to pass this?

Oh...wait...

I could not agree more. I cut my teeth on Dr. Dobb's starting in high school during the early 80's. Looked forward each month to receiving my copy in the mail and then, digesting it's contents from cover to cover. While some of the discussions and techniques covered didn't always have immediate impact, I have found that, over the years, that much of the older content was actually still relevant today.

This view of "It isn't relevant to me today" will come, in time, to bit developers. The seemingly limited discussions which involved older tech, has opened the doors for the current generation.

Sadly, when they went entirely online, they lost their relevance and I saw limited value to the once vibrant tech journal known as Dr. Dobb's.

Goodbye, old friend.

Bumming...I invented the Write Only Drive while at college. Now, it looks like I infringed on the Patent. Mine, however, used the Pauli-Exclusion and Heisenberg Uncertainty Principles to store information on each atom. Problem was, we hadn't figured out how to get the data back out (it was just a s SCSI cable going into a black box. I think we just needed Heisenberg Compensators.

Even though we published our "Announcement" it during our April's Fools edition of our Newsletter, we received one call from a company wanting to commercially build it. We had to explain it was a joke.

Sounds like a really bad porn movie.

We've been capable of doing this since 1980's. Even the early Xerox word processors had this orientation. The author must be a hipster.

Is often "Have you ever been arrested?" and "Have you ever been convicted of a felony?".

If you answer "Yes", the next question is often to describe why you were arrested and whether you were convicted.

If it's a juvie record, you might not have to answer.

When and if you are hired, they are putting a lot of trust in the hire. For positions that demand that level of trust, a hire is unlikely. For others positions, they might hire and you'll have to prove yourself as not being a risk. Evenually, if you stay clean, most will forget your earlier transgressions. Keep your performance evaluation as they will help you in the future if hired.

Good luck!

Now, let's bring that logic here to the US.