It seems like new Web language options appear every time you blink. The one you choose can make or break your Web development project, and this article is going to guide you toward the right choice.
Written by Joe Pluta
It's getting difficult out there. We've got more Web languages than we know what to do with, and we've heard no end of the pros and cons of each. People point out the sheer number of programmers for one language or the huge base of applications for the other. Some pundits appeal to purity of architecture; others swear by ease of use. The arguments are endless and opinionated and frankly pretty hard to objectively judge one way or the other.
There are varying payoff horizons for employing such a tool, ranging from short- to long-term benefits.
Written by David Brault
Editor's note: This article introduces the LANSA white paper "System i Modernization Survival Guide," which is available free at the MC White Paper Center.
Many organizations were caught off guard by software development's rapid evolution over the last decade. The evolution had many catalysts: the mass adoption of the Internet; requirements for better visibility into accounting practices; company acquisitions and mergers; and a host of government, industry, and technology mandates. For IT departments to keep up with the rapid change in technology, they purchased tactical solutions that combated business requirements as they surfaced. Now, a decade later, they struggle to manage their technology collection, and it's making them counter-productive.
Over the years I've published a lot on security best practices. In fact, our SkyView Risk Assessor product is based on all of those recommendations. But today I feel a bit contrarian so I've decided to post a few "worst practices." And like my "best practices" these are based on my years of experience in the security world.
Worst practice #1 - when asked how all users ended up with *ALLOBJ special authority, the answer was, "I didn't want to take calls in the middle of the night - so I just gave everyone *ALLOBJ."
Worst practice #2 - No auditing. No joblogs. History log cleared. The reason - lack of storage. Also meant that there was a significant lack of evidence when we were called in to investigate a breach that had occurred on their network!