skysight-inc/HackerNews huggingface dataset:
I find the logistics hard when it comes to food business - you prepare some good stuff but how to sell it in time so that the food is still fresh? Same goes for ingredients, storage. It seems the most low-risk would be to go with non-fresh food, i.e. keep everything frozen until needed.
As with many things, the solution is complex because the problem is complex. Managing code history in a distributed manner, handling conflicts and allowing cooperative coding is not an easy problem to fix.

Having said this, Git doesn't make it easy by the terminology and concepts that are used. And also the inconcise UI (you use git reset for a lot of very different actions, some harmless, some very destructive) doesn't make it easy for a newcomer. Who will often resort to just remember oneliners or look them up from a manual without knowing what they actually do.

What really helped me in understanding Git was to understand the mechanics of the database on an abstract level. Commits and how branches/tags relate to them. If you understand that commits (not branches) are the tree and the branches just post-it's you put on the commits and can rearrange as you please everything becomes much more malleable. Once you discover commits are hardly ever deleted/lost, but just the post-it's are moved (which makes the commits invisible), things become easily recoverable and fixable. Also not using code, but cats[1] also seems to greatly reduced the complexity of learning Git for me. Visual tools like Ungit[2], Tig[3], or plain Git log[4] help to see the commit tree and attached branches and gives an idea of how the data is manipulated.

There is also the Gitless[0] project which tries to redefine the UI of Git, without changing the data format itself. It offers a different look at the same repository and more clear and dedicated commands/concept to perform certain tasks. And since it just uses Git itself underneath you can seamlessly switch between it and Git without issues.

[0] https://gitless.com/

[1] https://girliemac.com/blog/2017/12/26/git-purr/

[2] https://github.com/FredrikNoren/ungit

[3] https://github.com/jonas/tig

[4] git log --oneline --decorate -50 --all --graph --remotes
If you're going to pay for someone to manage Postgres for you, why not pay an official supporter/contributor to the project? I don't see Google investing in features nor community. Are you simply reaching for whatever seems more convenient?
> In sum, it’s fine to decry the company but I disagree that people who like it and accept its tradeoffs should be immediately labeled as extremists.

Well Apple is notoriously abusive of the developers on its platform. Two things are particularly cried about across most of the ecosystem: the 30% cut they take off pretty much everything and the vague terms that you have to comply with, and that they enforce in a mostly random way (app gets pulled out of the app store, won't tell you why, won't tell you what you did wrong).

Now add the exhorbitant prices for their low-specced, low-quality hardware.

Now add the continual rip-off of their users.

Now add the subject of the original linked page.

At this point I think that yes, defending Apple is extremism.

It's fine to accept the tradeoffs, it's not fine to pretend they do not exists:

- "Yeah this stuff is unreasonably expensive but we have to use it"

that is honest

- "the apple ecosystem is the best for creative and developers and what apple does across all the spectrum is fine"

that is dishonest.
Hyperrealistic 3D Scans
Git's plumbing is simple and intuitive.

Git's UI has grown organically and is still not great for common tasks like undo, however they are working on it and it is slowly improving. For example, they've just added a restore command which should make it simpler to undo changes (git restore filename):

https://git-scm.com/book/en/v2/Git-Basics-Undoing-Things

Things I'd also like to see improved:

Undoing things locally should be very simple and intuitive - perhaps restore will help.

Conflict resolution when changes happen on the same line, so that there are fewer clashes on rebase/merge.

Git log should be compact and pretty by default

Git push should push tags as well by default

Deleting tags etc on a remote has a really weird syntax - git push origin :tagname git push --delete origin tagname just feels really odd instead of using the tag command.

There should be a simple way to add all changes and commit - e.g. git add --all && git commit -m "Message" if that could be git commit "Message" that'd be great (probably not possible but at least a flag on commit would be nice). I have an alias set up for this. I like being able to add files separately to a list then commit too, but that is far rarer, most of the time I want to commit all changes.

A blessed workflow - perhaps this isn't possible but having one workflow would make it simpler to move between repos and simpler. Many projects seem to have settled on main=production with short-lived feature branches rebased off main and edit as necessary locally before sharing on main. This works well for us at my workplace.

git start - a guided tour command which steps a user through a typical workflow and shows them the commands they need (probably about 5 commands initially), and tells them the difference between local and shared commits (fine to change vs never try to change).

These are pretty minor gripes though most of which can just be fixed with some aliases for commands - I'm pretty happy with it and much prefer it to what came before.
I think https://learngitbranching.js.org/ shows the internals of git's graph model quite nicely.
It's the case with most UNIX CLI tools and if the author's complaints are true, do we then have to change all UNIX CLI tools? Maybe? The reality is we can't and probably don't need to.
The correct response to that statistic is to wonder why COVID appears to have so neatly replaced deaths from other respiratory viruses, and to wonder - given the relatively vague symptoms - if there's some reclassification going on.

