Meta tags:

Headings (most frequently used words):

2010, wednesday, 2011, friday, eclipse, april, the, databinding, git, to, sputtering, digitized, 27, march, december, saturday, september, 25, february, 12, january, blog, archive, about, me, re, myth, of, lisp, genius, eclipsecon, and, high, performance, tabular, android, vs, ios, nother, developer, perspective, aggregation, mon, apple, more, praise, for, at, using, submit, patch,

Text of the page (most frequently used words):
the (128), and (44), that (31), git (30), #eclipse (28), for (22), you (17), with (16), was (15), code (15), org (14), have (14), this (14), apple (13), lisp (12), more (12), when (12), just (12), jface (11), all (11), can (11), about (10), posted (10), out (10), from (10), language (10), juckel (9), but (9), iphone (9), anthony (8), comments (8), bug (8), minutes (8), had (8), their (8), branch (7), would (7), new (7), developer (7), databinding (7), 2010 (6), working (6), like (6), into (6), now (6), change (6), has (6), not (6), software (6), they (6), use (6), write (6), apis (6), android (6), app (6), writing (6), programming (6), september (5), april (5), 2011 (5), been (5), time (5), work (5), than (5), cvs (5), must (5), using (5), swt (5), r3_5_maintenance (5), then (5), before (5), very (5), even (5), carbon (5), hardware (5), test (5), what (5), only (5), want (5), also (5), own (5), applications (5), list (5), device (5), process (5), level (5), december (4), labels (4), relatively (4), latest (4), project (4), start (4), through (4), another (4), wanted (4), actually (4), add (4), control (4), available (4), don (4), makes (4), commit (4), until (4), origin (4), dev (4), error (4), text (4), 275686 (4), one (4), your (4), platform (4), documented (4), apps (4), student (4), average (4), marketplace (4), ability (4), first (4), talk (4), feel (4), much (4), february (3), march (3), myth (3), genius (3), blog (3), around (3), rather (3), making (3), myself (3), after (3), didn (3), development (3), could (3), where (3), patch (3), quick (3), though (3), come (3), past (3), clone (3), wednesday (3), build (3), programmer (3), silenio (3), over (3), find (3), host (3), friday (3), model (3), developers (3), allow (3), already (3), may (3), data (3), example (3), each (3), how (3), quality (3), which (3), there (3), fee (3), perspective (3), ios (3), performance (3), syntax (3), vocabulary (3), allows (3), express (3), largely (3), languages (3), will (3), system (3), concepts (3), inc (2), fan (2), 2008 (2), 2009 (2), january (2), posts (2), getting (2), comfortable (2), late (2), say (2), tools (2), since (2), those (2), projects (2), some (2), old (2), compiled (2), issue (2), hand (2), told (2), while (2), really (2), commits (2), realized (2), make (2), reset (2), fixed (2), file (2), bugzilla (2), easy (2), full (2), against (2), outside (2), easier (2), checkout (2), http (2), bugs (2), few (2), found (2), integration (2), same (2), results (2), 2rc3 (2), comes (2), door (2), correct (2), url (2), choose (2), install (2), above (2), usage (2), post (2), should (2), b294929 (2), cherry (2), pick (2), nice (2), ipad (2), are (2), fact (2), convinced (2), blend (2), manner (2), prescribed (2), call (2), any (2), private (2), originally (2), written (2), objective (2), executed (2), directly (2), link (2), others (2), rcp (2), aggregation (2), framework (2), well (2), suggestions (2), map (2), given (2), observablebeanlist (2), observablebeanset (2), classroompackage (2), literals (2), lower (2), google (2), single (2), ostensibly (2), reason (2), running (2), order (2), store (2), paid (2), ready (2), market (2), application (2), works (2), simple (2), them (2), completely (2), openness (2), mean (2), itself (2), sdk (2), extremely (2), see (2), reading (2), things (2), eclipsecon (2), proper (2), high (2), tabular (2), these (2), two (2), generators (2), idioms (2), cognitive (2), entire (2), serialized (2), nested (2), lists (2), asts (2), lead (2), programmable (2), higher (2), thought (2), shared (2), statement (2), productivity (2), sputtering (2), digitized (2), awesome, theme, powered, blogger, view, complete, profile, sales, trader, jruby, osgi, enthusiast, bicyclist, melissavoegeli, 2007, august, archive, subscribe, atom, home, older, came, poke, decided, off, although, tolerable, huge, improvement, external, contributors, started, importing, workspace, noticed, compilation, errors, due, recent, changes, chase, switched, instead, fine, poking, probably, opposed, drilling, tree, followed, fetching, coffee, waiting, check, realizing, different, point, back, normal, workflow, mucked, separate, broken, head, ignore, committed, formatted, send, painless, experience, real, benefit, play, longer, lived, local, trying, feature, version, locally, maintain, patchset, upstream, hearty, thanks, everyone, pushing, forward, repositories, migrate, canonical, repo, having, mirror, significantly, repeat, satisfied, format, b130854, snippets, mirrors, 130854, submit, yesterday, iamkevb, tweeted, needs, help, attach, patches, 294929, happened, downloaded, builds, succeeded, reproducing, steps, luckily, exhibit, comment, hoping, someone, who, knew, able, deduce, changed, between, today, quarti, believed, result, figured, plenty, whether, headed, turned, touch, bindings, specifically, opened, imported, export, deployable, plug, ins, fragments, restart, workbench, voila, solved, took, left, enough, sing, praises, snip, log, grep, a7d0c902cae6382be0b0812a773f651f75a801d8, author, mkeller, date, thu, oct, 0000, painting, rulers, draw, paint, a7d0c902c, finished, ahead, praise, next, laptop, unibody, macbook, pro, upgrade, early, unless, pretty, hard, face, vote, wallet, take, business, elsewhere, large, puts, macbooks, fantastic, viewpoint, exploded, decade, brazen, lock, policies, does, dictate, unconscionable, perform, aapl, refuses, onto, purchase, immediately, current, continue, statistics, jobs, uses, his, keynotes, demonstrate, popularity, javascript, webkit, engine, compile, intermediary, translation, compatibility, layer, tool, prohibited, noted, made, following, program, license, agreement, daring, fireball, mon, especially, displaying, numeric, table, often, wanting, support, built, students, examresults, easily, bind, tablecolumn, exam, end, created, extending, greatly, appreciate, api, design, extend, functionality, pulled, tests, github, here, create, observable, score, iobservablelist, writablelist, studentlist, class, iobservableset, listtosetadapter, iobservablemap, aggregateproperties, emfproperties, student__test_results, values, exam_result__score, observedetail, net, aggregate, saturday, regarding, observation, side, approach, wide, open, crowd, sourced, gatekeeper, place, purely, reasons, free, reject, delay, indefinitely, little, entrusting, ultimate, authority, patentgate, bought, phone, literally, hello, world, sure, confident, satisfaction, physically, installed, wants, friends, beta, walking, configuration, setting, pointing, finally, opt, sell, independently, sort, freedom, care, biggest, win, its, freely, documentation, source, big, part, hobbyist, get, got, thing, bit, party, availability, final, straws, buy, disappointed, sign, account, were, charging, allowing, upload, servers, dissemination, fully, target, during, paying, year, tithe, marketing, whereoscope, share, nother, november, honored, selected, amongst, batch, audition, sessions, conference, fast, approaching, finalize, materials, watched, taking, scott, heart, eliminate, suck, progress, prep, noticing, shot, far, information, properly, covered, likely, remove, nattable, xviewer, comparison, focus, simply, upon, tables, give, opportunity, dive, deeply, methods, gathering, interested, hearing, anyone, considering, attending, most, worthwhile, excited, san, jose, couple, weeks, series, video, recommended, combine, regular, seamless, becomes, right, straightforward, read, other, raise, abstraction, developed, quicker, stems, facts, abstract, trees, expressions, parsed, second, several, layers, specify, run, execution, compiler, generate, expression, generated, bunch, good, processing, recode, doing, intend, she, developing, involved, turn, whole, programmers, discussing, non, still, required, dumb, down, constant, specification, sometimes, inhibit, recognition, intent, tether, consider, natural, affect, communication, processes, without, cultural, cumbersome, complex, nuanced, ideas, generally, trial, paraphrase, restatement, both, parties, understanding, our, mind, trouble, holding, adequately, john, foderaro, cacm, 1991, core, gain, response, ensuing, particular, respond, apparent, confusion, claimed, increased, versus, traditional, java, conversation, reddit,

