awj

47 ms·

391.
by awj 14y ago
For the various tasks involved in a chess engine Python and Ruby are likely to either be performance equivalent (in that performance doesn't really matter) or entirely unsuitable.
392.
by awj 14y ago
Follow up: The Computer Language Benchmark Game still only marginally relevant to real world use.
393.
by awj 14y ago
If I had to invent a name I'd call it "path compatibility", but I've never seen anything mentioned.
394.
by awj 14y ago
In that case, they've been doing this same kind of stuff with their other brands for quite a while and either are ignoring the pain it generates or aren't feeling it.
395.
by awj 14y ago
In my mind "I need to turn to my version control system to have a clue what just happened" is a great example of having too much magic for a production product.
396.
by awj 14y ago
That's only a concern when continuing your behavior results in a decrease of revenue. EA has been acting like this for a long time. If driving off these kinds of customers was going to create future pain for them, it would have by now.
397.
by awj 14y ago
If that's the case, pulling people in is still stupid. You're going to drive off good remote workers who don't want to be in the office just to cut the chaff.
398.
by awj 14y ago
In all fairness, twenty ounces of anything but water is probably going to have nutso calorie numbers. That said, even a tall white chocolate mocha is 310 calories.
399.
by awj 14y ago
According to recent discussions, turbolinks. It's built into Rails 4 and essentially works by making a call out to the server to fetch raw html and replacing some/all of the DOM with the result. Personally I just use Backbone and try to str
400.
by awj 14y ago
Are you trying to make some roundabout assertion that people do always work in precise patterns? If so, come out and say it. Otherwise carry on with what might be an interesting aside.
401.
by awj 14y ago
Unless you've got a lot of experience changing spark plugs on a 1996 Porsche 911 Turbo, I think that statement applies to both you and the GP. It's reassuring to think our problems are harder than those of other professions, but it's not al
402.
by awj 14y ago
I think the problem is that any servers which can handle concurrent requests now need to decide how many requests they can handle. Since most application servers seem to have concurrency values of "1, ever" or "I dunno, lots" this is a ha
403.
by awj 14y ago
Rails is commonly run as one or more application servers behind an http server that proxies requests to them. Rails itself doesn't manage threads or forked processes for accepting requests, so the only way it fits into Heroku's dyno model i
404.
by awj 14y ago
For this specific issue round robin isn't really any different from random routing. Anything that stands a good chance of queueing a request while other machines sit idle is going to be a problem. The only way that round robin would be argu
405.
by awj 14y ago
> but I do know first-hand that if using Rails as the basis of an efficient and high-capacity SaaS backend, it is the wrong decision. Ok, I'll tell 37signals that it's time to shut down Basecamp. You get on the phone with Shopify and br
406.
by awj 14y ago
As RPython is a subset of Python, that statement is technically correct but misleading. Stating that Topaz is "Ruby written in Python" leads to the idea that it's written in / runs on CPython , which is really not the case.
407.
by awj 14y ago
You actually want ".reduce(:|)", & does intersection on arrays. You can replace that .tap block with gsub abuse for a bit more golfing, and can replace the map/reduce combo with flat_map/uniq to eliminate one symbol-to-proc: def s
408.
by awj 14y ago
It more looks like this was a natural extension of (part of) the Rails vulnerabilities. People saw that YAML on Ruby has a giant gaping security hole in it and was commonly used to decode user-supplied data. I would not be surprised if we
409.
by awj 14y ago
...did you link to the right post? The one I'm reading says he is aware that he is capable of this kind of behavior and has taken steps to mitigate it. If anything it hurts your I'm-right-in-declaring-this-guy-an-irredeemable-asshole thesis
410.
by awj 14y ago
I can comfortably say, based on more than a few arguments and discussions, that Steve Klabnik is not a bully. This situation sucked all around for a lot of reasons, but "that's it, this guy is an asshole end of store" is a poor reaction to
411.
by awj 14y ago
Meanwhile calling people assholes and declaring that the reason is "in [their] personality" based on what they may have considered saying, that's perfectly ok? Have you really never made a comment without fully thinking out the ramificati
412.
by awj 14y ago
Actually if you're using google apps for business, you are a customer. Also, that bit of snark is getting old and tired, and wasn't ever very accurate to begin with.
413.
by awj 14y ago
> yet the Prosecutors and MIT both kept going at it - for the sake of political gain (prosecutors). Do you have proof of this, or is it just what you believe of the situation?
414.
by awj 14y ago
So I can load up your web app on my phone, do some work, then switch over to my laptop and pick up where I left off without noticing that your app server is down? I'd like to know how that works.
415.
by awj 14y ago
Yes, judging platforms by how many people are paid to work on them instead of track record or other verifiable merits is totally the best way to go.
416.
by awj 14y ago
Because Time.now is a global method whose behavior you've just (temporarily) modified. Any tests or code that do depend on Time.now returning the actual current time won't work correctly.
417.
by awj 14y ago
...and while you're at it, rewrite those into some other form. Everything but the find_by_* dynamic finders is going to be deprecated soon anyways. http://edgeguides.rubyonrails.org/4_0_release_notes.html#ext...
418.
by awj 14y ago
It tells you to do that in the "Workarounds" section when talking about how the vulnerability can be mitigated . At no point do they tell you not to pass user provided data to this method. The problem is an argument parsing bug that lead
419.
by awj 14y ago
That method predates the "Forum.where(:url => ...)" syntax of xentronium's demo code. Previously it looked like this: "Forum.find(:first, :conditions => {:url => ...})". Dynamic finders were really sugar over this form, which wa
420.
by awj 14y ago
> To whit, if you look at the bug report it says that the problem is when an application is passing user-provided data into the framework. They say "don't do that" and then apparently provide a patch to somehow get around if you don't T

More ›