telent

9 ms·

31.
by telent 15y ago
Indeed. Google is a free service and Google Apps is a paid service, but I wouldn't expect significantly more longevity from the latter just because I'm paying them $x a year than I would from the loss-leader service.
32.
by telent 15y ago
I don't think the issue is so much "what should they do now", because what they should do now is constrained by what they can do. The issue is "what should they have done in 2008?" - should they for example have said "please note that ou
33.
by telent 15y ago
It's interesting (to me at least) that we have largely dispensed with the Unix privilege model in production and replaced it with running an entire unix system for each application, virtually hosted on the real one. I wonder if, had ther
34.
by telent 15y ago
I thought it was a jsmin "do no evil" analogy. Even Apple ships GPL code
35.
by telent 15y ago
Guess what? I consider that a bad thing too. But you're still reading things into my comment other than what I said. (1) Rails had insecure defaults which encourage bad programming (2) pthreads has an API which - at least, in its designer'
36.
by telent 15y ago
Indeed it is as you say. "attr_accessible kerfuffle" was my (apparently, and quite bizarrely, considered inflammatory) shorthand to refer to the whole episode. I'd edit the post to clarify, but it won't let me do that any more
37.
by telent 15y ago
I think you've jumped at a different parallel than the one I was trying to draw. It's considered a bad thing that Rails prioritised developer convenience over the encouragement of reliable programming practice. Why should it be considered
38.
by telent 15y ago
The difference is that memory checking in debug C runtimes doesn't paper over your mistake: instead it breaks your program reliably so that you know you have a mistake. As per the linked article, "While recursive mutexes may seem a conveni
39.
by telent 15y ago
Compare and contrast with the Rails attr_accessible kerfuffle of last week, where it was generally held by (I think) the majority of commenters that the library should not have provided this convenient feature or at least should have made i
40.
by telent 15y ago
If I set my browser window to a reasonable width I can have legibility without foofy margins and I can use the rest of my 1280 pixels for something else. Window systems - they rock
41.
by telent 15y ago
I said it was a nitpick, but the post to which I responded did say "all economic activity". Does it even matter? It matters if it means our fully automated jobless future is penury and starvation instead of the post-scarcity Culture we're l
42.
by telent 15y ago
This is a nit pick, but much economic activity these days is nothing to do with alleviating scarcity and everything to do with introducing artificial scarcity where it didn't previously exist. See e.g. Intellectual property.
43.
by telent 15y ago
AFFECT, grrr. Not effect. To effect every coder would be to bring them all into existence, which is clearly not what happened here.
44.
by telent 15y ago
Here's a rather less paranoid article that's (partly) about SO. http://www.tbray.org/ongoing/When/201x/2012/02/29/Undocument... Seriously, given that the data is freely available and for as long as it remains so, "OMG you're making mone
45.
by telent 15y ago
What's not true? Exec used some OO techniques in non-OO languages. So does Linux. I can't see which post this was intended as a response to
46.
by telent 15y ago
If "I've never heard a good argument", "a completely academic waste of time" and "why should anyone non-academic building actual systems care what it means" aren't implications that your experience is valid and others' experiences aren't, t
47.
by telent 15y ago
See where I said "usually"? And where I said your experience is valid but don't assume it's universal? Right
48.
by telent 15y ago
How can you say (TCP|Unix|C) is going to give you a bunch of stuff "for free" when you haven't even seen the application. How do you know you're even going to get what you want? You don't, of course, but it's usually a pretty reasonable as
49.
by telent 15y ago
Bundler and rvm? "now you have two problems" :-)
50.
by telent 15y ago
From my perspective Rails popularized (perhaps even normalized) tdd, which I think is probably a significant contribution to programming culture. Or were high-ceremony Java enterprise folk doing tdd all along and rails just adopted it? I do
51.
by telent 15y ago
For "could be used for", read "was designed for".
52.
by telent 15y ago
I have that exact alias. But it still adds 3 seconds to the startup time of any command run under it Maybe my laptop is underpowered, but three seconds to do essentially nothing is still a long time
53.
by telent 15y ago
I use emacs and have done for ~ 20 years, but I don't think this article would sell me on it if I didn't already. An editor is just an editor: an editor with a variety of unrelated crap (text adventure, tetris game, mail reader) bolted on t
54.
by telent 15y ago
"I think that trying to shoehorn Vim or Emacs into becoming something that it’s not [an IDE] isn’t quite thinking about the problem in the right way." This may or may not be true for Vim, I don't know. But I think the majority of GNU Emacs
55.
by telent 15y ago
Yes. "let x=1" is quite clearly syntactic sugar for "(lambda(x) { ... rest of block here ... })(1)" so while you might argue that it's unnecessary (I'd disagree, but it's a respectable argument), you can't realistically claim that it would
56.
by telent 15y ago
But what does it do that makes it apparently uncacheable? Your pages change when you write a new blog entry, or when someone posts a comment - and even then there's no hard constraint that requires their comment appear immediately - serve