littlehood

That way we would be able to create integration test coverage of 100% while still being able to panic on real hardware, until all messy behaviour is implemented. It's like writing unit-test kind of integration tests which then fail when provisioned :)

You could've asked politely, but it looks you missed your chance.

We are able to create tests with emulated hardware from specification, but writing emulation taking into account quirks, edge cases and speculative behaviour would be great amount of work, even for simplest devices.

I'd recommend reading Dolphin emulator release notes for a reference how much work is required to properly emulate hardware such that actual software may run without glitches and errors even for (AFAIK) 3 hardware sets.

You asked for that block in the second question. You sound very entitled to answers.

Aztec is more compact than QR - does not need margin and because it's optimised for lowercase letters (used a lot for urls). Also has tunable error correction.

It is an experimental option for Xamarin. Though haven't played with it.

I've using Standard Notes for almost three months already. It's neat, but "standard editor" is kind of weak (like not supporting tab to indent), I have to try using the extended editor. Everything syncs nicely BUT on two occassions a tag got duplicated with some of the notes. I have no idea how - but at that time I had it open on two desktops. Not sure how nicely the encryption is done. You can create your own server for notes too!

I've started using Standard Notes, but it kind of feels like it's still beta.

Depending on the depth of the pond, it may have not frozen to the bottom - water has the highest density around 4°C (~39°F).

I've used sublime 2 for some time, but changed to VSCode. Reason: VSCode is good enough for my stuff.

Gmail does something to divert it - it downloads all the resources once and CDNs them for you, so the email author can't see who and where opened the email.

Most asp.net workshops rely on SQL Server, which up to version from 2012 did not support MVCC and relied on locking on writes and reads. The problem is, it had problems with web-kind load. If something was writing into a table X, and there would be a parallel query for table X join... (especially including index seek and not just lookups), you'd get into territory of heavy locking. Add ORM to that, which wouldn't let you influence the order of the joined tables and you've just got yourself a deadlock. This happened on a few occasions in a few different projects I've worked on. The real problem is: there is lot of technicalities you need to know and understand, to use it. Some NoSQL solutions (including MongoDb) try to abstract away those technicalities, and that was the point of my comment.

My biggest problem with SQL for systems with web interfaces is that it forces you onto OLTP, when your workflow is just "select data, show to the user" -> "user saves changes, save them in the db". Googling for "asp.net deadlock" gives 160k results.

Porting existing/legacy software to cloud. Though SQL Server is just a part of the stack and you still can't fool software it's running Windows.

But it's like SQL Server on Windows Server Nano - nobody asks for it, because only full system has required tools and features.