News for hackers. Stuff that matters.
Re:“Because I'm a bastard, and proud of it” (2000) by gnaritas on Wednesday December 30, 2015 @04:59PM (#10814633)
> Lol if everyone did open source like Linus

We'd have less, but much better software.

Re:“Because I'm a bastard, and proud of it” (2000) by this_user on Wednesday December 30, 2015 @05:13PM (#10814716)
Would we? Your statement implies that creating the kind of environment Linux is developed in somehow weeds out the bad developers while retaining the good ones. Yet, I am not aware of any data that would suggests a positive correlation between development abilities and resilience towards a hostile work environment. Therefore, we can assume that good contributors, too, will be put off, thereby making the project worse than it could be. The best example of this is Alan Cox who did a lot of good work before leaving the Kernel project. I don't think anyone would argue that his exit made the project stronger.
Re:“Because I'm a bastard, and proud of it” (2000) by mwcampbell on Wednesday December 30, 2015 @07:25PM (#10815353)
Having less software isn't an actual option though. The world demands both more and better software. So we should take advantage of the best available tools to produce it. Yes, those tools make it easier to write crappy software, but when used well, they also make it easier to write great software. Put another way, an uber-developer who could write a good program in asm with no debugger could write an even better program, or more programs, in a higher-level language with a debugger and strong static analysis. So if these tools are available, working without them is just misguided masochism.
Re:“Because I'm a bastard, and proud of it” (2000) by gnaritas on Wednesday December 30, 2015 @11:37PM (#10816147)
I agree, I wasn't saying I'd prefer it the other way, only stating what I thought the consequences would be.
Re:“Because I'm a bastard, and proud of it” (2000) by vezzy-fnord on Wednesday December 30, 2015 @05:14PM (#10814718)
I didn't know the better the software, the more primitive the development tools.
Re:“Because I'm a bastard, and proud of it” (2000) by gnaritas on Wednesday December 30, 2015 @05:51PM (#10814931)
A debugger is a thinking crutch, yes, it's easier and more productive to just see what it's doing; but to fix something without a debugger, you have to understand it better. That's his point, and he's right. Quite simply, the easier you make something, the more people who are less intelligent can do it and the result is more but less quality software. Examples abound, but every attempt to make something easier results is people producing more shitty stuff with pointy clicky interfaces.
Re:“Because I'm a bastard, and proud of it” (2000) by vezzy-fnord on Wednesday December 30, 2015 @06:04PM (#10814976)
Again, this would require us to reject most advances in software after 1968 if we are to apply the logic consistently. Go back to single-tasking, cooperatively multithreaded systems with static file allocation tables and no access control. Actually even the Multics of 1968 was far more advanced than that.

Fact is, without debuggers, most highly subtle war story bugs would go unsolved. Logic analyzers, tracers and ICEs are debuggers, too. "Debugger" doesn't just mean gdb. Not that there's anything wrong with it.

Re:“Because I'm a bastard, and proud of it” (2000) by gnaritas on Wednesday December 30, 2015 @06:07PM (#10814992)
As I said, we'd have "less" but better software; that doesn't preclude we'd not have some things we have today nor does it imply better software can't be built with debuggers; it only means we'd have fewer less capable developers making software and thus the overall quality of what we would have would be higher than the overall quality of what we have today given how much shit code exists.

There's a ton of programmers who can't code without a debugger because they don't really understand what's going on any other way than line by line. Those people would be filtered out. Debugging doesn't require a debugger, it's just the easy way to do it.

Re:“Because I'm a bastard, and proud of it” (2000) by vezzy-fnord on Wednesday December 30, 2015 @06:14PM (#10815024)
We'd certainly have less. There would be no reason to presuppose that it would be better: https://en.wikipedia.org/wiki/IEFBR14

The key to better software is learning from the research literature, not thinking that you're improving because you write nothing but ASM macros in ed(1) in a TTY emulating a VT100 from the 70s.

Re:“Because I'm a bastard, and proud of it” (2000) by gnaritas on Wednesday December 30, 2015 @07:02PM (#10815253)
> There would be no reason to presuppose that it would be better:

Sure there, it's been said multiple times; those still writing software would be the smartest around. That alone is reason enough to think the overall quality would be higher; if you don't believe that, then imho you don't know what overall (average) means. You're not listening, you're focusing on outliers and I'm taking about the mean. It's a valid logical inference that if you weed out less intelligent developers by making developing harder, that the average quality goes up; not the absolute quality, the average, mostly because you'd be weeding out tons of bad developers who write tons of bad software. This really isn't debatable, it's logic. Weeding out the bad raises the average quality, there's nothing to argue here, that's just a fact.

Re:“Because I'm a bastard, and proud of it” (2000) by venomsnake on Wednesday December 30, 2015 @05:27PM (#10814815)
Voyager still works superbly. Unlike my just completed reactive js mvp single page framework ridden app. Making good software is hard. Step by step debugger is not suitable for a lot of tasks - not least because it tends to fix some bugs like memory initialization and race conditions. What can save your ass is automatic formal verification and static analysis. And not using C/C++ creatively.
Re:“Because I'm a bastard, and proud of it” (2000) by vezzy-fnord on Wednesday December 30, 2015 @05:33PM (#10814852)
What can save your ass is automatic formal verification and static analysis.

That's hardly what I'd rate as "primitive".

That a lot of people carelessly throw together CRUD apps does not contradict what I'm saying. In fact, I'd say most CRUD app development is highly primitive, notwithstanding the complexity of the web platform itself.

Debuggers do tend to sometimes to mask heisenbugs, but this goes the same for just about any tool performing intricate binary analysis. And there's some subtle timing bugs where it's a fact of life that you'll get misleading readings.

Re:“Because I'm a bastard, and proud of it” (2000) by kalail on Wednesday December 30, 2015 @05:04PM (#10814661)
THIS

For an opposing example, look at the world of JavaScript.

Re:“Because I'm a bastard, and proud of it” (2000) by moron4hire on Wednesday December 30, 2015 @05:15PM (#10814724)
People have really only been doing JavaScript in earnest for the last 7 years. When you consider that, and how terrible the base language actually is, I think it's pretty amazing what people have done with it.
Re:“Because I'm a bastard, and proud of it” (2000) by edejong on Wednesday December 30, 2015 @05:53PM (#10814940)
I started writing AJAX callbacks in 2004, and I'm sure I wasn't alone, so 11 years of higher-level JS is certainly a better range.

But we should abstract away from the language. We've had 35+ years of experience of designing and implementing user interfaces, including their design patterns (MVC, Action/Event based). History is filled with successful designs.

Just consider a sophisticated tool such as your standard IDE: do/undo functionality, separation of concerns, event based, MVC, good standard graphical toolkit, easy deployment and upgrades. These designs are not new, and date back to at least the late 90's (Delphi).

What changed? Well, we've been doing incremental design: throw something at the wall, see what sticks and debug the hell out of it while adding new features. Perhaps that design philosophy is not very tenable in the long run.