Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Comment: Re: stable (Score 1) 223

by jeremyp (#49749399) Attached to: Linux 4.0 Has a File-System Corruption Problem, RAID Users Warned

On every popular PC operating system in use today (and Linux), the kernel and the drivers share the same address space. It is thus beyond reasonable expectation for the OS to be able to protect itself from faulty drivers. Although Linux was designed this way from the start, OS X and Windows both started as microkernels (where the drivers have their own address space) but were "downgraded" to monolithic kernels because of performance concerns. Switching between address spaces has an enormous cost.

Comment: Re:Yes & the sheer amount of existing code/fra (Score 5, Insightful) 407

by jeremyp (#49744269) Attached to: The Reason For Java's Staying Power: It's Easy To Read

Actually, it's easy to read because it is verbose and inexpressive as you put it. Generally speaking, the more information you pack into a sequence of characters, the harder it is to understand. There are also relatively few syntactic constructions to get your head around and tokens are not usually overloaded with different meanings. It doesn't take long to learn the whole language, which means that even a newbie has a good chance of reading a piece of code without coming across something they haven't seen before.

Comment: Re:Only one and it's vi not emacs. sorry (Score 1) 439

by jeremyp (#49742657) Attached to: Choosing the Right IDE

Our sysadmin once made a Linux VM unusable with nano. He used it to edit the pam.conf file and nano helpfully wrapped a long line by putting a line feed in at the last space before 80 characters. After that, nobody could log in anymore, not even the sysadmin who had logged out to test the change he had made.

We got the system back with a Linux live CD and the sysadmin started the vi tutorial the same day.

Comment: Re:An Old Story (Score 1) 386

by jeremyp (#49680253) Attached to: Criticizing the Rust Language, and Why C/C++ Will Never Die

A deep copy that handles circular references is slower, but the addition cost is constant time because it only needs at most an O(1) lookup and O(1) insert at every node.

Actually, if it requires O(1) for every node then it is O(n) where n is the number of nodes in the object graph, so not constant time.

Comment: Re:Swift is not ready to replace ObjC (Score 1) 270

by jeremyp (#49671817) Attached to: Swift Vs. Objective-C: Why the Future Favors Swift

Swift Blog July 11th 2014 entry.

you can target back to OS X Mavericks or iOS 7 with that same app. This is possible because Xcode embeds a small Swift runtime library within your app’s bundle. Because the library is embedded, your app uses a consistent version of Swift that runs on past, present, and future OS releases.

The embedded part is actually quite small and it's only there because the language is still evolving (and to allow apps to target the previous versions of OS X and iOS). The main reason it is necessary to do it like this is that the Swift ABI is not yet stable. When the ABI stabilises, Apple plans to incorporate the runtime into the OS (where it should be).

Maternity pay? Now every Tom, Dick and Harry will get pregnant. -- Malcolm Smith

Working...