Re:Adobe gives up on web-design product to rival Figma after...
by poisonborz on Wednesday January 31, 2024 @02:13PM
(#39208014)
Graphics is harder. More users means more use cases, needs to work on more platforms, layout and output to work on various resolutions/dpi, GPU/driver dependence and issues. Print, web, UI design, prototyping, photo editing, all wildly different areas, whereas audio is way narrower scope with less or more mature standards background (eg MIDI spec is 1983).
[ Parent
| on HN ]
Re:Adobe gives up on web-design product to rival Figma after...
by PaulDavisThe1st on Wednesday January 31, 2024 @02:44PM
(#39208368)
I don't know how much you know about graphics programming, but this comment is strong evidence you don't know much about audio/MIDI programming.
Re:Adobe gives up on web-design product to rival Figma after...
by mattkevan on Wednesday January 31, 2024 @03:05PM
(#39208660)
I don't know how much you know about audio/Midi programming, but this comment is strong evidence you don't know much about graphics programming.
Re:Adobe gives up on web-design product to rival Figma after...
by PaulDavisThe1st on Wednesday January 31, 2024 @03:11PM
(#39208720)
My comment doesn't say anything about graphics programming, so it's pretty neutral on that particular point.
This dismissal of the complexities of audio programming is fairly common in general (and particularly bad on HN). Remarks about "less data", "less formats", "less demanding" are typical. But throwing in the specific mention of visual resolution as if somehow sample rate and depth are not more or less precise analogs seems like a fairly major red flag.