<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Php on ROBOCO</title>
    <link>https://roboco.io/en/tags/php/</link>
    <description>Recent content in Php on ROBOCO</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 16 Oct 2026 18:00:00 +0900</lastBuildDate>
    <atom:link href="https://roboco.io/en/tags/php/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Modernizing Legacy Code with Vibe Coding (2/2): PHP, Built Up Alongside the History of the Web</title>
      <link>https://roboco.io/en/posts/legacy-php-vibe-coding-modernization/</link>
      <pubDate>Fri, 16 Oct 2026 18:00:00 +0900</pubDate>
      <guid>https://roboco.io/en/posts/legacy-php-vibe-coding-modernization/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;The risk in legacy PHP lies not in pointers but in aging runtime environments, implicit type conversions, authorization checks, and the database and external integrations. In most cases the right answer is not to abandon PHP, but to move it to a supported version and put verification and deployment practices in place first.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://roboco.io/posts/images/Dohyun.png&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;h4&gt;Dohyun Jung - Principal Consultant, ROBOCO&lt;/h4&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;In &lt;a href=&#34;https://roboco.io/en/posts/legacy-cpp-vibe-coding-modernization/&#34;&gt;Part 1&lt;/a&gt;, I covered how to modernize C/C++ applications that are more than 20 years old with vibe coding.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; This post covers the legacy web, and PHP in particular.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
