![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/b13dd487-9001-491f-b5b2-60fe23af667a.png)
decades too late
Actually almost 100 years now.
decades too late
Actually almost 100 years now.
If you send them the message in plain text they have no way of verifying you aren’t just making it up to get someone you don’t like banned. Keeping it encrypted means they know the sender wrote it.
If it’s with asymmetric encryption, wouldn’t it be possible for the report button to generate a key based on their private key which can only be used to decrypt the given message?
I believe Java is the best option for this type of application
Why?
Rust’s speed is a cherry on top. The main reason to use it is its language design / correctness guarantees.
I’ve been programming for several decades and understand nuance and subjectivity vs objectivity when it comes to this, and strongly believe Rust is just objectively much better than Java as a language.
One example is that Rust doesn’t have null while Java does. The creator of null gave an excellent talk called The Billion Dollar Mistake about why null was such a bad idea, and said languages shouldn’t not have used it. Instead, the alternative he gives is what Rust does.
Things like this are actually hugely important.
Also, Rust was “most loved” language in the StackOverflow developer survey for eight years in a row for a reason.
Other than Sublinks, I have never seen anyone post about how they really want to work with Java.
Doesn’t it just use Google / Bing under the hood? If those both suck then it wouldn’t improve much, right? Isn’t SearXNG more about privacy?
Cross platform? It’s a browser extension.
Java is horrible. And Lemmy is open source. We could just fork it and have the best of both worlds.
Rust is mainly designed to overcome common memory problems people have with low level C systems without the overhead of garbage collectors
So you didn’t read my comment then.
A concrete example of what my comment means is opening files. When you open a file handle, you can read from it, write to it, but then you should close it. After you close it you shouldn’t be ready to or write from it again. If you do, bad things can happen.
Rust is the only language where you cannot. It’s a compile time error. This has nothing to do with low level systems programming. Using file handles is very high level.
Same goes for thread safety. Web servers often can benefit from multithreading. Java does not enforce thread safety at compile time. If you send some data across threads and you don’t already understand what is thread safe and what isn’t, you’ll end up with data races, which is a form of memory safety violation. This is not possible in Rust, but it is in Java.
Rust also isn’t subject to “the billion dollar mistake” since it doesn’t have the concept of null references. It also doesn’t support exceptions, which are the exact same issue as null references. These are also general programming problems and not specific to low level systems.
Regarding frameworks, I’ve used Spring before and, although Rust doesn’t do some things Java frameworks do, IMO that’s a very good thing, and the web frameworks I’ve used in Rust have been a far better experience than what I saw from Spring.
“Having a car with no seatbelt is not a problem if you’re a good driver”
LMAO
Rust is a general purpose language which is excellent for API servers and many other things. I’d say it’s definitely a direct competitor to Java. The only difference is in the ecosystem of libraries.
Rust’s type system is really just about enforcing correctness, which is very important in a general sense. Memory safety is just a subset of correctness.
You can see this is in practice since there are a TON of devs like myself coming to Rust from JavaScript.
What’s the point of that?
That seems like a reasonable approach though, unless I’m missing something. If you need “loads of credit cards” then you’re already but living within your means.
Holy shit, it looks so much better, and it’s written in Rust.
Mobile is horrible though.
Exceptions opt out of the type system. The problem with them is the same problem as null. Here’s a video of the creator of null explaining: https://www.infoq.com/presentations/Null-References-The-Billion-Dollar-Mistake-Tony-Hoare/
Null and errors are just values at the end of the day, and should be treated as such. Doing so means your code is far easier to reason about.
Rust takes this approach and is one of the many reasons people love it so much.
If you can write off JS because “you have to use it because it’s the internet” then I can write off Java because “you have to use it for billions of 20 year old legacy applications”.
You actually think there’s more Java code than JavaScript? Basically every website in the world feels the need to use JS nowadays.
I don’t think these are actually ways you’re supposed to hold them.
Ah I see. Yeah, that is better.
Similar to OG Beauty and the Beast. Originally the Beast was kind from the start and it was all about appearance. Disney changed it so he was a fixer upper. Kinda misses the whole point.