tr1ll10nb1ll

my bad, try out at wav0.app/daw

Recently talked to the founder of wavtool (acquihired by Suno which probably accelerated their work on Studio) and from my understanding, their overarching goal is to reduce to the time from concept to actual production. faster workflows, in other words.

I produce music as well on the side and I can assure you things like making beatpacks, finding the exact sound are non-trivial at times and a unified interface that lets me go fast asf without losing expression is vital.

I'm making my OSS version of this (faster than ffmpeg.wasm tho) called WAV0 - github.com/fluid-tools/wav0

Footer. also Jekyll/Hugo sites use generator so you can mostly find it in the meta generator tag.

Next.js sites are also a super easy find like this.

unrelated probably, but it made me realize how I don't really see Hugo/Jekyll type websites anymore.

Inflammatory comment imo (or perhaps meant to be humorous). Either way, every developer you interact on DevClad with is approved manually. The factors used to manually approve a profile include a history of building side-projects or employment as an SDE at a company. This is the reason there's a 2-step onboarding process before you get to use DevClad.

This is so on point. I've thought about this a lot and it's definitely something I will aggressively pursue if I manage to have good engagement initially.

The preliminary step before pursuing this would be allowing users to work on projects and hackathons (or at least, showcase projects better) on DevClad.

I'll try replicating it.

Update: It's a possibility you didn't hit Save on Step 1.

Fair point.

Two things.

1. The page mentions:

  Github is only for login. To create an account, go to Signup.

2. It's completely optional to connect it. The reason it asks for all those permissions is because I'm planning to use it to integrate common Github actions in DevClad. Again, you don't need to do any of that. Optional.

From the POV of a marketing copy, I don't think that sticks. I could possibly change it on the Github, however. Or, elaborate on what is meant by an ML algorithm in the context of DevClad.

It indeed is. I'll try to find someone better at ML than me over time but I think this approach should serve well at least for the first 1k users or so if I'm not wrong.

You might be much more experienced than me so feel free to discard my suggestions if you objectively know you're right.

However, I would strongly disagree with you on the part about it not being suitable for complex applications.

If you feel that way, you can choose to have a decoupled backend (which is what I do with Django) or go all in with full-stack integrations (tRPC in conjunction with edge functions) on top of Next.js.

I have seen great apps built with both of those ideologies.

Imo, makes it the best bet for building anything.

There's still a new JS framework everyday but if you ignore all that noise and for production-quality software just have a look at React and the most popular meta framework on it, Next.js, you'll be more than alright.