#include 
  int m

  #include 
  int m

Comments URL: https://news.ycombinator.com/item?id=47788678

Points: 4

# Comments: 0

I'm reading the opposite: "If you're currently using any script or technique that inserts or replaces deceptive or manipulative pages into a user's browser history that [...]"

Comments URL: https://news.ycombinator.com/item?id=47740885

Points: 1

# Comments: 1

Not sure if we're all looking at the same plot, but I see things hovering above zero, not exactly at zero.

Leaving aside that I am skeptical millions of Ukrainians sincerely believe the devil has been launching missiles at them from the northeast (regardless of what you write here)... it's rather hypocritical to speak for millions of Ukrainians and then tell me to only speak for myself, don't you think?

Can't speak for iOS and no idea if this relates to the above functionality, but Pixel lets you deduplicate notifications across Pixel devices.

For an app that prides itself on privacy, it's kind of crazy that you're making it so easy to accidentally blow it.

Pretty sure they used "ripped off" correctly: https://dictionary.cambridge.org/us/dictionary/english/rip-o...

- WinForms applications also took visibly longer to load than Win32. I didn't dread loading them nearly as much as WPF, yes, but I still did. They weren't what I'd call "snappy", but they were... usable enough.

- WinForms also stuttered (in my experience) with the GC. Again, not "snappy" in my experience, but this was more dependent on your use case.

- WinForms were .NET 2.0 rather than .NET 3.0, with fewer modules to load. It certainly felt more lightweight, which from my memory (of how the hard disk behaved) correlated with that.

You're still confused, unfortunately. (Note: In everything that follows, I'm just pretending "Arabic numerals" came from Arabic. The actual history is more complicated but irrelevant to my point, so let's go with that.)

First, you're confusing intuitive with logical. They are not the same thing. e.g, survivorship bias (look up the whole WWII plane thing) is unintuitive, but extremely logical.

Second, even arguing intuitiveness here doesn't really make sense, because the direction of writing numerals is itself intrinsically arbitrary. If our writing system was such that a million dollars was written as "000,000,1$", suddenly you wouldn't find big-endian any more intuitive.

In fact, if you were an Arabic speaker and your computer was in Arabic (right to left) rather than English (left to right), then your hex editor would display right-to-left on the screen, and you would already find little-endian intuitive!

In other words, the only reason you find this unintuitive is that you speak English, which is (by unfortunate historical luck) written in "big-endian" form! Note that this has nothing to do with being right-to-left but left-to-right, but rather with whether the place values increase or decrease in the same direction as the prose. In Arabic, place values increase in the direction of the prose, which makes little-endian entirely intuitive to an Arabic speaker!

To put it another way, arguing LE is unintuitive is like claiming something being right-handed is somehow more intuitive than left-handed. If that's true, it's because you're used to being right-handed, not because right-handedness itself is somehow genuinely more intuitive. (And neither of these has anything to do with one being more or less logical than the other.)

Every WPF program was laggy and took ages to even start up (is everyone forgetting hard disk speeds?), partly due to it being managed code. The components didn't feel native either, and the coupling to managed code and garbage collection basically ensured all those would be perpetual issues. Yeah the programming model was beautiful and all, but you're supposedly developing to make your customers happy, not to make yourself or computer scientists happy.

You can see how terrible it would've been to base Windows's shell on WPF by looking at how much users have loved the non-Win32 windows since then.

> It is usually easy to write code that is endian-safe. Any code that is not endian-safe is poorly written and harder to maintain at best, and possibly obscuring security bugs at worst. Any project maintainer should be jumping for joy when they receive a patch adding a big-endian port of their project, especially if it includes reports that tests pass and the software works. That is the sign of a codebase that has a level of sanity that should not be noteworthy, yet is.

And every single sentence is false.

The tower collapses once you remove any of the bases, let alone all of them.