Donations are not the main CTA. If you want to support the initiative you can donate.
We don't need money to build the MVPs for people but if we get donations we might convince other devs to join (they would get paid).
I didn't do a benchmark. Phalcon is probably faster than Django (by a few miliseconds) but it is a compiled extension and also doesn't have all the functionality that Django has.
Django compared to Laravel (which is now probably the most popular PHP framework) is orders of magnitude faster.
This is what I meant with Django being faster that PHP (this statement compares a framework with a programming language - not fair)
Without a benchmark I remain unconvinced. PHP7 performance was shown to have doubled since 5.6 in most cases, including with frameworks like Laravel. Prior to PHP7 it wasn't noticeably slower than Python.
It takes a while getting used to the names, but after that it's just awesome that you don't have to think about padding, margin and font-size values anymore. Just slap "pa1" or "pa2" there and everything looks pretty.
Doesn't it lead to inconsistent layout if someone forgets to add it?
I am not a designer, but few things irks me more than paddings varying across the same 'components'.
From experience, your method is easier to think through, but later on it is more time consuming to modify a layout. pa1 and the like should be treated the same as magic numbers.
That is the point. Padding can't be inconsistent if there are only 7 values to choose from, not 1..7, but powers of two, so 0.125, 0.25, 0.5, 1, 2, 4, 8rem.
Joe will chooses 0.25, Mary picks with 0.125 while Huan goes with whatever is the default.
There will be inconsistency if there is more than one choice available (empty is also a choice). Someone will slip up, it is only inevitable.
And if somebody doesn't use the library, but pixels or percentages, you get the same problem. You can't use a library to replace communication in a team.
But having 7 rem-relative steps, that fit together makes the common use-case way easier: Joe: "I need more padding on this, so I use pa2 instead of pa1".
If you feel the urge to check your code base it's easy to write scripts that count the occurences of "pa1..pa7". It's not so easy if you have to take into account "padding: 1px", "padding: 20%", "padding: 3em" etc.
I've started an online store (https://adorely.ro) with a friend of mine using dropshippers (so we don't buy stock and manage the delivery) and we're getting our most valuable traffic from price comparison sites. While there is a limit of how many visitors you can get, the conversion rate is amazing (in some cases is more than 10%) and the cost is extremely low.
Adwords is not a good idea if you don't have a good lifetime value.
Also we tried to increase our Facebook fanbase but the conversion rate is pretty low (still bigger than adwords).
Agree with most of your points. I was only pointing out that Oracle now wants a piece of that pie. BTW, they support both revenue share and number of click model.
I was thinking about bootstrapping business and target the small - medium businesses. If I want to tackle the enterprise business it might take 2 years for an MVP, but an alternative for a WooCommerce store shouldn't take that long.
They basically offer you a backend and a set of APIs to create your store. It's a great tool to use if you want to be in control of your store behaviour. On the other hand it requires you to have some technical knowledge.
We already support pattern unlock, if there are requests for pin unlock, it'll be really easy to integrate it.
Custom feeds is on our roadmap. Sometimes in the near future.
