Sorry to say, but once I realised how euro-centric, and to my ear/eye, latin-centric esparanto is I completely lost interest.
I don't know if anyone has tried, but something which similarly draws influences from the languages that the vast majority of the world speak would be wonderful.
Anyway, the eurocentrism argument, while perhaps true due to the Latin root, seems to be a little bit of a savior complex don’t you think? China itself pushed for Esperanto to be used as a business language internally late last century as I recall.
Who cares if it's European sounding, it's still an interesting language that is relatively easy to learn, even for people from non-romance backgrounds.
What do you find challenging about multiple dispatch? I don't use Julia for my job, so I can't say I've had enough experience to have a strong opinion. MD seems like a valuable tool though.
The guy behind the youtube channel Context Free (about programming languages) made this site that tracks language popularity based on github/stack overflow: https://tjpalmer.github.io/languish
Came here for Zig too. I never programmed anything in it other than hello world stuff. I think the world is waiting for the 1.0 release with complete tooling and package manager and a solid foundation that won't change too soon. I watched talks from Andrew and what this guy and his team is doing is amazing. It's a small team.
Zig is what I thought Rust would be like when I first heard of Rust. I'd love to try Zig for some hobby things but can't get it running on OpenBSD (yet!).
Haskell. I think that more people being familliar with Haskell concepts would be good for programing culture and it would increase the odds of me being able to write Haskell professionally, which is something I enjoy a lot when writing hobby code at least. Having more access to tooling and a bigger eco system would be nice as well.
I'm not a 100% sure about my answer though. For one, I might grow to resent Haskell if I had to use it at work, and there's also a risk that it would be harder to do cool innovative stuff with the language when more big companies depend on it.
At this point, I think it's almost mainstream, and it's still growing fast (and it's getting better, rust-analyzer is really awesome these days, I was there at the beginning, no comparison to today...))
I may be biased, but I think it'll be the next big main language probably leaving other very popular ones behind it in the coming decade (Entry barrier and ease of use got much better over the last couple years, and the future sounds exciting with stuff like this)
Rust. I've been using it for a while, and I've been using more software written in it lately. Stuff you make with it is just better in most ways. In other languages, you have to go above and beyond to make your code fully correct, safe, user friendly, and every trait I value in software. Rust makes those things easy, and so people are more willing to do them, and so things that get made in it are better. Oftentimes it's just a matter of pulling in a crate and adding a few lines of code.
I'm learning Rust at the moment and I too think I have some reservations with its syntax. Most of these reservations come from my strong preference for functional programming over OOP.
I am unsure if I like method-syntax period, even if it isn't inherently OO. Chaining just makes me feel uncomfortable in a way piping doesn't.
Also it seems idiomatic for values of enumerated types to be written Type::Enum, which seems ugly and unnecessary.
I think what you're calling ugly is just static typing. There's no way to make it look beautiful unless you leave the types away, but then you either end up with some kind of dynamically typed looking language by declaring things twice: once with types and then without.
At first glance, sure it would be easier to read, but if you have to look for the types then things get much harder. Either the types will be in comments, on different lines, or in a different file entirely.
It's doubtful you'll find a statically typed language that does a better job. C/C++ look even worse than rust. Go and Zig don't look good either, IMO.
I’m obsessed with an extremely little known language called Grain. It’s not quite ready for production but it has an insanely intuitive functional syntax that I want to use noww.
It's a pity there is not 1 code example on the Front Page. I spent a few minutes trying to find a page with some code and all I found was Why, Why Not, what is different etc and not any code examples so I am out. Look at Zig within seconds I can see if I like the syntax, does it make sense to me. I would love to know what Pony lang looks like. I might like it but it seems like
I would like to see Ada grow. Its clean syntax, rich expressive capabilities, and early error detection by the compiler due to strict typing create a very pleasant experience during development. This year, the language got a new standard. Recently, a package manager and a community index were created. There's an extension/LSP for vscode, etc. Along with great educational materials on learn.adacore.com, it's easy to pick up and start using this language.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: [email protected]
Assembly, which flavor IDK but some RISC architecture.
If everyone spoke assembly the world would be a very different experience. I'm not saying that it would be better or worse, but it'd definitely be different.
I think the problem is that processors can have slightly different instruction sets, possibly less likely with ARM and RISC (Reduced Instruction, after all), and how they interpret bits and jumps (big endian, low endian). Chibi Akumas has a lot of material for learning assembly of various CPUs, including older ones like 68k and 6502, something I'm doing on and off once in a while
Go. I love writing go, its so simple and predictable and the accessability of multithreading and being allowed to create as many "threads" as I want make me feel smart as fuck.
It's a wonderful language, it's general purpose, it's cross platform, and it's open source (Apache license). I wish it was a mainstream language outside the of the Apple universe.
What I love the most is it's so flexible. It's a full featured OOP language, a full featured Procedural language, a full featured Functional language, a full featured declarative language, and you can relatively easily make it work with anything else you can think of.
It also has the best concurrency system I've ever seen - and with high performance computing relying so much on parallel computing these days that's a must and often what I miss the most in other languages.
A lot of other languages do some things just as well as Swift, but Swift does everything really well.
Completely agree. Unfortunately Apple will need to start treating Swift on non-Apple platforms as a first class citizen for it to achieve any sort of wider popular use.
When Lattner left, it was a signal that they were unlikely to ever move in that direction. Since then, I'd say they've moved further away if anything. They certainly made a hell of mess introducing SwiftUI and Combine (though glad to say things have recovered significantly since then).
Super niche, but I wish wren caught on. It's a language very similar to lua, but indexes start at 0. Also it has some cool features too, but mostly the index thing.
Some fun stack-based concatenative language (like Forth or Min) :3 I like playing with odd/new-to-me things that change how I have to approach things in some way. ... Also I wanna find a Forth community I can stand 😅 That or maybe a similar low-level language, I suppose. I was thinking of using it for a project but... eegh. Bleh. Et cetera. Still might, but purely on my own terms I guess.
Also, more Haskell please >:3 Or something else like it. We must spread the glory of FP nerdery @.@ ...And maybe get some more useful (and maintained) packages to work with instead of just kinda having to wonder what even builds any more v.v
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: [email protected]
most of the apps written in Klingon would have the "today is a good day to die" directive, which means no exception handling at all and bringing the whole OS down in glory if needed
An alternative to regex sounds interesting, too bad their site lacks proper examples and, more importantly, side by side examples of equivalent regex, that's the best way to sell such an idea.
I love perl. It feels like I'm just writing exactly what I'm thinking. But then when I go to read it, I get the horrific feeling that jesus christ, this is how I think?!
I've heard of one I don't know the name of that is trying to make it so you can just write the program with natural English kind of like how AI works off of prompts. Having grown up watching Star Trek and seeing how they would "write" holodeck programs by just giving the computer a detailed explanation of the program they wanted to run always made me wish we could do that IRL.
Inform 7 is the closest I'm aware of, for creating text adventure games.
Honestly, I prefer the control that comes with a more syntactically consistent grammar, but I definitely see a use-case for a higher level tool for non-programmers, or for prototyping.
I don't know why you're being downvoted, but this could truly be the future of programming languages. We don't have to manually compile everything to assembly today, do we? Imagine simply using English for pseudocode, with an AI compiler that writes the most performant code.... How much would that speed up development time? Noone would need to know different languages.... The learning curve for programming relatively basic shit would be low.
I dunno, but I've seen a lot of unecessary hate for AI in the left leaning communities....
Syntax has never really be an issue. The closest thing to plain english programming are legal documents and contracts. As you can see they are horrible to understand but that the only way to correctly specify exactly what you want. And code is much better at it. Another datapoint are visual languages like lego mindstorm or LabView. It's quite easy to do basic things, but it doesn't scale at all.
A compiler has mostly fixed rules for translation. The English language often is ambiguous and there are many ways to implement something based on a verbal description.
Programming by using the ai as a "compiler" would likely lead to many bugs that will be hard to impossible to trace without knowing the underlying implementation. But hitting compile again may lead to an accidental correct implementation and you'd be none the wiser why the test suddenly passes.
It's ok as an assistant to generate boilerplate code, and warn you about some bugs / issues. Maybe a baseline implementation.
But by the time you've exactly described what and how you want it you may as well just write some higher level code.