TLDR; unfinished wood that is rinsed and dried on all sides will naturally trap and kill bacteria as it dries. Any finish interferes with this process.
Check out VSCode's "Ruby in Visual Studio Code" page [1].
Ruby LSP already does quite a bit and started gaining go-to method abilities last month [2], though it isn't complete quite yet [3]. It's build on Prism, so promises to be more robust than past attempts. Shopify has been moving fast on improving things here.
The Rdbg integration works great too [4]. Just add a `launch.json` and VSCode can hook into the very nice capabilities Koichi Sasada has been adding to the official `debug` gem.
Perhaps if the software is more isolated? Many good points here, and I absolutely can avoid a lot of maintenance by my choice of languages and libraries, BUT just being online (or even on-network) forces quite a bit of maintenance.
I'm generally writing web apps, requiring me to keep up with a stream of security updates just to stay online: browsers deprecated TLS 1.0 and 1.1 [1], browsers require TLS certificates to be renewed ~annually, languages only fix security vulnerabilities for the last few releases, etc. Even linux kernels are getting shorter support going forward. [3]
The ARRL Ham Radio License Manual, 3rd edition, section 1.1 explains the term:
> How did “amateur” become “ham”? The real answer is unknown! Even before radio, telegraphers referred to a poor operator as a ham. Perhaps this was derived from a poor operator being “ham-fisted” on the telegraph key — an operator’s “fist” referred to his or her distinctive style over the wires. With all radio stations sharing the same radio spectrum in the early days, commercial and military operators would sometimes refer to amateurs as hams when there was interference. Regardless, amateurs adopted the term as a badge of honor and proudly refer to each other as “hams” today.
While you'd buy the latest 5th edition from the ARRL [1] to prepare for the exam, the older 3rd edition is freely available online [2].
Had to give this a +1 before skimming on with my feeds (Feedly).
I feel my RSS feeds can largely be configured to serve me. The configuration is transparent. I am in control of what internet I consume regularly.
With my social media feeds, the configuration is limited and opaque (e.g. what exactly does "Not interested in this tweet" do?). I don't feel I have much control. I severely limit social media...too many chances to disrupt me.
Yes. It is for "JS Sprinkles" on your existing HTML. This makes it "modest" compared to something like React that would typically generate HTML/DOM for you.
For me, a large part of React Native's appeal is the docs giving me a clear path to make stuff and a fairly public development process. Sure it is also an extra layer of trouble, but I prefer the trouble I can engage with (RN) over the risk of being stranded in the unknowable (Apple).
I really want to cheer with hope, but I'm screaming inside. My crappy app auth code needs to stay buried...forever. It's almost October 31, so definitely filing this under scary.