I got annoyed because Ikea has their app with all this info and all it takes is for someone to link it with their systems - they already do when you buy stuff there.
But the use case is quite common in physical shops when ordering something that you are going to pay for when it becomes available.
Same procedure when returning something to the shop. You have to give your personal info and this is what takes 1/3 of the time used by the employees.
I guess I thought that a protocol (wireless or not) to give your entrypted info for the shop to use when alllowed to would be an improvement..
This is why a surprising number of GTK applications (more than I realized) are coded in Vala. I lowkey wish they had just adopted D instead of building up Vala. D is basically compiled C# to me in its own ways.
My takeaway from all this is a little bit different though: I feel this whole situation ultimately some credence to the Scheme/Racket philosophy, where you can effectively make yourself a domain-specific language without ever leaving the base language. In an alternate universe, we don't choose between adopting D or inventing Vala. We can just stay in Racket.
This is a slight tangent, but one possibly unintuitive rule that I always like to add is to avoid asking "why" questions, like
> Why is `x` a single-precision float?
It's unintuitive because as the reviewer you may well want to understand that "why," but the problem is that this phrasing is secretly a personal question, not technical. (By the way, my number one rule of code review is never make it personal. It's about the code, not the coder.) Note that you can't get around this by replacing the "why" with a synonym, like "what is the reason for...," which is just more words and not much better.
The solution to this as a reviewer is to recurse into your own thought process and ask yourself why you want to ask the "why" question, and just say that instead. In practical terms, what this usually means is to just say what you think may be the better alternative and why, which makes it a concrete technical choice that can be discussed.
> I think `x` should be double-precision because [...]. What do you think?
(And if you actually are just curious about the "why" and not implying a coding error, say that explicitly.)
Or maybe he was upset because he expected a lot more from someone who works at Google and has been working on RISC-V since 2019?
I don't know Linus, so I'm not sure what to make of this.
I read the message again to understand the actual issues being discussed. There are two: (1) the patch came too late in the merge window, and (2) the patch adds an unnecessary and obfuscating helper function. I don't have an opinion on (1), but I think Linus is completely right about (2). Calling it garbage is pretty harsh but not really wrong, so I wouldn't even say it's particularly over-the-top.
> Or maybe he was upset because he expected a lot more from someone who works at Google and has been working on RISC-V since 2019?
I don't know Linus, but I doubt "works at Google" carries much weight, and frankly that's an odd thing to focus on. If I had to guess, he probably read the patch, decided it was garbage, and wrote that in a message, not caring about where it came from. That's what I would have done (except I probably wouldn't have explicitly called it garbage, because I'm not Linus and that's not my style).
https://offline.bashnota.com/docs/getting-started
More to the point, why should I hate Jupyter notebooks, and what specific problems with them is the new thing trying to solve?
;)
As someone unfamiliar with systemd-homed, I have a very basic question: why would someone want (or not want) to do this?