All I need from Ruby is an extension that allows sections of programs to be completely static typed thanks to explicit type hints. Not for the speed, just for the ability to catch errors at compile time.
Where does Ruby go from here?
71–80 of 93 posts
Re: Where does Ruby go from here?
#72Earlier quoted context omitted.
I think this comment shows exactly what I was getting at. If no one disagrees, the happiness manifesto will die in a sea of nods and shrugs. :) > I'd rather have really good code, even if written by a racist or sexist, than bad code (period). That's a perfectly valid choice. In some cases, it's a completely correct choice. But that's not the tradeoff that I want to make. Take a look at the original Agile Manifesto: h…
"That's a perfectly valid choice. In some cases, it's a completely correct choice. But that's not the tradeoff that I want to make." The problem is that it's used too often to shun or control people that don't agree with a political ideology. A good example of this is the Mozilla CEO. An open and "accepting" community should also accept people they might not agree with..otherwise you should't call yourself open, acce…
> An open and "accepting" community should also accept people they might not agree with..otherwise you should't call yourself open, accepting, or inclusive.
Being "accepting" does not imply being accepting of those who are themselves intolerant, and indeed the meaning and value of liberalism dissolves into something toothless and even dangerous when interpreted that way.
If the Russel's paradox aspect of this you bugs you, then label the position "accepting of all other beliefs except those which are themselves intolerant." In practice, this is what most liberals, even die-hard ones, subscribe to.
Re: Where does Ruby go from here?
#73I think this is a great idea. The ruby community is a wonderful thing, and part of that is reflected in the technology. However, the original Agile Manifesto was powerful because it made tradeoffs. "We value X over Y", even when Y is a valuable thing. For this HDD thing to take off, it has to make the similar tradeoffs explicit. For example: We value readable code over runtime performance. We value open-source framew…
The Agile Manifesto is the opposite of tradeoffs. "We value X over Y" is not a trade off, it's a dogmatic claim. "We should do X in these conditions and Y otherwise" is a trade off. For each of the items you list above, I can come up with a few scenarios where doing the opposite of what the Agile Manifesto says would be the better approach (and that's probably one of the main reasons why hardly anyone takes that Mani…
There's that bit at the bottom of the Agile Manifesto: "That is, while there is value in the items on the right, we value the items on the left more." I think the spirit of it is to try and discourage outright dogmatism. That said, I'm coming to think of the Agile Manifesto as a collection of four rather ugly false dichotomies. It's the assumption that those 4 pairs of things are somehow separable that's what's really dogmatic about the manifesto.
For example:
Processes and tools can often be one of the best ways to improve interactions among individuals. See Scrum, which is hardly a panacea but sometimes it works wonders.
For a large project, comprehensive documentation is essential to producing working software. Ideally the documentation should be so comprehensive that it pervades the very fabric of your application in the form of good factoring, command-query separation, etc.
Contract negotiation can be an important first step in customer collaboration. Everyone needs to know where everyone else's needs, boundaries and comfort zones are.
Without a clear plan, how can you be sure of the best way to respond to change? See: Duke Nukem Forever, WinFS, RIM.
Re: Where does Ruby go from here?
#74I think this is a great idea. The ruby community is a wonderful thing, and part of that is reflected in the technology. However, the original Agile Manifesto was powerful because it made tradeoffs. "We value X over Y", even when Y is a valuable thing. For this HDD thing to take off, it has to make the similar tradeoffs explicit. For example: We value readable code over runtime performance. We value open-source framew…
The Agile Manifesto is the opposite of tradeoffs. "We value X over Y" is not a trade off, it's a dogmatic claim. "We should do X in these conditions and Y otherwise" is a trade off. For each of the items you list above, I can come up with a few scenarios where doing the opposite of what the Agile Manifesto says would be the better approach (and that's probably one of the main reasons why hardly anyone takes that Mani…
I think you might be confusing "tradeoff" with "compromise".
"I'm willing to give up some valuable-thing-Y in exchange for more X" is a textbook example of a tradeoff.
Re: Where does Ruby go from here?
#75Earlier quoted context omitted.
points of view aren't all equally valid. Example: any pov about something that can be factually checked.
Sure, but if you shut out people you'll never find out if they're valid or not.
What does that mean? I can generate an infinite amount of nonsense ideas. Or worse, a good amount of superficially-nice-sounding-but-terribly-flawed ideas. You can't consider every "point of view", if only from the fact that there's limited time.
Re: Where does Ruby go from here?
#76Earlier quoted context omitted.
I think this comment shows exactly what I was getting at. If no one disagrees, the happiness manifesto will die in a sea of nods and shrugs. :) > I'd rather have really good code, even if written by a racist or sexist, than bad code (period). That's a perfectly valid choice. In some cases, it's a completely correct choice. But that's not the tradeoff that I want to make. Take a look at the original Agile Manifesto: h…
"That's a perfectly valid choice. In some cases, it's a completely correct choice. But that's not the tradeoff that I want to make." The problem is that it's used too often to shun or control people that don't agree with a political ideology. A good example of this is the Mozilla CEO. An open and "accepting" community should also accept people they might not agree with..otherwise you should't call yourself open, acce…
He was CTO for quite some time, so it appears people were OK with him making technical decisions.
Edit: Also, is there evidence that he was a vastly superior choice? I'd accept sufficiently advanced technology even from a wicked murderer.
Re: Where does Ruby go from here?
#77The Happiness Manifesto? Happiness-driven developers? Enough, already. This is an interesting time for computer programming and computer science in general. We're witnessing the coming of age of a very important profession. We owe it to ourselves to advance this profession by developing a body of knowledge based on scientific, mathematical, and engineering principles, as well as empirical observation of what has work…
Ruby has always been a little cultlike in its approach. I don't necessarily mean that as a negative, I'm just not sure what other word I can use - and it's true of so many other platforms as well, it's not solely a Ruby thing by any means.
I've always viewed computers as lowly tools meant to do my bidding, so I don't really understand this sort of emotional attachment that people get, but it's definitely a real thing that people feel. The only pragmatic way forward is to accept that this happens and figure out how to incorporate it into the larger context of software engineering.
Re: Where does Ruby go from here?
#78I don't want to leave ruby, but at the end of the day, it's slow. Jruby is pretty decent, but the clunkiness of the JVM takes the fun out of it. Maybe it's just the lack of a corporation pouring billions into it like google did with V8, but I suspect that ruby can never be fast, due to ObjectSpace and the like. That awesome/insane object model we all like so much is just impossible to optimise. All the other weird sh…
Ruby is not inherently a slow language. An ideal setting, will be a Ruby open source compiler (similar with what RubyMotion does) that could be used to package your code. I would use the the interpreter to test/develop the code and the compiler to actually package it.
Re: Where does Ruby go from here?
#79I think this is a great idea. The ruby community is a wonderful thing, and part of that is reflected in the technology. However, the original Agile Manifesto was powerful because it made tradeoffs. "We value X over Y", even when Y is a valuable thing. For this HDD thing to take off, it has to make the similar tradeoffs explicit. For example: We value readable code over runtime performance. We value open-source framew…
"We value readable code over runtime performance."
Re: Where does Ruby go from here?
#80>- I value respect and tolerance to all in my community
What does that even mean? If a Time Cube guy shows up, does it mean I'm just supposed to politely ignore/shadowban him?
Does it mean I can't use "master-slave" replication?
I think what that line is supposed to mean is "I value not being needlessly abrasive to people" and "I value ignoring unrelated-to-my-project aspects of people".
That is, even if you have some belief or participate in an activity that I find abhorrent, if it's not relevant to the project we're working on, I value avoiding talking about such things so we can focus on the project.