Wow just realized Firefox has this feature built-in but not enabled by default! Just needed to turn on "Ctrl+Tab cycles through tabs in recently used order".
The author mentioned the vimium addon with the ability to quickly flip back to the previous tab. This makes me want something similar to the recently-used-tab selector in VSCode - pressing ctrl-tab pops-up a list of recently used tabs in reverse-chronological order and makes it super easy to flip back and forth. I wonder if there's any browser extension like this?
The section about signature hashes could use some improvement. Cryptographic hashes have multiple use cases. The main one that comes to mind is basically just secure checksum/integrity hashes where you want to guarantee nobody could force a collision. For this case, all the scary warnings about "don't use these algorithms directly" makes no sense.
But where are the reports/blog posts from the thousands of companies using these algorithms that ran into performance problems the last few times cloud providers used time smearing? I’ve done some searching and can’t find any, which suggests this is mostly a theoretical issue.
Yes I could come up with an algorithm where this is a problem, but in most cases I’d favor a solution that doesn’t depend on separate systems having clocks perfectly in sync.
Seems a weird way to write an algorithm. Easier to rely on database locking and/or the obvious fact that if you have received some data telling you about an event having happened, then it has happened… Curious if there are any real reports where this caused issues?
Sure but that’s why I think the take-away here is to design the system such that you can do such automated rollbacks. For example, the devices should also be connected to some sort of isolated management network. Granted, pushing out a config to the routers could also break their connections to said management network, but it is less likely anyways.
The router config is not the top of the stack though. There should be orchestration systems that push out changes to these devices and can roll them back when required.
I’ve seen this type of thing happen a few times. Usually a combination of a human error at the factory plus flaky backend systems that like to do upserts.
You are arguing purely on price but not considering other factors. To the person who bought the beer, the deemed value is probably more than they paid for it, and to the seller the beer was a liability due to having a limited shelf life and occupying shelf space. Thus there was a gain for both parties.
Same - the row format itself starts with a bitmask listing all null columns. You don’t need to read the column data itself to determine if a column is null.
I think this is a great change. I wish NULLS NOT DISTINCT was the default already - if I wanted the constraint to ignore null values I’d have used a partial index to only index non-null values. Doing the opposite is much more difficult.
Your last statement would be better written as:
Because NULL values are of unknown equality, they may or may not violate UNIQUE constraints.
The safest implementation would assume that they do violate the constraint, rather than the current behavior assuming they don’t.
In practice I don’t think I’ve ever added a unique index on a nullable column where null might imply unknown. I have used it in cases where null meant “none”.
I ordered chicken wings at a vegan fast food restaurant. I too would have preferred if the name was more specific, even though it’s implied by the context. It was my first time at the restaurant so I specifically asked them to confirm it was vegan.
Also some chains/brands do a very poor job labeling their things so that it’s obviously plant-based. For example at Tim Hortons: Farmers wrap=meat based, Harvest wrap=plant based. Feels intentionally confusing.
Apparently it hides the shadows when you screenshot an individual window. Neat trick, although I think I'm going to apply the trick from the article, since I don't think I ever actually want the shadows.
I was in a gifted program but it was poorly executed and I deem it to have been detrimental to my growth.
I was randomly pulled from normal classes in order to hang out with a few other gifted students and do weird puzzles or whatever. Then later I’d have to figure out from classmates what I missed, including what homework to do etc. My social skills already sucked, and being labeled as special to the classmates whom I’d have to spend most of the day with certainly didn’t help.
I’m sure there a ways to do it better, but having no gifted program is better than a bad gifted program.
I use both awk and jq infrequently enough that I tend to struggle with anything non-trivial. I think zq would be the same.
> Not entirely convinced by the zq syntax either though; it also seems "arcane enough" that I would keep forgetting it.
I think this is the main thing. I’d prefer a streamlined CLI tool where you passed in some JS code and it’d just run it on the input (with the same slurp/raw args as jq). Could just be npm with underscore.js autoimported.
Yes I’ve run “git status”, “git log” and “git diff” on other people’s repo’s plenty of times to help debug things, so it’d be sad to see this stop working. It seems some basic readonly operations should still be supported.
I'm surprised nobody else has mentioned this yet - a LEFT JOIN can be more efficient than an INNER JOIN precisely because the database doesn't need to enforce the filter during the query plan.
This comes up for me most often with views, when a query referencing the view doesn't end up using all the columns - when a LEFT JOIN is used, the database can potentially skip querying those tables entirely, but not with an INNER JOIN.
If you are running a 10-year old version of python 3, and you try and install some recently written python 3 application, it will never work - you'll be stuck in dependency hell, even getting pip to run may be a challenge due to outdated certs or TLS versions.
If we can’t agree on permanent DST vs permanent standard time, I propose we divide the continent in half and have permanent DST on the West and permanent standard time on the East, leaving a 2 hour time gap between the coasts. Over time the morning people will flock to one side and the evening people the other, and all will be harmonious.
I get npm, but is it that realistic that yum will pull down a virus? If yum could be infected, then you are either pulling down obscure packages or using a 3rd party repository. If a mainstream package could get infected, it’s just as likely to end up in the base image that you started with (ISO, docker container, etc).
To me the mistake here sounds like the fact that they rolled it out all at once. I’d have expected to see this implemented by slowly ramping up tariffs on non-organic fertilizers/pesticides over a number of years (like 5-10). It probably takes a few years for a farmer to effectively adapt to such a transition.