The wrong response is to ignore the point of the Swedish numbers specifically, even though the conclusions are painful. A reasonable conclusion isn't "oh that's terrible they're lying with statistics" and then proposing a meaningless alternative (nobody cares if COVID shifts expected mortality around by a few months, they only care about deaths that were avoidable and wouldn't have happened anyway). The correct response is to remember that Sweden was supposed to be a bloodbath in which every single hospital would be overflowing onto the streets, in which people would be collapsing unable to breathe in their hundreds of thousands whilst the rest of the world looked on in pity, safely locked down at home.

Clearly that didn't happen, which invalidates the claims of the 'experts' that said it would. When you read their papers the problems that led to these erroneous claims are very clear, but given the top rated comment on this thread it'll probably be a long time before the wider HN community is able to critically examine the deep structural flaws in the field of epidemiology. If ever.
I think it boils down to Git solving a complex problem in a very elegant way. Other version control systems try to simplify the problem, but the result tend to make some part of a dev team more unhappy than git does
SARS-CoV-2 in Italy Since September 2019 (Milan National Cancer Institute)
Yes, that is the part that is inane.
Author did not mention trackpad at all. I have my doubts the trackpad works well, or nearly as well as macOS. Without it being mentioned, I just shaked my head and went on.
Awesome Coder was blocked by an email chain, not a lack of understanding of the code. Unblocking him wasn't a technical challenge:

> She talks to some people in real life, figures out what the confusion is, sorts it out.

She didn't "demonstrate a deep technical understanding of the codebase". She did management work.
Safari generally does current OS minus two.
This kind of tricks is used by sending mail to users with legitimate looking links, which can be used for phishing.
We shouldn't need a cheat sheet. We shouldn't need Linus's brain dump to be able to use a tool. The Git UI directly models the Git internal model and that's just bad design. It's a completely leaky abstraction.

I can use git all right but the fact that I need about 20 different commands to do my job, 95% of them with extra parameters and almost all of them with names that don't reflect what I want to do from a functional point of view is utterly dumb. Again, functional! not technical! The UI should reflect end user functionality, not internal technical details.
There is a technical difference between an local repo and a remote repo (bare repository) - although I think you can clone from a repo and make this "authoritative", what you usually do is (in your client, not the server)

- add a new remote

- push your tree to this new remote

- remove the old remote (optional)

And that's it.

You're further not supposed to make commits on a remote directly. Usually this fails hard, for a reason.
actual link (past google redirect): https://www.cnbc.com/2020/11/15/coronavirus-emerged-in-italy...
The DTK was running an old iPad chip (without virtualisation support) instead of the new M1 chip (with virtualisation support).
I know git internals. But I still struggle to have a correct mental model of developping features on branches that you then merge into a very distant branch.

It is ok when you create a branch from develop, code your feature and merge back to develop.

But then things get messy: you need to backport that feature to some release branches.

And all that is asynchronous (backport feature « n+1 » but not feature « n » nor « n-1 » from develop onto branch 1.0 LTS and branch 2.0-SNAPSHOP. ok done? Perfect, let’s ship that. Good feedback from users? Ok cool. Now do the same with « n-1 »)

you want to keep track of code movements between branches, so you use merge (not rebase or cherry-pick).

Pffffiou I honestly do not know how to handle that at scale with Git.
If anyone can find a link to the study, please replace the link with that.
Yes I agree there are issues with git, and this may be a great solution!

But the github cli tool being pushed on github as the defacto user interface feels like internet explorer all over again.

And this media flurry at the same time as the switch on github away from ssl links is disheartening, frightening, and just another example of Microsoft's fingerprints on this product and our ecosystem.

Combined with the recent DMCA takedown fiasco... I cannot wait until if or when web 3.0 decentralization makes these problems non issues.
I mean this with utmost sincerity: I legitimately never thought “socially progressive” people would advocate banning books. I guess we have many more lessons to learn regarding censorship and puritanism. I’m not surprised about that — I’m just surprised that it was the people I thought could be trusted to not make this mistake that seem to be doing so.
Consider the same piece of "sheet music" delivered by different conductors, eg., Beethoven's 5th:

https://www.youtube.com/watch?v=1lHOYvIhLxo&t=24s
https://www.youtube.com/watch?v=9aDEq3u5huA

Sheet music is a guide for human beings who understand "musical context" to, with much leeway, create a cohesive sound.

The sound created does not have a deterministic relationship to what's written, or else, why have any live music at all?

And, more importantly, even if it did deterministically produce the same "sound", that sound is layered to us by our prior familiarity with instruments (, room geometry, etc.).

