Time |
S |
Nick |
Message |
04:13 |
|
prologic |
pung? |
04:13 |
|
prologic |
ping? |
04:13 |
|
prologic |
pong! |
10:13 |
|
pdurbin |
pang |
10:15 |
|
prologic |
quiet around here lately |
10:46 |
|
pdurbin |
perhaps everyone is heads down coding |
11:53 |
|
prologic |
haha |
11:53 |
|
prologic |
unlikely :) |
12:20 |
|
dotplus |
so should I gather that people are more interested in the react tutorial as a alternative language demo than the addressbookmvc? I've been sort of buried in real work and sort of onvacation since we first talked about itand I first worked on my golang code for addressbookmvc |
12:21 |
|
dotplus |
and I'm on such a bad connection, I can't see what I type quickly so y'all get to see how I normally type without my error correction |
12:21 |
|
pdurbin |
dotplus: no, no I'm still bitter that I haven't gotten pull requests from prologic or aditsu for https://github.com/pdurbin/addressbookmvc ;) |
12:21 |
|
dotplus |
I mean, I'm still going to finish it eventualy |
12:22 |
|
pdurbin |
dotplus: awesome. looking forward to seeing it |
12:23 |
|
dotplus |
although I suspect that's only for my own edificationbecause I'm sure that if I bring up golang as a language for a (suitable) work project, trivial api service for storing the results of Ansible runs), I'll get laughed at/told to use python like almost everything else we write |
12:24 |
|
dotplus |
although, I might be able to get away with doing it in circuits instead of flask |
12:24 |
|
dotplus |
or it might be considered important enough to be shunted off to a real developer on the Eng team instead of me ("devops" team) |
12:24 |
|
pdurbin |
so far so good with circuits for me |
12:25 |
|
pdurbin |
but I'm sure flask is fine too |
12:25 |
|
pdurbin |
dotplus: nothing wrong with knocking together a prototype. that's what happened with slashdot :) |
12:27 |
|
dotplus |
my only reservation about circuits vs flask is that flask is extremely well known, so much so that almost anyone who claims (non-specialty) python dev expereince could be expected to have some exposure to it, whereas I suspect that ~0% of our team have even heard of circuits |
12:27 |
|
dotplus |
pdurbin: in golang? I think that would irritate @coworkers. |
12:28 |
|
dotplus |
I can't wait to finish the CI effort so that I can start on an Ansible callbak plugin that reports activity and the api api service to receive/store that data. |
12:29 |
|
pdurbin |
dotplus: a prototype in go would irritate people? that makes no sense to me |
12:31 |
|
dotplus |
"why do it in golang whenyou could have done it python and then we wouldn't have to redo/port it?" |
12:32 |
|
pdurbin |
meh. I think a proof on concept can be in any language |
12:33 |
|
pdurbin |
let the real engineers step in if need be and rewrite the thing, like they did with slashdot |
12:34 |
|
prologic |
sorry pdurbin dotplus |
12:34 |
|
prologic |
I just haven't gotten around to find the motivation to finish my addressbookmvc demo |
12:34 |
|
prologic |
I really hate doing uis :) |
12:34 |
|
prologic |
haha |
12:35 |
|
prologic |
dotplus, re circuits exposure; I agree |
12:35 |
|
prologic |
so help me improve it :) |
12:35 |
|
prologic |
there is no magic silver bullet that'll get something that's been around since ~2004 to suddenly be well known by all Pythonists :) |
12:40 |
|
dotplus |
no silver bullet, sure. I suspect that the only real way to get circuits significant visibility/mindsahre would be a) create a non-trivial set of example apps that actually do useful things b) present at *lots* of conferences such as various pycons and whatever their local versions are called and things like devops days, LISA, etc. |
12:41 |
|
dotplus |
one other possibility would be to get it used by some big, *vocal* tech darling like etsy or facebook. |
12:43 |
|
prologic |
*nodS* |
12:43 |
|
prologic |
getting there :) |
12:43 |
|
pdurbin |
need a killer app :) |
12:43 |
|
prologic |
presented circuits in PyCONAU in 2014 |
12:44 |
|
prologic |
haha |
12:44 |
|
prologic |
yeah :) |
12:46 |
|
dotplus |
no, not a killer app, but a really useful set of example apps that both show it off and provide stealable patterns especially for those who are not "real" pythonistsas |
12:48 |
|
prologic |
yeah okay |
12:49 |
|
prologic |
guess I could write somes :) |
12:49 |
|
prologic |
the examples we do have are trivial at best but do show the things you "can do" |
13:12 |
|
pdurbin |
prologic: these? http://circuits.readthedocs.org/en/latest/#examples |
13:28 |
|
prologic |
http://circuitsaddressbookmvc.vz1.bne.shortcircuit.net.au/#/add |
13:28 |
|
prologic |
here you go :) |
13:29 |
|
prologic |
pdurbin, and https://github.com/circuits/circuits/tree/master/examples |
13:30 |
|
pdurbin |
prologic: whoa! way prettier than mine. good job |
13:30 |
|
prologic |
thanks |
13:30 |
|
prologic |
wanna see the backend code? :) |
13:31 |
|
pdurbin |
as a pull request? yes! :) |
13:32 |
|
prologic |
https://gist.github.com/prologic/7df15bb03d96fadb4873 |
13:32 |
|
prologic |
yeah sure :) |
13:32 |
|
prologic |
lemme tidy it all up first |
13:32 |
|
prologic |
and I think the search doesn't work I'll fix that too |
13:32 |
|
pdurbin |
so fancy |
13:34 |
|
prologic |
lol |
13:35 |
|
prologic |
told ya I hate uis :) |
13:35 |
|
pdurbin |
well, it doesn't show |
13:49 |
|
prologic |
hah |
13:56 |
|
prologic |
pdurbin, you have your PR :) |
14:16 |
|
prologic |
so what now? |
14:16 |
|
pdurbin |
prologic: merged! thanks! https://github.com/pdurbin/addressbookmvc/pull/6 |
14:16 |
|
prologic |
no worries :) |
14:22 |
|
dotplus |
interesting. you're certainly making the case that time-to-develop is very low, which is compelling to me. |
14:22 |
|
prologic |
haha |
14:22 |
|
prologic |
well it kind of is :) |
14:22 |
|
prologic |
but these examples are trivial |
14:22 |
|
prologic |
the power comes from the components |
14:23 |
|
prologic |
and loosely coupled architecture |
14:23 |
|
prologic |
Like yu see here: http://shortcircuit.net.au/~prologic/blog/article/2015/06/02/circuits-react/ |
14:23 |
|
prologic |
in adding Auth |
14:24 |
|
pdurbin |
dotplus: prologic has been working on that code for months :) |
14:25 |
|
dotplus |
yes, addressbookmvc is trivial; it would be nice to see dumping to sql/nosql databases instead of afile, and examples of how to modify for more complex data structure than name/phone number, input validation, etc. |
14:26 |
|
pdurbin |
dotplus: well, maybe all that should be in the spec: https://github.com/pdurbin/addressbookmvc/issues/4 |
14:27 |
|
prologic |
dotplus, *nods* yeah |
14:27 |
|
prologic |
it can get vastly more complex obviously |
14:27 |
|
dotplus |
of course. and there's a balance to be struck. If you make the example too complex, it becomes harder to understand |
14:27 |
|
dotplus |
and therefore less useful as a pedagogical tool |
14:28 |
|
dotplus |
pdurbin: it should! |
14:28 |
|
dotplus |
oh what? you're expecting a PR from me on that issue? um. |
14:28 |
|
dotplus |
:) |
14:30 |
|
pdurbin |
:) |
14:35 |
|
prologic |
yeah indeed |
14:35 |
|
prologic |
but we can trivially back the data by a database |
14:35 |
|
prologic |
that's not too hard |
14:35 |
|
prologic |
circuits has powerful coroutines |
14:35 |
|
prologic |
so we can wrap/thread calls to dbapi easily |
14:35 |
|
prologic |
:) |
14:36 |
|
prologic |
and turn "data" access into a seaprate component |
14:41 |
|
dotplus |
exactly. but those "trivial" additions warrant example code. |
14:43 |
|
prologic |
yeah kk |
14:43 |
|
prologic |
so shall I code that up as the "next ting" |
14:43 |
|
prologic |
sort of like |
14:43 |
|
prologic |
this commit is the initial simple example |
14:43 |
|
prologic |
the next commit moves the data to a database store |
14:43 |
|
prologic |
learn by commit |
14:57 |
|
dotplus |
so long as you make good use of tags and squashing uninteresting intermediate commmites, I think learn by commit could be very useful. |
14:58 |
|
dotplus |
I've been meaning to write a blog post on that for a while |
14:58 |
|
dotplus |
so many ideas, so little time |
15:01 |
|
prologic |
tell me about it |
15:01 |
|
prologic |
I was thinking of some good non-trivial apps to write |
15:09 |
|
prologic |
dotplus, pdurbin there is ofc http://circuitswiki.vz1.bne.shortcircuit.net.au/ |
15:09 |
|
prologic |
which has existed for quite some time now as a non-trivial demo |
15:09 |
|
prologic |
backed by sqlite |
15:10 |
|
prologic |
The nice thing is this has existed without modification really for years |
15:10 |
|
prologic |
so we really don't break out API(s) :) |
15:30 |
|
|
aditsu joined #sourcefu |
19:47 |
|
pdurbin |
aditsu: you use jetty, right? and I use glassfish |
19:47 |
|
pdurbin |
"Tomcat provides a lightweight and inexpensive container for the bulk of HUIT Java applications, where enterprise features like JMS and EJB are not required. Alternatives like Jetty, Resin and Glassfish are bit players in this space and simply don't have enough developer mindshare to make them worth pursuing." https://wiki.harvard.edu/confluence/display/HUITArch/Standardization+of+Instance+Components |
19:53 |
|
aditsu |
pdurbin: yeah, what's HUIT? horrible unawareness of internet technologies? |
19:53 |
|
aditsu |
seems like the server equivalent of "IE only" :p |
20:04 |
|
pdurbin |
aditsu: maybe they mean developer mindshare within Harvard. not sure |
20:06 |
|
aditsu |
pdurbin: they're not necessarily wrong about that.. tomcat is pretty popular I guess; but that doesn't mean it's awesome :) |
20:06 |
|
aditsu |
I watched https://www.youtube.com/watch?v=Zu0l-Ac7fTU earlier :p |
20:11 |
|
pdurbin |
semiosis: you use tomcat, I think |
21:40 |
|
semiosis |
pdurbin: erry day |
21:40 |
|
semiosis |
bit players, lol |
21:45 |
|
semiosis |
http://w3techs.com/technologies/overview/web_server/all -- tomcat is at 0.5%, no other java server is over 0.1% |
21:46 |
|
semiosis |
surprisingly, google is 1.3% of all web servers according to this survey. 2.0% according to netcraft, http://news.netcraft.com/archives/2015/05/19/may-2015-web-server-survey.html |
21:46 |
|
semiosis |
err, 2.36% |
23:32 |
|
pdurbin |
hmm |
23:45 |
|
pdurbin |
not sure how google has a web server but whatever |