I think (outside hobbies) new programming language development is basically dead at this point. The major use cases have been filled, and there are more forces than ever towards using a battle-tested language with a massive ecosystem. Further, less and less code is being written or read by humans so the actual language ergonomics matter less than ever to those who would fund new language creation.
This gives me "why build dropbox" energy. We never know when a revelation or unmet customer niche arrives around the corner. Never bet against it.
Cyberscript
51–60 of 65 posts
Re: Cyberscript
#52Re: Cyberscript
#53Re: Cyberscript
#54Earlier quoted context omitted.
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.
Internet Messages have been ASCII since Internet Messages.
Re: Cyberscript
#55This 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
In the 90s/2000s people also used to shorten cybersex to cyber. I guess if they wanted to have fun with it they could add a "Wanna Cyber?" in place of the usual "Try ".
Re: Cyberscript
#56Earlier quoted context omitted.
Internet Messages have been ASCII since Internet Messages.
True, but humans have been speaking non English languages since humans.
It's not like internet standards don't know there are other languages, it's just that they documented how things were done at the time. Some legacy has remained ever since.
Re: Cyberscript
#57Earlier quoted context omitted.
Internet Messages have been ASCII since Internet Messages.
Most internet protocols these days have shifted to UTF-8.
Re: Cyberscript
#58Earlier quoted context omitted.
True, but humans have been speaking non English languages since humans.
The first networked computers predate unicode by several decades. Back then, the word length could be 8 but not neccesarily. All sorts of different encodings existed and a given common standard wasn't yet agreed upon It's not like internet standards don't know there are other languages, it's just that they documented how things were done at the time. Some legacy has remained ever since.
Unicode-aware strings are the right choice for 99% of code. The last 1% should be a special case.
Re: Cyberscript
#59Earlier quoted context omitted.
The first networked computers predate unicode by several decades. Back then, the word length could be 8 but not neccesarily. All sorts of different encodings existed and a given common standard wasn't yet agreed upon It's not like internet standards don't know there are other languages, it's just that they documented how things were done at the time. Some legacy has remained ever since.
Sure, but most code doesn't interact with raw packets. Legacy, ascii-only internet standards probably make up much less than 1% of new lines of code written today. Programming languages should support this use case. But not at the expense of the other 99% of software. Unicode-aware strings are the right choice for 99% of code. The last 1% should be a special case.
You don't need a raw socket to get into trouble. You also don't need a "legacy" protocol.
Re: Cyberscript
#602022-2023 on the bottom of the main page, last release from 2023 & most recent commit from 8 months ago... seems almost dead to me