xmattx

For a Senior perhaps. The figures I find for Switzerland are more in the 90-120 range depending on the source. Also, I think what OP was referring to is the 'most markets' bit. Switzerland is the best paying country in Europe (discounting London).

Tried it, it failed at the first hurdle, which is scanning the glyphs correctly. Seems to be an offset somewhere as they get shifted vertically.

Any plans of open sourcing your MJML extensions? We hand-code MJML for our mails and fairly frequently run into compliancy problems.

Runs kinda counter to your business-case I suppose, but might help someone (me) out :)

Additionally, the only info they need is your name, birthday and photo. Anything else can be blocked out. I don't really consider that 'giving them my government issued id'.

Reminds me of a framework-agnostic vue-cli. Though that simply builds a configuration/tooling-setup which you can then tweak to your liking. Not sure what I think of using a neutrino-specific config in the package.json for overrides, feels bloated compared to just editing the webpack config directly, and doesn't make it any easier. But to each his own, I guess.

That name though, I guess particles are en vogue :)

Just a few random observations: I can't seem to toggle off bold/italic/...? Neither can it be toggled on before typing it seems. Also, setting text alignment removes bullets.

Nice idea, but functionally not quite there yet.

I agree with KirinDave. I've been using it since the first insider preview that had it. Back then, most of the workflows I use (mostly frontend development, npm/gulp/webpack/php, that kind of stuff) ran into some sort of problem. Right now, I use Bash for about 90% of my commandline needs, only occasionally reverting to cmd. Bugs are few and far between (though still breaking in a lot of cases, so we're firmly in beta territory yet). In the latest builds it's possible to use windows executables from Bash (for me that's mainly Atom), which has upped my use by a few more percent.

One annoying thing is that PHP's built-in webserver (which is also used by Laravel for it's development server) causes file read errors under WSL. Easy enough to avoid until they fix it though, by setting up Apache in Ubuntu or a local LAMP stack on the Windows side.