Python and C# for the most part. I'm also putting serious effort towards learning Rust, but I likely won't be able to use it at work. It's a good learning experience, and I can tell that my code after learning basic Rust in C# and Python is better than before.
The "correctness" of my code would probably the greatest single difference I've noticed in my own habits.
For example, I've become very strict with myself about using type hints and relying on appeasing type checkers and such. The way I structure my projects has changed, where I separate functionality from data to a larger degree, mimicking struct and impl where it makes sense to do so. I've pretty much stopped using dict, and rely on dataclasses instead when writing Python. I've given up on forcing everything to be OOP (even C#), which has made my code easier to read and maintain. There are probably other things as well, though I can't list them at the top of my head.
Some of it is probably just good practice, a result of having matured after being exposed to new languages. Some of it probably wouldn't be considered pythonic or idiomatic, but I'm not sure I care anymore. My code is more reliable (and often faster), and that's what matter in the end.
I work with C# & TypeScript, which frankly I don't find too bad
I love to work with Scala though, I find there's a really nice way to do almost everything, and C is nice because it allows so much control over what your program is actually doing - same with OCaml really, however the ability to use Java libraries in Scala makes it that bit better
I'd quite like to try Spatial for hardware in the future
I most regularly use Python, followed by MATLAB C++. Python has been practically mandatory for writing code for my undergrad research. My classmates usually know "a little" Python, and it's pretty easy to pick up on the fly. I'm trying to phase out MATLAB for Python seeing as I'll be graduating soon and my student license will run out. I know about Octave, but work done in Python is probably easier to integrate.
My favorite is C++. It's the first language I learned and it feels like home. It gives me enough abstractions to get actual work done, but it also has the low-level tools I need to shoot myself in the foot for working with Arduino or other microcontrollers.
I'm looking into Rust for audio programming. Although audio programming is done almost exclusively in C++ these days, Rust's safety features without performance penalties look like a promising language to write fast and reliable code suitable for real-time operation. Joining Lemmy and seeing how it compared to Kbin has cemented my interest in the language because so far, despite the bugs I've run into, Lemmy and Jerboa has been fast above all.
My main languages are Ruby and Python (does SQL count?), but I dabble with Javascript when needed.
I have been liking Ruby more and more because of how easy it is to use and the community support it has. I have really appreciated RSpec, and that's the main reason I enjoy it over Python.
I really want to get into Rust because it is so different from Ruby. I am also a strong supporter of adopting a different language if you need to. I am not a fan of introducing types into Ruby or Python because there are other languages that have it built in and also the dynamic nature of those languages are their strengths.
I could see value in adding type checking to a codebase that is transitioning from exploratory to maturity without having to rewrite in another language.
It's not really a coding language but I use SQL a lot for work. Occasionally Python and R. As you can probably imagine with this list, I'm a data scientist.
My favorite to work with is actually autohotkey, which I use to automate stuff, because it can be a fun little challenge to figure out how to automate based on the system it's running on and what I'm trying to do.
At work it's mostly python, .net core and javascript (regrettably).
Personally, I used to write a lot in C and C++ for embedded, but recently diving more into other areas. Developing quite the love for Golang (GO) and it's simplicity.
My favorites right now are Julia & Rust. In their respective fields they're a breath of fresh air and I enjoy coding in them so much. If Carbon ever manages to get off the ground floor I'll be interested in trying it out. Regular C++ has too many footguns
@ericjmorey@beehaw.org A course in software development got me started with Clojure! At first I hated the language, but it slowly grew on me :vibe_cat:
Regularly use: Common Lisp (SBCL mainly) and Crystal.
Favorite to work with: same as above. They seem to match how I think well, so it's easy to solve problems in them. Their speed is also a nice bonus, as is Common Lisp's debugging and image-based development. I also really like how Crystal feels like a dynamic language (it's very reminiscent of Ruby), yet is still statically typed and compiled.
Interest in trying: m68k assembly for some ungodly reason lol
I really like working in the dotnet ecosystem; it's well maintained and supported.
I'm fairly weak in JS and find it a bit frustrating at times. Mostly because it seems that packages are obsolete or abandoned by the time I'm done reading the docs.
I know enough SQL to be dangerous.
Everyone seems to like Rust, maybe I should see what all the fuss is about.
Mostly C++, I develop back-end with algorithms that require all the performance we can get. We 're currently trying Rust for a small project, I hope it will succeed, I definitely love this language. And python when merformance is not the main concern.
At work I mostly use Matlab and a smattering of C++, at home I'm trying to learn more C++ but prefer to use python. I think my next endeavor will be learning Rust, not sure yet what I'll use it for though.
I'm mostly a hobby programmer, and I mostly use nim for most of the stuff I do, it just works very well with how I think and things just work, which I'm really happy about. The type system is really nice, with the right kinds of granularity for things that I want to do.
For now I'm mostly focused on learning the langauge that I use, and I have been playing around with a lot of different stuff, maybe some kind of forth would be nice to do some real down to the metal stuff, but I very seldomly have to do that. I did play around with factor for a long time, and it's a very interesting language, it just never really felt comfortable for me, more like a fun puzzle game in a way.
Mainly JavaScript, typescript, html, and scss. Occasionally bash and groovy. My favorite to work with is typescript. It’s a superset of JavaScript so naturally JavaScript is a very close second. I am interested in ruby and rust. Just because those are the two languages that I have been enamored with in the past so they are the ones that I have spent more free time than any other learning about them and using them for side projects.
Professionally, I mostly use Kotlin, Typescript, and Java.
For fun, I've recently been using BQN, which is quite nice compared to J, which I had been previously using. I also use Elm, Rust, Python and a smattering of others.
Yeah, I think they're just the more vocal subset of users. The same thing happens in functional languages. (Especially Lisp.)
Array languages in general are fun to use because you can express a great deal in very little space. Of course, you have to think more about how to encode something, or even when reading. I feel like those are good muscles to exercise for when you're reading more densely written code in any language.
I teach a class taught in OCaml. Despite that, I don't really like OCaml. It's good for education but IMO not that great for actually using it. My brother works at Jane Street and even he agrees... Like, it's fine, but not great.
Beyond that I make regular use of Haskell and Python for my graduate research and personal projects. I recently took a course in Java, but unless I don't have a choice, I'd rather use Kotlin. I'm also involved in the hardware simulator Turing Complete, so a lot of my side projects lately have been ETCa assembly programs.
I want to learn Rust and Scala, probably in that order.
edit: I also quite like Scheme and I used it for advent of code last year. Unfortunately I don't get opportunities to use it much, but if I ever get to teach a compilers course, I want to try the "reverse nanopass" approach that is currently used, I believe, at Brown University.
I don’t really like OCaml. It’s good for education but IMO not that great for actually using it. My brother works at Jane Street and even he agrees… Like, it’s fine, but not great.
I don't get to converse with a lot of OCaml users. What makes it "not great"? Is it the tooling?
The tooling is actually OK, provided you work on Linux. If you work on windows, the tooling is basically telling you to go get Linux.
It doesn't capture a lot of what many functional programmers consider the essence of FP: the language, and the people who use it, actively encourage mutable state in programs, and the type system is not powerful enough to capture useful abstractions like functors (generalized containers) or monads (generalized patterns of computation).
There are also some specific language design decisions that I don't like. For example, this code typechecks:
let id : 'a -> 'b = fun x -> x;;
The 'a -> 'b is a type annotation that says "you give me anything of type 'a (a type variable), and I'll give you back something of type 'b." That's complete bogus - that's not possible. It typechecks because OCaml goes "OK, this is fine as long as 'a and 'b are the same variable," and then for the rest of the typechecking process, that's what happens. id actually gets assigned the type 'a -> 'a. In the best case, this is confusing and occasionally useful to do what other languages do with "type holes." In the worst case, it's actively wrong. Using different type variables in a type can provide static guarantees that some things cannot mix, and with OCaml that is simply not possible for a declaration like this one. You can do it, but with a lot more boilerplate. Compare that to Haskell, where the right behavior is the default, and you can obtain a type hole just by using a variable name that starts with _.
My graduate work is currently on type error provenance. You know some piece of code has a type error, but where is the actual problem? This is a hard problem that compilers are notoriously bad at answering.
For work I currently use C and python mainly, and for some personal projects I've been using python backends with JS/Vue frontends.
I really enjoy Python, but as I use it more I've found the quality of the docs to be an impediment. They're hard to reference quickly.
I really want to start using Rust, but it's not really applicable to the kinds of projects I'm currently working on. I've started picking up some Clojure and PHP for two open source projects that I've started contributing to.
I really enjoy Python, but as I use it more I’ve found the quality of the docs to be an impediment. They’re hard to reference quickly.
this, and the need to understand the wordpress core, pushed me into php long ago; python used to be my primary language.
since about the beginning of the year, php docs now are often behind captchas. i don't know what in my environment triggers them, but i know they trigger me, and so i've been refactoring things back into python. mediocre and accessible docs >> somewhat better docs behind captchas. it's impossible to navigate the changes for change's sake between php 7 and 8 when you keep getting stopped to identify which fuzzy photo is of a dust cloud.
these are my home projects. for work, it's typescript/js/react against java/spring back end. i code mostly the front end now, but since i've also done java, i can make better tickets when there's a back-end problem :)