5 ms·

Been there seen that from the software side too. However it really wasn't that big of a deal. We just re-did the thing in HTML and re-used most of their graphi

Been there seen that from the software side too. However it really wasn't that big of a deal. We just re-did the thing in HTML and re-used most of their graphics. Hardly worthy of a "The No* Movement" title. The part about "you stop talking about it, you stop challenging it" resonates with me. But isn't that the job of whoever's responsible for the website? Can we really blame a file format for that? Let's all try to be a little bit flexible and try to let everyone use the tools they prefer.

ThomPete 13y ago
Who is saying people can't use the tools they prefer? And it's not the fileformat it's the process that leads to delivery of the fileformat that is being challenged as far as I understand it. The argument is not a dictate, it's an argument for why they choose not to do it and some of the problem they think arise when people do it in sofware development.
- marshray 13y ago
  > Who is saying people can't use the tools they prefer? Isn't "the NoPSD Movement" basically referring to Photoshop?
  - ThomPete 13y ago
    Is the Python language really a python? The NoPSD movement is making a point against what 90% of what all designers use. PSD is just used a common reference point.
    - marshray 13y ago
      No, it's a tool. If we went about promoting a "NoPython Movement" in the context of computer programming I suspect that some people would get the idea that we didn't like Python very much. Substitute 'XCF' and 'Gimp' in place of 'PSD' and 'Photoshop' and my point still makes sense.
      - ThomPete 13y ago
        The difference is that 90% af developers do not use python, 90% of designers do use photoshop. So no your point does not stand. All you have done is shown that you either doesn't know anything about the design community or you deliberately don't want to understand what is meant. I am guessing the last.
        marshray 13y ago
        I do understand about the popularity of Photoshop. I know relatively little about "the design community" and am just a bit skeptical that it is as monlithic as some folks make it out to be. Again, my point was simply that in our development process, "asset pipeline", or whatever you want to call it, we ought to be a bit flexible to let professionals use the tools they feel they are most productive in. Obviously, sometimes the workflow calls for HTML output. But if there's a brilliant designer in town who only knows how to generate EPS, PDF, or PSD (we've all met them) maybe it's not the end of the world if someone else does the HTML/CSS/Javascript. The tools and the processes exist to serve the talent, not the other way around.
        ThomPete 13y ago
        I don't think you got are getting the point they are making though. It's not about the result of the PSD files, it's about the result of the process of designing for something that isn't a final composition but rather an ongoing process. It doesn't matter whether someone is a brilliant designer. What matters is that the de-facto way most work is creating friction that isn't necessary and is often counter-productive. It's not argument against photoshop or psd, but rather a process philosophy if you like. And for something very specific namely app design.
        marshray 13y ago
        I get it: using bitmap files for an app introduces a big ugly manual process step and so using them as a static master for an app design discourages iteration and evolution. > It doesn't matter whether someone is a brilliant designer. Perhaps we can agree to disagree on that. > What matters is that the de-facto way most work is creating friction that isn't necessary and is often counter-productive. Maybe I've just heard this 'lessons learned from assembly-line manufacturing' applied to design and construction too many times.

ThomPete 13y ago

Who is saying people can't use the tools they prefer? And it's not the fileformat it's the process that leads to delivery of the fileformat that is being challenged as far as I understand it. The argument is not a dictate, it's an argument for why they choose not to do it and some of the problem they think arise when people do it in sofware development.

marshray 13y ago
> Who is saying people can't use the tools they prefer? Isn't "the NoPSD Movement" basically referring to Photoshop?
- ThomPete 13y ago
  Is the Python language really a python? The NoPSD movement is making a point against what 90% of what all designers use. PSD is just used a common reference point.
  - marshray 13y ago
    No, it's a tool. If we went about promoting a "NoPython Movement" in the context of computer programming I suspect that some people would get the idea that we didn't like Python very much. Substitute 'XCF' and 'Gimp' in place of 'PSD' and 'Photoshop' and my point still makes sense.
    - ThomPete 13y ago
      The difference is that 90% af developers do not use python, 90% of designers do use photoshop. So no your point does not stand. All you have done is shown that you either doesn't know anything about the design community or you deliberately don't want to understand what is meant. I am guessing the last.
      - marshray 13y ago
        I do understand about the popularity of Photoshop. I know relatively little about "the design community" and am just a bit skeptical that it is as monlithic as some folks make it out to be. Again, my point was simply that in our development process, "asset pipeline", or whatever you want to call it, we ought to be a bit flexible to let professionals use the tools they feel they are most productive in. Obviously, sometimes the workflow calls for HTML output. But if there's a brilliant designer in town who only knows how to generate EPS, PDF, or PSD (we've all met them) maybe it's not the end of the world if someone else does the HTML/CSS/Javascript. The tools and the processes exist to serve the talent, not the other way around.
        ThomPete 13y ago
        I don't think you got are getting the point they are making though. It's not about the result of the PSD files, it's about the result of the process of designing for something that isn't a final composition but rather an ongoing process. It doesn't matter whether someone is a brilliant designer. What matters is that the de-facto way most work is creating friction that isn't necessary and is often counter-productive. It's not argument against photoshop or psd, but rather a process philosophy if you like. And for something very specific namely app design.
        marshray 13y ago
        I get it: using bitmap files for an app introduces a big ugly manual process step and so using them as a static master for an app design discourages iteration and evolution. > It doesn't matter whether someone is a brilliant designer. Perhaps we can agree to disagree on that. > What matters is that the de-facto way most work is creating friction that isn't necessary and is often counter-productive. Maybe I've just heard this 'lessons learned from assembly-line manufacturing' applied to design and construction too many times.