Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming > #698 > unrolled thread

Help needed for choosing server side technology !

Back to article view | Back to comp.programming

Contents

  Help needed for choosing server side technology ! vaib <vaibhavpanghal@gmail.com> - 2011-07-24 13:28 -0700
    Re: Help needed for choosing server side technology ! Ian Collins <ian-news@hotmail.com> - 2011-07-25 09:11 +1200
      Re: Help needed for choosing server side technology ! vaib <vaibhavpanghal@gmail.com> - 2011-07-25 01:52 -0700
        Re: Help needed for choosing server side technology ! "BartC" <bc@freeuk.com> - 2011-07-25 10:17 +0100
          Re: Help needed for choosing server side technology ! vaib <vaibhavpanghal@gmail.com> - 2011-07-25 05:54 -0700
            Re: Help needed for choosing server side technology ! Ian Collins <ian-news@hotmail.com> - 2011-07-26 09:27 +1200
              Re: Help needed for choosing server side technology ! vaib <vaibhavpanghal@gmail.com> - 2011-07-26 01:01 -0700
                Re: Help needed for choosing server side technology ! Ian Collins <ian-news@hotmail.com> - 2011-07-26 22:38 +1200
                  Re: Help needed for choosing server side technology ! vaib <vaibhavpanghal@gmail.com> - 2011-07-26 09:37 -0700
        Re: Help needed for choosing server side technology ! Rui Maciel <rui.maciel@gmail.com> - 2011-07-27 00:54 +0100
          Re: Help needed for choosing server side technology ! vaib <vaibhavpanghal@gmail.com> - 2011-07-27 00:51 -0700

#698 — Help needed for choosing server side technology !

Hi all,

Myself and my friend have been discussing an idea for some time now.
It involves location based social networking not very different from
Foursquare. My friend is a mobile developer and I am a .Net developer
at work. These are exciting times with Node.js out. I am also pretty
proficient with all client side technologies like html5, css and
javascript.

Though I only know asp.net as server side technology but we both can
really take up any technology.

We'd like to get suggestions on what to use on server side -
Php, .net, java\scala, ROR, node.

What do you think we should be using on server side? Please suggest.
We'd like to start soon.

Thanking in anticipation.

[toc] | [next] | [standalone]

#699

On 07/25/11 08:28 AM, vaib wrote:
> Hi all,
>
> Myself and my friend have been discussing an idea for some time now.
> It involves location based social networking not very different from
> Foursquare. My friend is a mobile developer and I am a .Net developer
> at work. These are exciting times with Node.js out. I am also pretty
> proficient with all client side technologies like html5, css and
> javascript.
>
> Though I only know asp.net as server side technology but we both can
> really take up any technology.
>
> We'd like to get suggestions on what to use on server side -
> Php, .net, java\scala, ROR, node.
>
> What do you think we should be using on server side? Please suggest.
> We'd like to start soon.

Probably anything other than .net.  That way you won't be tied to a 
single platform if you are looking for low cost hosting.  PHP will be 
available anywhere, is a doddle to set up and should meet your needs.

-- 
Ian Collins

[toc] | [prev] | [next] | [standalone]

#700

On Jul 25, 2:11 am, Ian Collins <ian-n...@hotmail.com> wrote:
> On 07/25/11 08:28 AM, vaib wrote:
>
>
>
>
>
> > Hi all,
>
> > Myself and my friend have been discussing an idea for some time now.
> > It involves location based social networking not very different from
> > Foursquare. My friend is a mobile developer and I am a .Net developer
> > at work. These are exciting times with Node.js out. I am also pretty
> > proficient with all client side technologies like html5, css and
> > javascript.
>
> > Though I only know asp.net as server side technology but we both can
> > really take up any technology.
>
> > We'd like to get suggestions on what to use on server side -
> > Php, .net, java\scala, ROR, node.
>
> > What do you think we should be using on server side? Please suggest.
> > We'd like to start soon.
>
> Probably anything other than .net.  That way you won't be tied to a
> single platform if you are looking for low cost hosting.  PHP will be
> available anywhere, is a doddle to set up and should meet your needs.
>
> --
> Ian Collins

But what about the learning curve Ian? I mean we are talking about
coding an enterprise level application here. You think we'd be able to
write optimized code in a language we just picked up?

Learning is one thing and coding professional stuff is another.

Just trying to discuss it through.

Thanks for replying.

[toc] | [prev] | [next] | [standalone]

#701

"vaib" <vaibhavpanghal@gmail.com> wrote in message 
news:2ca47388-5408-4b72-932d-0137360a45e0@h17g2000yqn.googlegroups.com...
> On Jul 25, 2:11 am, Ian Collins <ian-n...@hotmail.com> wrote:

>> > We'd like to get suggestions on what to use on server side -
>> > Php, .net, java\scala, ROR, node.
>>
>> > What do you think we should be using on server side? Please suggest.
>> > We'd like to start soon.
>>
>> Probably anything other than .net.  That way you won't be tied to a

