azov

There should be a hefty tax on corporations insisting on having people in the office for jobs that can be done remotely. Maybe frame it as a tax break for companies that avoid stressing public infrastructure and wasting resources for dubious reasons.

whatever compensation you're going to extract, if any, is almost certainly coming out of taxpayer pockets - the cop couldn't care less about it.

What was the mistake? Can’t P1S work offline? I thought they can print from SD card, and there’s also LAN mode?..

Is somebody organizing a rally to oppose this?

Your code is that contract (unless your tests cover every possible input, which is not practical in most cases).

Same for me. The arrows are so small I can’t even see them on my phone, but animation makes direction clear.

Most codebases that ban exceptions do it because they parrot Google.

Google’s reasons for banning exceptions are historical, not technical. Sadly, this decision got enshrined in Google C++ Style Guide. The guide is otherwise pretty decent and is used by a lot of projects, but this particular part is IMO a disservice to the larger C++ ecosystem.

If my system doesn’t work - I want to be alerted. If notification was supposed to be sent but wasn’t - it’s an error regardless of whether it wasn’t sent because of a bug in my code or external service being down. It may be a warning if I’m still retrying, but if I gave up - it’s an error.

“External service down, not my problem, nothing I can do” is hardly ever the case - e.g. you may need to switch to a backup provider, initiate a support call, or at least try to figure out why it’s down and for how long.

If you mean that sites with expired certificates may technically be accessible if one jumps through enough hoops and ignores scary warnings - yes, of course you’re right.

Maybe this will just teach everyone to click through SSL warnings the same way they click through GDPR popups - for better or worse.

We wanted TLS everywhere for privacy. What we ended up with is every site needs a constant blessing from some semi-centralized authority to remain accessible. Every site is “dead by default”.

This feels in many respects worse than what we had with plain HTTP, and we can’t even go back now.

If the cost of building software dropped so much - where is that software?..

Was there an explosion of useful features in any software product you use? A jump in quality? Anything tangible an end user can see?..

I was hoping for easy backup via zfs send as well, but turns out it’s not so easy atm.

IncusOS does not give you shell access, you have to figure out IncusOS ways to do things via their CLI/API. I haven’t found an easy way to do incremental backup of the whole system yet. You can backup individual instances/volumes via incus export (which seems to use zfs send under the hood), but not the whole thing.

I have mixed feelings about their decision not to give you shell access. Guess those who want flexibility can always just install Incus on top of any Linux they like, but it would be nice to have an escape hatch for when IncusOS gives you almost everything you want…

The ticketing system might very well be the oldest.

AFAIK the very first large-scale commercial deployment of what we now call "distributed cloud apps" was SABRE, a ticket reservation system built back in 1960s, still in use today.

Well, direct democracy already exists in various forms (e.g., referendums, propositions on California ballots, etc.). Sometimes bad decisions are made, but I wouldn’t call it a total disaster. Can it be improved through technical means? How much improvement would it take for it to be better than the status quo?