Live data from Hacker News

Beads: Computer language and toolchain

beadslang.org

181–190 of 235 posts

Re: Beads: Computer language and toolchain

#181
post #177

Not really a technical comment but this is the first time I've seen language syntax written down with graphs in documentation. I honestly would've preferred text but it is interesting. What tool did you generate them with?

The syntax diagrams are from a handy free web service at this link: https://www.bottlecaps.de/rr/ui#nonterminal

Re: Beads: Computer language and toolchain

#182

Is there a good tool in the same space? I'd love to have something _simple_ to develop quick-and-dirty desktop applications. RN does not qualify as "simple".

Beads can generate desktop and mobile, however 99% of the users so far are just wanting to make web apps so i spend 99% of the time working on improving the web side and client/server output mode.

Re: Beads: Computer language and toolchain

#184

Is the manual a PDF file? No HTML pages? That was getting already old in the 90s. No Linux version. Maybe is it a language only for GUI apps?

PDF prints well, and has nice search features, and has a nice zoom feature to accommodate people of different visual acuities, which the web does not always do well. This is the first time i have ever seen anyone prefer the web. Maybe if i put a table of contents in the PDF that would help.

There are some people reporting that the Windows .EXE runs okay under Wine in Linux, but yes it would be nice to support Linux desktop natively.

Re: Beads: Computer language and toolchain

#185

Earlier quoted context omitted.

> You have an embedded graph database? Why? This is just a symptom of developers general disrespect for the depth and complexity of databases. I disagree. This is a recognition of the fact that the line between database, programming language, and operating system is very blurry. It's not that the programming language has a graph database tacked on, it's that the language is a database and leverages that fact to provi…

If you use an external database you are not going to get time travel debugging, nor will you have a perfectly uniform internal representation of values. Beads has a primitive type of physical units of measure, so you can store 3 Newtons which internally will be stored as the magnitude 3 plus an array of fundamental units with their exponents. This datatype is not found in MySQL, so external databases work okay as lon…

I think I mentioned the time travelling debugger part of beads earlier. Having built a time travelling debugger a few years ago in clojurescript I immediately understood that this would be the killer feature of beads (for me at least). I do also realise that a lot of the comments here are attacking the author of beads or the initial presentation based on the website. This means that people either like a good flame war or that they need to dig further into the product, which is quite solid. Anyway fixing the home page of beads and the messaging of beads is probably one of easier things to fix , compared with making beads itself

Re: Beads: Computer language and toolchain

#186
post #139

Earlier quoted context omitted.

The protected arithmetic rules in Beads are mostly a copy of the proven-to-be-useful protected arithmetic of Excel. Instead of using #UNDEF and #ERROR, those 2 meta values, are abbreviated U and ERR in Beads. ``` 3 * ERR yields ERR 3 * U yields U (3 times undefined yields an undefined value) ``` The mathematical truth tables are in the appendix of the reference manual. It is quite useful in a language to have a unive…

Doesn't honestly seem that different from 'undefined' and 'NaN' in javascript and I think the fact that your 'NaN' is called 'ERR' is making people who think of errors as exceptions recoil. (I'm not necessarily sure I like the trade-off you've chosen here, but I think the viscerally negative responses people are having are because of that, rather than thinking through the trade-off on its own merits)

In practice any JS programmer will find that the use of the undefined value is very familiar. In Beads it is abbreviated to U as it is used constantly, because the default value of something in the graph data structures is U.

For symmetry reasons, the error and undefined values work across all types, which cleans up one of the messes in JS, where you have undefined, NaN, null, and goodness knows what else. That we have a uniform error value for nodes is a very minor point; it is almost impossible to generate an error value in the protected arithmetic world of Beads. Square root of -1 is one of the only ways I can think of.

There is no try/except in Beads, there are no exceptions as all functions are total, and all arithmetic closed (like Excel).

Re: Beads: Computer language and toolchain

#187
post #28

Reminds me a bit of Rebol [1] and its close cousin Red [2]. [1] https://en.wikipedia.org/wiki/Rebol [2] https://en.wikipedia.org/wiki/Red_(programming_language)

