Uh, he's on a schedule. 1.8 is not scheduled for release until later this month IIRC. As a plugin dev for bukkit (a modded version of a MC server that handles plugins), I'm relieved that updates aren't jammed together. Updating also means downtime for many modded servers too.
Maybe you should brush up on basic statistics before calling others out on being wrong. It is feasible to have a experimental high success rate while having a low chance of individual success given that there are few enough trials. IOW you can't say with good certainty that any trial has a good success rate if you have too few previous trials to back it up, no matter their rate. TL;DR That's not proof.
All of the technology was new and unproven at some point. If you keep trying at it, it becomes less new and more tested. It's the nature of the game. Also, MER is not proven, it just happened to succeed twice. Don't get me wrong, they were excellent successes, but it's just 2 for 2.
You want spend the most effort to conserve the most expensive resource. And that is not the cpu, ram, or disk time. It's human time. Hell, even working for low wage, a person is expensive. Thus the most effort should be put in having them do the least effort. Unless you have a case where the hardware time is getting expensive, but that's the exception as hardware costs go down while salary doesn't.
And no, that's not an excuse to be sloppy. "Back in the ancient days" it was important to write good code for the limited resources. Now you still need to write good code, but the constraints are relaxed. But we still need code that is maintainable, dependable, extendable, flexible, understandable, etc.
It could be that gp's post was centered around strawmen. Horrible way to make a point.
Re:Data, Images, Binary builds etc.
on
The Rise of Git
·
· Score: 1
Heh yeah, math I can do. Unfortunately I decided I liked programming more, but too late to change to a CS major.:)
Re:Data, Images, Binary builds etc.
on
The Rise of Git
·
· Score: 1
I'm not a professional, I'm a student in mathematics. Programming is just a hobby of mine. Nor do I have the disk space left to back up everything I own since my computer is old enough to be eligible for kindergarten if it were human. And don't tell me to buy more disk or buy a service, I struggle with affording basic living necessities as it is, so sorry if I can't climb on to your high horse.
Re:Data, Images, Binary builds etc.
on
The Rise of Git
·
· Score: 1
Learned that the hard way with git. Upon checking out older commits after a computer crash (yeah, macs crash too) since the sub-directories were cleaned: "Uhm, where did my src folder go?"
Why or how I retroactively lost data, I don't know. To be fair, it was probably one of my own build scripts that was to blame.
Slashdot Mirror
Yeah, but their computer science side seems . . . lacking. I didn't see anything on the level that Stanford is offering.
Uh, he's on a schedule. 1.8 is not scheduled for release until later this month IIRC. As a plugin dev for bukkit (a modded version of a MC server that handles plugins), I'm relieved that updates aren't jammed together. Updating also means downtime for many modded servers too.
Nah, Linus is smarter than whatever idiot created git . . .
I consider it a praise to a piece of software if the only thing people can bitch about is its release numbering system.
Maybe you should brush up on basic statistics before calling others out on being wrong. It is feasible to have a experimental high success rate while having a low chance of individual success given that there are few enough trials. IOW you can't say with good certainty that any trial has a good success rate if you have too few previous trials to back it up, no matter their rate. TL;DR That's not proof.
All of the technology was new and unproven at some point. If you keep trying at it, it becomes less new and more tested. It's the nature of the game. Also, MER is not proven, it just happened to succeed twice. Don't get me wrong, they were excellent successes, but it's just 2 for 2.
This rover is about the size of a small car, so it is a wee bit harder to get onto the ground in one piece. Pics or it didn't happen? Here ye go: http://en.wikipedia.org/wiki/File:Mars_Science_Laboratory_wheels.jpg
I think javac is a java program.
The average Case backhoe can dig down 15 feet. A long-reach excavator can dig 72 feet. You'd be hard pressed to bury fiber "deeper than stupid".
Problem is that the planet is only 4,000 miles in radius.
I'm pretty sure "import ruby.on.rails" should work in python.
The bug where KDE still is inferior to GNOME? :P
I do read it, and my last statements in both paragraphs was to address that issue.
You seem to have this mental model that more efficient code must take longer to develop.
I did not say, claim, or imply that. I was talking about factoring in developer time as a resource.
You want spend the most effort to conserve the most expensive resource. And that is not the cpu, ram, or disk time. It's human time. Hell, even working for low wage, a person is expensive. Thus the most effort should be put in having them do the least effort. Unless you have a case where the hardware time is getting expensive, but that's the exception as hardware costs go down while salary doesn't.
And no, that's not an excuse to be sloppy. "Back in the ancient days" it was important to write good code for the limited resources. Now you still need to write good code, but the constraints are relaxed. But we still need code that is maintainable, dependable, extendable, flexible, understandable, etc.
Your religion is mostly likely capitalism, practiced more virulently than any other religion in history.
With the exception of grammar-nazism
Broken window, anyone?
That would break OS X and most software running on OS X.
Oi, there's nothing wrong with sla
Technically both are correct, you slobbering idiot. :P
It could be that gp's post was centered around strawmen. Horrible way to make a point.
Heh yeah, math I can do. Unfortunately I decided I liked programming more, but too late to change to a CS major. :)
I'm not a professional, I'm a student in mathematics. Programming is just a hobby of mine. Nor do I have the disk space left to back up everything I own since my computer is old enough to be eligible for kindergarten if it were human. And don't tell me to buy more disk or buy a service, I struggle with affording basic living necessities as it is, so sorry if I can't climb on to your high horse.
Learned that the hard way with git. Upon checking out older commits after a computer crash (yeah, macs crash too) since the sub-directories were cleaned: "Uhm, where did my src folder go?"
Why or how I retroactively lost data, I don't know. To be fair, it was probably one of my own build scripts that was to blame.
I thought modern OSs already did this? http://en.wikipedia.org/wiki/Address_space_randomization
Hm . . . I wouldn't be surprised if there was a +5 "I'm a deadbeat post" somewhere on /. .
- Your friendly neighborhood dead beet