@matigo I have deliberately left the Javascript non-obfuscated. I know it isn’t the most elegant code out there, but if someone can learn from it it has fulfilled its purpose.
@matigo Yep. I have decided to stick with the vanilla Javascript on my site, but it can be abused as well, as I have noticed. Well, once I get those fixed, things should be running smoother in the future.
@matigo They are. I was reminded why I don’t like Javascript as a language…
Now that I am fixing the issues spotted by Javascript linter(s) on the code that is running on my website, I keep on wondering how the whole thing was even working in the first place. When I fix a linter error or warning, the functionality gets broken. Yes, that is unfortunate, but apparently the original implementation worked by pure magic in the first place. This means that I need to rethink the approach a bit, which will make it work The Right Way™ .
@matigo Yeah, had I written them in-place the post would have been even longer… 😁
What was your impression on it? Have you been applying a similar approach in your work?
New software blog post: Running automated checks on your code on commits [pekonen.cc]
Also, a small CSS tweak that might make you happy. 😊
@variablepulserate Yeah… People want way too complex things, which in turn makes
1. The implementation complicated and2. The solution to be inaccessible.
I work on a mobile app that has a legal requirement to be accessible, so my initial idea of making things simple and straightforward has been amplified quite a lot.
// @matigo
@variablepulserate Really? 😳 I just use a simple design pattern and very few special effects, and the font I use on my site is pretty funky (Averia, the ”average” of various fonts)…
// @matigo