home | log | search | bash | stats | wiki


Matches for gabriel_laddel, 3496 total results Sorted by newest | relevance

Tue Feb 24 18:37:56 UTC 2015  <gabriel_laddel>   -- http://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD898.html

Tue Feb 24 18:37:55 UTC 2015  <gabriel_laddel>   And also for the American Universities the tide may be turning. Traditionally they have been asked to train the work-force for the American industry, while the question of educating the industry so as to be worthy of their graduates was left untouched. But, currently, companies in Silicon Valley seem to be folding up at a higher rate than they are erected. I consider that good news because it could drive home the me

Tue Feb 24 18:37:55 UTC 2015  <gabriel_laddel>   ssage that neither slogans like "knowledge-based decision aids", nor a combination of adhoccery and brute force will do the job. (It is regrettable that large groups only come to their senses after their day-dreams have turned into nightmares but, this being so, we should occasionally welcome the nightmares.)

Sun Feb 08 20:33:22 UTC 2015  <gabriel_laddel>   kk. I should be discussing this in design documents anyways.

Sun Feb 08 20:32:18 UTC 2015  <gabriel_laddel>   Why might one want to see the C ast? Let's say that we've got a codebase like the linux kernel, or opengl drivers. You know that somewhere you've got some stuff that talks to the hardware, but grep returns false positives. You instead pull the ast into memory, query across it for the bits your looking for. False positives now indicate something about the language (i.e., that I don't understand it as well as I though

Sun Feb 08 20:32:18 UTC 2015  <gabriel_laddel>   t) rather than just a false positive. Again, I've never written C, and perhaps the ast is so complicated that it's actually impossible to get any useful information out of it, but my current experience suggests that having this ability is a good idea. Building something like `slime-who-calls' suddenly becomes simple.

Sun Feb 08 20:32:00 UTC 2015  <gabriel_laddel>   ..

Sun Feb 08 20:31:51 UTC 2015  <gabriel_laddel>   As for PGP, I'm assuming that I'm going to have to spend a decent amount of time with the codebase and reading the spec. Perhaps not.

Sun Feb 08 20:25:42 UTC 2015  <gabriel_laddel>   trinque: in any case, I hate everything about the browser.

Sun Feb 08 20:24:47 UTC 2015  <gabriel_laddel>   trinque: well, there is that too.

Sun Feb 08 20:24:35 UTC 2015  <trinque>   gabriel_laddel: the outputted JS is more comprehensible?

Sun Feb 08 20:24:20 UTC 2015  <gabriel_laddel>   modifying parenscript isn't terrible.

Sun Feb 08 20:24:13 UTC 2015  <gabriel_laddel>   trinque: Modifying clojurescript is god-awful.

Sun Feb 08 20:23:28 UTC 2015  <trinque>   gabriel_laddel: how do you find using parenscript?

Sun Feb 08 20:22:11 UTC 2015  <gabriel_laddel>   "As for what language I'll be using on any given project, it will be determined entirely by what is correct for the project."

Sun Feb 08 20:21:22 UTC 2015  <thestringpuller>   !up gabriel_laddel

Sun Feb 08 20:19:21 UTC 2015  <gabriel_laddel>   merely an aid.

Sun Feb 08 20:19:17 UTC 2015  <gabriel_laddel>   it, and nothing else will ever be a substitute for thought.

Sun Feb 08 20:18:57 UTC 2015  <gabriel_laddel>   mircea_popescu: I have some code now that converts javascript to parenscript

Sun Feb 08 20:18:00 UTC 2015  <gabriel_laddel>   asciilifeform: I'm assuming, at least for now, that I'm going to have to /look/ at the current PGP sources (thus the C sexprast ). This has no bearing on what will be released other than - I will do what makes sense given the situation.

« Previous Page    Next Page »