Ideas and Projects for 2021

I want to target three languages and tools for learning in 2021: Vue, Go, and Electron. These projects are the ones I’ve thought about so far. I may have additional ones come up as the year progresses. This will also enable to create of a monorepo for each of these projects that need one and use Bazel as the build system. WordPress in Vue I’ve always liked Vue better than React (regardless of the latter’s popularity and usage) so I started working on a combination of Vue and the WordPress REST API. See the following blog entries for the work

CDS 2020: Moving to Modern Javascript

Handling both current and older browsers Javascript has gotten more complicated since Javascript adopted an annual release schedule. We are not talking about the stark difference between ES2015/ES6 and ES5 but on a more nuanced set of differences and what it means for transpilation and browser support. Take, for example, Async/Await, a feature introduced in ES2017. If we want to use it in production we have to provide a fallback for browsers that may meet all our other Javascript requirements. Take the following list of Javascript features along with the version of the language they were introduced in: Classes (ES2015)

CDS 2020: New CSS properties for performance

There are two new CSS properties that may help with the layout shift core vitals issue. The content-visibility property allows us to tell the browser when to render an element. The “magic” value here is auto, which tells the browser not to render an element until it’s visible in the viewport. This makes page loads significantly faster, the browser doesn’t need to render above-the-fold content initially. The content-visibility property works hand in hand with the contain-intrinsic-size property to prevent potential issues with Cumulative Layout Shift. Because the browser isn’t rendering the element fully on load, there may be some shift

Bazel Build System: Overall Notes and Observations

Bazel is hard to get to work but it’s really interesting to work with once you get started. Like Ant and other build systems I’ve worked with before they use their own terminology and their own tooling to make things work better for their intended audiences. These are some notes that I’ve collected along the way… they’ve informed my own research and are good things to keep in mind as you work with the tool and its ecosystem. Why Use Bazel In my opinion, Bazel works best in a monorepo with multiple languages attached, whether the monorepo builds a single

Bazel Build System: Backend code, even more choices

Just like with the frontend, the backend gives you multiple choices of languages and feature sets for working with Bazel. C/C++, Go and Rust are the three languages that I tested generating WASM code with so it may be interesting to see how well they work with Bazel and how they abstract WASM generation. We can keep all the code for our project in a single monorepo and let Bazel sort out what tools to use to compile which part. I use C and C++ as the baseline for testing Bazel with backend languages. It also works slightly differently from