> But what about the learning curve Ian? I mean we are talking about
> coding an enterprise level application here. You think we'd be able to
> write optimized code in a language we just picked up?
>
> Learning is one thing and coding professional stuff is another.

OK, what are the choices then, if you can only use a language that you know 
inside-out?

-- 
Bartc 

[toc] | [prev] | [next] | [standalone]

#706

On Jul 25, 2:17 pm, "BartC" <b...@freeuk.com> wrote:
> "vaib" <vaibhavpang...@gmail.com> wrote in message
>
> news:2ca47388-5408-4b72-932d-0137360a45e0@h17g2000yqn.googlegroups.com...
>
> > On Jul 25, 2:11 am, Ian Collins <ian-n...@hotmail.com> wrote:
> >> > We'd like to get suggestions on what to use on server side -
> >> > Php, .net, java\scala, ROR, node.
>
> >> > What do you think we should be using on server side? Please suggest.
> >> > We'd like to start soon.
>
> >> Probably anything other than .net.  That way you won't be tied to a
> > But what about the learning curve Ian? I mean we are talking about
> > coding an enterprise level application here. You think we'd be able to
> > write optimized code in a language we just picked up?
>
> > Learning is one thing and coding professional stuff is another.
>
> OK, what are the choices then, if you can only use a language that you know
> inside-out?
>
> --
> Bartc

Hi,

Well thats where we are confused.

Whether to code in what we know(this will help us ship faster and we'd
write good code with some technology oriented best practices but have
certain disadvantages - the server has to be windows) OR should we
delay the project and pick up a new technology (like Php) altogether
and code the project in it. Picking up something new has certain
disadvantages too - we'd ship late and the initial betas will have a
lot of inefficient code(being practical) since we also have to attend
office during daytime.

So, we are looking for people who might have made such decisions in
the past. And also, what do you think should be the right way to go
about it? What would you do if you were in our boots?

Thanks for tolerating :)

[toc] | [prev] | [next] | [standalone]

#710

On 07/26/11 12:54 AM, vaib wrote:
> On Jul 25, 2:17 pm, "BartC"<b...@freeuk.com>  wrote:
>>
>> OK, what are the choices then, if you can only use a language that you know
>> inside-out?
>
> Well thats where we are confused.
>
> Whether to code in what we know(this will help us ship faster and we'd
> write good code with some technology oriented best practices but have
> certain disadvantages - the server has to be windows) OR should we
> delay the project and pick up a new technology (like Php) altogether
> and code the project in it. Picking up something new has certain
> disadvantages too - we'd ship late and the initial betas will have a
> lot of inefficient code(being practical) since we also have to attend
> office during daytime.
>
> So, we are looking for people who might have made such decisions in
> the past. And also, what do you think should be the right way to go
> about it? What would you do if you were in our boots?

The first time I picked up a PHP book was the day I agreed to write the 
server side of a web application in PHP!

If you are familiar with a couple of other programming languages 
(especially anything derived from C), PHP is very easy to learn and it 
is trivial to deploy.  It has a very good unit test framework (PHPUnit) 
that integrates well with at least one IDE (NetBeans), so you can write 
quality code from day one.  It might not be optimal code, but you can 
always go back and refactor it later.

-- 
Ian Collins

[toc] | [prev] | [next] | [standalone]

#711

On Jul 26, 2:27 am, Ian Collins <ian-n...@hotmail.com> wrote:
> On 07/26/11 12:54 AM, vaib wrote:
>
>
>
>
>
>
>
>
>
> > On Jul 25, 2:17 pm, "BartC"<b...@freeuk.com>  wrote:
>
> >> OK, what are the choices then, if you can only use a language that you know
> >> inside-out?
>
> > Well thats where we are confused.
>
> > Whether to code in what we know(this will help us ship faster and we'd
> > write good code with some technology oriented best practices but have
> > certain disadvantages - the server has to be windows) OR should we
> > delay the project and pick up a new technology (like Php) altogether
> > and code the project in it. Picking up something new has certain
> > disadvantages too - we'd ship late and the initial betas will have a
> > lot of inefficient code(being practical) since we also have to attend
> > office during daytime.
>
> > So, we are looking for people who might have made such decisions in
> > the past. And also, what do you think should be the right way to go
> > about it? What would you do if you were in our boots?
>
> The first time I picked up a PHP book was the day I agreed to write the
> server side of a web application in PHP!
>
> If you are familiar with a couple of other programming languages
> (especially anything derived from C), PHP is very easy to learn and it
> is trivial to deploy.  It has a very good unit test framework (PHPUnit)
> that integrates well with at least one IDE (NetBeans), so you can write
> quality code from day one.  It might not be optimal code, but you can
> always go back and refactor it later.
>
> --
> Ian Collins

And Ian you were doing this stuff by yourself or was it something
required at work?

[toc] | [prev] | [next] | [standalone]

#712

