GeoffWozniak
Emacs is one of my favourite tools on a computer. I love Lisp (even Elisp, which is getting closer to Common Lisp as time goes on) and I love the interaction, but Emacs is not good for serious terminal/shell work and it, sadly, is pretty annoying as a tiling "window" manager.
Maybe with multi-threading it will get better, but until then, I can't see a compelling reason to work exclusively in Eshell.
There were some spots that things got hairy though, and the code was pretty hard to follow. I don't fault SQLAlchemy here, but I wrote the query in SQL and it was simpler to work with.
SQLAlchemy is absolutely on the right track, but using the core doesn't diminish the fact that you need to know SQL to use it effectively.
I agree with your assertions that just an ORM is not enough, raw SQL is hideous, and that raw SQL spits in the face of programming language advancements. Sadly, it's the assembly language of databases and, unlike CPUs, doesn't have a good abstraction model.
Assuming "every book" includes books I own, then that constitutes theft.
I actually enjoy reading on a Playbook more than an iPad or a Kindle. But the PDF reader is abysmal software.
RIM is quickly discovering that it is not a software company -- and never has been. They are also discovering that software is hard and is the future of mobile.
I say this as someone who was happily employed there a little as three weeks ago (I left to join a startup -- and yes, I absolutely loved my job at RIM). They have some good people but the majority of upper management is lost without a map.
They opted to create another mobile OS/ecosystem. The talent is certainly there, but the time is quickly running out. Apple has been working on iOS for years. Microsoft has been in the OS business for decades. Android is based on Java which has countless man-years behind the tools. RIM is working from QNX which is nice, but is not a full-blown OS/toolchain. There's a lot of work to do there; they've really only been at it for less than a year.
And let's face it: BBOS was something only its mother could love.
Ungar isn't saying that we have to give up determinism. What he's saying is that to take advantage of massively parallel systems, determinism comes at a high cost.
Clearly, we can write programs on current architectures that are deterministic (well, perceived as such, at least) and we don't have to forgo that. But there is no reason to believe it has to be the only architecture. Ungar is looking at what happens when you try to do computation in a highly networked environment with low latency (like say, a brain).
Also, if you don't see it helping for the practitioner, perhaps practitioners aren't asking good (or enough?) questions.
That's pretty specific. Why not "Ripping off is wrong"?
I wonder the same thing when I hear "Violence against women is wrong". I tend to think "Violence is wrong".
In fact, it's so bad that my alma mater has put out a call for something else. http://webct.uwo.ca/owlflightplan/ (Admittedly, they make it sound like it's due to licensing, but if people were happy with it, they wouldn't be asking.)
LMS strikes me as a problem best dealt with at the course level, not the university level. Give profs some web space and let them put up something and go from there. The centralized "hub of all courses" seems overly complex.
"I would rather cry in the back of a BMW than laugh on the back of a bicycle."
Are gadgets ruining our kids' brains?
Right now it doesn't look possible to sign up without a Twitter/Facebook account.
Doing the dishes is a good one. It doesn't take all that long, it gives you time to reflect as it rarely requires great attention, and, even in a dwelling that is habitually cluttered, a moderately clean kitchen will make it seem like you have accomplished something.
Doing the dishes/cleaning the kitchen is my number one low-tech way to feel better about myself and my surroundings. (With the added benefit that my wife greatly appreciates it, since she can relax and watch video clips on her iPhone.)
There's a place for that, but the future of programming languages, in my mind, lies in changing the metaphor of the process from specification to experimentation. After all, the problem with the specification metaphor is figuring out what the specification actually _is_. To me, the best route to get there is experimentation.
Make programming more about experimentation and I think we'll get somewhere.
(I'm still going to read more about Omega. It looks interesting enough.)
Perhaps he should talk to few. From my experience, it involves writing grants.
The end of online privacy
http://rwc.hunter.cuny.edu/reading-writing/on-line/countable...
I beg (plead!) of the submitter to update this to read "Too Many Things That You Want To Do?" to prevent the regular wincing that results from reading the grammatically ugly version.
Since I was bring paid about $1250 CDN a month and was trying to finish my PhD, I didn't press the matter. Still, it seemed as though students didn't want what likely would have benefitted them. (Or perhaps they knew how to play the current system to get passing grades...)
Two approaches were shown: changing data structure representations to meet requirements and generating class structure/hierarchy. The thesis showed that it is possible to do this and how to do it, but it is a huge topic.
If you're interested, I'll put more effort into making my thesis available online in HTML format. In the meantime, you can get it in a variety of places.
http://duckduckgo.com/?q=Structuring%20Data%20via%20Behaviou...
Incidentally, generating behavioural elements (like entire functions) to pass tests would be very difficult although I have been toying with ways to try it out.
Protip: look for heavy, entrepeneurial employees.
It's a bit like an ancient Roman Twitter account.
During office hours and personal consultation I would also do live coding with students, but that wasn't rehearsed. In some cases it went really well, in others, it didn't (usually because something would just take too long -- or maybe because it was Scheme). Still, I enjoyed it and I know at least some of the students did.
This talk was, to me, an entertaining rant to get a point across, not a serious critique of others' writing.