| Re: getting a php capability on ubuntu was Re: using scripting languages to automate a browser [message #180448 is a reply to message #180426] |
Sun, 17 February 2013 07:48   |
Arno Welzel
Messages: 317
Registered: October 2011
Karma:
|
Senior Member |
|
|
M. Strobel, 2013-02-12 15:29:
> Am 12.02.2013 14:50, schrieb Peter H. Coffin:
>> On Mon, 11 Feb 2013 22:29:42 +0100, M. Strobel wrote:
[...]
>>> Maybe I confound it with the question which desktop is best for *nix
>>> development, but it just does not make sense develop for *nix on a MS
>>> Win desktop. You do not even have a decent shell. MinGW and Cygwin are
>>> not THE REAL THING.
>>
>> I am not sure how this matters, since 99.9% of development doesn't
>> even touch a shell, and wouldn't need the facilities of even those
>> (MinGW/Cygwin) anyway. An IDE works with files, it may compile things,
>> it probably does some socket stuff connecting to a versioning system
>> or source repository, but all the capacities of the programs being
>> developed depend on the capacities of the languages that they're built
>> in, and all stuff outside that can easily be provided by the IDE itself.
>> (EG: Who cares if you've got a posix grep utility around if your IDE
>> would be built with a regexp library bound in anyway?)
>>
>
> Then it looks like I am doing something completely wrong.
>
> I have to: write helper scripts, distribute them on my servers into the search path,
> version them, pump data out one database piping via ssh to remote servers, automate
> remote server setup and management, set up remote versioning repos, testing PHP
> snippets because of version differences and fine tuning, test HTML5 features and
> javascript in browser versions, write DB consistency checks, ... and yes, brute force
> grep through everything for refactoring.
>
> It really helps to work within the same OS family.
In *this* case - yes, for you.
But "PHP development" does not necessarily involve "helper scripts",
"piping via ssh to remote servers", "automate remote server setup and
management" etc. This is just a use case - and even a rare one compared
to the number of existing PHP installations and what they are used for.
There are a lot of PHP based applications which only need PHP itself and
probably a database like MySQL - and run fine on a Windows based system
as well.
Therefore i would not say that Linux is the "native" platform for PHP.
Apache is also not the "native" platform for web servers - other systems
like nginx or IIS exist and are used as well.
Of course - depending on what you want to do, it is important to have
the same environment for development as for production (same web server,
same libraries etc.). But this may also just be "Apache", "MySQL", "PHP"
- and nothing more.
--
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]