Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:And the barrier for Rust isn't? (Score 1) 149

I'm pretty sure the number of programmers who know C is several orders of magnitude higher than Rust.

You don't get it. In every respectably-sized C project, there are lots of assumptions about "objects" lifecycles (who allocates, who has to free), concurrency access, etc. Unless you have spent a long time in the code it's difficult to know all the conventions used throughout the project, and you're pretty sure you'll shoot yourself in the foot the first time you'll try to modify the code.

In Rust, all these conventions are encoded in the type system and are checked by the compiler. Which means that when your modification compiles, it already respects these conventions and you're pretty sure it won't break one of those subtle assumptions. At least not so easily than in C. So your patches are easier to review. So the barrier to entry is generally lower.

Comment Rust vs Swift (Score 1) 339

Hi Chris,

I have my opinion about the respective merits of Rust vs Swift, both being relatively new languages with interesting takes on safety, elegance and performance. What's your take on it ? Retrospectively, what would you have done differently in Swift that Rust got right, and what do you think Rust misses that you put in Swift ?

Comment Re:I bet half the people who said "C" actually (Score 3, Insightful) 252

Forcing projects to C avoids possible bugs and unreadable code from cowboy programmers on your team using some of the more esoteric features of C++.

This ! I've been working in several embedded systems companies, and we always have avoided C++ precisely because of this.

It also is a requirement for embedded systems, which includes everything for an arduino and their bigger cousins.

(OTOH not really this, I'm seeing more high-level languages, even JS, everywhere)

Comment Re:Love it. Love it. Love it. (Score 2) 85

I can't wait until everything is routed over USB-C.

You don't get it. Everything will be routed through USB-C, but it will be only one protocol at a time. So you will have to carefully choose your port, cable and device that go together if you ever want Displayport, Thunderbolt, HDMI or whatever else which isn't plain USB working correctly.

Comment Re:No problem (Score 1) 164

But the main "problem" (if you want to consider it so) with Android is that it's a FOSS platform. Apple and Microsoft heavily strangle their respective closed platforms so that OEMs and carriers can't do anything to interfere with Apple's and Microsoft's business (aside from, in the case of Windows, pre-installing bloatware). But since anybody can legally install Android on anything, Google can't use the same kind of leverage. Well, that's a good thing, I say. It means I'm not on Google's leash.

Ubuntu is also a FOSS platform, and it has no problem updating without the PC manufacturer consent.

Slashdot Top Deals

"The eleventh commandment was `Thou Shalt Compute' or `Thou Shalt Not Compute' -- I forget which." -- Epigrams in Programming, ACM SIGPLAN Sept. 1982

Working...