Skip to main content

PyCon: Lighting Talks

Resolver is a Rapid Application Development tool with a spreadsheet interface. Imagine a spreadsheet where you can embed Python objects in the cells. It's written in IronPython. It's commercial.

FIVEDASH is fully-featured, general-purpose, open source accounting software. It's brilliant. Competing with QuickBooks Pro has got to be tough. However, QuickBooks Pro can't possibly address the long tail of accounting needs. For instance, who's going to write tax software for Brazil? Someone can come along and extend FIVEDASH to do it. Since FIVEDASH is GPLed, they'll benefit anytime someone else extends it. It's the classic win win situation for open source. Accounting software is one thing I never thought I'd ever see someone bother doing open source, but now I see that it makes perfect sense for a company to do so.

Dragon NaturallySpeaking is speech recognition software. They code their prototypes in Python. It's used by Google 411 and Microsoft Sync.

Leo is an outline-based Python IDE. Imagine the entire project being treated as an outline with project-wide code folding. One drawback is that it leaves metadata in the code in the form of Python comments.

"Why Does Client Side Python Suck" was a lightning talk focused on improving software distribution for Python-based Windows applications. Python is a large download. The output of py2exe isn't extensible once it's downloaded. The speaker wants to treat Python as a platform and have it installed separately of the main application under Windows.


Giles said…
Hey there - it's worth saying that although Resolver One is commercial, it's free for non-commercial use so long as you don't mind attaching an open-source license to your spreadsheets.

(Full disclosure - I work for Resolver Systems.)

jjinux said…
> so long as you don't mind attaching an open-source license to your spreadsheets.

Weird. That's sort of the opposite of gcc. gcc is free software, but you can still use it to compile commercial software ;)
Giles said…
Heh, so we've invented an inverted form of the LGPL :-)

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p