Programming

17398 readers

107 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Welcome to the Chata programming language (github.com)

submitted 10 months ago by bachatero@lemmy.world to c/programming@programming.dev

6 comments fedilink hide all child comments

Hi everyone, this is a little project I've been working on. Chata is a programming language that's just for DSP or Digital Signal Processing.

DSP is the core technology behind a lot of fancy things like noise cancelling headphones, medical radiology equipment, and other advanced mathy things like that. Unfortunately, it's hard to deal with unless you want a barrage of bespoke, often closed-source tools and libraries.

The idea behind Chata is to get rid of everything you don't need for DSP in order to make it easier and freer to do awesome stuff with DSP. If you're wondering where I got the motivation to do this, just scroll to the bottom or look at my Lemmy username!

you are viewing a single comment's thread
view the rest of the comments

[–] Paragone@lemmy.world 5 points 10 months ago (1 children)

Y'all say that like it's a bad thing...

: P

_ /\ _

[–] Paragone@lemmy.world 3 points 10 months ago

It looks like you're considering different programming-paradigms, and I'm asking you to consider having a toggleable set of modes, so something which needs ( for whatever reason ) to be in a particular paradigm, .. can be in that paradigm.

Functional, imperative, whatever.

Make it like radiobuttons, from the user-perspective: modal, with a declarable project-default, and variances declared on a per-file basis.

THIS file needs to be THIS paradigm, e.g...

( functional overall, imperative for the tricky-to-make-fast/efficient bit, as 1 possible example: eradicate many bugs & put performance where it needs to be. )

just an idea from somebody whose been working on cracking what the proper minimal-set of maximally-orthogonal programming languages requires, for a decade or 2...

Salut, Namaste, & Kaizen, eh?

_ /\ _