Earlier quoted context omitted.
Typically by reading docs and writing compliant code.
Were it only that easy
I can't stand using VSCode so I wrote my own
141–150 of 186 posts
Re: I can't stand using VSCode so I wrote my own
#142The non-open license is a blocker for me; an editor is perhaps the most important tool for me as a programmer, I'm unwilling to risk not being able to use it how I want. This looks like the same reason that made the author write their own editor. I won't do that, I will stick to vim and emacs.
Re: I can't stand using VSCode so I wrote my own
#143I use vscode for doing devops-y things (Terraform, OpenTofu, JSON, python, yaml, txt, dockerfiles, etc.) and sometimes the way it bogs down my system drives me bananas. I'll punt to Sublime Text on occasion and use it for a few days, but then start running into papercuts in various places and have to go back to vscode. I so, so wish there was a better way to do this without fucking electron.
Exactly. Talk about something as simple as code folding. VsCode does the best job of it I know, and yet the other day it simply stopped working properly for pure JS code, not sure if that's because Microsoft prefers we use Typescript instead of JS. Nothing I did fixed it, and something as simple as that messes us with your workflow. And then I remember that VSCode has introduced a recent bug where after you collapse…
Re: I can't stand using VSCode so I wrote my own
#144Or just use Vim. Not sure I understand the obsession with VSCode.
Re: I can't stand using VSCode so I wrote my own
#145>I'd tweak the script; then to see the results I would press F5 to run the already built binary and wait over a second EVERY SINGLE TIME (about 1480ms). I put in a bug report for this years ago but it got ignored :( https://github.com/microsoft/vscode/issues/137066 Vscode has gotten slower over time. It's true you can't get nanosecond performance out of JS, but anything under 17ms should be trivial. I believe the vsc…
Re: I can't stand using VSCode so I wrote my own
#146Earlier quoted context omitted.
You're not disabled yet . But you may want to care about this before your eyesight, motor accuracy, etc. start failing. It's not some big "disabled/not" switch - setting the font 1pt higher is accessibility, changing the colours is accessibility, being able to tab through fields consistently is accessibility, etc.
The idea that I might eventually become disabled still doesn't make it an essential feature. Disabled users are not a significant portion of the userbase of most software. Accessibility is an essential feature for a text editor in the same way that Linux support is an essential feature for Fortnite.
Flat out you will eventually need glasses and your ability to see differentiate two different colors with a low contrast difference will fall apart.
Re: I can't stand using VSCode so I wrote my own
#147Earlier quoted context omitted.
You're not disabled yet . But you may want to care about this before your eyesight, motor accuracy, etc. start failing. It's not some big "disabled/not" switch - setting the font 1pt higher is accessibility, changing the colours is accessibility, being able to tab through fields consistently is accessibility, etc.
The idea that I might eventually become disabled still doesn't make it an essential feature. Disabled users are not a significant portion of the userbase of most software. Accessibility is an essential feature for a text editor in the same way that Linux support is an essential feature for Fortnite.
Re: I can't stand using VSCode so I wrote my own
#148This reminds me of the famous Visual Studio rant by Casey Muratori https://www.youtube.com/watch?v=GC-0tCy4P1U And the hundreds (if not thousands :D) of rants by Jon Blow saying how contemporary software performance sucks
Have you seen "Jonathan Blow plays Visual Studio"? I ran across it after I started and understood his pain
Re: I can't stand using VSCode so I wrote my own
#149Earlier quoted context omitted.
Turbo Pascal was so fast in the 80s that if I saw a syntax error further down the page it was faster to hit "compile" and let the compiler move the cursor to the error than it was for me to move the cursor myself. It was a very special compiler and they don't make them like that anymore.
The trick is to have language "optimized for compilation" and do not do fancy optimizations. Java is similar (but overall infrastructure around compiler makes it slow). Golang also quite fast.
(1) Single-pass compiler. No separate pass to convert to object or executable.
(2) Written in assembler (!). Helps that Pascal has fewer dark corners.
(3) No use of disk. A single file read or write would take 10-20s on a floppy. Instead, it's memory to memory.
Re: I can't stand using VSCode so I wrote my own
#150Earlier quoted context omitted.
This is the way. Anytime I have had issues with an open source project, creating a PR even if it's not great will often have it taken over, improved and merged.
I'm sure someone named some "law" after themselves for this. But it is true that the fastest way to get an answer to a question online is not to ask a question; post the wrong answer.
This is Cunningham's Law [1]! And it seems exceedingly plausible after observing behavior on many online forums!