Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment Re:Smoke and mirrors (Score 1) 55

Rust touts its amazing memory safe etc, but then it appears that to do much of anything (especially replicate existing non-rust code functionality) then rust reaches for allowing "unsafe" code. So, what was the point?

Is that the design of Rust or is it developers porting existing code in the laziest way by just encapsulating "unsafe" code with a keyword and calling it done? I think is the latter.

Comment Re:How to Make Rust Grow (Score 1) 55

You should be able to use Rust without using Unsafe, otherwise it doesn't solve the problem it claims to solve (or rather, it solves them in a "good enough" fashion, the same as smart pointers in C++ and there's no reason to switch from one to the other).

Do you have examples where Rust is implemented with unsafe? I would think Google implementing Rust code in Android for memory safety would not just allow unsafe everywhere.

Comment Re:Huh? (Score 1) 206

Err you're talking about a car made in a country that literally is just hills coming out of a fault line in the ocean. Kei cars don't struggle on hills. They may not accelerate as quickly. They may not be able to tow a heavy load up them, but they'll do perfectly fine. Hell they are far better than the Fiat 500 - staple of the South Tirol alps.

And you're making the assumption that somehow the OP's roads are "badly designed" based on nothing. Miss the point, much?

Comment Re:That was fast (Score 1) 161

Again, I don't believe anything China says just like I don't believe anything Intel says. Intel said their 14th generation was better than their 13th generation. It was not; it just used more power to artificially achieve better performance.

It is not just the semiconductor industry where China's claims are to be met with skepticism. In high-tech industries like combat aircraft, China's J-20 was lauded to be its next generation stealth fighter that rivals the US F-35. However China also claimed its older (and "stealth killer") J-10C shot down one of their J-20s in a war drill. So their 1990s fighter shot down their "next gen stealth fighter". Can you see what is wrong with that statement?

Comment Re:Growing like C++ does? (Score 1) 55

This is exactly how Rust started, like all projects. Designed by naive usually younger developers but not always (eg. the Java calamity, the Perl 6 debacle, etc).

I would not call James Gosling young nor naïve at 39 when he started Java in 1994. Nor Larry Wall who was 46 when he announced what would become Perl 6 in 2000, a language he started at 33. You can have opinions about their strategies and design but calling them "young and naive" is rather ignorant of programming history.

Then to make it actually work in real life they learn it's not so easy and start shoehorning stuff, and scope creep, and .. .

[sarcasm]As opposed to every other language that never had scope creep. All other languages were perfect on inception to current day. [/sarcasm]

Rust has nearly an identical design to Scala and Scala is like OCAML, and they all suck because the code is nearly impossible to maintain and there isn't enough energy to fix all the bugs.

Er what? Scala was designed to over come the criticisms of Java. It is a high-level language that translates to bytecode and requires a JVM. How is that "identical" to Rust which is more general purpose but can be used as a low-level language that compiles directly into machine code? That's like saying a gasoline combustion engine has "nearly an identical design" to an electric vehicle engine.

Comment Re:Growing like C++ does? (Score 1) 55

Sure but did you ever figure out why no one has yet done that? There are ways to harden C and C++ like with compiler options, but no one has come out with a version that has safety built in. Bjarne Stroustrup has started efforts to harden C++ but that come only after Rust started making progress. The main reason I can see is the some C/C++ developers do not want to be told what to do or how to write safer code. They know better than anyone else. They will not embrace a safer C/C++ just like they will not embrace Rust.

Comment Re:"All your accounts are belong to us." (Score 1) 28

My assumption here, and I know what they say about assumptions, but I'm assuming this is about making sure they can collect fees on those apps that are sold in other parts of the world where they've been forced to allow apps loaded from outside the app store.

And that is the assumption you made. The article specifically mentions "affiliates, parents, or subsidiaries” accounts. The way I read it, if you owe Apple money, Apple is not asking Epic Game Store for the money. If you have multiple accounts, Apple is not limiting withdrawing from the main account. Banks have done this where overdrafts on checking gets pulled from savings or other accounts. I would assume if the amount owed exceeds money in all accounts, then Apple would use a third party debt collector.

Comment Re:"All your accounts are belong to us." (Score 1) 28

So, this is Apple saying that they can arbitrarily make up a number that they believe is a developer's income from an app, then charge them fees based on that vapor-based number, rather than charging based on actual revenue generated?

Where in the world did you read that Apple "can arbitrarily make up a number"? The article says that IF a developer owes Apple money, Apple can pull the funds not from the developer's primary account but other accounts the developer might have. For example if a developer has a separate account for two apps and one of them is in the red, Apple can withdraw money from the other account.

Comment A very loose interpretation of "debt collector" (Score 0) 28

If I read the article correctly, Apple will go after debt that a developer owes them by withdrawing from other accounts that developer might have. If the developer has "affiliates, parents, or subsidiaries" accounts, then Apple will get the money from them. How is that a debt collector again which is normally someone recovering debts for a third party?

Comment Re:Depressingly inevitable (Score 2) 161

The idea that one country can develop a technology that no other can, is as flawed as it is arrogant. And by refusing to sell advanced technology, the reasons to produce domestic alternatives get stepped up a gear - or several. Once you accept that a competitor or adversary has both the ability and the will to create technologies domestically, that they would be prohibited from purchasing, you have to accept that the originator has lost control. What is worse is the possibility that they might just make a better version than you have.

And no one said any of that. In the world today, the current EUV machines are made by one company in the world. It is ASML in the Netherlands. The US nor Japan produces them, and both countries have a long history with making lithography machines. The problem was the cost of R&D and the specific strategies to make EUV was successful only for one company. Making EUV machines is not an easy task that someone can do in their garage this weekend.

Can China copy everything ASML did? Sure. The issue is that it will take them a while to do so as part of the difficulty with EUV is that only very specific companies make the parts as EUV is on the cutting edge of technology. And as long as China is willing to spend huge amounts of money so that their machines are never profitable, they can do that.

Slashdot Top Deals

"A mind is a terrible thing to have leaking out your ears." -- The League of Sadistic Telepaths

Working...