Firefox UI person: "I know! Let's change the bookmarks folder icon to just a black outline with no fill, so it doesn't stand out at all and people have a harder time navigating their bookmarks."

FFS.

I swear, Mozilla's motto is "If it ain't broke, break it."

#Firefox #UI #UX #designer #CADT #broken #BrokenByDesign #IfItAintBroke #BreakIt #software #Mozilla

"Your PyCharm subscription will auto-renew soon! Or you can renew it manually."

<go to renewal page>

<buy renewal>

<download new version>

<start new version>

"PyCharm has a brand-new UI!"

Totally flat, colourless design virtually barren of controls, i.e. absolutely useless in an advanced tool for technical work. FFS.

"But there's a plugin that restores the old UI!"

Well, thank fsck for that.

<enable old UI>

Ah...

(Seriously, UI designers: tools for engineers shouldn't try to look like phone apps or whatever else you're modelling your "no menus and almost no buttons and hey isn't negative space great in everything" designs on.)

#flat #FlatDesign #SaveUsFromDesigners #designer #UI #UX #CADT #tool #technical

@qwertzuiop

That was the one I was thinking of. Though I now see someone has added a please-revert comment, because of course someone has added a please-revert comment.

#CADT

ObNote...

Every Implementer of "web board" software ever: "Hey, we use a Postgres or MySQL database, and I know how to use the LIKE operator, so we can implement search ourselves! How hard can it be?"

<facepalm>

Doing it badly is very, very easy. Doing it well is not.

And they still do it.

<shrieks into void>

#WebBoard #forum #discussion #web #CADT

@tamas

It sounds like a close relative of, if not an actual instance of, the CADT open-source development model.

https://www.jwz.org/blog/2003/02/the-cadt-model/

#jwz #CADT

The CADT Model

In February 2003, a bunch of the outstanding bugs I'd reported against various GNOME programs over the previous couple of years were all closed as follows: Because of the release of GNOME 2.0 and 2.2, and the lack of interest in maintainership of GNOME 1.4, the gnome-core product is being closed. If you feel your bug is still of relevance to GNOME 2, please reopen it and refile it against a ...

As a #developer of various open-source/Free Software projects, I feel entitled to #bitch about this kind of #stupidity.

A #program I've used for many years, after upgrading to Debian Bookworm, now emits this every time it is invoked from my backup #scripts:

> WARNING: this command line interface is deprecated and will disappear, start
> using the new one as described with '--new --help'.

Yes, by all means, completely backward-incompatibly change the #UI. Don't add a new, different one. #CADT

@mcc I know this isn't what you're interested in hearing, but that's basically the reason why I stick to Debian, X11 and a barebone window manager (awesomewm). It avoids most of the issues related to the #CADT model
https://www.jwz.org/doc/cadt.html
that is sweeping Linux in an effort to “modernize” it (= make it more palatable to corporations without actually fixing the underlying issues, and creating more), at the cost of some friction which, for me, is WAY less effort than fighting the news mess.
The CADT Model

Today for some reason I have an uncontrollable urge to remind everyone on the Internet about @jwz immortal words

https://www.jwz.org/doc/cadt.html

#CADT

The CADT Model

I am a +1 on celebrating achievements when they are one.
2+ years to migrate part of an app to #React Native, for example, is not one of them: https://shopify.engineering/migrating-our-largest-mobile-app-to-react-native.

It is a perfect example of the #CADT-model (https://www.jwz.org/doc/cadt.html): people rewrite because fixing it is not fun.

Migrating our Largest Mobile App to React Native

In 2020, we announced that React Native is the future of mobile at Shopify. As part of that journey, we’ve been migrating Shopify Mobile (our largest app at 300 screens per platform) from native to React Native. Here’s how it’s going.

Shopify

“We all need to start being forthcoming about just how shockingly buggy and incomplete most of the #JavaScript tooling is across the board.

“I don't hate JS. I don't hate frontend engineering, and I don't hate Node. What I hate is developer tools with awful DX due to hacks upon hacks upon endless modules of widely-varying quality as a result of constant churn.”

#FreeSoftware #CADT #CriticalInfrastructure

https://dev.to/jaredcwhite/the-shocking-immaturity-of-javascript-c70

The Shocking Immaturity of JavaScript

Do code newbies realize just how shockingly buggy and incomplete all the tools they use really are?