briancr

6 ms·

1.
by briancr 8mo ago
Yes, multithreading seems to be a consistent theme among the comments.. so I should definitely look into that. Thanks for the comment. (I actually haven’t done much threaded programming myself so this would be a learning experience for me
2.
by briancr 8mo ago
Yes and the simplicity extends to function definitions too, since you don’t have to specify any type info. E.g. f :: { ; print(args) } Brevity is especially nice for inline/anonymous functions. You can definitely use args.num, args.typ
3.
by briancr 8mo ago
“IMO it's pointless to distinguish syntactically between iterating forwards and backwards” — I completely agree. It’s really a compiler-macro limitation that’s preventing me from doing this.. though I don’t have to go that route. I th
4.
by briancr 8mo ago
Also, if someone else has access to the member, meaning that there is an alias to the member, then the reference count should reflect that. Here’s an example: i :: int | 1 reference a := @i | 2 references remove i | 1 reference T
5.
by briancr 8mo ago
No, there are both referenced-based and tracing-based GC routines that will deallocate short-lived objects. Sorry, I was just trying to enumerate the ways memory goes out of scope to show that none of those ways results in an invalid pointe
6.
by briancr 8mo ago
Seconded.
7.
by briancr 8mo ago
Yes very C-like.. One immediate difference is that in these C-like scripting languages there’s a split between definitions and executable commands. In Cicada there are only executable commands: definitions are done using a define operator
8.
by briancr 8mo ago
Yes I like this one. It’s similar and even more C-like, in that it discriminates between classes, class instances, functions, methods vs constructors, etc. (Cicada does not).
9.
by briancr 8mo ago
This one’s Brood VI!
10.
by briancr 8mo ago
Very cool! I’ve never used Kotlin..
11.
by briancr 8mo ago
There’s no multithreading so race conditions don’t apply. That simplifies things quite a bit. There’s actually no ‘free’, but in the (member -> variable data) ontology of Cicada there are indeed a few ways memory can become disused: 1)
12.
by briancr 8mo ago
Yes there are lots of runtime checks.. unfortunately, but I always fork the time-consuming calculations into C anyway so those checks don’t really affect overall performance much. Scripted functions have no set arity, and the same applies t
13.
by briancr 8mo ago
Yeah this is why the syntax is customizable.. maybe it’s not optimal. The example I gave was strange and I’ll have to change it. Not sure what I was trying to show there. The basic syntax is just: for counter in <1, 5> print(counte
14.
by briancr 8mo ago
I know, I was dismayed to find out that there’s even another scripting language called Cicada. The name came when I was living in Seattle and missed the sounds of east coast summer..
15.
by briancr 8mo ago
There’s no multithreading capability built into Cicada. So a given instance of the interpreter only has a single concurrent state, and all C callbacks share memory with that global state. Multithreading would require a C-based thread mana
16.
by briancr 8mo ago
Good questions! The short answer to the first is that the language is interpreted, not compiled, so optimizations are moot. Aliases are strongly-typed which helps avoid some issues. Memory mods come with the territory —- if ‘a’ and ‘b’ po
17.
by briancr 8mo ago
Thanks! I’m unfamiliar with Janet but I’ve looked into the others you listed. One personal preference is that a scripting syntax be somewhat ‘C-like’.. which might recommend a straight C embedded implementation although I think that makes
18.
by briancr 8mo ago
Should have replied directly —- thanks! That’s a great list..
19.
by briancr 8mo ago
To be more specific (see my general comment), I’ve used the language in two open-source projects: 1) a chromosome conformation reconstruction tool, and 2) a fast neural network generator (back end). Re Project 2: I’m also planning to embed
20.
by briancr 8mo ago
Thanks for the references! Writing a language was almost an accident — I worked on a neural networks tool with a scripted interface back around 2000, before I’d ever heard of some of these other languages.. and I’ve been using/updatin
21.
Show HN: Cicada – A scripting language that integrates with C(github.com)
57 points by briancr 8mo ago|35 comments
22.
Show HN: Added visuals to my 1-second neural network generator(cdeeply.com)
1 points by briancr 1y ago|0 comments
23.
Show HN: APIs for quick (1-second) neural network generators(github.com)
1 points by briancr 3y ago|0 comments
24.
by briancr 3y ago
As a newbie I really enjoyed your explanation of the synthesis process and why everybody should Fourier-sum phases rather than amplitudes.
25.
Show HN: Quick (1 sec) neural network builder with architecture search(cdeeply.com)
3 points by briancr 3y ago|0 comments