I think for preexisting solutions, the "best" one is Rectangle Pro, but it isn't free, so maybe that doesn't count. That said, eventually I realized I don't even want the whole "window split" stuff and I'd prefer to just have a few keybinds that throw windows into specific coords on my screens, so I installed Hammerspoon (free) and wrote a screen's worth of Lua to do this for myself. It is written for my two adjacent 1440p monitors and personal preferences, but the code is really obvious so if you're comfortable with making your own bespoke solution, this is pretty nice, and free.
When I first heard it, it was billed as a riddle, not a joke. It only really makes sense in any way as a riddle / brain-teaser if it successfully plays on your biases of the operating room doctor being incapable of being his mother (or other father, etc). In a 1950s, old-timey-wimey, nuclear family mindset, the father is the breadwinner and the mother is the homemaker, and there is no other reasonable possibility. Anyone that was taught to think that way will hear the father dying in the car accident and then be confused when someone else can also refer to them as their son.
This came up a few years ago for the first time for me, and I tried it on my (elementary school) sons and they immediately said "uhh, its his mom, I guess?"
I get that the Tesla FSD crashed once, but did it hold some king of grudge and followed him to the hospital? Or did Tesla build Skynet and it was a second Tesla and they were coordinating the attack? Was the son named Connor?
Ah I get it now. Where I live this usually the family structure and doctors etc are mostly male anyway therefore I assumed surgeon to be the father too and got very confused. Thanks for explaining.
I guess it is too soon to say impact-wise one way or another, but I'm the author of libavif (and the avifenc/avifdec tools), which is the reference library for AVIF. I helped it get integrated into Chrome* and I worked with the author of the AVIF layer for Firefox too (it does not use libavif). I've been taking a more advisory/administrative role in the library's development over the last year, but it is basically my brainchild (for better or worse; just the library, not the standard). The folks that have contributed many changes over the last year are some really smart folks and I look forward to seeing where the library goes. I've also put a bunch of work into our HDR rendering pipeline and analysis tools at my current job, which doesn't necessarily have public impact, but mattered/matters a lot to a few teams at work.
* Before anyone asks, I was not involved in any of the recent JPEG-XL removal choices happening over at Google (I don't work there). I was as surprised as everyone else was. I'll admit I haven't given JPEG-XL as much of a R&D spin as I should, but it seems like it has a lot of cool features and if people prefer it to AVIF, game on. I'm proud of the library, but I'd rather people used their preferred format in any avenue and not be locked into something they dislike. I'd certainly rather that any technology succeed or fail on its own merits than any other possible reason.
It uses the idea of "putting a penny down" on the graph and moving it around, and I found the conversational tone of the description to be very easy to grok. Assuming this is the exact same mechanism (which the author cites), it might resonate for some of you too.
Nice article. On this bit: " It's about how you would write a regex package from scratch, in a language like C that doesn't already have regexes."
There's a 30-line C regex matching program that Rob Pike wrote and Brian Kernighan wrote about here. It only implements . ^ $ * (where c is any literal):
> "Rob's implementation itself is a superb example of beautiful code: compact, elegant, efficient, and useful. It's one of the best examples of recursion that I have ever seen, and it shows the power of C pointers. Although at the time we were most interested in conveying the important role of a good notation in making a program easier to use and perhaps easier to write as well, the regular expression code has also been an excellent way to illustrate algorithms, data structures, testing, performance enhancement, and other important topics." - Brian Kernighan
As I said before: that's a simple backtracker with exponential complexity, and it adding more operators will trigger that behavior faster. I think Thompson's NFA matcher is O(nm), but I didn't check the patent. If it isn't, it's fairly easy to make it that.
Your usage of "wiki" here suggests you meant Confluence (an Atlassian product) vs just "why use anything Atlassian offers", but I think the answer is the same.
Disclaimer: I'm not necessarily advocating for choosing Atlassian's suite of products over a handful of separate open source tools, but just offering a guess from what I've seen at companies I've worked for.
I believe people choose Atlassian's tools as an overall package, often surrounding their issue tracking tool (Jira). If you happen to use/need/prefer Jira for your issue tracking, the wiki-like tool that Confluence offers just happens to be integrated tightly with Jira (and their other tools). If you've already chosen Jira (say) and you need a wiki (Confluence), or a git repository (BitBucket), or a status page system (Statuspage), etc, my guess is Atlassian bundles and integrates this all together in such a way that companies just go for the total package.
To your point, I'm not sure why someone would use Confluence as a wiki over some other wiki software, assuming they had no interest in integrating their wiki with a bugtracker, git repository, etc. I think the selling point has always been the bundling/integration.
I think that’s a fair point to make. What would you say about something like Trac, which is also open-source, includes a wiki and rolls in git along with subversion. Really I guess the ask is this:
Why even bother trusting someone else with reliably hosting data?
Perhaps I'm not up to date on Atlassian's hosting options, but every company I've ever worked at which uses Atlassian (including my current) hosts the servers themselves, I believe. You pay for the software/licenses/updates, and Atlassian simply hands over a pile of Java jars and documentation. It is up to your ops staff to choose a server, fire it up on there, back it up, update it, etc. This would be the same as running your own Trac, right?
The current issues people are running into are the ones who went for the cloud hosting option.
Some do run it onsite which is similar to running Trac but with two major differences:
1. Contributing bugs to Atlassian helps only Atlassian.
2. You have to pay Atlassian.
The counter argument is that a company of Atlassian or even further scaled, at Google’s size, should be able to provide some meaningful customer support or engineering around bugs or issues while using the platform.
But in reality, Atlassian’s cloud outage is over 2 weeks, could have likely been resolved if everything was handled properly on-site (for those who like to play Devil’s advocate, there’s your hinge) as opposed to going to the cloud.
What I’m arguing for is the idea it’s beneficial to everyone to support platforms which enable the user to DIY, and we consider engineers or admins people who do that: Engineer and admin.
In other words: the car industry doesn’t compete over the shape of the wheel, why do we?
If self-hosting is the best option for you, do it. I won’t judge you. I just don’t want to take that option for myself, and I don’t want to be judged for it either.
* https://www.hammerspoon.org/
* https://gist.github.com/joedrago/bfc54f4083b070fe998d519cc6c...
reply