Live data from Hacker News

Penpot: The Open-Source Figma

github.com

141–150 of 213 posts

Re: Penpot: The Open-Source Figma

#141
post #131
post #68

Earlier quoted context omitted.

For now. Mattermost too used to be cheaper than Slack, and Gitlab too used to be cheaper than GitHub. I know the story, "look we did X, the open-source Y" and two years in you now have two versions, the free and the "enterprise" one with exclusive features.

That's the beauty of the open source, self-hosted option then, no? If they radically change pricing one day, pick up your ball and self-host without any limits.

And that's exactly why they don't do radical changes, because people hate those. They do slow, small and insidious changes over a long time period. And then it isn't as easy to simply "pick up your ball" and be on your way.

Re: Penpot: The Open-Source Figma

#142

Earlier quoted context omitted.

At the time i wasn't sure if it was PEBCAK, which is why i started a discussion in the forums. As there were no replies, i received no notifications, and so I forgot all about it. If anyone is interested in opening a bug report you can see the issue here: https://imgur.com/a/hZ1ja9o

Personally, I do not understand why you think there is a bug from this screen capture alone. Maybe because I am that familiar with penpot and figma, but still, I do not find it obvious. This is why it's important to describe explicitly the three points in text: - steps to reproduce; - what you expected to happen; - what actual result you observe instead. Something that might be obvious to you but isn't for others wil…

> I swear I did not see the change in button width before reading the linked comment.

I didn’t either! I stared at that gif for a few minutes and I couldn’t tell what the problem is (or what to look for). It wasn’t until you said “changing button width” I knew where to focus my attention.

Re: Penpot: The Open-Source Figma

#143

Earlier quoted context omitted.

Personally, I do not understand why you think there is a bug from this screen capture alone. Maybe because I am that familiar with penpot and figma, but still, I do not find it obvious. This is why it's important to describe explicitly the three points in text: - steps to reproduce; - what you expected to happen; - what actual result you observe instead. Something that might be obvious to you but isn't for others wil…

> This is why it's important to describe explicitly That is a fair point. I will take it on board when giving people screenshots and videos of bugs in future. > I did not see the change in button width There's actually a lot more visual changes than that just the button, but I will leave that to the reader as an exercise in spot-the-difference ;)

> There's actually a lot more visual changes than that just the button, but I will leave that to the reader as an exercise in spot-the-difference ;)

This is fair. But issues like this will never get my attention in general because I don’t have time to do this exercise - I would much rather have it all spelled out. Even if there are a bunch of related issues they won’t get fixed in a single PR, it likely will be multiple.

I guess my point is that if you really want OSS projects to improve, the issue submitter can’t just ask the maintainer “figure it out”. It totally works this way in the corporate world though (IME).

Edit: I’m sorry to have jumped to conclusions. Leaving my comment up for accountability.

Re: Penpot: The Open-Source Figma

#147

Earlier quoted context omitted.

I think it would help to open an issue on github making explicit the following three points explicit in the report: - steps to reproduce from scratch; - what you expected to happen; - what you actually observed (include the screenshot or video capture in addition to a textual description). Otherwise, you might risk your report being ignored due to a silent misunderstanding about the mismatch between your expectations…

At the time i wasn't sure if it was PEBCAK, which is why i started a discussion in the forums. As there were no replies, i received no notifications, and so I forgot all about it. If anyone is interested in opening a bug report you can see the issue here: https://imgur.com/a/hZ1ja9o

"Content not available in your region"

So, given that Penpot appears to mostly be developed in the EU, you'd need to fix that part first.

Re: Penpot: The Open-Source Figma

#149

Earlier quoted context omitted.

> This is why it's important to describe explicitly That is a fair point. I will take it on board when giving people screenshots and videos of bugs in future. > I did not see the change in button width There's actually a lot more visual changes than that just the button, but I will leave that to the reader as an exercise in spot-the-difference ;)

> There's actually a lot more visual changes than that just the button, but I will leave that to the reader as an exercise in spot-the-difference ;) This is fair. But issues like this will never get my attention in general because I don’t have time to do this exercise - I would much rather have it all spelled out. Even if there are a bunch of related issues they won’t get fixed in a single PR, it likely will be multi…

[deleted]

Re: Penpot: The Open-Source Figma

#150

With the integration of AI, people are using Figma for more than just design. A recent use-case that a friend was gushing about: - Input notes, data into Figma and ask its AI to summarize it into presentation worthy slides with built-in games to keep meeting members engaged, and host them to a website.

What? That’s crazy.
Post reply on HN