Rebol and is rebirth Red, is a very concise and powerful language. They are well funded, and will be a force to reckon with going forward. I would say the languages are very different in the sense that Beads is clearly aimed at graphical interactive software, with a layout/drawing/event model built into the language, while Red exists as a systems programming language, a variant customized for building crypto contract…

> They are well funded.

Rebol Technologies went bankrupt, and Rebol is de-facto dead since more than a decade; Red barely manages to get by thanks to a recent crypto spike.

> I would say the languages are very different in the sense that Beads is clearly aimed at graphical interactive software.

So is Red with it's native GUI engine. [1]

> Red exists as a systems programming language, a variant customized for building crypto contracts, and then as a general purpose language.

"Domain-specific languages" is the term you are looking for.

> They are so different that it is hard to compare.

Both share the same goal of replacing modern software practices with biased, batteries-included toolchain, varying only in implementation.

> Red being a concatenative language has more in common with FORTH than Algol.

Red is not concatenative in any sense of the word, nor any other language in Rebol family that I know of.

[1]: https://github.com/red/docs/blob/master/en/view.adoc

Re: Beads: Computer language and toolchain

#188
post #48

- promises far fewer bugs - promises to replace entire stack - ...and Excel - "declarative languages have almost no bugs" - built-in database Yeah color me skeptical. I love experiments, but I prefer those that under-promise and over-deliver. People have been promising unification languages since there were only two languages. People have been promising cross-platform since there were two platforms. And people have b…

Beads does not replace Excel, but it can close the gap between Excel and the popular programming languages, which have a great deal of unnecessary complexity in them. For example, in HTML/CSS/JS, the comment syntax varies between the 3 languages. Why are there 3 distinct languages in one source file? When in history was this ever done? I can remember mixing 2 languages, but 3? that's just ridiculous.

Code which doesn't execute has very few bugs in it in my experience. And those bugs tend to be easier to fix, than say a register clobberation bug in assembly language which i have had to wrestle with before. Telling the computer what to do, but not telling it how, does cut out a lot of effort (and potential errors).

You have every right to be skeptical, but i hope you can overcome your initial skepticism to at least take it for a test drive.

Re: Beads: Computer language and toolchain

#189

I would seriously consider toning down the marketing speak. This project is making very bold claims, without citations, while trying to appeal to an often skeptical crowd (developers). "Graph databases are considered more powerful and modern than relational databases," ... okay? According to what benchmark and for what workloads? A statement like that is an immediate turnoff because it is dismissive of 30 years of da…

Hi, I would like to chime in here on your comment on the marketing speak of the Beads project. I know the author of Beads, and was happy that he gave me a shoutout for my own project, Visual Javascript. Anyway, I have been following this new coding space for a while and I was also the initial angel investor for a project called Eve (the follow up for Light Table) which was an excellent project made by someone called Chris Granger (https://news.ycombinator.com/item?id=12817468). Anyway, I agree that the presentation of the Beads language could be improved massively, but the Beads language itself has some very interesting features, so should not be ignored. I think reading through all the comments on this hacker news thread it would be very useful to know what parts of Beads actually interest readers, and how they would present/market Beads themselves if it was their own project. This could be very constructive. For me personally it is the time travelling debugger that it interesting in Beads. What is it about Beads that you find interesting?

Re: Beads: Computer language and toolchain

#190

Earlier quoted context omitted.

Nope. The guy posts with his real name on YouTube so this is like TempleOS and the creator is non anonymous, quite active on Reddit, and not very young (as if the style of graphics wasn’t a dead giveaway, like a time machine to the early 90s). In any event I engaged with the creator before and what I can say is the conversations are entirely one-sided, in fact some of the most I have personally experienced. Will take…

While I've not interacted with the author, his Twitter and blog opines on all kinds of subjects and has the firm, authoritative tone of an older person who is not exactly ignorant but who doesn't recognize the depth of his own indoctrination, the silencing of the internal critic. He has all the answers already. And, really, that's the only kind of person that could make something of this encompassing but simultaneous…

It reminds me of the bold claims Paul Graham originally made about Arc. This website here is proof that at least something can come out of that, I guess.
Post reply on HN