We aren't deconstructing it by "mere frequency", but by meaningfully parsing out & grouping frequencies. There is no naive algorithm to do this.
> It will do so with ~2% of GDP in defense spending, basically what Trump wants NATO members to comit.

This "2%" figure is a top contender for "the biggest load of bullshit in politics" award, I (as a German, if it's relevant) hate it with a passion.

The reason is simple - all this target does is incentivize waste and disincentivize control and oversight. After all, if the only thing that's compared is how much money was spent... what's to keep states from blowing the money on bullshit and hoping that the US will save their butt once again?

What would be way better is to define goals on capability targets. Like... France being responsible for having one combat ready aircraft carrier, Germany 200 tanks, UK 7 nuclear submarines. That way governments would be incentivized to keep the vendors accountable to deliver safe and working products at reasonable cost, instead of basically letting them do whatever the f..k they want and milking the taxpayers for shit like marine helicopters that aren't certified for flight over sea (German NH90 scandal).
> Git is one of those technologies where it's super important to get a good grasp of how to internals work.

In my opinion relying too much on user understanding implementation is a mark of bad design. I don't care about more advanced functionalities of git, on daily basis I have very simple workflow that I want to "just work". Sure I can spend few days studying git internals, but it feels unnecessary. Especially given that in the past I've worked with simpler proprietary tools that "just work" (though did not have equivalent of "power" features).

On the other hand I think git is like bash - has some serious warts but it's good enough to be used widely; and unlikely to be replaced by anything else at this point.
Thank you, noticed I published the Google redirect after clicking submit...
Over the past few weeks (i.e. right now), the number of deaths per capita in the European country I live in is far higher than the number of deaths per capita in the USA. Some of the best hospitals on Earth are running out of ICU beds. My country is not alone in this, as you can see in the numbers I provided. This is the context for my response to the original commenter.

You have a different way of measuring the problem and you are extrapolating into the future, and that is also fine. We are just making different points.
Cooper – professional network centered on introductions
Least Recently Used cache in C++
Oh wow, ClearCase. That's a blast from the past that I'd forgotten even existed. CC was the stuff of nightmares.
>This is just orientalism

I've spent time in Vietnam and China, both of which are in the orient and as far as I can see this is a case of China being a bully and using aggression to grab territory off Vietnam and similar. I'd be more anti bully than anti orient.
Am I being down voted because I can't find the specs of the paid version they are offering?

HN, please...
at that point why bother ordering out though? I order prepared food because its fresh and better than I can make it. If its made from frozen ingredients, I might as well make it at home.
> Most people agree these arguments are irrefutable, but no one ever really accepts the conclusion. The experience of having free will is too powerful for an argument to overrule.

It would be equally convincing, also without bringing anything to back it:

> Most people agree these arguments are irrefutable, but no one ever really accepts the conclusion. The experience of reassurance that offers determinism¹ is too powerful for an argument to overrule.

¹ Don’t blame me, the universe determined that things should be in a way which make me unresponsible of all that is wrong in this world. Also that’s the universe determined nature that anything positive should be credited to me.

My current opinion/impression/illusion (you name it), is that free will is an undecidable topic. As you can not "go out" of your actual experiment, you can only pick between models of the outside world. But for this very reason, you can’t "objectively" decide what causes or not your decision of believing in free will or determinism. Deterministic people will say that free-will believers are determined in such a way which forces them to do so, and free-will believers will say that the deterministic mindset people freely chose to believe in a deterministic model.

The concerned issue is not what the external world provides as data, but how we interpret it. That is, how we decide to opt for this or that interpretation. How we decide to opt for a model which includes free-decisions or only completely-bounded-decisions is not evaluable before a model is selected.
> If you have a software engineer being promoted to senior software engineer (1 -> 2) without at least intermediate knowledge of the codebase, that'll make other seniors suspicious/wary.

She clearly did. Without that she would not be able to onboard or contribute to the design discussions and would not be able to help customers out. You can't assume that customers implies non-technical. In mid to large orgs most of your customers are other teams with very technical needs.

> if you hire a software engineer that does mainly/only glue work, you mis-hired

No, it depends on what your team needed. You can't have a 5-person team where everyone is great at crunching code unless your only success metric is LOC produced. You need diverse set of skills to deliver and maintain the product. You mis-hired only if your glue competencies are already covered.

In general I see this as a massive problem that many engineers believe that technical excellence is all that's needed to build a product. It isn't. Design reviews, code reviews, and onboarding for technical staff are very much technical.

And simple technical tasks that are tedious and boring are still technical tasks. And as a senior I would never assign them to a junior developer unless there's a lesson to be learned by doing them (once). If your glue person is picking them and you judge glue person's output by the complexity of those tasks (not technical enough!) then your metrics are wrong.
It's the same situation with USB Bluetooth dongles - many purport to be based on a Cambridge Silicon Radio (CSR - now owned by Qualcomm) chip, but are in fact using one of several cheap alternatives.

Many of these clones have their own quirks, and the amount of work-arounding that's been added to the Linux drivers is quite notable. Kernel 8.5 onwards seems to incorporate most of the fixes, but along the way, patches like this were available:

https://gist.github.com/nevack/6b36b82d715dc025163d9e9124840...

Despite the fantastic efforts of the driver maintainers, I still managed to find a "CSR 4" cheap dongle that threw all sorts of errors in the logs and didn't work. I'm waiting for some Broadcomm chip-based replacements to arrive.
Exactly.

I like to say that git is a "white box". You need to understand the internals to be able to use it.

Contrast this with "black boxes" where you don't have to or even can't understand what's going on.

Some would argue that software shouldn't be built that way, but I will respectfully disagree. It's not an end user facing consumer product, it's a tool for professionals. You wouldn't expect anyone to operate a table saw or a milling machine without some understanding of what's inside the machine.

I do agree that the git user interface is inconsistent and full of caveats. But as long as you understand it's just a directed acyclic graph of commits, you can dig yourself out of any hole you get into.
Unrealistic? The same pricing like many other commercial products in this area, and even cheaper than Google.

EDIT: Posteo doesn’t have custom domains, total deal breaker for me.
It would be great to have a GUI tool that allows you to do common tasks with a sort of Wizard interface with validation, precise human-understandable explanations, delayed execution (like GParted) and Undo functions. Personally, I don't use GUI tools for Git because they are either as complex as the command line version or I'm afraid they do something under the hood that is not what I intended. I'm not sure GUI tools for Git are programmed in a way that makes data loss impossible.

Some kind of troubleshooter GUI tool that covers 90% of all use cases would be great. I'd certainly be willing to pay for it.
Point is, that even assuming winter deaths, Sweden's excess mortality for the year can't at this point get high enough that it'd have been noticed in any normal year. Normality+some winter deaths does not make for a disaster. Yet we see posts here saying it's too early to tell if Sweden is a COVID success or "disaster". That looks like motivated reasoning: under what plausible scenario could Sweden end up a disaster for 2020 with these stats? There'd have to be an actual natural disaster for deaths to become high enough to be noticeable.
> I'm happy to pay a fair price.

But, that's the thing. Would you? OP's article is a follow up to an original that focusses on and explains price forks and how that affects these delivery services. [1]

[1] https://themargins.substack.com/p/doordash-and-pizza-arbitra...

Why would you - the customer - pay a restaurant 24$ for a pizza while you could get that same pizza for 16$ via DoorDash in a far more convenient fashion? How much do you care about the restaurant's business if the exact same thing is offered to you at 2/3rd's the original price just 2 taps on your smartphone removed from your door?

Companies like DoorDash are currently losing money and they are happy about it. Why is that?

It's a cost/benefit trade off. DoorDash perceives covering the remaining 8$ of that pizza as an expense. What they bank on is being able to buy an established position of dominance as a middle man on the delivery market.

Two things are happening right now. The first is a race to the bottom and drive other delivery services out of the market. That happens by accruing as many restaurants and their customers on their platform. The second is that restaurants get pressured over time to lower their own prices since they compete less with the menu's displayed in their windows on main street, but with the cheap offerings on DoorDash or GrubHub.

If and when the price gap closes over time, incumbent delivery services who remain get to flip their losses into a profit.

The societal cost? Keeping a regular restaurant open becomes prohibitively expensive (which is why ghost kitchens are becoming a thing), low wages for gig and restaurant workers, impact on the quality and diversity of the food on order.
>This seems like an iteration of https://qira.me/

But qira README says: QIRA is a competitor to strace and gdb

This is very different in itself. Cutter is competitor to IDA, Binja or Ghidra.
In fact, Debugging in Cutter is still in beta while all other features work very well.
The ability to communicate is a separate skill from the ability to comprehend something.

Once you separate the two skills you get 4 classes of people (with gradations):

1. don't understand it, cannot explain it.
2. do understand it, cannot explain it well.
3. don't understand it well, can explain it well.
4. understand it well, explain it well.

Number 2 are good practitioners and not as good teachers.
Number 3 are good teachers but not as good practitioners.
Number 4 are good teachers and good practitioners.

Everyone wants to learn from a number 4, but they are more rare then the 3s and 2s. Between a 2 and a 3, you'd rather learn from a 3. If you don't need to learn, you'd probably rather work with a 2 than a 3. Basically, even if their mental model isn't perfect, they deliver explanations that can quickly lead others to at least be as good as them and possibly better quickly if you can see the mistakes in their mental models (their descriptions could potentially be 100% accurate without it reflecting their poor mental model).

Anyways, this observation leads to the standard cliche, "Those that can, do; those that cannot, teach."