As I understand it, Yuzu was backed by an actual company that they setup to process their "donations", and by getting donations you could get privileged access to new builds.
So for Yuzu there was an legal entity making money off (Nintendo argued) selling access to playing pirated games.
Dolphin doesn't accept donations, so there's no good way of arguing anyone is making any money off it. Sure, Nintendo could go after individual contributors to Dolphin (if they can find out exactly who they are - presumably many of them are aware of the risks and try to stay anonymous) but it would be costly and it's unlikely to yield any positive results.
I think it's more likely the original BeOS source code contains proprietary code licensed from third-parties, which means someone would have to spend significant effort on figuring out what can and cannot be released.
This looks great! As an engineer who has used Mixpanel at multiple companies it has always annoyed me that what you get for what you pay seems quite poor, so I'm very happy to see some alternatives.
I'm also happy to note that you are from (the wrong part of ;)) Sweden.
I have an XPS 13 (the current Intel version, not the ARM version obviously) and they definitely have not. In fact, I've had the touchbar replaced 3 times and the whole computer replaced once because when the touchbar gets too hot, it starts "phantom pressing" the keys on it.
The replacement machine still has the issue, but it has a newer generation CPU which generally runs a bit less hot, so it's not as big an issue as it was on the previous machine.
It might not be a problem for DOS 4, but often the source code of software that was only ever meant to be published as closed source contains source code that was licensed from 3rd parties. This license may not allow publishing the source code.
Doing an investigation of what licensed software was used and possibly trying to get permission from the relevant rights holders (if you can even figure out who owns the rights so many years later) can be a big and expensive task, unfortunately. I understand why companies might not want to take that on (even though it sucks).
AFAIK there's no "certifying body" that would be able to provide an external "certification".
In any case Filip Skokan has essentially made a career out of building open source OAuth stuff, so even if it's a bit humorous that he certifies his own stuff, it's likely that this implementation is one of the most compliant out there.
Their about page (https://rolldown.rs/about) describes why they want to do this, but after reading it I'm still unsure why they can't accomplish their goals by adding features to esbuild? Maybe the project goals are too different?
I'm not sure if you are joking or not, but in case you aren't, your iPhone won't let you directly address subpixels, so no.
There's a whole subcategory of beautiful bugs caused by recursive algorithms going way farther than their authors intended - it probably doesn't apply here.
> This is a topic that is useful for many more situations than just the military.
Fair enough, but that's not who funded your research (according to your own disclosure, the military paid for it).
If this topic is so useful for "more situations" , why didn't those "many more situations" fund it? Will you be conducting research into how this topic will have non-military usages, or is that just something you tell yourself to sleep better at night while the military pays for more research that "is useful for many more situations than just the military"?
Cloud providers (and everyone else) are unfortunately always downplaying their incidents though, so I don't trust that information. I have no idea about this particular case though since I'm not a GKE user.
Would be interesting to hear from actual users how serious this is.
Now I'm curious if it can handle the classic reading comprehension assignment I've been given multiple times in my life. You know, the one that goes something like this:
1. Read through all steps carefully.
2. Do X
3. Do Y
(...)
99. As you have now read through the instructions, simply put your name in the top right corner of the first page.
I once discussed this with a coworker who had worked a lot on various things related to typesetting, and he claimed the main issue with doing good text justification for the web is the lack of good, free hyphenation dictionaries (or rules) for most languages. In order to do full paragraph justification in a way that makes sense and always looks good you need to be able to hyphenate words dynamically (and fairly aggressively).
LaTeX does come with hyphenation libraries for some languages, but web browsers would need wider support. There's also the question of how to standardize this, because you would have to ship hyphenation dictionaries for every language, and you would need to standardize this across browsers so they render pages the same.
LaTeX does ship with hyphenation libraries for a bunch of languages, but if you try to use it for any of the minor languages, you'll find the results are so-so and you need to manually hyphenate words to get decent results (this was my experience a decade ago at least).
All of the above could be solved, but sadly I suspect it wouldn't be worth the cost for the players that would have to be involved in solving it.
I'm Swedish, and I can confirm that all my Swedish cookbooks contain recipes for "pancakes", "crepes" and "American pancakes", which are definitely 3 different things, and a Swedish "pancake" is a lot like you describe it.
I also have a recipe for what my cookbook calls Danish pancakes, or "æbleskiver" in Danish. Those are more like small round doughnuts prepared in a special frying pan. I'm not sure if the Danish would consider those "pancakes" though.
> Did you ever need to do git rebase --continue over and over again just to get your own branch up to date?
Not really. The secret is to rebase fairly often, at the very least daily (depending on the size of the organization you work in, this could be more often). I often see complaints like this from junior devs. They work in isolation on their branch for a week, and then they complain about how hard it is when they try to do a rebase on top of the 100+ commits that happened while they were out there doing their own thing.
Another common issue comes from not understanding how rebase works well enough. You are supposed to adjust just the changes of this commit, not take anything else into account. If you start making unrelated changes when rebasing, your commits will soon conflict with each other, which means you'll run into a lot of very confusing conflicts.
It's fine to squash before a rebase if you are not interested in the history of your branch. But if you are, it's just not an acceptable solution.
So for Yuzu there was an legal entity making money off (Nintendo argued) selling access to playing pirated games.
Dolphin doesn't accept donations, so there's no good way of arguing anyone is making any money off it. Sure, Nintendo could go after individual contributors to Dolphin (if they can find out exactly who they are - presumably many of them are aware of the risks and try to stay anonymous) but it would be costly and it's unlikely to yield any positive results.