51–60 of 124 posts
Just saying: in Flanders, 'janet' or 'jeanette' is an offensive slur for a homosexual man.
In Flanders, people think they speak much better English than they do. Janet and janet are pronounced differently.
I wonder how many users these sort of languages have, aside from its creators and perhaps the company where it has been born. There are tons of embedded languages, many with libraries and all sort of utilities, why should someone invest themselves in such languages with all the risk it takes?
Problems such as: additional build steps, security, ecosystem, train employees and maintainers into new languages, additional maintenance barrier, etc
Earlier quoted context omitted.
How Lua is viable in embedded? You mean microcontroller/low-level programming right?
Embedded is a fuzzy category, specs range from Lua is extremely lightweight and portable. The interpreter doesn't exceed 500 kb in the fattest build, and the used dialect is a strict subset of ANSI C that is equally comfortable running on mainframes as on Nintendo consoles. In short : If it has a C compiler and can spare 300 kb ram, it can run Lua. So people sometimes use it there.
Depending on the context, "embedded systems" go even larger, although usually people stop calling it "embedded programming" at some point. Obviously many problems in large embedded systems are different from small ones, but others remain similar.
I was a donator to Janet for a little while and then eventually stopped. I think it would be a great programming language if it arrives 5~10 years earlier. Highlights to me are: green thread, TCO, easy distribution, great interop with C, flexibility of choosing between imperative vs immutable data structures. However, I just couldn't find a good use case for it. For embedded programming, I would always choose Lua if…
How Lua is viable in embedded? You mean microcontroller/low-level programming right?
I was a donator to Janet for a little while and then eventually stopped. I think it would be a great programming language if it arrives 5~10 years earlier. Highlights to me are: green thread, TCO, easy distribution, great interop with C, flexibility of choosing between imperative vs immutable data structures. However, I just couldn't find a good use case for it. For embedded programming, I would always choose Lua if…
How Lua is viable in embedded? You mean microcontroller/low-level programming right?
Earlier quoted context omitted.
It’s not like they are trying to sell anything. And who cares what your CTO wants to adopt? Some people simply enjoy computers and are not looking for external validation. Spin up your jvm/.net bloatware and code yet another CRUD application and leave us alone.
The way people are coming out of the woodwork to aggressively dismiss someone asking about why they would use Janet over other alternatives makes it pretty apparent that there is nothing novel about this language, no reason to learn yet another scripting in a sea of choices, and a lot of over-invested individuals. You people are everything wrong with tech.
The thing you fail to understand is that we aren’t in this for the money or the validation or the status. We simply like fiddling with computers, languages, etc.
Computers were my hobby way before they were my job.
Is this how "the good place" is built and run?
What is with new programming languages with women's names? It seems a bit cringey to me, like the guy in my first-year cs classes who would name variables after his girlfriend.
If you name it after men you get even more problems.