Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Comment Swift (Score 3, Insightful) 45 45

Swift isn't going to make it so "anybody can write apps." That is something that's been tried for decades, with things like drag-and-drop programming. SQL was originally intended for non-programmers. It doesn't work, because the difficulty of programming isn't the syntax. The difficulty of programming is logic. You have to learn to think like a programmer, describe a sequence of steps, ask "what will happen in the user does.....X." You have to reasonably understand the if several things in a row are true, but the next one is false, then all of them are false (if anded together, but not if or'd together).

The logic of programming is why it's good for everyone to learn programming. If it helps people learn to think a little more formally, then it's worth it.

Comment Re:Change Is Life (Score 1) 121 121

You seem to be ignoring the overwhelmingly positive utility of a site like that.

Please note, I didn't say that the website has no utility......the utility comes from compensating for weak developers and weak projects. If the developers are not weak and the projects have high discoverability, then there's no need to ask questions about it on stackoverflow.

(Of course, it can still fill a role, but all the basic questions would be gone).

Comment Re:Here's the list (Score 1) 94 94

My first thought on reading this is that this guy started coding this year. #1-3 is solved by using GitHub, TFS online or one of the popular choices most FOSS projects already seem to use. (e.g. How would an experienced developer get these problems in the first place?)....I see he's employed by Red Hat. Does this list as news suggest that Red Hat's internal development processes are immature too?

He wrote the list based on things he'd seen in Chromium, so it's Google's problems. Here is the full list. Not surprising, since they used to jam all their code into a single repository.

(It's hard to fault them for a 100+MB source code download though, unless there's a lot of redundancy in the code).

Comment Re:Change Is Life (Score 1) 121 121

On the other hand if you fall behind current dev tools, you miss out on the potential for a lot of community support

I might be flamed for saying this, but if you can't be a software developer without "community support" like asking questions on StackOverflow, then you're not really a software developer. (Likewise, if a tool can't be used without asking questions on stackoverflow, it's the wrong tool to be using for anything serious).

Comment Re:ran debian on sparc for over 10 years (Score 1) 146 146

Successful projects are ones where the people who want to use it want to use it enough to fund development.

I'm going to call you a moron right here because you only think of success in terms of monetary value and popularity. Success is not measured by money alone.

A successful project is one that produces great code, one that makes its creator happy.

Comment Re:Correct link to TRA (Score 1) 94 94

An alarming number of those hold for Chromium and they all stem from one core issue: Google developers do not understand how to design APIs. A lot of the bundled projects could be entirely separate repositories and shipped as shared libraries if they did, but gratuitous API churn means that they have to keep copies of things like v8 and Skia for Chrome and build the whole thing at once. It's fine to do the aggregate build thing if you want LTO, but it should be a performance optimisation, not a requirement of the software engineering workflow.

A programming language is low level when its programs require attention to the irrelevant.