On 28/04/2008, at 8:29 AM, badeguruji wrote:

Hello,

I plan to develop a money management app for personal use on OpenBSD. Since I am not big on any backend /prog.language I have decided to ask the experts, what should i choose. Based on the consensus and depth of a response, I will devote my time studying that language/server and try to build this app.

[cut]
which components will be a good fit?:

1. Backend: MySQL or SQLite
2. webserver: apache or Lighttpd
3. development language: PHP or Java or Javascript (and XML I guess)

Thanks in advance.
-BG


Well, you might as well ask which editor to use, as well. That will start a few posts.
The correct answer is vim, of course!  8-)

My 2c - you will be fine with BAMP - BSD, Apache, MySQL and PHP.
Easy to get going on OpenBSD, well-supported, well-documented (TONS of sites, books, forums, etc.) Just RTFMs, and find the information that emphasizes good
coding practices.

Worry about JavaScript and XML when you need to (and Ajax can be a useful tool
in the right places.)

Unless you are an absolute genius, you are NOT going to get this right first time, so the design of the site, the pages, the database, the flow through the site - way,
way, way more important than the technologies you use.

Use modules / OOP / shared code. Use standard SQL rather than extensions.

Once you've got the basic plan, do some prototyping, learning, tweaking, etc. You will go around a few times until you get it right. Don't be afraid to refactor
and get things right.

Once it is hanging together and you've actually done some coding, you'll find the technology/language that works *for you* Maybe you do it in PHP first, and then decide PHP sucks - because you had a plan and a modular (or OOP) approach, it
should not take long to move your code to another language/database.

Whatever you go with, be confident that you can upgrade your system when issues are found in those technologies (MySQL, PostgreSQL, PHP, Python, etc. have all
have security issues found and resolved in the last 3+ months.)

HTH

Reply via email to