201–210 of 327 posts
The only issue I have with VS code is it's awful UI/UX performance - it behaves like an Electron app or something. I realize that's a fair insult around these crowds, but it really does have that lack-of-polish, weird-UI/UX feeling. I know Microsoft would obviously never build an IDE off it, but I'm almost curious to see what on earth they did wrong. Comparing it side-by-side with Xcode is certainly the easiest way t…
Earlier quoted context omitted.
Maybe it’s because the editor was taught to students at places like MIT, Berkeley, etc?
I learned emacs in the late 1980's -- it is now an ingrained part of my brain. I hate when I have to use an IDE w a different editor -- at least most editors (and GUI components like browser textfields) respond to common emacs key-sequences.
Having gone through Triplebyte's interview process, I'll propose another interpretation: Triplebyte's interview is on aggregate biased against Java and C# developers. I'm not accusing Triplebyte of "being biased", but rather pointing out that Java and C# tend to correlate to a skill set that Triplebyte's test process values less. My experience of Triplebyte's interview process is slanted towards frontend/backend deve…
> Engineers who use Go are also especially strong. If you know why, please let me know. Because there is almost no reason to learn Go. Most shops want JS/Java/Python/C# etc... The primary reason to learn a language like Go is because you want to for it's own sake. It's not that you must learn Go in order to be good, or that knowing Go makes you better. Rather it's difficult to be bad and still have the desire/interes…
No, that's not it. It's that if you can only learn one programming language, Go is not a very good choice, so those who learn Go are almost always multilingual ("lingual" as in programming languages, not natural languages). Python and JavaScript are Swiss Army knives with outstanding ecosystems that make them excellent choices if you can only afford one tool. There are plenty of reasons to learn Go but, as a more specialized tool, it makes a better component of a nice toolset than a solitary multitool.
My anecdotal experience says that 1) most programmers are monolingual, 2) almost all Go programmers are multilingual, and 3) the average multilingual programmer is a better programmer than the average monolingual programmer for various reasons, so the average Go programmer is better than the average programmer. And, by that logic, the average Rust, Haskell, Erlang, Lisp, etc., programmer would be, too.
The "live shared coding" angle in VSCode makes it a great option in many areas where there's a need for it. People have been asking jetbrains for this for a decade, and there's nothing on the horizon as far as I can tell.
Earlier quoted context omitted.
I feel like you should spend some time with Go. If I were building a startup, I would probably choose Go for core infra for being able to move quickly as a developer and write incredibly performant code with about as much mental overhead as most dynamically typed languages. Anecdotally, I've seen it replace Java in quite a few small and medium sized established companies.
I feel like Python is your pepperoni pizza can't go wrong option for almost anything. Go feels similar but younger. I love languages with big standard libraries. Just need their package management story to settle down for a while. There's something wonderful about a language being so popular and around for so long that there's plenty of resources and answers on just about anything. I think that's a core part of what…
What editor do Go devs use??? Their numbers for Go only add up to 12%! https://d25hn4jiqx5f7l.cloudfront.net/file_attachments/files...
Earlier quoted context omitted.
This is what Paul Graham calls the Python Paradox; namely that in 2004, when Python jobs were relatively more rare, you could find smarter Python engineers than Java engineers for any given project. "[I]f a company chooses to write its software in a comparatively esoteric language, they'll be able to hire better programmers, because they'll attract only those who cared enough to learn it. And for programmers the para…
Both of these are still just very roundabout ways of telling yourself you're awesome because of whatever mildly unusual thing you think you might be doing.
This could go round and round. The point is that there SEEMS to be a correlation with people who learn things for the sake of learning them and folks who do well at exercises that test for adjacent skills.
VSCode is fast, stable, and the plugin ecosystem really beats Sublime Text at this point. I was skeptical because Microsoft but it is hands down my favorite editor.
How can anyone say VSCode is fast, and then compare it to Sublime Text ? They are not even in the same order of magnitude. VSCode is definitely fast enough for most uses cases, but I still wish it was as fast as Sublime Text, from Scrolling Frame-rate to response time.
But I miss sublimes speed it was unmatched, and the jump to symbol using @ or # in a file is worthless in vs code because it waits to calculate until you use it.
Like it was said in this thread, as long as you have an editor that is built on something js-related like electron or node-js, it just cannot beat alternatives that are made in C++. I've tried VSCode because I wanted to have UI breakpoints with GDB, I admit that vscode seems better than atom, but for performance I have my doubts. I really don't understand why engineers choose to use JS to made a text editor. I know t…