On 07/26/11 08:01 PM, vaib wrote:
> On Jul 26, 2:27 am, Ian Collins<ian-n...@hotmail.com>  wrote:
>> On 07/26/11 12:54 AM, vaib wrote:
>>> On Jul 25, 2:17 pm, "BartC"<b...@freeuk.com>    wrote:
>>
>>>> OK, what are the choices then, if you can only use a language that you know
>>>> inside-out?
>>
>>> Well thats where we are confused.
>>
>>> Whether to code in what we know(this will help us ship faster and we'd
>>> write good code with some technology oriented best practices but have
>>> certain disadvantages - the server has to be windows) OR should we
>>> delay the project and pick up a new technology (like Php) altogether
>>> and code the project in it. Picking up something new has certain
>>> disadvantages too - we'd ship late and the initial betas will have a
>>> lot of inefficient code(being practical) since we also have to attend
>>> office during daytime.
>>
>>> So, we are looking for people who might have made such decisions in
>>> the past. And also, what do you think should be the right way to go
>>> about it? What would you do if you were in our boots?
>>
>> The first time I picked up a PHP book was the day I agreed to write the
>> server side of a web application in PHP!
>>
>> If you are familiar with a couple of other programming languages
>> (especially anything derived from C), PHP is very easy to learn and it
>> is trivial to deploy.  It has a very good unit test framework (PHPUnit)
>> that integrates well with at least one IDE (NetBeans), so you can write
>> quality code from day one.  It might not be optimal code, but you can
>> always go back and refactor it later.
>
> And Ian you were doing this stuff by yourself or was it something
> required at work?

I was paid for the work if that's what you're asking.

-- 
Ian Collins

[toc] | [prev] | [next] | [standalone]

#714

On Jul 26, 3:38 pm, Ian Collins <ian-n...@hotmail.com> wrote:
> On 07/26/11 08:01 PM, vaib wrote:
>
>
>
>
>
>
>
>
>
> > On Jul 26, 2:27 am, Ian Collins<ian-n...@hotmail.com>  wrote:
> >> On 07/26/11 12:54 AM, vaib wrote:
> >>> On Jul 25, 2:17 pm, "BartC"<b...@freeuk.com>    wrote:
>
> >>>> OK, what are the choices then, if you can only use a language that you know
> >>>> inside-out?
>
> >>> Well thats where we are confused.
>
> >>> Whether to code in what we know(this will help us ship faster and we'd
> >>> write good code with some technology oriented best practices but have
> >>> certain disadvantages - the server has to be windows) OR should we
> >>> delay the project and pick up a new technology (like Php) altogether
> >>> and code the project in it. Picking up something new has certain
> >>> disadvantages too - we'd ship late and the initial betas will have a
> >>> lot of inefficient code(being practical) since we also have to attend
> >>> office during daytime.
>
> >>> So, we are looking for people who might have made such decisions in
> >>> the past. And also, what do you think should be the right way to go
> >>> about it? What would you do if you were in our boots?
>
> >> The first time I picked up a PHP book was the day I agreed to write the
> >> server side of a web application in PHP!
>
> >> If you are familiar with a couple of other programming languages
> >> (especially anything derived from C), PHP is very easy to learn and it
> >> is trivial to deploy.  It has a very good unit test framework (PHPUnit)
> >> that integrates well with at least one IDE (NetBeans), so you can write
> >> quality code from day one.  It might not be optimal code, but you can
> >> always go back and refactor it later.
>
> > And Ian you were doing this stuff by yourself or was it something
> > required at work?
>
> I was paid for the work if that's what you're asking.
>
> --
> Ian Collins

Yes and No. All I wanted to point out was that I work on .net at work
and then would it be feasible to come back home and learn\do php?

[toc] | [prev] | [next] | [standalone]

#715

vaib wrote:

> But what about the learning curve Ian? I mean we are talking about
> coding an enterprise level application here. You think we'd be able to
> write optimized code in a language we just picked up?
> 
> Learning is one thing and coding professional stuff is another.
> 
> Just trying to discuss it through.

You do have a point.  Yet, consider this: you have a choice between using 
the wrong tool which you happen to know well or the right tool which you 
need to learn.  As I see it, the first one is only beneficial in the very 
short term while the second will actually develop your skills which you will 
certainly find to be very useful.  As an added problem, if you start 
something in bad terms then nothing assures you that things will get any 
better with time.


Rui Maciel

[toc] | [prev] | [next] | [standalone]

#716

On Jul 27, 4:54 am, Rui Maciel <rui.mac...@gmail.com> wrote:
> vaib wrote:
> > But what about the learning curve Ian? I mean we are talking about
> > coding an enterprise level application here. You think we'd be able to
> > write optimized code in a language we just picked up?
>
> > Learning is one thing and coding professional stuff is another.
>
> > Just trying to discuss it through.
>
> You do have a point.  Yet, consider this: you have a choice between using
> the wrong tool which you happen to know well or the right tool which you
> need to learn.  As I see it, the first one is only beneficial in the very
> short term while the second will actually develop your skills which you will
> certainly find to be very useful.  As an added problem, if you start
> something in bad terms then nothing assures you that things will get any
> better with time.
>
> Rui Maciel

Hmmm......you have a point.
Thank you all for answering. I'd let you know what I went ahead with.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.programming

csiph-web