This is cool, for binaries that provide a web interface, for admin purposes, maybe a blog, or whatever, keeping it simple with some styling to make it a little more swish, this is all I'd be looking for. I'll give it go for sure.
When all you need for the UI is a text area to input text and a button to render the markdown, I am at a loss as to what would contribute to a beautiful UI. Is the question correct?
When not using VSCode + preview, I have found https://dillinger.io/ pretty good as you can download the result in various formats.
Agreed! A useful comment would only be present to describe an edge case, a related business rule, a future change that might affect this code, virtually anything another engineer might need to be aware of, that is not the code they are looking at.
The only reason I have a mac is for work, developing iPhone applications. For home and hobby development I run Ubuntu Linux which satisfies all of my requirements and needs very little attention. I attempt to keep dependencies at a minimum which lowers ongoing maintenance and troubleshooting.
"Go is pretty good for almost anything server-side."
Absolutely! REST API servers, data processing jobs, messaging servers, etc etc. I use Go now for virtually everything server side. It is fast, reliable, great tooling, promotes unit testing, and now that I have hit that "comfortable with the language" spot, I have never been more productive.
SpaceX announces a one way mission:
"...to explore strange new worlds. To seek out new life and new civilizations. To boldly go where no man has gone before!"
I can second this. From being proficient in multiple languages to then picking up Go for primarily API service's I'm not looking back. It has taken a little while to level up to expert but the effort in learning how to build from the ground up by not using a framework is well worth it!
"Most of my daily tools are Windows based, so I’ve been spending a lot of time getting Windows Subsystem for Linux working alongside the rest of my daily workflow, which comes with its own headaches."
My work place is considering switching providing developers with a MacBook Pro to a Dell Windows machine. At one point we were all allowed Linux which was awesome.. Is WSL still painful to use? My prior experience came to a dead end when I had irreconcilable Docker issues, the fine details I don't quite remember now other than it had something to do with accessing the host network. All good now or still meh?
With the release of WSL2 and the new versions of Docker that take advantage of it, I would say that most of the pain around the WSL toolchain has been resolved.
Compared with trying to get anything working in powershell or dealing with the slowness of git bash or Cygwin, WSL2 is a breeze.
The only pain point I still have is running Linux GUI applications. It requires running an XWindow server on the Windows side and letting WSL talk to it over TCP. Apparently MS is working on that now and hopes to have a solution later this year on the slow ring of windows update. That'll make running things like Cypress a hell of a lot easier and (fingers crossed) prevent me from squinting on HiDPI displays.
