It would be nice if the examples included an integration with an existing game engine. Game scripting is a very common use case for those languages.
Cyberscript
11–20 of 65 posts
Re: Cyberscript
#12This is by far the most stupid name for a new language imaginable. Shortening it to "cyber" on the landing page too.. When will devs learn that being able to search for a term on the open internet without having it polluted by normal language is kind of important
Google's Go has made finding info on the ancient Chinese board game generally referred to in English by its Japanese name Go difficult. This has has interestingly lead to increased use of its original name Weiqi or its Korean name Baduk.
The Japanese name is actually 囲碁 (igo). 碁 (go) is just an abbreviation; I don't see it often in Japanese text, but for some reason the Anglosphere decided to adopt it.
囲 is a simplification of 圍, and 碁 is a Japanese-specific letter that roughly maps to 棋. If you read 圍棋 in Chinese, you get weiqi.
Re: Cyberscript
#13This is by far the most stupid name for a new language imaginable. Shortening it to "cyber" on the landing page too.. When will devs learn that being able to search for a term on the open internet without having it polluted by normal language is kind of important
Devs will never learn this because naming languages after common words is exactly the PL dev culture. It's not important to pldevs because they know the median number of users for a pl is 0, large companies know they can buy the search results, so names are chosen for reasons other than SEO.
People get around it by appending "-lang" or "-script" to the name and that solves the SEO.
Re: Cyberscript
#14My gripe with new languages like this is that strings are always UTF-8 and that makes it needlessly difficult to parse HTTP headers correctly. This has led to vulnerabilities in the past.
I disagree. UTF-8 is the right default. Pure ASCII strings are rarely needed in modern software. Unless you know that you need ASCII, your strings should support unicode.
Re: Cyberscript
#15My gripe with new languages like this is that strings are always UTF-8 and that makes it needlessly difficult to parse HTTP headers correctly. This has led to vulnerabilities in the past.
I agree. At this point scripting languages should have native support for string subtypes with custom charsets (ascii/utf16) or just regexp-defined or even ENUM()'erated values. IIRC historically on Windows, a string was UTF16, on unix it was ASCII; nowadays everywhere it's UTF8 without a way to specifically limit what goes into a string. For example UTF8 opens the door to homoglyph attacks and various other things (…
Homoglyph attacks and RTL work just as well in UTF-16. UTF-8 and UTF-16 are different character encodings for the same character set (Unicode).
That being said, Windows permits unpaired surrogates in its "UTF-16" strings, even though that is not actually valid UTF-16. Similarly, many Linux APIs accept arbitrary bytes, not just valid UTF-8.
Re: Cyberscript
#16Earlier quoted context omitted.
I agree. At this point scripting languages should have native support for string subtypes with custom charsets (ascii/utf16) or just regexp-defined or even ENUM()'erated values. IIRC historically on Windows, a string was UTF16, on unix it was ASCII; nowadays everywhere it's UTF8 without a way to specifically limit what goes into a string. For example UTF8 opens the door to homoglyph attacks and various other things (…
Homoglyph attacks and RTL work just as well in UTF-16. UTF-8 and UTF-16 are different character encodings for the same character set (Unicode). That being said, Windows permits unpaired surrogates in its "UTF-16" strings, even though that is not actually valid UTF-16. Similarly, many Linux APIs accept arbitrary bytes, not just valid UTF-8.
Of course. I was trying to say that it would be nice to limit certain variables to an ASCII charset, or ASCII+umlaut+accents without any of the 10k other UTF8 shenanigans.
Re: Cyberscript
#172022-2023 on the bottom of the main page, last release from 2023 & most recent commit from 8 months ago... seems almost dead to me
Re: Cyberscript
#18Interesting concept I guess. But the website reads like poorly AI generated code. No information as to what the grey and orange bars mean, overlapping text and such.
Re: Cyberscript
#19Great you came up with a compiler and some syntax.
What libraries exist.
What's package management system.
How does it interop with existing code?
Is there a JSON parser, an XML parser? Crypto algorithms? Database drivers?
People who invent languages from scratch inherit the technical debt of recreating the entire software ecosystem.
It looks like they are just pulling from the internet at the top of source files:
`use rl 'https://mycdn.com/raylib'`
Good luck with securing that. At least JavaScript has the sense to put it all in a single config file.
Re: Cyberscript
#20Interesting concept I guess. But the website reads like poorly AI generated code. No information as to what the grey and orange bars mean, overlapping text and such.
"Showing script time (orange), load time (gray), and peak memory usage."