comis

I do really love Zeplin, and I use it at work since my company prefers Sketch over Figma. It's great if you have to use Sketch.

Most designers use Macs, sure. But just giving a link to product owners, QA, clients, and developers is a whole lot easier than trying to get them to successfully use Zeplin or manually keep track of what static images I've copy/pasted in tickets etc.

Also: I use Mac at work and PC at home. So now you know one designer who uses Figma on PC.

You can use Figma + Zeplin. Maybe have your designer export a design to Zeplin and see if you have the same issues inspecting elements there as well.

It's most likely that your designer just has a messy file. I've never had an issue with the Figma inspector.

I've never used Sketch Runner, but you can search assets in Figma which appears to be 90% of what you're looking for.

1 minute of searching also reveals a plugin called "Figma Walker" which, as the name implies, is an attempt to copy the exact functionality of Sketch Runner.

> “Maine's decision to impose unique burdens on ISPs' speech—while ignoring the online and offline businesses that have and use the very same information and for the same and similar purposes as ISPs—represents discrimination between similarly situated speakers that is impermissible under the First Amendment,” the lawsuit claimed.

I agree. The law should apply to everyone, not just ISPs.

In general I feel that developers are very poor clients. Designers are better off finding freelance work or donating time to a non-profit they care about imo.

I agree, Slack replies are awful. The only chat reply feature I've ever enjoyed was Flowdock's. It doesn't create threads it just connects replies with colors. It's great.

> Robert Skidelsky wrote that fears of technological unemployment were not so much wrong as premature: “Sooner or later, we will run out of jobs.”

You're arguing timeline when that's not what the article is about. A world without work is our likely future, and it's worth talking about.

Your hypothetical either assumes that machines will never be able to be plumbers/doctors/yoga instructors, OR just takes a snapshot of some point in time between now and the eventual future when machines are superior at all work currently done by humans.

The former is incredibly short sighted and the latter doesn't seem super productive to me.

In 2010 this was a reasonable position. Predicting the current absurdity that is Facebook data collection and sales would have been quite the hot take in 2010.

Correct, Contentful is a CMS.

Question for you though: why would you want product/marketing people feebly attempting to create new pages/layouts with some tool when you could just have a React engineer code up whatever they design with ease? I mean I get it, graphic designers and business analysts are cheaper than engineers, but if it takes them 2-3x as long (or more) to do the same job are you really saving any money?

When I was a kid I remember using Server Side Includes (.shtml) to achieve this. It's how I ran my "blog" before blogs were common.

No clue if anybody still does this, but it worked great in 2001.

Flying on a 737 Max and Driving aren't the only 2 ways to travel long distances.

haha

Yea there's plenty of benefits using a truncation library (we're currently using react-lines-ellipsis) over just css truncation. More control over how the truncation happens, callback so you can do more stuff on the condition that truncation has occurred, multi-line truncation as you mentioned, etc etc.

I get the feeling that most of the time when people are complaining about unnecessary libraries they simply haven't personally run into the problem that the library solves yet.