181 karma · joined August 15, 2022
Before 2004 Germany had a %vol limit for selling alcohol to 16 year olds. In 2004 they changed the law such that it is not based on percentage, but whether it contains distilled alcohol to prevent under 18 year olds from drinking sweet alcopops, which apparently was a big thing back then.
> This mirrors how Apple has always segmented Pro vs. non-Pro iPhones: base models got LTPS panels while Pro models got LTPO, and only with the mainline iPhone 17/17 Plus did that gap close the standard versions previously lacked the smoother 120Hz ProMotion technology and the always-on display feature, unlike the Pro models — the 17e is the one model line still using the older, cheaper panel.
(emphasis mine)
I mean, I can guess what it is trying to say, but who RL'd this nonsense?
Nobody expects an engineer to be a git expert, but if a senior software engineer has heard of git only yesterday or don't have a vague concept of how DVCSs like hg or git work (DAG of commits), then something has gone very wrong.
Maybe there are use cases where SVN is superior (I can't come up with any but they may exist), and maybe engineers in that industry really are so specialized that they never get around to working on anything else!
But maybe it's because nobody else is willing to hire them.
I think I disagree a little bit about the value of type and lifetime annotations, I think if I used this, I would put a lot of [sig ..] into my code.
I think having a similar syntax for lifetimes would be valuable so I as a developer can make sure that some value is not 'static (or has the lifetime of some other object that lives as long as my program). Basically I want to ensure that my values are actually dropped at some point.
One thing the docs could be more explicit about is where this runs. I saw that it has a Wasm backend, but can I also compile this to native code? Do the effects require some runtime (and I don't mean something like the JRE, more like what Go has)? Maybe I missed this, though.
Anyway, I hope I get to play with this soon!
Because if you apply it to binary search, you need to compare the strings at every step, and by that logic, each of these operations is O(log n), which means your binary search is now O(log^2 n).
I guess the crux is that we are still comparing apples to oranges (or multiplication operations to comparison operations), and at the end what probably makes hashing faster is that we are not branching.
Still I don't think it makes sense to think of both hash tables and binary search as O(log n).
But I hope we have more efficient ways to do this in a century.
Edit: But you are of course right about inflation! According to this website[1] it would bump them to 3.2 EUR/h.
[1]: https://www.inflationtool.com/euro-netherlands/2005-to-prese...
> retn 4
> That's it.
I've seen this before; it's a random() function.
E) (I believe) don't enable E2EE with more than one device
You make it sound like it happens all the time and everyone is used to it. I know of once case (Pimmel-Andy), and that led to a shitstorm, including part of the police operation being declared unlawful after the fact.
https://www.lto.de/recht/nachrichten/n/landgericht-hamburg-a...
(neither the "me" nor the "you" here refer to you or me personally ofc.)
2. The "more free" market in the US seems to have produced worse food, based on what I am reading here
I guess the words "could" and "potentially" are doing quite a bit of heavy lifting here.
Either way, I agree it's a cool project! The transparency is needed, on both sides of the pond.
I get why they capture this data, and by doing so they managed to build an exceptionally great service. But I also understand why one would be uncomfortable with exposing this data.
Edit: Not sure why I am being downvoted, I tried to say the same thing dmonitor said.