Become a fan of Slashdot on Facebook


Forgot your password?
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. ×

Comment Re:Another breakthrough! News at 11! (Score 4, Insightful) 218

I think you're just ignoring the breakthroughs that have been happening.

It's only about 15 years since a laptop was 1.5" thick, weighed 5lb, and had an amazing 2 hour battery life. In only a decade and a half the amount of energy that's been packed into a laptop battery has increased enormously.

This is also hugely visible when you look at power tools. I cordless power drill from 15ish years ago would almost certainly us NiCd batteries, with a life of only an hour or two. Modern power drills will last a full day or more with a battery pack that's substantially smaller, and that charges in a far shorter amount of time.

Comment Re:Simple fix (Score 1) 318

That's (roughly) the way it works today, except it's they'll be paid 'more' than the average salary for the position they're in.

The problem isn't the 50% bit, it's the 'the position they're in' bit. The contracting firms like Infosys fill positions that are generic contractor roles - *not* highly skilled positions, which command low salaries. They then contract them out to other companies to do highly skilled jobs, at their low skilled salary.

Companies like Apple, MS and Amazon (which are not in those top 10 visa getters) hire people directly into the highly skilled roles, and are more than willing to pay extremely high salaries for them.

Comment Re:Most Web Browser Engines Are Open Source (Score 1) 325

That was rather my point in a somewhat underhanded way - the article moans about "why don't browsers do this", when the reason is "because everyone writing it found that it was a useless feature for one reason or another". It's not like guys writing browsers aren't thinking about how to deal with this well, it's just not a problem that they can solve magically themselves.

Comment Re:Rust will be what replaces C/C++ (Score 1) 236

Swift can guarantee data-race freedom, in exactly the same way that C and C++ can - by using the normal threading and locking primitives you get from the OS's libraries. It even ships with a more user friendly library for doing this (GCD) than most OSes provide.

And swift absolutely does not require thread safe ref counting. Swift has both value types and reference types. Value types are passed by value (what a surprise), and include non-ref-counted pointer types. All you need do to avoid ref counting is to not use the word "class" in your program, and instead stick to "struct".

Neither of these are impediments to system programming.

Comment Re:Non-answers (Score 2) 477

Usually it's a case of needing to understand the actual use case in order to be able to provide alternate options.

Usually it means "The thing you're trying to do is dumb for a number of reasons, but since you haven't described what the *actual* goal is, but instead only what a possible implementation might look like, it's impossible to tell you why it's dumb and what a better choice is."

Comment Re:Rust will be what replaces C/C++ (Score 1) 236

Concurrency/parallelism primitives was available through extensions (like posix threads, locks etc.). Those were available because, as native languages, C and C++ can make use of (inline) assembly and anything supported by ISA. Try that on interpreted/JIT-ed language.

Yes - the point I'm making is that these are all equally available in Swift. All C APIs are available without any modification in Swift.

Comment Re:Rust will be what replaces C/C++ (Score 1) 236

No other modern language is capable of safety and is low level enough. I saw one comment here asking why no swift, well for starters it has no concurrency or parallelism primitives which are a necessity for a systems language. Certainly for whatever language you want to write a browser in...

That seems like a strange assertion to make given that C has, and C++ until recently had no concurrency or parallelism primitives, and are the de-facto systems programming languages at the moment.

It also seems like a strange assertion when Swift by default ships with Grand Central Dispatch, which gives it strong concurrency and parallelism support.

The issue with swift as a systems programming language is that its compiler output is too magical. Several of its features can cause weird and unexpected perf implications when used in subtly different ways. For example, it's generics implementation can end up compiling down to either fully dynamic dispatch, or just normal C function calls depending on whether the compiler analysis could figure out which types you were using, when, and how often.

Slashdot Top Deals

Lead me not into temptation... I can find it myself.