Today, I attempted to learn a bit about Blender’s new rendering engine, Eevee. The goal is to have Eevee replace the old blender internal engine, and work as the new default viewport engine
The biggest, strongest benefits that Eevee brings is render times and use of familiar material settings. All of Cycles’ node setups are basically immediately ported to Eevee upon swapping render engines, with render times being counted in seconds rather than minutes.
With that said, it’s still got loads of stuff that needs to be done to make it production ready.
While it’s supposed to be aimed at replacing the current viewport, I’ve found that Cycles currently provides a better work experience than Eevee. And there’s lots of little things that just don’t work yet, with modifiers being at the top of that list.