cesarb

52 ms·

751.
by cesarb 3y ago
> People move into new homes. Don't people bring their appliances with them when moving?
752.
by cesarb 3y ago
> It has one job, display pixels, that's it, that's all I want it to do. If that's all it does, it's a monitor, not a TV. A TV has a second job: to directly receive over-the-air (and/or cable) channels. That is,
753.
by cesarb 3y ago
That "real names" policy is the reason I have always been careful to never open YouTube while logged into any Google account: the understanding I gathered from the noise back then was that, if you ever logged into YouTube or Googl
754.
by cesarb 3y ago
> No code should cast a pointer to a `long`, ever. Trying to excuse it it with "we don't support 32-bit" is deeply wrong. It's deeply wrong as an excuse but for a different reason: casting a pointer to long also works
755.
by cesarb 3y ago
> At one point 16 bits were universal, and then 32 bits came along and broke everything. That's not an issue in mainstream Linux, since 16-bit Linux (ELKS) never caught on. Other than ELKS and perhaps some new experimental stuff, si
756.
by cesarb 3y ago
The HDMI standard has it (and the cable generation shouldn't matter, as long as it has all pins connected), but does anything actually implement that Ethernet channel?
757.
by cesarb 3y ago
> There's still some 32 bit software (usually proprietary stuff, and/or libraries used by Wine). Wine is going to stop being an issue somewhat soon. The Wine developers are adapting it to work more like Windows, by making even
758.
by cesarb 3y ago
> And incorrect casts from pointers to longs (instead of using uintptr_t). That's not an issue on mainstream Linux, since uintptr_t and long always have the same size, both on 32-bit and on 64-bit. It's an issue only when using
759.
by cesarb 3y ago
> If you can guarantee L2 MTU will be fixed and known for every device along the path then there is not really a need for a variable L3 MTU anymore The L2 MTU is fixed and known for every device on that same L2 network . The Internet is
760.
by cesarb 3y ago
> When comparing solar to nuclear we also need to include storage and dimensioning to get an equivalent 24/7 output. No, that is a red herring. That exact comparison would be only for greenfield projects disconnected from everything
761.
by cesarb 3y ago
This discussion is about truncating at L3, not L2; it assumes that the L2 MTU is fixed and known by every directly connected router, but a L3 packet transits over several L2 networks, each with its own MTU. A L2 network with variable MTU (o
762.
by cesarb 3y ago
I'd add a fourth potential positive aspect of truncation: it could be implemented at full speed in the data path, instead of a separate process running on another CPU to generate, route, and send the ICMP packet. All these advantages w
763.
by cesarb 3y ago
> That is probably the ONLY beef I have with RFCs covering IP/TCP/UDP: did not detail what to do in event of overlapping packets (first overlapped takes precedence or last overlapped overrides old data?) For a correctly operati
764.
by cesarb 3y ago
> most routers can and do read info in tcp/udp headers. Do most routers really do that, or just the ones which are also trying to act as a firewall?
765.
by cesarb 3y ago
> which is odd, since Apple allegedly added support for Webm in iOS 15. I’m on iOS 17. Which video codec? Originally webm could contain only VP8, but nowadays it can also contain VP9 and AV1. It's possible that Apple only implemente
766.
by cesarb 3y ago
> it miserably failed because the OS required x86_64_v2 (I didn't even know this existed: I thought all x86_84 linux OS would boot on that machine...). As the sibling comment mentioned, this decision was made for RHEL 9, so distribu
767.
by cesarb 3y ago
This reminded me of this article from last year: https://arstechnica.com/security/2023/08/windows-feature-tha... (HN discussion: https://news.ycombinator.com/item?id=37151220 )
768.
by cesarb 3y ago
> mkfs.ext4, so you could make a filesystem with 128-byte inodes At the cost of introducing a Y2038 issue. The timestamp fields in the first 128 bytes of an ext2/ext3/ext4 inode are only 32 bits each, they are extended with an
769.
by cesarb 3y ago
> (Swift also crashes on overflows and runs your phone.) AFAIK, over half of the mobile phones in the world, and probably nearly all of the fixed phones, do not run Swift, but instead some older language which does not have this "cr
770.
by cesarb 3y ago
> libjxl is written in C++ so undoubtedly will be full of undiscovered security issues. There's the WebAssembly sandboxing trick ( https://hacks.mozilla.org/2021/12/webassembly-and-back-again... ) which migh
771.
by cesarb 3y ago
> However, unlike Google Glass, modern smartphones play a "camera shutter" sound to at least give some indication that they are capturing an image to the people around you. I just tried with my modern smartphone: it's comp
772.
by cesarb 3y ago
> You could do something like an active optical cable Wouldn't that add more latency due to the extra encoding/decoding step?
773.
by cesarb 3y ago
> Gargoyle is also apt. For those who don't know, this is a Snow Crash reference. Quoting Wikipedia: "Stephenson also describes a subculture of people choosing to remain continuously connected to the Metaverse by wearing portab
774.
by cesarb 3y ago
> I’m not aware of this problem in MSVC The compiler I was thinking of was indeed MSVC. From a quick web search, it seems that more recent versions of MSVC have changed them to be thread safe by default, so if you can make sure that your
775.
by cesarb 3y ago
> Furthermore, such initialization is thread safe so that one initialization happens despite multiple concurrent calls of the function. IIRC, there are some popular compilers in which initialization of static variables inside functions i
776.
by cesarb 3y ago
> Reputation is basically meaningless here. If they fix the software, people will figure that out in short order. What matters is not just "the software is working", but also "the software will keep working" (for both
777.
by cesarb 3y ago
> BUT it's not super useful to say this is good, the hard part is knowing WHEN to put this much effort in and when you can skip it. I learned git in the context of Linux kernel development (its original use case). In that context, t
778.
by cesarb 3y ago
It might depend on which tools you're using. When I'm doing historical research for how a function evolved, I normally run "gitk" on the file, and walk through the commits; the full commit message is shown together with
779.
by cesarb 3y ago
> RFC6598 defines CGNAT IP space as 100.64.0.0/10 That's a relatively recent RFC; there are ISPs which have been using CGNAT for longer than that, and they do use RFC1918 addresses for their CGNAT (for instance, I know of one w
780.
by cesarb 3y ago
> The "magic", as I understand it, of the 192.x.x.x network is that the Internet "knows" to not route it. Networking isn't my strength, so I don't know where, or what part of the my local network decides tha

More ›