i18n??

Hey guys someone knows how to deal with the internationalization of a php website (on a lamp setup basically), shoud I use gettext or what??

lamp setup
Now you have four problems.

>>2
On its own, the first one is not a problem.

Linux, Anything-but-MySQL, Perl.

>>4
What's so bad about MySQL?

OP here, it's the first time i came here hoping you guys were more serious but your just trolls like the rest of 4chan.
I just asked this same question on /g/ and at least they gave me some answers...
what's your problem with lamp everybody uses it, it has the largest market share right now. The only thing i would think about changing is maybe mysql, cause maybe it lacks some features and it has been bought by oracle so i'm not sure about its future.
Anyway facebook runs on mysql and is certainly one of the most demanding websites in terms of databases.
Perl? Why perl? give me one good reason to prefer perl to php. Nobody uses it anymore, and i certainly won't start using it unless you give me a good readon.

>>6
PHP is a bad language and you should feel bad about it.

>>7
well, it's slow, but i plan to use precompilation and caching to some extent, and coming from languages like C i just love the flexibility of php, you don't have to care about types or pointers it always works it almost scares me!

>>7
That's true, but it still does not explain, why he should prefer Perl to PHP.

>>9
He shouldn't, unless it's a quick hack.

If it was me, I'd love to try writing a web project in CL as the language is nice and there are quite a few libraries and web/application servers, but I don't do much web dev these days.

I did use PHP in the past for a few web dev projects, and it has 2 advantages: 1) supported everywhere, cheapest hostings included 2) it's very popular which means you can reuse other people's code, and there's usually a lot of it. The disadvantages are that the language sucks, the implementation is rather crappy, and it made me hate myself when writing in it, even more if I had to maintain other people's code ;_;

Last time I checked CL had pretty shitty string handling, which I consider a disadvantage for doing web servers. I suppose you could use something else for the templating language, but still.

Linux, Any webserver, Postgres, Django. It's the only stack that makes sense.

>>11
There's cl-ppcre, and it's not hard at all to make a few functions/macros to simplify various string processing tasks. There's also various xml/html/json/... parsers available, and some yacc-like utils. So, it's usable and can be easily improved. The standard library is maybe a bit too generic, which makes doing various common string mangling operations a bit lengthy, but it's easy to make a few functions which represent common usage.

PHP has amazing parsing http://stackoverflow.com/posts/2809162/revisions

>>14
sounds like a horror story programmers would tell each other around a bonfire :)
Anyway I think it's so improbable it will happen to me that i'd say it's impossible

>>12
I'll endorse Postgres, not that it's particularly good, it's just particularly not bad given the landscape. The rest is sort of ``who-cares?'' Linux isn't any better than BSD, or whichever Unix. I would really avoid Apache unless a client requires it (and has withstood being talked out of it.) Apache isn't bad, it's just unnecessary. (OTOH, mod_security is nice if some LAMP moron is building the website unmonitored.)

FAPP!

FreeBSD + Apache + Postgres + Perl!

>>16
Of course Linux is better than BSD [sic] or ``whichever Unix'', if only because of the size of the development community and the sheer amount of resources available to people running webserver on it, which are a consequence of its popularity. The BSDs are feature-anemic and not nearly as well-tested, not because their developers are less competent (usually the reverse is true), but because they just don't have the resources. The other Unices are a joke at this point.

>>17
Anyone using Perl for web development post the mid-'90s should be shot.

>>18
Climb back down to earth for a moment and reflect on the fact that the goal is to run a web server, not to feel good about what you suspect the operating system will be capable of in other avenues come 2759.

>>18
You're saying we should use a macro language instead?

>>18
Anyone still not using Perl for web development post the mid-'90s should be shot.
ftfy

>>19
That's not the point. The point is that if you want to run any combination of software on Linux, someone else will certainly have done it before you and fucked up in ways you haven't even thought of, and will have documented it. If you're using a BSD or other obscure OS, any problem you will run into (and you'll run into a lot) will be yours and yours alone to solve.
A competent sysadmin should be able to solve those problems himself, but it's stupid to waste time on that when all you want to do is run a webserver.

Unless all you want to do is serve up static HTML for a low-traffic website, which even Windows can do, Linux is your best bet.

>>21
Enjoy your PHP for neckbeards, hghgd.

>>22
Troll on dude.

>>24
Perhaps /pr/ will appreciate you. Here you're just a waste of space.

>>25 see >>24

>>26 see >>25

>>26-27
guys we don't need any more kopipe in here you guys

>>28 see >>20

>>6
your just trolls
What about my pack of just trolls?

>>30
They are patriots of truth and justice.

33 Name: Anonymous 2011-01-31 21:01

<-- check em dubz