I wouldn't. Tourism has plummeted already. I don't know how things are going for international conferences, insofar they had survived Covid. Based on anecdata, I assume they do feel the isolation.
Usually big sport events are used to improve optics for authoritarian regimes, often outbidding well-functioning democracies. Quatar, China, Russia, Nazi Germany [1] to name a few. I think the world cup football is a welcome event, as it gives some 'normalcy' to the US regime, and legitimacy to their policies. It is interesting to study the history around [1], as not many things have changed how people approach these kinds of dilemmas.
> According to [...], Rove’s grandfather was Karl Heinz Roverer, the Gauleiter of Oldenburg. Roverer was Reich-Statthalter—Nazi State Party Chairman—for his region. He was also a partner and senior engineer in the Roverer Sud-Deutche Ingenieurburo A. G. engineering firm, which built the Birkenau death camp, at which tens of thousands of [...]
Oh, also Rove and Kenneth Lay of the Enron deregulatory debacle that put California hospitals in rolling blackouts in the dark.
> "All of those golfers that remain ‘loyal’ to the very disloyal PGA, in all of its different forms, will pay a big price when the inevitable MERGER with LIV comes, and you get nothing but a big ‘thank you’ from PGA officials who are making Millions of Dollars a year,” Trump wrote. “If you don’t take the money now, you will get nothing after the merger takes place, and only say how smart the original signees were.”
> Imagine a commit in a patch series changes 100 lines. 99 of the lines are good, but the first round of review suggests to add a missing semicolon on one of the lines. The author does that by amending the existing commit, to avoid an unseemly "add missing semicolon" commit ending up in the project history. After a force-push (or new patch series submission), reviewers are generally presented with the full 100-line diff to review, because the tools don't understand that only one line changed since the last review.
In the PR-workflow, why not add fixup! commits? I think that when the PR is approved, the PR owner should be free to rewrite the history in their PR.
Flirt looks interesting, but I am not sure if it would solve a real problem for me.
Urgh. This problem with git is so unforced. Essentially, people want commits to mean 2 different things at the same time:
1. Store the uncurated history of how the project was developed. 1 commit is created whenever a dev types 'git commit'.
2. Be a linear list of PRs / changes / whatever to a project. Each PR is created by squishing many commits together. It is associated with a conversation around code review, a ticket / issue and often some feature or bug.
Commits can't be both of these things at the same time, so we end up with unnecessary tooling like this.
The answer seems pretty obvious. Git just needs 2 separate mechanisms for these 2 different ideas. The obvious approach would be to leave commits as being atomic units of code change, and invent a new concept in git which represents a feature / feature branch. It would essentially just be a metadata object naming a set of commits, and it would have links to an issue tracker, CI results and code reviews.
> The answer seems pretty obvious. Git just needs 2 separate mechanisms for these 2 different ideas. The obvious approach would be to leave commits as being atomic units of code change, and invent a new concept in git which represents a feature / feature branch. It would essentially just be a metadata object naming a set of commits, and it would have links to an issue tracker, CI results and code reviews.
git already has a tool for this called a "merge commit". A merge commit is mostly just a metadata object pointing to multiple previous commits. Sure, this forms a DAG rather than a line, but when all you want to see is a line just walk the graph in a specific pattern. In git that graph walking pattern is usually called `--first-parent`.
Mostly we just need UIs that stop trying to draw a "subway diagram" at all times and just does a `--first-parent` overview. It's strange to me how much work is being put into squashes and rebases and more just to avoid complicated "subway diagrams" when that often would be just fine with merge commits and adding `--first-parent` to your git log defaults and/or pick a UI tool that does that for you.
This is a non-problem. Git primary role is a VCS. What you decide to version is up to you.
On the main repo I like linear commits on the main branch where each is tied to a PR and a ticket number. On my local, how I work is relevant to no one except myself.
When I create a PR, I expect the reviewer to do a full review. If I update, it would be best to also do a full because that’s what will be applied. I believe, as a reviewer, you need to understand the full patch, not little snippets over days.
> Git just needs 2 separate mechanisms for these 2 different ideas
Git is distributed. What is shared between two instances are patches. These are immutables. If I was sent a set of patches that I would not accept for some reason, I would discard it and wait for an updated set of patches. What you propose should be good according to you, I don’t want days long back and forth.
Yeah, I will happily make small commits like this and then squash all of them before merging. There's been a built-in option for this on Github that's been around for close to a decade at this point and is easy to make the default. I don't feel like this is a real problem.
> Taxes don't usually work as efficiently because the state is usually a much more sloppy investor. But it's far from hopeless, see DARPA.
Be careful. The data does not confirm that narrative. You mentioned the 1950s, which is a poignant example of reality conflicting with sponsored narrative. Pre WOII, the wealthy class orbiting the monopolists, and by extension their installed politicians, had no other ideas than to keep lowering taxes for the rich on and on, even if it only deepened the endless economic crisis. Many of them had fallen in the trap of believing their own narratives, something we know as the Cult of Wealth.
Meanwhile, average Americans lived on food stamps. Politically deadlocked in quasi-religious ideas of "bad governments versus wise business men", America kept falling deeper. Meanwhile, with just 175,000 serving on active duty, the U.S. Army was the 18th biggest in the world[1], poorly equipped, poorly trained. Right wing isolationism had brought the country in a precarious position. Then two things happened. Roosevelt and WOII.
In a unique moment, the state took matters in their own hands. The sheer excellence in planning, efficiency, speed and execution of the state baffled the republicans, putting the oligarchic model of the economy to shame. The economy grew tremendously as well, something the oligarchy could not pull of. It is not well-known that WOII depended largely on state-operated industries, because the former class quickly understood how much the state's performance threatened their narratives. So they invested in disinformation campaigns, claiming the efforts and achievements of the government as their own.
BTW the New Deal tried central planning and quickly rejected it. I'd say that the intense application of the antitrust law in the late 1930s was a key factor that helped end the Great Depression. The war, and wartime government powers, were also key: the amount of federal government overreach and and reforms do not compare to what e.g. the second Trump administration has attempted. It was mostly done by people who got their positions in the administration more due to merit and care about the country than loyalty, and it showed.
The post-war era, under Truman and Eisenhower administrations, reaped the benefits of the US being the wealthiest and most intact winner of WWII. At that time, the highest income tax rate bracket was 91%, but the effective rate was below 50%.
Even with Defender etc off, it is not fun. Lots of small file IO brings it on its knees. Some wants to blame the Windows I/O system, I don't know, but what I do know is that when people choose NTFS it is because they haven't an alternative. Nobody chooses it based on its quality attributes. I dare to say there is no NTFS system that is faster than an EXT4 system.
NTFS on Linux should be near-par with ext4 on Linux.
Remember, I said the _file system_ was just fine. It's that extensible architecture above all file systems on NT that causes grief.
The only method to 'turn off' Defender is to use DevDrive, which enforces ReFS, and even then you only get async Defender, it's not possible to completely disable.
The bigger problem is that data can be part of a migration. A diff is far too rudimentary.
If I split a Fullname into FirstName and LastName, a diff will only tell half of the story. In EF Core, you will adjust an Up and a Down generated method to make the change reversible, plus you deal with data transformation there.
So I would love to know how people handle that without an explicit notion of migrations.
If that would be true, expect in the next decade a frantic search for seclusive grey beards, those who haven't given up their rituals and ancient languages.
If your workforce is vibing all day, they will have no capacity for maintenance, because it isn't their code. So the maintenance that happens will be slop and more spaghetti. I am not saying cases like that never existed before, but such companies will face a moment of truth sooner or later.
Some are more tech savy than others here, but I guess almost anyone can do the following trick successfully:
step 1. visit https://endeavouros.com/
step 2. download iso
step 3. flash iso on medium
step 4. boot medium, installation window shows
step 5. you choose KDE, yes: KDE. Do more mouse clicks.
step 6. system tells you it's done, and offers you to reboot.
almost everyone knows the formula for olvine and quartz, too, of course
theres probably less than 10 people in my entire company that know half of the words you wrote there. whats an "iso"? what is "flashing" the "iso"? how do i "boot medium"? what is "KDE" and why do i want to say yes?
(i know what these are, and maybe most people browsing a tech-focused forum with "hacker" in the name, but the vast majority of people do not)
You are right, I somehow forgot the word "here" after "anyone". I don't expect the average laymen be able to follow these steps, but I have those expectations from the people here.
reply