This is just completely misleading. Unity may “run poorly” if, and only if the project demands make it so. Unreal “runs poorly” as a matter of design unless you have a higher end card, even if the game you are developing isn’t much more than flappy ducks.
I was able to make a 2D-runner on my Macbook Air (Intel HD4000) without any performance problems at all with Unity. Several small (and definitely un-fancy) 3D project-tutorials also ran without any indication that I was stressing the machine.
The same Macbook Air can’t even load an empty UE4 project without dropping to under 1FPS and kicking on its fans immediately. A Macbook Air with an HD3000 can’t even run a packaged project (probably due to the bug that clearly isn’t a priority) that consists of nothing more than 2 static lights, 3 cameras, and 6 objects with less than 500 tris each. I don’t know about you, but I had machines in the 90’s - without any kind of GPU whatsoever, only a single core processor measured in Mhz, and memory measured in single-digit megabytes - that were capable of rendering 3,000 polygons (and one of the first shaders) without a problem. The demands of UE4 are far-and-away much more massive than the demands of the Unity Engine.
Because it was misleading. darthviper107 is just one of those people who has to be right (especially after an expert they can’t argue against tells them how they are misleading) and makes the all-to-easy confusion between personal perception and objective reality. By not accepting other people’s experience, these guys’ (and they’re almost always guys’) experience is entirely misleading, and usually puts them into isolation with people who tolerate this behavior, if not agree with the mindset. But since he was just told he was misleading by someone with certified expertise, his only recourse - other than backing off - was to find someone who he can preach at - and you happened to be the most readily available target. Try not to take the actions of a broken person (and indeed, we are all broken in different ways) personally, it’s not about you, it’s about his inability to heal his damage.
However, mattsatt also make clear that if* the drivers were fixed, the HD3000 is still going to be an abyssmal performer. It’s safe to say the HD3000 will never be supported. Even if the driver is fixed, your machine won’t be strong enough to run the engine well.
I can assure you that an HD4000 is also poor, and not really usable (at least on OS X). It’s not until the HD5000 that performance starts to become smooth enough to get work done. However, the machine I’m currently using that has a HD5000 is a mac mini, duo core i5 (which is 2 cores short of spec), but has 16GB of RAM. It’s still pushing its limits. Builds and compiles take about 12x longer on this machine than my PC that is above the min-specs (quad-core i7, DX11 Radeon 270, still 16GB ram).
If you need to develop on a low powered machine, even for 2D projects, Unreal is not a good choice. At least not now. With their expanded user-base, and attempts to reach mobile, I would expect that to change, but slowly (case in point; this issue has been bubbling for 2 years now and has no indications of being improved in the near future).
*which is indeed a conditional that implies the condition is a possibility, in addition the indicators you called out and darkpoison dismissed to try and feel better.