@xcodesucks To me, "if let" visually suggests "if the assignment is valid" or "if there is something inside this optional that can be assigned", the same way " if ! my_condition" doesn't visually suggest that my_condition has to be true. If your visual intuition has a tendency to skip over tokens, consider FORTRAN or COBOL.

C++''s error printing is very barebones, it basically tells you where the type solver got stuck. Nice error printing is really hard so I don't really blame them, but I think it would be worth some more attention.

did you catch a ddos botnet virus?

Drastically less funny with the new monarch. Old fucks rule the world.

Is it still super deadly? Does the strawberry flavour replace the visceral flight reflex caused by the signs of necrosis bubbling up from untold depths of evolutionary history that has accompanied all warm blooded species, or is the animalistic fear now strawberry flavoured?

@IHateForALiving React has the same shit, as does every mainstream framework, because they all have a custom scheduler. Instead of the really long call stack, React gives you fake bullshit plaintext call stacks, because they conceal the scheduler by logging and then swallowing all errors.

It's truly incredible how IP is enshrined as like a fundamental moral good rather than a practical law to encourage creators to monetize their creation. Every justification for IP laws that has ever been presented is void when the IP is no longer in use, but it's like this magical exception that, unlike literally every other law, requires no justification.

You don't have this problem with other frameworks because source maps are one of very few technologies in JS land that work nearly perfectly, and the two main hazards are that your compiler doesn't generate them or that your bundler strips them out as comments.

Does angular not have source maps? Are they not configured right?

actually yeah, the "if" statement could also be redefined to keep re-running its body as long as the argument is true, breaking every program in existence, and it would be exactly as stupid as the change you're preparing for.

In terms of correctness, a change is a change, big or small. In terms of practicality, people rely on if statements accepting numbers greater than 1. If that was redefined as UB, most real-world programs would translate to an empty executable.

@xcodesucks I see what you mean about C, but that's not what happens in Swift at all. "if let" is _defined_ in terms of optional. It doesn't assume anything about the implementation or truthiness of either, no boolean is ever created, no if statement is ever executed. "if let" shares a keyword with "if" because of their shared purpose of conditional execution.

I'm way more concerned that their manufacturers subvert democrarcy to hinder progress that could render their products obsolete.

Your ultimate safety is that if someone locks you out of your account you can always get in touch with the admin over email or matrix and manually verify your ownership of a bunch of things the account claimed to own in the past.

@tosensei what are you protecting? This is a dying forum. The mobile app has long been off the store. And even when it was active, dfox was just as much a random bloke as retoor is. The stakes are limited by using an alt name and unique password, what happens to those is ultimately up to the randoms.

I also wouldn't trust anything important on that server accesible to Retoor and anyone who makes the slightest effort to gain access, but nothing here actually is important.

@xcodesucks What you describe as "taking multiple lines of machine code" (which is not a useful distinction at all given how many factors affect the performance of machine code) is either a nonzero or an iszero check which is the same cost as a boolean true check, followed by an assignment to local which doesn't exist in assembly and serves purely to encode the value flow graph used by both the compiler and the author in a way that's easy to read by a second human. This is the case whether the optional is translated to a tagged union or a nullable reference. I pointed out that booleans don't exist because you attempted to describe how inefficient the conditional assignment is by pretending that _nil has to be cast to false_ in machine code, an exceptionally funny preposition where neither of the operands, nor the operation actually exists in machine code.

Booleans are exactly as real as optionals too. The dumb tagged union implementation of an optional is literally a boolean, and the nullable reference implementation is created the same way a boolean is created, by assigning one meaning to one subset of the possible values of a number, and a different meaning to another. The main difference is that optionals are a distinct concept so the compiler can choose even more efficient implementations for special cases, such as by niche elimination.

I also don't see why either is bad form. They hide a minuscule amount of behaviour, much less than is lost or gained from arbitrary reordering of non-inlined calls to functions that use different registers, they don't hide any usercode dispatch, they branch on the structure of a container. You can also use the C construct incorrectly like everything in C but its correct use involves a trivial datastructure containing either a 1-based ID such as a pointer or nothing

I don't see how this is worse than the C version. I don't know swift specifically, but I would assume that optional is either a tagged union or a nullable reference, both cases should result in exactly the same optimized machine code as the corresponding C technique for value and reference types respectively.

I've heard a couple experts from both sides entertaining the idea that the reason recruitment is fucked is the same reason dating is fucked; the internet shows you a huge variety of options, but it isolates you such that you forget about all the other people being shown those same options. This completely breaks activities where success is hard to measure and so methodology is never developed, as participants have to purely rely on their thus-broken intuition for judgment.

@tosensei The Win32 API is at present 32 years old and it shows its age. I'd be very surprised if old graphics accelerator APIs still worked the same, and weren't reimplemented in terms of newer APIs that dictate different choices of UB, which in turn broke a bunch of games each time it happened, because game development is a notoriously hacky process rife with dependence on unspecified but nonetheless present environmental factors.

It would appear that cementing market domination, whether that be by subverting democratic institutions or via gifts to the glorious leader, isn't condusive to a good service.

@jestdotty Depends on the community. Reddit works better the more niche your interest, that was its original intent and they never really figured out large subs. The biggest community I'm in is r/IndieDev, and those are overwhelmingly real people.

Both because of echo chambers. Users who can distinguish real humans select for them and are thus identified as an in-group by the algorithm. Users who can't are shown the type of automated content with fake replies that they engage with.

My grandma now has a facebook, she can't distinguish between real and fake human interaction, but she also loathes postmodern and later art and all politics, so her facebook feed is like 10% fake people ragebait and 90% fake profiles uploading scans of modern art. She's happy on average I guess but it's frankly surreal whenever I need to fix something and get a glance into her digital world.

This is on devrant, `.` is a valid URL character, but considering that the file uploader is built for devrant it may be a good idea to urlencode that too, just like spaces.

Also, nuclear recklessness isn't in short supply ever since Russia _besieged a nuclear power plant_, I don't expect any better from the US whose homeland is much further from the site of the attack and is thus much less exposed to the fallout.

can do!

I mean, getting the stuff to explode is pretty much exactly what the facility was working on. It's not like they were purifying it for fun.

@rootshell yeah, I think it's all just to secure billable hours and CV material for the dev.

no really, I need a fucking filter. AI is negatively interesting to me, each time it shows up in a conversation I'm instantly a bit less enthusiastic than I was before,

@rootshell the only part of your criticism I don't get is why the technology and not the incentive is at fault for the abuse. At least JS can be combined with SSR via hydration. Flash, java applets, and VB extensions can't, they are just inherently poorly integrated, and before JS, developers just overused them instead. There is demand for this. The best we can do is make good practices easy with hybrid SSR frameworks.