21–30 of 46 posts
I know, large teams make it work. It still is a source of potential headaches that I don't need.
Python. I've seen too much of what happens to code files on multi-person teams to ever want to have to deal with syntactically relevant white space. I know, large teams make it work. It still is a source of potential headaches that I don't need.
Earlier quoted context omitted.
After having dabbled a fair bit in Lisp, Haskell, Ocaml and, to a lesser extent, Elixir, I've found F# to strike a very nice middle ground when it comes to functional programming. edit: https://fsharpforfunandprofit.com/ is a very nice introduction to F# and all the things it can do.
Hm, I was always kinda scared about setting up .Net on my linux box. What setup do you use?
Or if you just want to learn it, you can run it in your browser here: https://try.fsharp.org/
Also while I don't really see C++ going anywhere anytime soon, I don't really see it expanding too much either.
Both of these facts make me a lot less interested in really diving into advanced features or low level details of the language.
Pretty much all of them. I started with C and never liked OO programming. Even when kind of optional in the language, for your own code, you still have to deal with an OO library ecosystem because everyone writes the libraries that way when the language supports it. It kind of depends on what you mean by popular. I don’t have much interest in Rust. It has a lot of hype right now. It doesn’t seem like a bad language,…
Do tell more, what high level stuff do people want to use Rust for?
C++. I know it, I use it, I don't usually like it. A lot of the language just feels like a hack. I usually much prefer to write performance critical code in C but sometimes the utility of C++ or of certain C++ libraries outweighs that desire. Also while I don't really see C++ going anywhere anytime soon, I don't really see it expanding too much either. Both of these facts make me a lot less interested in really divin…
Python. I've seen too much of what happens to code files on multi-person teams to ever want to have to deal with syntactically relevant white space. I know, large teams make it work. It still is a source of potential headaches that I don't need.
It's barely a hurdle, if you can't manage to configure your setup to meet your teams setup then it probably means you are not qualified.
But, you know, stuff happens. Somebody's machine loses the hard drive; in the process of building the new hard drive, they miss restoring the configuration for their editor. Somebody else installs a new editor, and forgets that configuration matters. A new employee gets hired, and doesn't know either how or why to configure properly. And behold, bugs get introduced invisibly.
That won't happen often. It will happen more than zero, though. And when it does, it's a headache I don't need.
Rust and the other new zero cost abstraction languages. Reason being that I think performance is a solved problem. The future is in safety and readability. Not squeezing the last few percent of fps out of your hardware. Go is in the same category. People are inventing better versions of C++ when I want them to invent better versions of Python. :)
In terms of use cases Go is much closer to Python than to Rust and C++.
Earlier quoted context omitted.
It's barely a hurdle, if you can't manage to configure your setup to meet your teams setup then it probably means you are not qualified.
Thank you for your charitable interpretation of my qualifications. But, you know, stuff happens. Somebody's machine loses the hard drive; in the process of building the new hard drive, they miss restoring the configuration for their editor. Somebody else installs a new editor, and forgets that configuration matters. A new employee gets hired, and doesn't know either how or why to configure properly. And behold, bugs…