The mostly unremarkable journey of two remote software engineers.
Background: Problem: Design the API for fetching specific scenes, and their items. We currently have a method to get the current scene based on a specific View. But we did not have a method to get a specific scene. Current XJS 2.x API is: import { Scene } from 'xjs-framework'; Scene.
A former colleague, who is a regular employee at SplitmediaLabs, started to contribute to XJS 3.0, and we're currently having a dilemma whether to go and fill the world with objects which we are doing right now, or make a u-turn, change our approach, and go with the functional
I currently have a dilemma with the structure of XJS. First off, a recap on the objective of 3.0: Minimal footprint - Partly achieved by having a modular approach. The single XJS class won't import everything else.Multiple Instance supportExtensabilityI'll drill down the 3 points, and the approach we
In popular frameworks like React, it is easy to not use the native HTML attributes to set a particular element's value since there are alternative approaches that has become popular, like currying. But with the importance of accessibility being quite a thing nowadays, we are ending up also setting some
Create React App (CRA) uses webpack as its bundler, with a couple of webpack plugins including a plugin that does the tree shaking to remove dead-code. Now, I'm no expert on webpack wizardry, but I do think it's the Terser plugin that does that. Anyways, one of the bane of
