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

FYI your "Try Live Demo" link 404's.

my bad, try out at wav0.app/daw

How do you even know? Don't those both just generate static html?

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.

You can trivially remove it e.g. `disableHugoGeneratorInject = true` in `config.toml`.

It says "Powered by Hugo" at the bottom of the page.

Depending on the theme.

I build my own themes and don’t include that either

Same here

I build my own with Jinja2 templates my custom python script + mistune library to parse markdown to html, and a YAML file in similar format to Hugo (the previous generator i used to use)

I found building my own custom one with python3, much more freeing in all sorts of interesting ways, I also exposed the static site generator with a FastAPI based API to auto build my website from my notes, my cooking recipes, database records, financials, git commits, etc to build me a private protected website (via nginx auth) from anywhere, whether via sending a text message to my telegram bot, or running a Shortcuts command on my iPad, or just directly running a command from my terminal.

It took barely a day to setup, and allows me to run interesting custom extensions in all sorts of interesting ways, and builds me a personal website curated to my interest, where the primary viewer is supposed to be me. and it exposes a public barebones website with barely any content for everyone else.

One of these days I think i’ll expose more of it to the world.

I see plenty of blogs generated from Markdown with tools like that.

Has something overtaken Hugo and Jekyll in that space?

If you like JS/TS, then Astro.

I maintain a blog on Hugo but also host a couple of Astro ones. I think Hugo is great but to my eyes at least Astro has more active development behind it, and I also enjoy it more (probably because I know Typescript more than golang)

I just use mkdocs for everything.

Have you found a decent bare bones starter theme? I've been using MkDocs Material, and I find the theme too complicated (HTML etc) - hoping to find a super simple one that looks decent - plain - and is a good base for theming / styling. Thanks & take care.

I use the readthedocs theme: https://www.mkdocs.org/user-guide/choosing-your-theme/#readt...

Not sure if that fits the bill for you, but I like it.

This looks interesting - thank you!

We use Github to Jekyll to host a few websites. Works awesome.

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.

I also had a problem. Figured it out by submitting with dev console open and reading HTTP response. There were no messages for errors: required fields, pronouns had a min lenght and stuff like that.

Really like the idea and willing to try it out. Hope it works well. Good luck.

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.

Thanks. I was imagining it'd use information from your GitHub account to match you better.

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.

maybe just say “similarity” rather than “ml algorithm” since that is what you are doing

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.

> you are matched with another dev using an ML algorithm

Could be simplified to just:

> you are automatically matched with another dev

Fair point.

Similar. I took that as a starting point for the developer niche and I plan on turning it into something where developers can work on ideas together.

I built an even more rough version of that here - https://connectdome.com (but then I realized I was dealing with feature-bloat) so now I'm experimenting a little slower.

*> connectdome.com

OT, but that's an expertsexchange kind of domain...

is connectdome still up and running or is it a dead project at this point?

might wanna try it and compare to this one

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.

Next.js is not a good general purpose React framework. It is good for static sites with sparse dynamic pages but nothing more complex. And the documentation is still woefully inadequate.

Don't be like me, choosing to build an entire app on Next.js and hating every moment of it after the honeymoon period ended 2 weeks in. Live and learn.

Hey there, I'm on the Next.js team. Sorry about this experience. I would argue Next.js is a general purpose React framework – we enable you to take advantage of all the latest React features. Apologies if there was a gap in the documentation. Could you share more so we can improve? You can also email lee at vercel dot com.

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.

What do you recommend instead (or are looking at)?

Sorry, I wouldn't know. I got out the frontend world after that experience, and I don't think I've seen any solid answer yet.

Can I ask how long you ended up using Next for? Did you quit frontend dev after 2 weeks, or only after working through the challenges etc.?

My Next honeymoon has been going on for a couple years now, and I think it's an AMAZING developer experience compared to anything I've worked with before (Perl/PHP/Laravel/Symfony/Angular/jQuery/React)... it's the framework that made me choose to specialize in frontend because it was so nice. What didn't work for you?

I designed and led that project for 3 years. The technology choice was mine, so it was a learning experience. Frontend was something I did alongside the rest of the stack, but I've seen so many terrible libraries by inexperienced developers come and go post jQuery, I actively avoid frontend-focused roles now.

> I've seen so many terrible libraries by inexperienced developers come and go post jQuery, I actively avoid frontend-focused roles now.

I don't blame you, heh. Every year I feel like the fragmentation is getting worse, not better. It's fun for a while, but makes it really hard to plan for long-term stability and maintainability. It's likely anything I write today will be unusable in 2 years.

I am still annoyed I took the time to learn Webpack and its overly complex configuration a few years back, and the world has already forgotten all about it. There definitely is the feeling that learning a new frontend library is a terrible use of your time.

He makes a lot of valid points. But he seems to be a Bitcoin maximalist, there’s clear bias especially where he refers to Vitalik as a scammer.

Yeah, stopped reading at exactly that moment.