91–100 of 109 posts
Earlier quoted context omitted.
I'm curious what kind of "massive performance slowdowns" they encountered with Rails 3 that could "not be identified".
Me too, because it sounds an awful lot like someone doesn't know how to use ruby-prof.
It's easy to armchair quarterback… especially if you're not hampered by actually reading the very brief bit of content you're speculating about.
If rails causes a kernel panic then this is really a bug in the kernel. No user land app should ever do this. Why not try to scale on *BSD or Windows all of whom have different kernel and scale just fine? $100,000 and no one said "hey what about running it on "?
I'm as bewildered as all of you. But let's give them the benefit of doubt, he probably just forgot to mention that they tried other OSes. I mean, who wouldn't?
Earlier quoted context omitted.
I'm as bewildered as all of you. But let's give them the benefit of doubt, he probably just forgot to mention that they tried other OSes. I mean, who wouldn't?
Yes, "Amy" is a historically male name.
Earlier quoted context omitted.
This is normal for Ubuntu kernels from experience. They are shitty. Various server releases have given us hell. They're fudging them somehow. We moved to debian after numerous problems and have had no issues since.
Do you have links to bugreports to your problems by any chance? Or more detail on what problems you ran into so I could have the Ubuntu kernel team check them out?
I don't have the report ids any more.
Earlier quoted context omitted.
Who gave these guys & gals $100k? Reading this must make founders striving to get investments furious..
Yes, the other gentlemen are correct. This was all our own money. Which we earned from scratch from our other products (all doing very well, thank you). And, perhaps more galling, VCs approach us every month to try to invest (but we're against it). I'm sure shutting down a perfectly good and potentially very profitable product will make lots of wannabes and aspiring entrepreneurs jealous. Luckily I don't make my life…
FWIW, it deserve respect to shut down something you built with your own money.
In hindsight, I think you would have gotten an entirely different response had you said "We can't run Charm with the team we currently have, there are technical challenges we can't solve". Understandable and believable. But for all the people dealing with problems like the one you blamed on a regular basis, saying what you did just sounds like:
"We spent or life-savings building this great house! But it keeps running out of toilet-paper, so we burned that s"#¤ down!!"
Earlier quoted context omitted.
This type of service has been written many times before without kernel panics. I didn't get to see Charm before they shut down, so I have no idea what they were doing. Could anyone speak towards how their experience was unique enough to cause kernel panics?
Anyone outside of the company would just be guessing. If anyone inside of the company could answer that question, they wouldn't be shutting down.
Earlier quoted context omitted.
Me too, because it sounds an awful lot like someone doesn't know how to use ruby-prof.
You realize that in your example, "somebody" would be several Rails Core team members, right? It's easy to armchair quarterback… especially if you're not hampered by actually reading the very brief bit of content you're speculating about.
Software is deterministic. If you can't explain why it's doing something, then it's not leprechauns fiddling with your bits - it's something that you just don't understand yet, and will have to dig a bit to find it. I'm not speaking from armchair quarterbacking here - I'm speaking from experience.
I am exceptionally dubious that you were encountering problems that were just not solvable, let alone explainable. Doing the handwavey "nobody can explain it" has a particuarly bad odor to it.
If you want to do a full writeup on the problems you encountered and what you tried to do to solve them and why you eventually gave up on them, I will be first in line to read it.
Earlier quoted context omitted.
You realize that in your example, "somebody" would be several Rails Core team members, right? It's easy to armchair quarterback… especially if you're not hampered by actually reading the very brief bit of content you're speculating about.
Yes, it's very easy to armchair quarterback. But I also have experience actually doing what I'm talking about - for example, I've contributed patches back to Haml and MongoMapper that have improved their respective speeds by ~25% and ~40% on average respectively. I've profiled and optimized multiple production apps to eliminate these kinds of issues, written tools to aid in memory profiling, tracked down and fixed me…
We did have 3-4 of the Rails Core team members investigating our Rails 3.x problems and none of them could figure out what it was. The problems were so terrible it made it impossible to develop with Rails 3.x any more. Obviously Rails Core members were both A) friends, and B) highly motivated for us to keep using Rails 3.x.
The problem with trusting your abilities is that you can't imagine a scenario where they will let you down. And yet, many such scenarios exist.
Earlier quoted context omitted.
Yes, the other gentlemen are correct. This was all our own money. Which we earned from scratch from our other products (all doing very well, thank you). And, perhaps more galling, VCs approach us every month to try to invest (but we're against it). I'm sure shutting down a perfectly good and potentially very profitable product will make lots of wannabes and aspiring entrepreneurs jealous. Luckily I don't make my life…
I'm sorry I jumped to the wrong conclusion. Not very sorry, but a little bit. FWIW, it deserve respect to shut down something you built with your own money. In hindsight, I think you would have gotten an entirely different response had you said "We can't run Charm with the team we currently have, there are technical challenges we can't solve" . Understandable and believable. But for all the people dealing with proble…