Avoid Costly Framework Upgrades | Anna Filina

Подписаться 5 тыс.

Просмотров 1,2 тыс.

50% 1

If your framework version was no longer supported, how much effort would it take to swap it for another? Does it look like you might need to rewrite your entire application? You can write your code in a way that will make the inevitable framework swap a piece of cake, instead of a 12-month sustained effort. Learn from the experience of dozens of framework swaps, some easier than others.
phpconference....
International PHP Conference Berlin
phpconference....
International PHP Conference Munich
phpconference....
International PHP Conference Blog:
phpconference....

Наука

Опубликовано:

5 окт 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 7

@iamise 2 года назад

Great talk, and something to do even at the start of a new project to prolong the lifetime of an application you probably don't want to deal with 5 yrs down the line :D.

@pragnesh3107 2 года назад

These types of talk need more views.

@medilies Год назад

Why isn't there a PSR for templating engines?

@TristanBailey 2 года назад

Nice to think though these issues.

@lako2023 2 года назад

So basically: Don't actually use the framework that you chose (& learned how to use). Instead invest a lot of additional work into preparing a very theoretical transfer to another framework years down the road... Realistically it's much better to use one framework properly and invest a little work to stay up to date. Most projects won't live for more than a couple years anyway and there's zero guarantee that in 5-10 years you'd even use the same programming language for a relaunch. A loosely coupled project won't help you at all then.

@frantisek_heca Год назад

Thanks for summing up the content of the video from your perspective. Even without watching I can bet what is video about based on your opinion. Easier to decide if I want to watch it now.