C5.7 Already legacy?
Permalink
I need to get this of my chest:
/angrymode_on
Looking at Concrete/composer.json shocks me. I cant understand why C5 still requires php 5.3 and so many old version of packages. I dont even want to think of security holes. It feels bad, i thought C5.7 would improve things, but having legacy bloated classes will eventually turn against you. Developers will flee. Its impossible to upgrade from 5.6 although there's still lots of 5.6 core stuff beneath the surface. Bad stuff imo. Its outdated. Get rid of it. You've polished the exterior to camoflage the inside which look like messy sticky glued parts.
"Its opensource, so you can contribute: stop trolling!"
Well its fubar imo. Start over! Oh wait.. you said you did.
/angrymode_off
How's the documentation going?
/angrymode_on
Looking at Concrete/composer.json shocks me. I cant understand why C5 still requires php 5.3 and so many old version of packages. I dont even want to think of security holes. It feels bad, i thought C5.7 would improve things, but having legacy bloated classes will eventually turn against you. Developers will flee. Its impossible to upgrade from 5.6 although there's still lots of 5.6 core stuff beneath the surface. Bad stuff imo. Its outdated. Get rid of it. You've polished the exterior to camoflage the inside which look like messy sticky glued parts.
"Its opensource, so you can contribute: stop trolling!"
Well its fubar imo. Start over! Oh wait.. you said you did.
/angrymode_off
How's the documentation going?
Hi MrKDilkington,
True, it is a huge task and i bet a dirty job. And comparing 5.6 to 5.7 huge steps are made. After a night of frustration i've come to reason.
Last night i tried to implement the illuminate/validator package. I ended up in dependancy circles and couldnt get it done. Why? Because Concrete uses old packages. Maybe today i find another way of doing this but it seems impossible at this moment.
I just hope to see newer packages, more builds, faster cycles. Only support PHP 5.6. Looking at the support graph its scary to keep supporting PHP 5.3 as a CMS.http://php.net/supported-versions.php....
Will check on github. thanks
True, it is a huge task and i bet a dirty job. And comparing 5.6 to 5.7 huge steps are made. After a night of frustration i've come to reason.
Last night i tried to implement the illuminate/validator package. I ended up in dependancy circles and couldnt get it done. Why? Because Concrete uses old packages. Maybe today i find another way of doing this but it seems impossible at this moment.
I just hope to see newer packages, more builds, faster cycles. Only support PHP 5.6. Looking at the support graph its scary to keep supporting PHP 5.3 as a CMS.http://php.net/supported-versions.php....
Will check on github. thanks
Php started out as a hacked convenient mess of a language that just happened to be in the right place at the right time. Every new version since has been like trying to polish a turd. If success on the web was only driven by using the absolute best and latest programming environment, no-one would be using php. It would be a dead language remembered for its quaint idiosyncrasies.
But php filled a gap, became popular and built up a huge legacy of code. Restricting a project such as c5 to the latest version of php would more likely stifle growth than promote it.
But php filled a gap, became popular and built up a huge legacy of code. Restricting a project such as c5 to the latest version of php would more likely stifle growth than promote it.
If you start building a house from ground up (at least thats what you say and aim for), it feels weird to use old bricks to support the foundation. Saying it's ok because we've been doing this for 20 years is kinda.. lame. You will always be that odd house in the street no one dares to enter.
Looking at other CMS and frameworks (drupal, laravel) its logical to get rid of the old code and mindset.
Looking at other CMS and frameworks (drupal, laravel) its logical to get rid of the old code and mindset.
Drupal, larvel .... Or WordPress?
If starting from the ground up, then any PHP version is an obsolete brick.
If starting from the ground up, then any PHP version is an obsolete brick.
Have you reached out to the core team to address your concerns?
I suggest creating a GitHub issue proposing how you would like to update the packages.
If you check GitHub, you will see that there is a lot of work being done by the core team and committed contributors to remove legacy code. It is a huge task that is being tacked file by file.
Documentation is minimal and only touches on a few areas. It is definitely an area that has a lot of opportunities to improve.