Sorry for the noise just wanted to chime in and in name of all the community thank @Spivak Vladimir (cwolf3d) for these improvements.
This is an important tool for architects and designers working with Blender and we really appreciate your work.

Really like the direction this took, congratulations, this is an improvement of what we had previously.

In T52668#769527, @Campbell Barton (campbellbarton) wrote:

If objects are being loaded into local view unintentionally it makes local-view operations unpredictable.

I don't really use background images myself much (asking for a friend), but for the sake of completion I'll post it here also.
Some users seem to miss an option to include images while in local view; this came up in Blender Stack Exchange a few times

Some comments on this: I don't think it is 2.8 related, 2.79 was equally slow.

I did think about Susanne but it seemed a little tacky, and it is relatively complex in terms of geometry, might not look that good as line art or at smaller scales

Your attempts aren't bad at all, I found most quite adequate.

Currently on vacations I decided to play a little more just for fun.
I wanted to try making an animated "Busy" cursor that was somewhat Blender specific without being too literal.
The idea of a spinning default cube seemed minimal enough but recognizable.

I'm really fine with the center aligned checkboxes proposal in the task description. The ´heading' text to the left and the description to the right really improve readability with minor downsides; but if we are going with any "wider" solution that's meant to make checkboxes as wide as other UI buttons and sliders, than I'd go with some sort of iOS style toggle buttons, that could stretch to fill the same width without looking too out of place.

In T61492#744236, @Harley Acheson (harley) wrote:

Why not instead treat this is an attribute of the collection instead: an optional secondary shortcut name?

In D4886#122474, @Harley Acheson (harley) wrote:

I think that crappy mockup was quickly whipped together by someone who didn't think it through because of insufficient level of caffeine.

Sorry for the delayed response. Right you are, my mistake.

Increasing folder icon size is a big plus for me visually, it makes them much more coherent and harmonious.
As for the icon design itself the second one seems much more adequate for the current UI, but I'd go with a monochrome version of it, following the current UI button icons guidelines, so it could eventually be themable.

In D5197#121955, @Harley Acheson (harley) wrote:

But we'll also need ones that are exactly twice as large as your smallest, and on a 64x64 field. This last one needed for hiDPI displays. I'm guessing we can just export your mid-sized ones to the larger size.

In T67744#736320, @Howard Trickey (howardt) wrote:

But would a way to achieve the desired result be to have a modifier that converts a Curve object (with bevel / extrude parameters set to something nonzero) into a Mesh

In T67744#736230, @Howard Trickey (howardt) wrote:

Booleans on elements other than meshes are out of scope for this task, which is already hard enough. The math and algorithms would be rather different for curve objects. Good to hear that the Curve Cad Tools addon supports boolean operations on curves. Maybe some future design task could consider porting those into the main C code for Blender, if the authors agree.

Would you be open to the idea of supporting Boolean operations on other object types, like directly bezier curve objects? Would be useful for operations without having to convert to mesh first

A few slightly tweaks for pixel-perfect tips on arrows. We were getting "double pixel" corners which are harmful for hotspot placement.

Here are tweaked versions for dark and light backgrounds, plus a few new ones. I think these are it for now, I can design more if needed in the future.

Besides modal maps, if these were also exposed as operator options for the move, rotate and scale tools, we could even define custom key map entries for direct access to any desired combination of base points

I'd vote to keep .. for parent directory. I understand the reasons for removal, it is a dying trend from an ancient era, frequently absent in modern UIs, but it is very convenient and fast to use.
Not only does it have a fixed position in the UI ( no need to hunt for it in toolbars or look around), it is also part of the file list, which is where yours eyes/attention is usually focused, making using it very fast because you don't have to shift focus to another part of the UI.

Tweaked some of them a bit for better dark background support, plus a few new ones in contrasting situations.

In D5197#120200, @Harley Acheson (harley) wrote:

The two "splitters" and four "direction" cursors are now shown just before, and during an editor split or join. You can see them illustrated here: https://docs.blender.org/manual/en/dev/interface/window_system/areas.html

Just one small note that came to mind now. Using 2 or 3 as hotkeys keys for two or three base points may cause conflict with introducing absolute values for rotation (as in 2 our 3 degrees).

In T66337#730538, @Paul Kotelevets (1D_Inc) wrote:

In T66337#730138, @Duarte Farrajota Ramos (duarteframos) wrote:

@Paul Kotelevets (1D_Inc)

Also, there is still no preference in axis placement order - here is still possible RB3-Z, R-Z-B3 or RB-Z-3 with the same result. Only RB3 part is in certain order.

In D5197#120138, @Harley Acheson (harley) wrote:

@Duarte Farrajota Ramos (duarteframos) - but here are a few first crude mockups I managed to sketch...

When I was playing with your knives earlier, it seemed quite nice and straight-forward to make the multiple sizes I need from an SVG source in Inkscape.

@Paul Kotelevets (1D_Inc) This is pretty close to how I'd envision things, if we ever get something even remotely like this that'd be perfect.

Sorry for the lack of progress, not much free time right now, but here are a few first crude mockups I managed to sketch.
Work in progress at the moment, most don't work that well over dark backgrounds, so definitely needs adjustments.

Are file names hardcoded? Should I use the same for export, or am I free to name them more sanely?

I see, fair enough.

Will do, I'll be glad to help with my limited knowledge.
I'll probably be a bit busy next couple of weeks so I can't promise much, but I'll try to squeeze in something. After that I'll probably have some more free time.

Well not really my area of expertise either, but I do enjoy it as a hobby.
Either way I made them in Inkscape, so they are available as vector graphics, should scale well to other sizes, though readability at lower res may dictate manual per-pixel adjustments.

A little nitpicking, I'm sure it is a matter of personal preference, but I think the new knife cursor is not as elegant as the previous.
Something about that 45º slanted tip looks off, like it is piercing through something. A pointier tip helps distinguish were the "hotspot" active pixel is.

Great proposal, this will be a huge game changer for Blender.

In T66337#724459, @Germano Cavalcante (mano-wii) wrote:

I didn't understand what you meant by "Base point support -> [2 and 3]point Alignation".

In T55194#708677, @Paul Kotelevets (1D_Inc) wrote:

So, mapping "|" and "\" keys that are currently seems to be empty will solve problem?

In T55194#708416, @William Reynish (billreynish) wrote:

Blender should not use the Tilde key directly, but always map to the key to the left of 1 on the number row.

Just for reference I'll leave a link to what I consider one of the most competent and comprehensive Blender batch rename addons Name Panel or the 2.8 version nS, including options to batch transfer names between datablocks.

Seems to be back to previous behavior for now, which is more helpful. Many thanks for the fix.

In rB9dafc8ee2c542949e87e5e81b0ba5088bbd46af9#235849, @Germano Cavalcante (mano-wii) wrote:

The workaround was to remove this new feature for vertices -> rB21b5af766d33
Sometimes it is better to keep the original behavior.

@Germano Cavalcante (mano-wii) While this is a very welcome addition and a definite improvement, it breaks the ability to snap to original curve vertex, even for non constructive modifiers, like say Edge Split which is a shame.