Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Wavvy – web-based audio editor (Audacity port)

wavvy.app

Post reply on HN
Print view View original

91–100 of 115 posts

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#91

Post by xnxn »

tuckerpo wrote: post #81
lukasb wrote: post #62

Earlier quoted context omitted.

I'm surprised at the pushback against ClawsOnPaws here. Why would you not want to make your apps usable by as many people as possible?

I'd be interested to see the man-hours-needed : people-helped ratio when it comes to user accessibility. There's certainly a threshold where it simply doesn't make sense to put in a man year's worth of work to cater to a proportionally very small percentage of the population.

I'd like to politely challenge your assumption that accessibility concerns are relevant only to a "proportionally very small percentage of the population". It's a common myth in this space.

Disabled people represent between 10% and 20% of the world population, and that's not even including those who don't identify as disabled but would nevertheless benefit from more accessible technology. If you've ever adjusted the text size in your browser or enabled captions while watching media, this group includes you.

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#92

Post by 0xedd »

ahilss wrote: post #71
xd1936 wrote: post #33

Earlier quoted context omitted.

I think this was tongue-in-cheek. Nobody would actually want to take a native C/C++ Audacity, port it to WASM, and then wrap it in Electron to make it a "desktop app" again.

On the M1 Mac I actually measured lower CPU usage during audio playback on WASM compared to the native desktop version which uses Rosetta. I'm not sure if the slowness is due to Rosetta or a performance bug on the Mac port.

Niche hardware popular in the US alone? Mild shock.

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#95

Post by sitkack »

lelanthran wrote: post #55
sitkack wrote: post #34

Earlier quoted context omitted.

It would give you safety properties that native Audacity doesn't have. It would also make distribution much easier.

> It would give you safety properties that native Audacity doesn't have. It would also make distribution much easier. Has Audacity ever had safety issues in the past? Because it sounds like you'll be going to a lot of effort to prevent a problem that had never surfaced in over a decade of use.

Audacity segfaults all the time when I use it. Don’t make it sound like it is more stable than it really is. Security bugs are a subset of bugs, of which Audacity has many.

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#96

Post by greggman3 »

ClawsOnPaws wrote: post #38
antoineMoPa wrote: post #23

This is awesome, and also awesome is this: > I originally developed a WASM port of wxWidgets I had some fun looking at the commits here[1] and I can imagine a lot of classic wxWidgets apps are going to be ported to wasm now. Congrats, that a lot of dedication! [1] https://github.com/wxWidgets/wxWidgets/compare/master...ahil...

I feel like I should preemptively apologize and I'm really not trying to knock the project in any way, and the achievement is pretty epic, but those who have seen my username on this site before know what's coming, especially in regards to people seriously considering using WX Widgets on the web... This app is inaccessible. Audacity on its own is already a bit difficult to use with a screen reader, but sadly, this po…

It's not just accessabilty, nothing but English works. Even the keyboard doesn't work as it's hardcoded to keycodes so click the top of the track and click "Name..." and try to enter é and nope let alone 音

I'm not trying to knock the app or the work put into wxWidgets. But, we need to not regress in supporting the entire world and not just the English speaking subset. I don't really want to go back to the 80s/90s. I like that in general, with HTML, international text input/editing just works.

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#97

Post by pseudalopex »

greggman3 wrote: post #96
ClawsOnPaws wrote: post #38

Earlier quoted context omitted.

I feel like I should preemptively apologize and I'm really not trying to knock the project in any way, and the achievement is pretty epic, but those who have seen my username on this site before know what's coming, especially in regards to people seriously considering using WX Widgets on the web... This app is inaccessible. Audacity on its own is already a bit difficult to use with a screen reader, but sadly, this po…

It's not just accessabilty, nothing but English works. Even the keyboard doesn't work as it's hardcoded to keycodes so click the top of the track and click "Name..." and try to enter é and nope let alone 音 I'm not trying to knock the app or the work put into wxWidgets. But, we need to not regress in supporting the entire world and not just the English speaking subset. I don't really want to go back to the 80s/90s. I…

Other wxWidgets apps don't have this problem.

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#98

Post by dark-star »

tuckerpo wrote: post #81
lukasb wrote: post #62

Earlier quoted context omitted.

I'm surprised at the pushback against ClawsOnPaws here. Why would you not want to make your apps usable by as many people as possible?

I'd be interested to see the man-hours-needed : people-helped ratio when it comes to user accessibility. There's certainly a threshold where it simply doesn't make sense to put in a man year's worth of work to cater to a proportionally very small percentage of the population.

With this same argument, could we please also stop catering to the "special needs" of the LGBTQ+ community? That also affects only a tiny fraction of the population, yet everyone has to live with huge dropdown lists for 25 genders, web forms that ask for "pronouns", and (e.g. in Germany) the "gendering" of every single word?

/S

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#99

Post by mwcampbell »

ivraatiems wrote: post #64
ClawsOnPaws wrote: post #38

Earlier quoted context omitted.

I feel like I should preemptively apologize and I'm really not trying to knock the project in any way, and the achievement is pretty epic, but those who have seen my username on this site before know what's coming, especially in regards to people seriously considering using WX Widgets on the web... This app is inaccessible. Audacity on its own is already a bit difficult to use with a screen reader, but sadly, this po…

I so frequently see this tone with accessibility discussions: "X is not accessible, so don't use it, stop what you're doing, this is bad." I don't think that kind of scolding - which is what it comes off as - is productive for solving the problem of "X is not accessible", because it presumes the problem is unfixable. I believe you wrote your comment in good faith, and I agree accessibility is important. But I think y…

> I don't think that kind of scolding - which is what it comes off as - is productive for solving the problem of "X is not accessible", because it presumes the problem is unfixable.

Of course the problem is fixable. But in the meantime, until it's fixed, a disabled person could fail to get a particular job, or even lose a job they already have, due to an inaccessible application. It's important to remember that the stakes are really that high. If we want to prevent that from happening, I think it's worthwhile to try to persuade application developers to not use inaccessible GUI toolkits, particularly for new projects. We can do that at the same time that we work on making more GUIs accessible.

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#100

Post by mwcampbell »

ClawsOnPaws wrote: post #38
antoineMoPa wrote: post #23

This is awesome, and also awesome is this: > I originally developed a WASM port of wxWidgets I had some fun looking at the commits here[1] and I can imagine a lot of classic wxWidgets apps are going to be ported to wasm now. Congrats, that a lot of dedication! [1] https://github.com/wxWidgets/wxWidgets/compare/master...ahil...

I feel like I should preemptively apologize and I'm really not trying to knock the project in any way, and the achievement is pretty epic, but those who have seen my username on this site before know what's coming, especially in regards to people seriously considering using WX Widgets on the web... This app is inaccessible. Audacity on its own is already a bit difficult to use with a screen reader, but sadly, this po…

> I feel like I should preemptively apologize

You should not. A mentor once told me that we disabled people tend to apologize too much. You are right to point out the problem of accessibility in this context, despite the negative responses you've received.

Of all the GUI toolkits with wasm ports, IMO wx is the most amenable to using native HTML controls rather than doing everything with canvas. I'm sure that kind of port would take more work though.

Post reply on HN