Hacker News new | past | comments | ask | show | jobs | submit login

Far too many to list here. A small sample:

- https://github.com/mholt/caddy

Caddy is an HTTP/2 webserver written in Go that integrates with ACME and serves websites of TLS by default. It powers https://paragonie.com and manages our HTTPS certificates automatically.

- https://github.com/twigphp/Twig

Twig is one of the sane templating languages for PHP projects that I use extensively.

- https://github.com/composer/composer

Composer revolutionized PHP development.

A lot of the "PHP sucks" arguments focus on things that haven't been true about the language since 5.4 (or earlier), but one thing that truly did suck was dependency management (before composer came around).

Dependency management also sucks in other languages (and still sucks in those). I suspect that's why few used that as a criticism of PHP.

- https://github.com/jedisct1/libsodium

Libsodium: modern cryptography that you can likely find bindings for in your favorite programming language.




I've been using PHP for most of my life, and used various template engine and it always end up with one question : what is the real purpose of a template engine in PHP instead of just using PHP ? When I see the examples in twig homepage it just looks like they tried to make PHP examples verbose for the sake of it.

I don't really mind them, but I find it extremely boring to have to register in the template engine every function that you will end up using somewhere else in your code and eventually have a language with less feature than plain old PHP and an other layer of cache.

So which use cases make you need Twig, for instance ?


If you have a designer who's worked with templating engines in other languages (e.g. Django/Python projects), they already know what they're doing.

It also makes it easier to separate your presentation logic from your business logic.

For example: https://github.com/paragonie/airship/blob/master/src/Cabin/B...

This uses macros and other fun things. Doing that in PHP would get messy.

https://github.com/paragonie/airship/blob/master/src/Cabin/B...


Okay, I've never worked with a designer that would touch code, so there is that. Macros seem a bit redundant with partial views in my opinion, except they take fixed parameters, but this is a interesting concept.


Working with designers who just want to make a few changes. All that PHP can be intimidating, but basic templating is doable.


+1 for twig when using PHP. Also, if working in Wordpress, the combination of ACF and Timber (twig for Wordpress) will get rid of a lot of frustrations.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: