A321 pilot flying reported encountering jet blast just before landing at PHL from a heavy jet that just departed.

Narrative

Arrival into PHL was uneventful and the airspace was not busy. We were vectored to visual and handed over to Tower. Tower cleared us to land Runway 27R at the same time clearing another aircraft for takeoff. Passing final approach fix; we noted 19-kt. tailwind. Once the first aircraft took off; the Tower cleared another heavy aircraft for takeoff. We voiced our concern to the Tower due to tailwind and faster approach speeds. The aircraft cleared for takeoff was slow on entering the runway and slow on takeoff roll. By that point; we were at 500 ft. and I was getting ready to execute a go-around. The heavy aircraft took off just in time for us to feel safe to land. The winds were [calm] on the runway. The aircraft encountered some residual turbulence from the heavy aircraft over the runway numbers. Around 50 ft. and reducing thrust to idle; just prior to flare; we encountered even more jet wash; wing tip turbulence that substantially rocked the aircraft wings. I was able to stabilize the aircraft; flare; and land safely.I am new to PHL. I experienced on multiple occasions and spoke to many other crew members who had the same experience with Approach vectoring too close; Tower clearing aircraft for takeoff and landing with extremely close or inadequate spacing. I personally had to execute S-turns on final. I was badgered into getting off the runway as fast as possible. It is unnecessary and could be potentially unsafe. A look into PHL airspace; arrivals and spacing to land; Tower operations; and requirements might be useful to uncover the primary cause of such tight; inadequate; or unnecessary risky vectoring; spacing; and clearances. A dialogue with ATC might be critical to prevent any future incidents.