lipstick

When the original is this incredible, why add lipstick?

JS is run on standards compliant VM's things like promises are just lipstick on the callback hell pig.

If their differences didn't amount to more than lipstick-on-a-pig there would only be one mainstream language.

Barcelona and in fact the entire densely populated Mediterranean coast (Valencia, etc.) is also lipstick-red.

But that doesn't mean we can't put lipstick on it!

So for the case of C++ specifically, ABI compatibility is lipstick on a pig.

Not very constructive but am I the only one who thinks that it looks like a giant lipstick?

No amount of lipstick will make a book with a boring plot shine, or a web app that doesn't fill a need, popular.

While nominally better, it would just be like putting lipstick on a pig.

They basically can hold your keys, a credit card, your phone, and maybe some lipstick, and that's about it.

He proposed we work on a project together (lipstick.com) and this ultimately led to acquisition talks.

I don't care how much lipstick they put on the pig, I want free speach.

The "effects" are like putting lipstick on Mona Lisa.

The standard JVM's don't support lightweight threading (like Go's Goroutines)...so yeah while you can do concurrency with callbacks, or "actors" (callbacks with lipstick on), it's not quite the same thing.

"Lipstick on a pig" is a saying that might apply here.

Lipstick.com, created by Reddit for Conde, took advantage of the social aspects of Reddit but was designed with a minimalist geek aesthetic.

Lipstick on a pig doesn't make a cow, you know.