sanxiyn

36 ms·

571.
by sanxiyn 4y ago
> Can AI invent calculus from first principles? The thing is, most people can't. In fact, if you reinvented calculus yourselves, you should be very proud of your mathematical ability.
572.
by sanxiyn 4y ago
Not so strange. Experience of people who write small programs all the time and people who work on big programs all the time will differ. Maybe the author worked on small programs half the time and big programs half the time.
573.
by sanxiyn 4y ago
Who said SOAP is bad? SOAP is good. bugs.debian.org provides SOAP API, and it just works. I imagine maybe SOAP was bad when libraries and tools were immature.
574.
by sanxiyn 4y ago
Well, you could go buy and read Fundamentals of Semiconductor Fabrication (I did). This should give you understanding comparable to reading The C Programming Language. Yes, it is shallower understanding than what you would get by writing a
575.
by sanxiyn 4y ago
> I wonder why number 36 was forbidden The most likely reason is because MySQL used Modular Crypt Format. From https://man.freebsd.org/crypt(3) "The salt must be terminated with the end of the string character (NUL)
576.
by sanxiyn 4y ago
That's mostly because people don't care about their social media posts. What I am saying is that it is demonstrably the case, that writing with stupid grammar and spelling mistakes is not a problem for working professionally. Tool
577.
by sanxiyn 4y ago
> Once you send an email and it's grammatically moronic and full of typos, the jig is up. No? That's what QuillBot is for, and QuillBot, like, exists. It's already the world we live in. Anyone for whom English is a foreign
578.
by sanxiyn 4y ago
It seems ksmbd developers are mostly interested in use cases like SMB Direct which benefits from in-kernel implementation, but most ksmbd users are, at this point, interested in avoiding GPLv3.
579.
by sanxiyn 4y ago
Well, one thing written to test-drive Rust for Linux was in-kernel server for 9P, which is probably the closest thing to ksmbd, in-kernel server for SMB, without being identical: https://lwn.net/Articles/907685/
580.
by sanxiyn 4y ago
Isn't in-kernel implementation necessarily more kernel specific? How is ksmbd more portable than Samba?
581.
by sanxiyn 4y ago
Note that economics doesn't work even with Korean nuclear plants: Korean nuclear is cheaper than Korean gas, but more expensive than European gas, because European gas is pipelined, Korean gas is liquified, and liquified gas is so much
582.
by sanxiyn 4y ago
Surely, guns also hurt predatory animals and historically that's why they were allowed? "Guns only hurt people" is a ridiculous urban bias.
583.
by sanxiyn 4y ago
Google did build Google Earth for macOS. I am not sure whether this supports or opposes your points. Probably supports.
584.
by sanxiyn 4y ago
As far as I know, AdNauseam is not against relevant Google ToS and no ToS term was ever cited.
585.
by sanxiyn 4y ago
From my experience observing Apple and Google in WebKit and LLVM project: it's relative. Of course Apple's culture is not literally "no unit tests" and "no comments", as can be easily verified by looking at sou
586.
by sanxiyn 4y ago
Indeed, battery life shows Apple's goal is being superb, not adequate. For features, that's what focusing on currently existing web is about, instead of future possible web.
587.
by sanxiyn 4y ago
I mean, obviously all of them have slants. I am saying that generally well respected media organizations exist right now without depending on ads, and I don't see what ads-supported media organizations add over that, except variety. Op
588.
by sanxiyn 4y ago
> save newspapers I don't think newspapers (here standing for media organizations in general) need saving. Newspapers have great influence, and they will be funded for that. Let's say, ads go to zero and all newspapers are bank
589.
by sanxiyn 4y ago
> Apple cares about making a browser that renders web pages just adequately enough to be acceptable I think this is biased. It's closer to "Apple cares about rendering currently existing web pages superbly" while "Goo
590.
by sanxiyn 4y ago
LLVM has JIT users, so LLVM can't do this.
591.
by sanxiyn 4y ago
Yes. I guess FastISel still isn't fast enough to overcome larger compilation unit, but isn't it a substantial improvement over the default code generator?
592.
by sanxiyn 4y ago
LLVM's fast path (used by clang -O0) is fast. Rust's primary problem is that it can't use LLVM's fast path (because it implements only a subset of LLVM IR) and LLVM upstream is uninterested in extending it because it wil
593.
by sanxiyn 4y ago
BigGAN trained on JFT-300M and it worked fine. In fact, JFT-300M was easier than ImageNet. In their own words: "Interestingly, unlike models trained on ImageNet, where training tends to collapse without heavy regularization, the models
594.
by sanxiyn 4y ago
Signed integer overflow flag is relatively painless to maintain, because compiler needs to be able to track it for unsigned integers anyway. That is, signed integer was modeled with a pair of flags (interpret bits as signed, can't over
595.
by sanxiyn 4y ago
It is the original reason. For example, register allocation is possible because stack smashing is UB.
596.
by sanxiyn 4y ago
> If you care that much about 1% you are probably already writing the most performance critical parts in Assembly anyway. I call this hotspot fallacy and it is a common one. This assumes there is relatively small performance critical par
597.
by sanxiyn 4y ago
Sure, I 100% support changing the C standard. Until it is done, compiling with flags is infinitely easier than trying to avoid these UBs.
598.
by sanxiyn 4y ago
Wikipedia has pointers here: https://en.wikipedia.org/wiki/Unisys_OS_2200_programming_lan... . It seems links are now broken, but googling e.g. "Unisys publication 7831 0448" etc. should lead you to correct do
599.
by sanxiyn 4y ago
Right, UB is essential part of C and can't be turned off. But it's entirely possible to turn off integer overflow UB by compiling with -fno-strict-overflow, and you should use it.
600.
by sanxiyn 4y ago
It is already implemented: -fno-strict-overflow.

More ›