If you use VSCode, open both files and then ctrl-shift-P "Compare active file with ..."
You're welcome.
Languages that make use of references rather than pointers don’t have this Dualism.
It's not about references vs pointers. You could easily have a language that allowed "null references" (edit: too much C++; of course many languages allow null references, e.g. Javascript) or one that properly separated null pointers out in the type system.
I agree with your point though, using a special Null value is usually worse than using Option or similar. And nullptr_t doesn't help with this at all.
I agree Bluetooth (at least Bluetooth Classic) is not very well designed, but not because of frequency hopping. That improves robustness and I don't see why it would cost any more power. The hopping pattern is deterministic. Receivers know in advance which frequency to hop to.
Yet another? The only other one is Node's and that is trash.
Sorry that example was a bit too limited to demonstrate the problem actually. Add a second lambda and you hit the issue:
Still totally fine from a safety point of view, but the borrow checker can't figure that out.
So either you agree with what it's called or you're "disruptive" and should be banned? Hmm.
I read a load of his comments and they seem quite reasonable. A million miles from ban-worthy.
I just looked up Deno and it’s part of an NPM stack.
It's not. It supports NPM modules for backwards compatibility, but the whole point is that it doesn't inherit the NPM tooling mess. You can go from a new Linux install to a running Fresh project in 3 commands.
You're right of course. I think the issue is that Linux doesn't care about the UI. As far as it is concerned GUI is just another program. That's the same reason you don't have things like ctrl-alt-del on Linux.
Yeah possible, but this of the amount of effort that would take!
If the build scripts were tiny and checked then the attack vector would have just been different, I’m not even too sure the language mattered.
I have to disagree here. Maybe they would have found another way, but it would have been a more obvious way, which is a very good thing.
Yes it would have still been compromised but it may have been detected earlier. So it's still pretty bad to have these incomprehensible build scripts.
That's just Typescript with extra steps.
Though I have also done this once or twice for single-file projects where I didn't want to deal with actually running tsc. It has some annoying downsides though, e.g. you don't get to have a tsconfig.json and the syntax sucks.
Microsoft had a proposal to allow TS annotations in JavaScript which would have been awesome and fixed the syntax issue.
Looks like it was discussed a year ago and hasn't really made much progress. Seems like lots of people wanting to shoehorn runtime type checking onto it.
FizzyOrange
joined 1 year ago
It's cloud based though... Not ideal. I get why they had to do that (they didn't want to expose people to the Python infra shit show) but it's still kind of a shame.
Would be better if they added Typescript support IMO.