Thread pools on the JVM should usually be divided into the following three categories:
- CPU-bound
- Blocking IO
- Non-blocking IO polling
Each of these categories has a different optimal configuration and usage pattern.
| # https://github.com/neovim/neovim/wiki/Installing-Neovim | |
| yum -y install epel-release | |
| curl -o /etc/yum.repos.d/dperson-neovim-epel-7.repo https://copr.fedorainfracloud.org/coprs/dperson/neovim/repo/epel-7/dperson-neovim-epel-7.repo | |
| yum -y install neovim --enablerepo=epel |
Tips for using less on the command line.
To navigate:
To search:
| #!/usr/bin/env python | |
| # written for tutorial: https://medium.com/@eyebool/creating-a-sample-database-for-influxdb-102a89464132 | |
| FILEPATH = 'citibike_station_data.sample.log' | |
| DATABASE = 'citibike_station_database' | |
| HOST = 'localhost' | |
| PORT = 8086 | |
| USER = 'root' | |
| PASSWORD = 'root' |
In PHP development environments, it is not entirely uncommon to use an auto_prepend_file to add development-specific functionality to an application.
Usually such a file is used for several projects at the same time. This means the prepend file resides somewhere in a more high-level location.
A more common practice is to use Xdebug te debug PHP code.
When combining these two with PhpStorm this will lead to the prepend file being marked as "not mapped".
SELECT *, Specify explicit column names (columnar store)tmux, like other great software, is deceptive. On the one hand, it's fairly easy to get set up and start using right away. On the other hand, it's difficult to take advantage of tmux's adanced features without spending some quality alone time with the manual. But the problem with manuals is that they aren't geared toward beginners. They are geared toward helping seasoned developers and computer enthusiasts quickly obtain the
国内从 Docker Hub 拉取镜像有时会遇到困难,此时可以配置镜像加速器。
Dockerized 实践 https://github.com/y0ngb1n/dockerized
I tried the WSL and it isn't quite seamless enough for me. I ran in to problems when editing in VSCode and having watchers on my files (ng serve, dotnet watch run, etc.). In addition, I kept running in to problems that only manifest themselves when running in WSL. For example, this issue with doing production builds and the terser plugin has made many a developer rage-quit on using WSL. Just figuring out that it was an issue with the WSL took a lot of time.
That terser plugin issue was never resolved and I ended up having to keep a git bash window open in addition to my WSL console window so I could do production builds. To make matters worse, my npm packages were platform-dependent so I couldn't use the same project folder. So, my procedure was: commit whatever changes to test branch, push to repo, git pull on my "windows" project folder, and do a production build there
Clojure is an amazingly powerful language. Using it (and watching Rich Hickey videos) has changed the way I think about programming, and the way I code in general. Once I learned the basics of the language, which was a relatively quick process, I fell in love and couldn't look back. I hope this post can help others who are new to Clojure get up and running quickly and painlessly.
This post is opinionated in the sense that I'll suggest certain tools to help those who are new to this scene get on their feet. The things you'll need are: