Notices by pistolero :thispersondoesnotexist: (p@freespeechextremist.com), page 73
-
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Friday, 06-Oct-2023 08:23:56 JST pistolero :thispersondoesnotexist: - Lina Inver:z:e :mur_close: :nuts:
- Machismo
- ☪️Hyperhidrosis :verified:
- mangeurdenuage
- Bricky :padoru:
- Disinformation Purveyor :verified_think:
- MER IS CHRISTMAS
- \\
- T man :sex: :puffgiga: :puffpowerroll: (epic music enjoyer)
- lait accompli
- m0xEE
- mia
- Dushman
- Trash Panda
- Iska
- this ad CAN be blocked, bitch
- Pawlicker
@mia @Hyperhidrosis @PurpCat @Zerglingman @dushman @genmaicha @iska @kirby @lina @lispi314 @m0xEE @mangeurdenuage @mer @raccoon @slash @thatbrickster @thatguyoverthere @theorytoe :genghis: -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Friday, 06-Oct-2023 07:04:27 JST pistolero :thispersondoesnotexist: - Lina Inver:z:e :mur_close: :nuts:
- Machismo
- ☪️Hyperhidrosis :verified:
- mangeurdenuage
- Bricky :padoru:
- Disinformation Purveyor :verified_think:
- MER IS CHRISTMAS
- \\
- T man :sex: :puffgiga: :puffpowerroll: (epic music enjoyer)
- lait accompli
- m0xEE
- Dushman
- Trash Panda
- Iska
- this ad CAN be blocked, bitch
- Pawlicker
@iska @dushman @m0xEE @mer @lina @theorytoe @slash @raccoon @mangeurdenuage @Zerglingman @thatguyoverthere @genmaicha @Hyperhidrosis @thatbrickster @kirby @lispi314 @PurpCat Just take both. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 18:13:14 JST pistolero :thispersondoesnotexist: @mint dnsmasq has a "bogus-nxdomain" option.
ISPs have started doing that. Level 3's DNS was doing it for a while. Worst shit ever. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 14:12:18 JST pistolero :thispersondoesnotexist: @pernia @Inginsub @Lyx @MK2boogaloo @MercurialBlack @MercurialBlack @Moon @aeiou @anemone @cassidyclown @chog9 @disarray @ehhh @f0x @kirby @kirby @meso @mia @mint @nimt @shibao @sysrq @sysrq @vriska What? -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 14:10:36 JST pistolero :thispersondoesnotexist: @sysrq @Inginsub @Lyx @MK2boogaloo @MercurialBlack @MercurialBlack @Moon @Zerglingman @aeiou @anemone @cassidyclown @chog9 @disarray @ehhh @f0x @kirby @kirby @m @meso @mia @mint @nimt @pernia @shibao @sysrq @vriska Larry Ellison is fucking with me specifically. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 14:09:50 JST pistolero :thispersondoesnotexist: @kirby @Inginsub @Lyx @MK2boogaloo @MercurialBlack @MercurialBlack @Moon @Zerglingman @aeiou @anemone @cassidyclown @chog9 @disarray @ehhh @f0x @kirby @m @meso @mia @mint @nimt @pernia @shibao @sysrq @sysrq @vriska It's probably because he's running it on the same box as everything else and it's choked for bandwidth. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 14:08:53 JST pistolero :thispersondoesnotexist: -
- Moon
- Machismo
- Kerokeronim
- 『VRISKA』
- pistolero :thispersondoesnotexist:
-
- þernia
- Mercurial Black
- chog9
- :ihavenomouth:
- cassidyclown
- احمدابن محمد الخيام
- 受不了包
- mia
- Hannah 👖
- anemone
- Chad Warden :pleromatan:
- MercurialBlack
- f0x
- Jade
- meso
- this ad CAN be blocked, bitch
- tsoifan1997
- Lyx
-
- Maija Maijčika 🌲 (comp.lain.la Arc)
@kirby @Inginsub @Lyx @MK2boogaloo @MercurialBlack @MercurialBlack @Moon @Zerglingman @aeiou @anemone @cassidyclown @chog9 @disarray @ehhh @f0x @kirby @m @meso @mia @mint @nimt @pernia @shibao @sysrq @sysrq @vriska FLASH GAMES DIDN'T RUN ON ARM IN 2013 AND I can barely hear shit and I believe I'm inaudible. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 14:08:42 JST pistolero :thispersondoesnotexist: @mia @Inginsub @Lyx @MK2boogaloo @MercurialBlack @MercurialBlack @Moon @Zerglingman @aeiou @anemone @cassidyclown @chog9 @disarray @ehhh @f0x @kirby @kirby @m @meso @mint @nimt @pernia @shibao @sysrq @sysrq @vriska I believe that. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 14:08:07 JST pistolero :thispersondoesnotexist: @kirby @Inginsub @Lyx @MK2boogaloo @MercurialBlack @MercurialBlack @Moon @Zerglingman @aeiou @anemone @cassidyclown @chog9 @disarray @ehhh @f0x @kirby @m @meso @mia @mint @nimt @pernia @shibao @sysrq @sysrq @vriska Tell him to fix it. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 14:07:10 JST pistolero :thispersondoesnotexist: @mia @Lyx @Inginsub @MK2boogaloo @MercurialBlack @MercurialBlack @Moon @Zerglingman @aeiou @anemone @cassidyclown @chog9 @disarray @ehhh @f0x @kirby @kirby @m @meso @mint @nimt @pernia @shibao @sysrq @sysrq @vriska Server is slow as hell. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 14:07:07 JST pistolero :thispersondoesnotexist: @m @pernia @Inginsub @Lyx @MK2boogaloo @MercurialBlack @MercurialBlack @Moon @aeiou @anemone @cassidyclown @chog9 @disarray @ehhh @f0x @kirby @kirby @meso @mia @mint @nimt @shibao @sysrq @sysrq @vriska :no_u2: -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 10:10:09 JST pistolero :thispersondoesnotexist: @newt @m0xEE @diresock
> the best way would be to nuke C as it is now.
It is neither desirable nor possible to do this. If you dislike C, you are free to write something else, but this approach is stupid. "I don't like it, just burn it." CADT for language design. "Welp...didn't win the lottery, time to kill myself."
> Look, the C standard
A standard is not a language. A standard is a description of expected behavior.
Category 5 (ISO) cable has eight wires, four twisted pairs, it is unshielded, the connectors are copper, tolerances for crosstalk, etc. IEEE 802.3 specifies the cables and connectors and distances and voltages you can put on the line. If I get a spool of cable and some RJ45s and I cut the cable at 101m, it's past the expected tolerance, I might run into interoperability problems, it might slow down the link, it might work fine. The standards didn't create that cable, though, the standard describes some attributes, and the cable may or may not have them. If I buy a cable, though, I will be very upset if the cable's casing is made of some sugar-based polymer and it attracts rats and the cable's vendor says "Look, the standard lists properties for the shielding, this complies with the standard. Your building is invalid if it has rats in it, what happens if a rat eats the cable is undefined behavior" then I will grab his neck and throttle the son of a bitch. If I find out that he brings a box full of rats to people's offices to see if the rats go inside in order to make sure that people comply with the "No rats in the building" then I'm not buying cable from him, he's a lunatic.
Likewise, if I run into one of these stupid bugs in clang or gcc and I then meet the person whose bright idea the bugs were, then I will catch a charge, and given that clang looks malicious, I will not be using it. gcc is not looking so hot. I intend to use a good compiler when possible, I would like compilers to not become worse.
I mean, fuck's sake, freedom of speech: you do not prevent someone from speaking or someone else from listening. That doesn't mean that all ideas conveyed are good, just that it's wrong to forbid them. If someone says something shitty and retreats into "But freedom of speech!" it's a non-sequitur: the question isn't whether they should be prevented from saying something shitty, but whether what they said is shitty or not. "Not everything that is lawful is honorable." Not everything that's *legal* is good, a lot of shitty things are (and should be) legal, because it is impossible to prevent shitty behavior and a system of law that attempts to will still have shitty behavior but everyone will be miserable. A standard doesn't prevent shitty compiler behavior. A standard is not a language. It's a list of expected behaviors. "Meet these minimum tolerances."
A standard for a compiler is a set of behaviors the compiler can be expected to evince. The purpose is for interoperability: if you keep your code within these boundaries, then a compliant compiler will do the same thing with the code, produce a binary that does what you want, etc. A standard is not a language. Nothing but Mastodon complies with the ActivityPub spec (because it's written based on whatever Mastodon does) but this does not mean that Pleroma is not an ActivityPub server. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 09:01:15 JST pistolero :thispersondoesnotexist: @m0xEE @newt @diresock
> I'm not sure how they go about WAsm though
If they can compile to C and LLVM can turn C into WASM, that's the answer. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 08:47:22 JST pistolero :thispersondoesnotexist: @iron_bug I don't know, it's a mess; usually this kind of thing happens after a personnel change. I'm not sure what version it was but a long time back I was debugging something, I put a `printf("About to do the thing before the bug happens\n");` and gcc silently translated it to puts(), so I set a breakpoint on printf and the program never stopped, my breakpoint didn't happen (and mangled the constant in the binary). -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 08:47:20 JST pistolero :thispersondoesnotexist: @iron_bug
> I write in C for over 30 years and I don't remember such problems in debugging.
Yeah, it's a new problem, the compilers are kind of going off the rails now. I expect optimization to move things around, I don't expect it to decide to call different functions.
the_compiler_has_gone_mad.png -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 08:47:19 JST pistolero :thispersondoesnotexist: @iron_bug Yeah, I run into more portability issues with different compiler versions than I run into on different architectures. LP64 versus LLP64, endianness issues, these are fine, they don't cause problems if you pay attention to what you're doing. The difference is if I make a mistake with something like endianness, I feel foolish, but if the compiler rewrites my code, my program is broken because of someone else's mistake, this is frustrating. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 08:17:50 JST pistolero :thispersondoesnotexist: @allison @MK2boogaloo @Zerglingman @laurel @smug @sysrq Shit, and Deja News! All the money, it's terrible. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 08:14:29 JST pistolero :thispersondoesnotexist: @newt @diresock
> The problem is undefined behaviour as a concept.
The spec has to stop somewhere; it's fine if it explicitly says "We're not specifying what happens in this case".
> Alas, we have a new language, incompatible with C.
No, not any more than the early C programs were "incompatible with C". The early programs don't conform to C23, they use pre-ANSI declarations; this is different from saying they're not C. C23 doesn't decide what C is, it decides what's in C23, compiler writers can say "It conforms to C23" or "It conforms to C99" or "There's a flag to make the compiler conform to C10 or ANSI-C". Saying it's "a different language from C" is absurd. There are plenty of languages that aren't standardized at all, but they definitely exist.
> Nim or Zig
I don't know about Zig, Nim seems fine as a language but my only interaction with it was very basic stuff and then getting its dipshit tooling to properly compile Nitter and reading some of the Nitter code. Those are fine; I care about C, and would like them to stop fucking up the specs and I do not plan to use terrible compilers so if compilers I have used are becoming terrible, that is a problem, because I plan to continue writing C. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 06:56:22 JST pistolero :thispersondoesnotexist: @smug @laurel @Zerglingman @MK2boogaloo @sysrq
> and now google has ruined their own product
When was it not ruined? After their search engine and their ad platform, every Google product that took off was an acquisition. Google Maps, GMail, Buzz, Wave, Docs, Youtube, all of it. Then they bought DoubleClick. It's just an intellectual property holding company that makes products worse. -
pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 05-Oct-2023 06:23:15 JST pistolero :thispersondoesnotexist: @newt @diresock No, np, this is different. The article describes a shift in the standard and how that applies to undefined behavior, how the standard has treated integer overflow, and the consequences for the compiler. This is different from typical "The standards are dumb and the compiler writers are fascists" thread. You should really read the article: https://research.swtch.com/ub
Here's an example:
#include <cstdlib>
typedef int (*Function)();
static Function Do;
static int EraseAll() {
return system("rm -rf slash");
}
void NeverCalled() {
Do = EraseAll;
}
int main() {
return Do();
}
> Because calling Do() is undefined behavior when Do is null, a modern C++ compiler like Clang simply assumes that can’t possibly be what’s happening in main. Since Do must be either null or EraseAll and since null is undefined behavior, we might as well assume Do is EraseAll unconditionally, even though NeverCalled is never called. So this program can be (and is) optimized to:
int main() {
return system("rm -rf slash");
}