ehm_may

Sorry...just been annoyed at rails lately, was drunk reading through here, and wrongly took out my personal frustrations as a diatribe against the author. I'm an asshole.

You have my compliments and respect for undertaking an endeavor like re-thinking (and actually implementing!) rails architecture, so my apologies if my comments sound harsh or cynical. (I just want to talk about it)

I'm having a hard time understanding the need for this, especially because I'm highly suspicious of building any significant amount of abstraction on top of rails. This is because rails core is fucking insane. Besides the fact that it's in a constant state of flux, the amount of dynamic/meta/runtime fuckery that takes place makes it a living nightmare for security (and performance).

Rails already provides a highly-specific set of "convention over configuration" settings that work for most users with a basic understanding of HTTP. How exactly does this framework make those settings "better" besides re-arranging the basic set of abstractions that base rails provides (and adding more "fuckery" on top of that)?

Who is your target user group? Rails already attracts a significant number of new developers who have never worked with the web before because the abstractions are relatively easy and straightforward to understand. This is what makes rails very impressive and attractive, but, at the same time it locks a whole generation of new web developers into "the rails way" of thinking about the web (and later have to be untaught when they realize performance is actually important).

IMO If a "better" ruby web framework was to come into existence, I would encourage it to be more in touch with the basic abstractions that are already built into HTTP (see https://www.ietf.org/rfc/rfc2616.txt) and not try to over-abstract those basic concepts so that moving among http frameworks (in ruby or other) requires significant domain knowledge.

Are there any performance benchmarks? I could see a project like this unintentionally adding 2-3x performance hits (without realizing it) due to the extra abstractions.

BTW, what the fuck is up with this book? I assume you want to sell it to me in the future so that I can learn how to "properly" use your brand new open-source framework? What the fuck is wrong with a readme and a wiki, especially if you ever considered larger open-source adoption? Are you so self-righteous that you think I should feel entitled to have the pleasure of being able to download "a preview" of your e-book in your fucking readme?

check out cedexis http://www.cedexis.com/reports/#?report=cdn_response_time&co...

http://fastly.github.io/epoch/ is built for real-time streaming data. It also uses d3

Why couldn't Sinatra create some sort of underlying tree structure that could perform in O(log N) as opposed to O(N). That way you get the readability with the perf.

Will there be a print version? I have the print version of the other no bullshit guide and love it. I much prefer print for this kind of material.

> Giving your product for free undermines its value.

Not if it's a fucking beta

Good post. So much this. If your pricing doesn't make sense, you will eventually find out one way or another - but don't give out discounts solely for the purpose of bringing in new customers. Especially if they are not seeing the value of your product at its listed price point. This will just lead to them wanting more. And I've often found that the users paying the least ask for the most.

So is this some sort of response to PG's comments about women?

I don't get it. Why not just use aliases?

alias <name>='cd path/to/<name>'

Then you can just type: $ <name>

You can even set up an alias to add a new alias -> alias ea='vim ~/bash/alias'

I feel like this is a huge decision.

Correct me if I'm wrong, but isn't this essentially ruling that everything that you own and store in the 'cloud' doesn't belong to you in the sense that it is not subject to the same protections as other property you own?

I can see this having huge negative consequences for all US 'cloud' business.

How about this site go fuck itself with its "log in with facebook" banner that won't go away

Cool greasemonkey script, bro

I pay github for the same reason I pay heroku. It just works and I don't have to do anything. That is why they exist. Sure you can set up your own git server, but what do you do when it goes down?

haha. Yeah, these guys have never seen a java spring app.

I've heard quite a bit about this case over the past month or so, but don't understand it.

Can someone explain what Apple 'fixing' e-book prices means and how that is illegal?

Good writeup, and I appreciate the section on deploying to heroku. Have used middleman before and had issues getting it running on Heroku.

lol. OP is bitching about internet karma. 1st rule of internet karma is it's irrelevant.

God that chart is terrible.

I bet you have an HOA. Use it. This issue should be an HOA thing, not a state/city thing.

"I don't understand money. Well, specifically, I don't understand how companies are funded, classify shares, or any of that finance stuff." lol - stopped reading

Have an indian friend who graduated from a top engineering program. I've never seen someone freak out (for fear of being kicked out of the country) so much between graduating and finding a job.

Moving from job to job is miserable. You have to ensure the company will pay for the H-1B. This has negative consequences because instead of moving to a place where you can perform better, you will often stay at the current employer and get taken advantage of.

Raised over $112M to date. Talk about a cash sinkhole.

link to actual rdio blog post because I hate gizmodo

http://blog.rdio.com/us/2013/04/introducing-vdio.html

Ha! Gotta love Zed

Internal use only code should be documented as well as any external facing code. It's easier to read through a readme or wiki than track down the person who owns or knows something about the code you want to use.

We use: internal wiki (confluence), readme's, rdoc - javadoc - etc., PR's on github enterprise

This works pretty well. For reference we have hundreds of devs. Most of the time you can find some sort of documentation in at least one of the above locations.

I actually wrote a blog post on CISPA a while back. http://michaelmay.me/2013/02/17/wtf-is-cispa

I'm not worried about it. However, I may not be entirely correct in my analysis. Would be interested in feedback.

cough every java project ever cough

I really like the hash key format.

Parsing JSON for arbitrarily nested keys is nasty, and this makes it extremely natural.