sleep_deprived

joined 1 month ago
[–] [email protected] 25 points 2 days ago

Fun fact, Rust has a special error message for this:

Unicode character ';' (Greek Question Mark) looks like a semicolon, but it is not.

It also detects other potentially confusing Unicode characters, like the division slash which looks like /.

[–] [email protected] 18 points 2 days ago (2 children)

Tell me you don't know what a programming language is without telling me you don't know what a programming language is

[–] [email protected] 79 points 2 days ago (1 children)

I have this great idea for an app, we can go 70/30 on it! 70 for me because the idea is the hardest part after all. So basically it's Twitter plus Facebook plus Tinder with a built in MMO. You can get that done in a couple weeks, should be pretty easy right?

[–] [email protected] 2 points 3 days ago

In simple terms, they just don't allow you to write code that would be unsafe in those ways. There are different ways of doing that, but it's difficult to explain to a layperson. For one example, though, we can talk about "out of bounds access".

Suppose you have a list of 10 numbers. In a memory unsafe language, you'd be able to tell the computer "set the 1 millionth number to be '50'". Simply put, this means you could modify data you're not supposed to be able to. In a safe language, the language might automatically check to make sure you're not trying to access something beyond the end of the list.

[–] [email protected] 3 points 3 days ago (2 children)

No, the industry consensus is actually that open source tends to be more secure. The reason C++ is a problem is that it's possible, and very easy, to write code that has exploitable bugs. The largest and most relevant type of bug it enables is what's known as a memory safety bug. Elsewhere in this thread I linked this:

https://www.chromium.org/Home/chromium-security/memory-safety/

Which says 70% of exploits in chrome were due to memory safety issues. That page also links to this article, if you want to learn more about what "memory safety" means from a layperson's perspective:

https://alexgaynor.net/2019/aug/12/introduction-to-memory-unsafety-for-vps-of-engineering/

[–] [email protected] 9 points 3 days ago

A person that does popular repacks of pirated games - essentially, she takes a pirated game, compresses it as best she can to optimize download size, adds an installer that also handles decompression, and ships it as a new torrent.

[–] [email protected] 1 points 4 days ago

Of course! Thanks for the discourse. Makes the world go 'round.

[–] [email protected] 7 points 4 days ago (2 children)

And as I said, if they manage to entirely switch, I won't have reservations.

As far as security in extant browsers and C++, see here: https://www.chromium.org/Home/chromium-security/memory-safety/

The Chromium project finds that around 70% of our serious security bugs are memory safety problems.

It's a serious issue.

[–] [email protected] 8 points 4 days ago (4 children)

Depends on a lot of factors. Due to uncontrollable factors like small untrackable debris, more satellites is always more dangerous, but that's still an extremely small problem. If all the Starlink-style companies cooperate properly and adopt high tech solutions for collision avoidance, it'll probably be fine - space is really, really big. Additionally, the extremely low orbits are a great mitigating factor for potential parts failures; even if a satellite outright dies, losing its telemetry and maneuvering capability, it'll be gone pretty quick.

Honestly, more than anything, I'd be concerned about the recent science showing that satellites burning up on reentry could be very significantly more damaging to our atmosphere and the ozone layer than previously thought.

[–] [email protected] 3 points 5 days ago (4 children)

Yeah, it was ok when the project started. The issue begins once it transitions from a toy to a potential competitor with Firefox.

view more: next ›