Home: Tag : J2EE

Businessmen and entrepreneurs (your customers) who hire independent developers (you) may need more impressive examples of what the LAMP solution stack can do besides the WordPress example we cited last time. After all, blogs are great for consultants or service businesses that must take on an air of authority. But surely, even a small businessman will appreciate what has been done with Wikipedia, arguably the best-known non-commercial site for some years now.

The earnest brother-developers of mine at HyTech Professionals could only agree enthusiastically with the even dozen advantages of the LAMP solution stack I run in the last post. Clearly, cost savings is not even the major advantage of using the LAMP combo.

Other than the fact that there is no dearth of developers who learn enough LAMP to competently put together a Web application, herewith an even dozen of enduring advantages to the LAMP solution stack: 1. Installation is easy because most Linux distro’s bundle all the other LAMP components.

In our last post, we identified the starting line-up for LAMP, argued that an open source stack inherently reduces investment risk for a start-up and well, the obvious benefit that all the components are dirt-cheap to acquire. Today, let’s delve into variations and why you still save money whatever you do.

As promised, we switch today to the open-source solution stack LAMP. What the Windows Server-Internet Information Services-Microsoft SQL Server-ASP.NET stack is for the Windows environment, the open-source equivalent to cobble together a Web application is LAMP.

Continuing with our brief overview of Ruby on Rails as drastically simplified, elegant, and stable platform for agile Web engineering, we take the word of some impressively-experienced RoR developers up in Nashua, NH, at HyTech Professionals that it is by no means the ONE, the “silver bullet” that will replace all other Web 2.0 frameworks out there. Still, the practiced applications architects insist

In yesterday’s post, I related how Ruby on Rails developers, the intense HyTech Professionals teams for instance, push the envelope for rich Web 2.0 applications by keeping their eye on five key RoR principles: trimmer code, segregation by sub-frameworks, not having to repeat one’s self, minimal configuration requirements, and instant feedback just by loading in a browser.

Today’s applications developer aiming for the next scintillating Web 2.0 site is spoiled for choice. How well, you might wonder, does Ruby on Rails live up to its promise to simplify development tasks while crafting rich visitor experiences?

In the last four years, we have seen how Ruby on Rails (RoR) built on, and accelerated the wider acceptance of, the object-oriented Ruby language. Consequently, the Ruby/RoR combo has become a workhorse of such independent software providers as Nashua (NH)-based HyTech Professionals.

The never-ending desire for riveting Web sites that “pull eyeballs”, lengthen stay and induce return visits has, since 2004, complicated the life of Web application engineers. Enriching a page with Flash, embedded video, visitor talkback, and self-serve communication channels means developer teams need varied expertise in Ajax, Web services and allied technological tools.