Posted by jpluimers on 2020/08/12
[WayBack] Roderick Gadellaa auf Twitter: “@ingnl Ik begrijp dat jullie gaan stoppen met TAN codes. Juich ik toe, 2FA met sms is behoorlijk lek. Maar nu moet ik jullie app gaan gebruiken. Ik werp 1 blik op de permissions die jullie app wil en denk: Neen.…”
Reminder to self: check what permissions are needed now.
–jeroen
Posted in Development, Power User, Security, Software Development | Leave a Comment »
Posted by jpluimers on 2020/08/12
This and built-in markdown support made the switch to Visual Studio code from Atom.io so much easier: [WayBack] PlantUML – Visual Studio Marketplace.
Atom.io was already on my list of tools to say good bye to: though a good project to show the versatility of the Electron Framework, over time – like Google Chrome – it had become a memory and CPU hog and a drag to use and update.
Integrating debuggers and other parts of the development life cycle involved too much fuzz, for which Visual Studio code (also known as vscode) was much easier from the start.
Probably Visual Studio code did not suffer from what the Dutch call Law of the handicap of a head start: it is much more responsive and versatile than Atom.io. Also the plugins – despite having come to the market later – feel way more mature in Visual Studio code than Atom.io.
Finally, the PlantUML support extension for vscode is so much nicer than in Atom.io, it for instance supports live updating and in addition to local rendering, rendering through a PlantUML server (see [WayBack] GitHub – plantuml/plantuml-server: PlantUML Online Server).
Source code is at [WayBack] GitHub – qjebbs/vscode-plantuml: Rich PlantUML support for Visual Studio Code.
Posted in .NET, atom editor, Development, Diagram, PlantUML, Power User, Software Development, Text Editors, UML, Visual Studio and tools, vscode Visual Studio Code | Leave a Comment »
Posted by jpluimers on 2020/08/12
For a project I’m going to be in need to compare version numbers.
I’m not sure yet if I need wildcards, or can leave them out (but for partial semantic versioning, I might need them).
Below a bunch of links that should get me started.
From a quick glance: versioning is hard, comparing even harder.
On versioning in general
Numeric versioning (usually without wildcards):
On semantic versioning (SemVer for short):
in versus CharInSet versus IsDigit versus IsInArrayOn the C# Version class (which handles most of semantic versioning except: leading zero’s, very large numbers, non-numeric release specifiers)
// A Version object contains four hierarchical numeric components: major, minor, // build and revision. Build and revision may be unspecified, which is represented // internally as a -1. By definition, an unspecified component matches anything // (both unspecified and specified), and an unspecified component is "less than" any // specified component.
Interesting idea, but not sustainable: using floating point values to compare versions:
On wildcards:
Via: [WayBack] Anyone tips for a TVersion structure that supports at max quad digits or wildcards and comparison? Like 3.2 matching 3.2.5.7, but not matching 3.3.4.28 ? – Jeroen Wiert Pluimers – Google+
–jeroen
Posted in *nix, *nix-tools, Development, Power User, rpm, Software Development, Versioning | Leave a Comment »
The Wiert Corner - irregular stream of stuff 