Timeline for We are moving an Access based corporate front-end into a Web-based App
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 7, 2012 at 4:23 | comment | added | GrandmasterB | "120K lines of code would be a nightmare to manage in PHP" - if you code it like crappy open source forum software, then sure, it'd be a nightmare. If you code w/ strong OOP fundementals, its no more difficult than 120k lines of anything else. | |
| Sep 6, 2012 at 18:20 | comment | added | GlenPeterson | Linux is so full of developer tools and so reliable, fast, and lightweight, it's hard to not like it as a server and development environment. Once again, your Microsoft technologies won't run there (well, Mono will, but that probably won't help you). Look into PostgreSQL instead of MySQL - Postgre uses the Apache license and can be distributed with closed-source software for free. It's also faster, but requires more work to set up. Maybe you stick with SQLServer so you can keep something the same? | |
| Sep 6, 2012 at 18:18 | comment | added | GlenPeterson | I'm a Java fan. Its trade-offs between reliability, speed, and maintainability are about right for the problems I tend to solve. It doesn't have great tools for web front-end development though. I mean they are OK, but not PHP or Ruby/Rails. If I were you, I'd weigh Java goodness against the programmer knowledge you have right now in C#/.Net. C# is pretty similar to Java, but C# is designed to be easier to work with and Java more reliable. Someone will disagree, but that's my take. | |
| Sep 6, 2012 at 17:49 | comment | added | Hannah Vernon | Thanks for that thoughtful comment. Upvoted. The issues are just as you suspect, both reliability from an exception handling point of view, and speed of the user interface are both concerns. | |
| Sep 6, 2012 at 17:47 | history | answered | GlenPeterson | CC BY-SA 3.0 |