Text of the page (random words):
sputtering digitized sputtering digitized wednesday april 27 2011 re the myth of the lisp genius this post is largely a response to the myth of the lisp genius and the ensuing conversation on reddit in particular i want to respond to the apparent confusion about where the claimed increased productivity could come from in a language like lisp versus a more traditional language like c java or c for me the core of the productivity gain comes from this statement lisp is a programmable programming language john foderaro cacm september 1991 consider how natural languages affect your communication with others and your own thought processes without a proper shared vocabulary and cultural idioms it can be very a cumbersome process to express complex and nuanced ideas it s generally a trial and error process of statement paraphrase restatement until both parties feel they ve come to a shared understanding our mind can even have trouble holding on to concepts that we can t adequately express in language programming a system can feel much the same when you first start out code test recode until you feel the code is doing what you intend as a programmer works on a system he or she will be developing a cognitive model of the concepts involved this will in turn lead to a whole vocabulary and language that programmers can use when discussing the system with one another but in non programmable programming languages they re still required to dumb it down when actually writing out the code this constant re specification of higher level concepts in the lower level language can sometimes lead to bugs in the writing and can inhibit quick recognition of the higher level intent when reading code it can also tether the entire thought process to the level of the language on the other hand lisp allows the programmer to raise the level of abstraction in the programming language itself so that you can more directly express in code the cognitive model that s been developed which makes the entire programming process much quicker this ability largely stems from two facts of lisp first it s syntax is extremely simple when writing lisp code you re largely writing abstract syntax trees serialized in nested lists rather than expressions that have to be parsed into asts second lisp allows you to write code at several layers of the language all programming languages allow you to specify code to run at execution time lisp also allows you to write code that will be executed by the compiler to generate the expression which should be compiled since the generated lisp code is just a bunch of asts serialized to nested lists and lisp is very good at list processing it s relatively easy to write these code generators when you combine these two things a very regular syntax with seamless usage of code generators then it becomes much easier to add vocabulary and idioms that blend right in with the language making the code much more straightforward to read write and reason about posted by anthony juckel at 1 44 pm no comments friday march 4 2011 eclipsecon 2011 and high performance tabular databinding this past november i was honored to have my talk high performance tabular databinding be selected from amongst the first batch of eclipsecon 2011 audition sessions now the conference proper is fast approaching so i m working to finalize the materials for the full talk i ve already watched the recommended video series and am taking scott s suggestions to heart in order to eliminate all suck from my talk as i progress in the prep i m also noticing that i had originally shot for far more information than i feel could be properly covered in 20 minutes so i m likely to remove the nattable xviewer comparison and focus simply upon databinding with swt tables that ll give me the opportunity to dive more deeply into my methods for gathering performance data and what i found in that data i d be interested in hearing from anyone considering attending the talk though what would make the 20 minutes most worthwhile for you all in all i m very excited to see you all in san jose in a couple weeks posted by anthony juckel at 11 19 am no comments labels eclipse wednesday december 8 2010 android vs ios a nother developer s perspective while reading android vs ios a developer s perspective from the whereoscope blog i realized a few things that i d like to share about my own perspective on android vs ios development for me the single biggest win of the android platform is its openness i don t just mean the freely available documentation and source for the platform though that is a big part of it what i mean more is the ability for a hobbyist like myself to get software running on the device itself when i got my iphone the first thing i wanted to do with it was write an app for it i was a bit late to the iphone party so the sdk was already out in fact the availability of the sdk was one of the final straws that convinced me to buy one but i was extremely disappointed to find you had to sign up for a paid developer account before apple would allow you to test software you were writing even on a device you ostensibly own i can see charging a fee before allowing developers to upload their app to apple s servers for dissemination through the app store but i d like the ability to fully test software i m writing on the target device during the development process and i don t want to start paying the 99 year tithe to apple until i m actually ready to start marketing the app when i bought my android phone i literally had a hello world app of my own running on the device in 15 minutes sure there s a fee to google in order to host your apps on the marketplace just as there is to host apps on the app store but that fee can be paid by the developer when they re ready to market the application after they re confident it works to their satisfaction when physically installed on a device also if a developer wants to have friends beta test their application it s as simple as walking them through a configuration setting change and pointing them at a url finally android developers have the ability completely opt out of the marketplace and market sell their applications completely independently if they so choose that s the sort of openness and freedom that i care about as a developer regarding the observation that the software is of lower quality on average on the marketplace i must say that i side with google s approach to this as well i d rather have a wide open marketplace with crowd sourced quality control than have a single gatekeeper which is ostensibly in place purely for quality control reasons but is free to reject or delay apps indefinitely with little to no reason given and then there s patentgate i m just not comfortable entrusting apple inc with ultimate authority over my work posted by anthony juckel at 9 17 am no comments saturday september 25 2010 eclipse databinding aggregation in rcp apps i m working on especially when displaying numeric data in a table i often find myself wanting to have some aggregation support built into eclipse s databinding framework as an example if i have a list of students and each student has a list of examresults it would be nice to easily bind a tablecolumn to the average of each student s exam results to that end i ve created a new project net juckel rcp databinding aggregate i m relatively new to extending the databinding framework so i d greatly appreciate comments on the the api design as well as suggestions for how to extend the functionality as a quick example pulled from the tests on github here s how you d create an observable map for the example given above average score for each student in a list iobservablelist observablebeanlist new writablelist studentlist student class iobservableset observablebeanset new listtosetadapter observablebeanlist iobservablemap map aggregateproperties average emfproperties list classroompackage literals student__test_results values classroompackage literals exam_result__score observedetail observablebeanset posted by anthony juckel at 3 09 pm no comments labels eclipse friday april 9 2010 c mon apple as noted at daring fireball and others apple has made the following change in their iphone developer program license agreement old 3 3 1 applications may only use documented apis in the manner prescribed by apple and must not use or call any private apis new 3 3 1 applications may only use documented apis in the manner prescribed by apple and must not use or call any private apis applications must be originally written in objective c c c or javascript as executed by the iphone os webkit engine and only code written in c c and objective c may compile and directly link against the documented apis e g applications that link to documented apis through an intermediary translation or compatibility layer or tool are prohibited the fact that apple refuses to allow me to install software i write onto the iphone 3g that i own has already convinced me to not purchase another iphone or ipad but this change makes me want to immediately blend my current iphone just so i don t continue to add to the statistics jobs uses in his keynotes to demonstrate the iphone s popularity i m a large fan of the hardware apple puts out the iphone ipad and macbooks are all fantastic from a hardware viewpoint but as aapl has exploded over the past decade apple has been getting more and more brazen in their lock in policies now not only does apple want to control the hardware platform and software platform they also want to dictate the tools that developers use to perform their work that s just unconscionable i really wanted my next laptop to be a nice new unibody macbook pro to upgrade my early 2008 model but unless apple makes a pretty hard about face on this i ll have to vote with my wallet and take my business elsewhere posted by anthony juckel at 8 23 am no comments friday february 12 2010 more praise for git at eclipse yesterday iamkevb tweeted swt needs help with a carbon bug on 10 6 if you have time and hardware attach patches to http bugs eclipse org 294929 i happened to have the hardware to test it so i downloaded a few carbon builds and succeeded in reproducing the error using the steps posted to bugzilla luckily i found that the latest 3 6 integration build didn t exhibit the same error now i m no carbon programmer so i just posted my results as a comment hoping that someone who knew more about swt would be able to deduce what changed between 3 5 2rc3 and the latest in the 3 6 integration build today silenio quarti posted that he believed the error was fixed as a result of bug 275686 now this is where it git comes in i only had about 30 minutes before i had to be out the door but i figured that would be plenty of time to whether silenio was correct i headed over to http dev eclipse org git to find out the url for the jface text project turned out bug 275686 was a jface change and didn t even touch the carbon bindings specifically git clone git dev eclipse org org eclipse jface org eclipse jface text git snip cd org eclipse jface text git log grep 275686 commit a7d0c902cae6382be0b0812a773f651f75a801d8 author mkeller date thu oct 8 19 22 34 2009 0000 bug 275686 painting rulers should not draw outside of swt paint git checkout b b294929 origin r3_5_maintenance git cherry pick a7d0c902c finished one cherry pick on branch b294929 your branch is ahead of origin r3_5_maintenance by 1 commit then i opened my 3 5 2rc3 carbon build of eclipse imported the org eclipse jface text project and file export deployable plug ins and fragments choose install into host and restart the workbench voila silenio was correct and that commit solved the issue all told the above took about 10 minutes and left enough time for me to sing the praises of git usage at eclipse in this blog post before i had to be out the door posted by anthony juckel at 10 47 am 2 comments labels eclipse wednesday january 6 2010 using git to submit a patch to eclipse i ve been getting more and more comfortable with git of late so when it came time for me to poke around at an eclipse bug 130854 i decided to work off the git mirrors rather than cvs i must say although the eclipse cvs tools making working with cvs relatively tolerable using git is a huge improvement for external contributors like myself since i was working on org eclipse jface i started with git clone git dev eclipse org org eclipse jface org eclipse jface git git clone git dev eclipse org org eclipse jface org eclipse jface snippets git after importing those projects into my workspace i noticed some compilation errors due to recent changes in swt now the bug i was working on was an old bug so i didn t have to chase the latest development so i just switched to the r3_5_maintenance branch instead git checkout b b130854 origin r3_5_maintenance now the project compiled just fine so i could start poking around at the issue at hand all told this was probably just 3 5 minutes as opposed to drilling through a cvs tree in eclipse for 3 5 minutes followed by fetching a coffee while waiting for the branch to check out another 3 5 minutes then another 3 5 after realizing i really wanted a different branch at this point it was back to a normal git workflow i mucked around with the code had about 3 separate commits all broken before i realized where i wanted to actually make the change just reset head on my branch to ignore those commits committed the change that actually fixed my bug then formatted a patch file to send to bugzilla git add git commit git reset repeat until satisfied git format patch origin r3_5_maintenance all in all a very quick and painless experience though this would be relatively easy even using cvs the real benefit of git would come into play if i had a longer lived local branch trying to add a new feature i d have full version control available locally to maintain my work as a patchset against the latest upstream work a hearty thanks to everyone at eclipse that s been pushing forward on making git repositories available even if projects don t migrate to using git as their canonical repo just having a git mirror available makes working from the outside significantly easier than it has been in the past posted by anthony juckel at 9 39 pm no comments labels eclipse older posts home subscribe to posts atom blog archive 2011 2 april 1 re the myth of the lisp genius march 1 2010 5 december 1 september 1 april 1 february 1 january 1 2009 8 december 1 september 3 august 2 april 2 2008 4 september 2 march 1 february 1 2007 7 december 7 about me anthony juckel sales trader jruby and osgi enthusiast bicyclist and fan of melissavoegeli view my complete profile awesome inc theme powered by blogger