@William Reynish (billreynish) and I continued work in the userpref_redesign branch. Mostly working on the panel/subpanel based layout.
Current screenshots:

I already have the latest driver (i checked).

Make sure you have the latest GPU drivers for you card and test again.

Indeed! Thanks!

@Cmb (Ine) If you go to File->Load Factory Defaults, the UV workspace should be set to the UV Editor.

The UV Editor is now its own editor in the editors menu, not a mode of the image editor.

Can confirm.

I wish the cursor had it's own color setting.

Could be solved by a combination of theme change and blinking?

Even if this blinks it can be hard to see - if I move my head 20cm to the right on my laptop I can barely see it for eg.

There's a reason why text cursors usually blink. We could add that in Blender too. Not a bug though.

Not technically a bug I don't think, and it didn't work in 2.7x either.

This is a tough one to theme, as it seems like it doesn't have a separate dedicated theme setting.

"Positions Only" reflects much better what the option does, since scaling or rotating don't affect object scale or rotation, nor its geometry; only its coordinates in the scene.

@Adrian Giddings (cunabula) Currently it's still called Spin. There's a 'Screw' modifier but that's something else.

Chiming in on the Spin / Lathe question.

These were removed, to be replaced by T54963: Industry Compatible Keymap.

I think the separation could be more like this:

• UV editor is for UVs and textures mapped to the mesh, tracking selection and modes in the 3D viewport.
• Image editor is for individual images and renders, independent of any mesh.

@Julien Kaspar (JulienKaspar)

In the Shader or Comp Editor and the Dopesheet or Graph Edior you at least get different content shown. In the UV or Image Edior you can display both UVs and Images.

Speed: It's much faster to directly be able to select the UV Editor, rather than first having to go to UV/Editor and then find the UV mode

The fact that we used to have to call it the UV/Image Editor in itself demonstrates that it makes more sense to be split.

One of the main reasons to do the split, is because of speed and discoverability.

Well we shouldn't decide weither to split features based on naming conventions :D

I still have this exact same issue.

I'm going to side with Julien. Being able to switch between UV editing with or without images, Image viewing with or without UV's, and Painting with or without UV's, is more easy as one editor. There are enough permutations and combinations that separating it into two editors will make some of those permutations not possible unless they are added as redundant features from one editor to the other, which is more work for developers. Also, the bespoke UV editing mode was a great adition for handling tools and the toolbar, I don't see how that isn't enough for things like Object mode uv editing

The fact that we used to have to call it the UV/Image Editor in itself demonstrates that it makes more sense to be split.

@William Reynish (billreynish) Right now it got split into 2 Editors but I was talking more as in what is planned (Or what I think is planned)
I think I misread one point above. I got the impression that the "New: 2D Paint" means that it becomes its own Editor as well. Would this still be part of the Image Viewer?

@Julien Kaspar (JulienKaspar) I'm not sure what you are talking bout with splitting UV/Image Editor into 4 distinct Editors. It isn't split into 4 - it's split into 2: UV Editor and Image Editor.

I don't know which arrows and checkboxes you mean exactly. Please share a screenshot of the issue.

I'd like to know more about the reasoning behind splitting the UV/Image Editor into 4 distinct Editors.
I get the reasoning behind making a Mask Editor since the masks are used in other Editors as well, but I don't see any reason for the others.
So we'll we have 3 editors that basically look the same and share similar functionality. To me this change seems very nonsensical and unintuitive.
Are all these Editors going to share the same interface and selected Image anyway, syncing up on all times in terms of panning and zooming? Then why have them separate Editors when we already had them as separate Modes.

I totally agree with this. I saw many users losing their work since blender does not automatically pack or save generated images inside Blender.
Blender's Automatically Pack Into .blend option is super cool, but it should also apply to generated images as well, not only external images.

Also getting this constantly printed to the console

col.prop_search(bone, "bbone_custom_handle_start", ob.data, bone_list, text="Custom")
AttributeError: 'NoneType' object has no attribute 'data'

Reproduced on MacBook mid-2014 MacOS 10.13.6
Additionally it shows a vertical black bar:

I could reproduce this bug happening too with Manjaro KDE, Plasma 5.14.4 with Nvidia GeForce GTX 750 Ti and 415.22 drivers.

@Brecht Van Lommel (brecht): Here's a patch to fix three issues in the Node Editor: D4055

I added a revision here for your diff.

Hey, I have a diff ready here.
What happens now?

Import/Down/In, Export/Up/Out - of course it is designed like that! I was so focused on making sketches and so fixed with the in/down - out/up concept, that I didn't notice the fact that icons are flipped. Sorry for confusion.

Not everyone agrees on what should be put here. Playback makes sense for a lot of people, starting by animators. Search bar is extremely usef by some, barely used by others, etc.

I agree, it's not a big deal since you can change the spacebar behaviour almost instantly by splash screen. I love it. But I still think search or toolbar is a better choice as a default since you need to do some work before starting to animate things.

I can reproduce when setting the UI scalling to 2. (macs with retina display uses the same by defaults)

If you swapped the 1st vertical arrows to Down on the Left and Up on the Right, then I think it's more understandable.
Import/Down/In, Export/Up/Out

I fiddled a bit with your proposal...