Live data from Hacker News

Viewing profile — rich-tea

rich-tea

HN member
Joined
Tue, Apr 30, 2019, 7:17 AM UTC
HN karma
3
Public activity
53 items

About rich-tea

No profile information was provided.

Recent public activity

  1. comment
    Comment #19968836

    With a recent stable or longterm kernel it's simply mitigations=off.

  2. comment
    Comment #19908836

    Oh no, I got the title wrong! Yes, of course I remember what it is about. And, yes, it is perfectly applicable here.

  3. comment
    Comment #19908667

    You may well be right. I probably only notice it with software because that's what I do every day.

  4. comment
    Comment #19908662

    Is it also gatekeeping to say that emacs is for programmers? What about C++? I don't keep any gates. Please come in and learn how to program. I love it and you might do too. But ju…

  5. comment
    Comment #19908646

    Subversion. Or some special purpose versioning system like "track changes".

  6. comment
    Comment #19907269

    Unfortunately this article, like almost all others, is still wrong because it looks like commits get mutated when you rebase and the old commits disappear. It is very important to …

  7. comment
    Comment #19907211

    That's because a file system is something you already understand, even if you've never actually used an old fashioned paper filing system. The software is providing you with someth…

  8. comment
    Comment #19907196

    Git is just for programmers. It was made by and for kernel developers, no less. There are better tools for other people. If you don't care what a DAG is, you will never understand …

  9. comment
    Comment #19907156

    You're actually getting at something deeper which I've been noticing more and more lately. Many people seem really reluctant to learn how to use things. It only seems to happen wit…

  10. comment
    Comment #19907088

    Git is not hard. It's very simple. But people learn it the wrong way. You have to learn it from the DAG up. If you cannot grasp how the DAG works you'll forever be reading and writ…

  11. comment
    Comment #19901614

    I refer you to the children's story "Crying Wolf".

  12. comment
    Comment #19898447

    I actually thought the flag code disallowed flying the flag in bad weather. But I'm now unable to find any confirmation of that.

  13. comment
    Comment #19898428

    The continual broadening of the definition of rape will only dampen its impact and harm the few genuine victims of rape.

  14. comment
    Comment #19898332

    It can contain a link to the list of all invoices. So you could have /customer/ /invoice which lists all invoices for the customer which are actually just links of the form /custom…

  15. comment
    Comment #19898288

    Is that based on the size of the vehicle? In my country it is not. It is only based on emissions. Some SUVs will pay less tax than a small sports car.

  16. comment
    Comment #19890501

    You gained the ability to find the invoice. There is no need to have customer id in the invoice url. Just /invoice/invoice_id is enough.

  17. comment
    Comment #19890479

    > When it storms and gets wet, it’s all I can hear inside my house. Isn't that illegal?

  18. comment
    Comment #19890459

    I agree but I'd also like to see tax paid on size of the vehicle because it's literally using more of the public highway. So motorbikes would still pay less, probably. The SUV user…

  19. comment
    Comment #19890422

    There shouldn't be separate endpoints that take an owner's ID. That's bad design. The owner endpoint should contain a list of invoices, ie. links to the invoice endpoint.

  20. comment
    Comment #19890417

    Indeed. Hyperlinked serialisers are built in and super easy to use. And it makes so much sense when you use DRF's API browser too.

  21. comment
    Comment #19885129

    Why does every docker image build have to pull the packages? Are you force rebuilding and defeating docker's cache mechanism?

  22. comment
    Comment #19884870

    As usual it will take a disaster for people to realise it was a bad idea. Microsoft tried to destroy Linux in the past. Literally. Linux is what gave us git in the first place, and…

  23. comment
    Comment #19882472

    All of these advantages don't make sense if half your commits are broken versions of the software. Rebasing helps ensure that each commit is valid. That's important for the reasons…

  24. comment
    Comment #19882447

    I'm not talking about squashing the feature branch. I'm talking about squashing all of master down to one commit (initial commit). If you don't take care of your history, my questi…

  25. comment
    Comment #19878482

    What do you use your git history for? History is either worth keeping, in which case you should maintain it like any other artifact, or it's not, in which case you should squash do…