← first ← previous page 60 of 61 next → last →
Doc Searls is blogging the 'Stevent' live.
The box has a dual G4s, fast L2&3 cache, an ASIC Gigabit Ethernet and FireWire sys controller, Big 266 MHz DDR SdRAM Dual Gigabit ports, quad ATA drives, on a 533MB/s bus, buncha other stuff I can't keep up with. "Fastest architecture we've ever built." (He's been describing the maximum configuration.)
Note to Dave - Mark may have said he does not like outliners; however, he DOES understand the power of an outliner:
I like to edit Python code in an IDE (or in Emacs in python-mode), which autoindents for me and allows me to "fold" code blocks (collapse an outline node) that I'm not currently using. He's already got what you're offering him in Radio's outliner (the one Frontier programmers all love)- but without the ability to easily edit that same script in some other text editor.
Mark Pilgrim investigates OPML. He makes some of the same observations that I've made in the past (unfortunately I don't believe I published any of them, so go read his).
I posted yesterday a response to some comments by Doc Searls at SXSW. Jim responded, which prompted me to respond again. I think my response was one of my better explanations of my political leanings, so I've formalized it here. Seth also had some comments worth checking out.
I'd never used MPW, so when I (almost accidentally) opened up one of BBEdit's new Shell Worksheets, I was a bit perplexed as to what I was looking at. It looked like a lot of text - a document - but there were commands in there as well - and the type of document I was looking at suggested that you could do something with them. Indeed, say the instructions - put the cursor at the end of one of the lines containing a shell command, and BBEdit AutoMagically behind the scenes runs the command in a shell, and dumps the output right into your document. OMG. This is... amazing. Hm. Combine this with a command-line xmlrpc client, and strange (and frightening?) things could happen... Muahahaha -)
uptime
7:49PM up 2 days, 23:13, 5 users, load averages: 1.30, 1.17, 1.06
Scripting News: Brent Simmons is leaving Userland, for parts unknown. Thanks Brent for years of awesome software, and for being a great guy! (that part's not going to change. ;-)) Look forward to seeing you around the 'net!
Ugh. Jim wanted to report a bug in Userland's Radio Userland, and ask a question. The reward for his trouble?
For some reason Dave, from this link on down on todays' Scripting News, there are no permalinks on the entries. I'm not logged on as "me" right now so I can't email you. What happened?
Jim is "urgently in need of work". If you need an awesome coder, a great mentor, or all-around great guy in your company, check him out.
Be aware - Jim needs to work remotely, and he's by far the one I would bet one if I could hire a teleworker. He's motivated, creative, and productive.
Dave is making a point on Scripting News regarding IDL (or in this case WSDL) for Frontier, and other non-typed scripting languages. His point is that he cannot generate at runtime the WSDL directly from the code, as can C# or Java developers - b/c their runtimes have information about the types and numbers of parameters to a call.
This means having to handcode the WSDL for a web service in these environments, which can be a PITA if your service is at all large.
I have an idea though. One way to get around this would be to implement a meta-data header for these environments similar to javadoc. I'll use Frontier as an example.
In Frontier, scripts are outlines. Frontier already has a rich set of functionality dealing with rendering outlines into other formats, esp. HTML. You can use[#directives](http://monkinetic.blog/tag/directives) in your outlines, which get translated into information in the symbol table when rendering the outline (or any other datatype for that matter).
So, I would propose a simple set of[#directives](http://monkinetic.blog/tag/directives) that can be inserted into a script outline above the actual script code, as a commented block. That block can be grabbed and processed to generate whatever idl format is desired.
This is just an idea, someone with more Frontier experience could come up with a better design. I also know that Perl has Perldoc and POD (inline support for manpages), so including this information in perl scripts in a long tradition in that community.
Also, at least someone is working on WSDL support in Python (which has an easily introspected runtime). "Therefore I am planning to write a WSDL generator that will examine our exposed methods and write out a valid WSDL file."
So, I think that lack of explicitly typed data should not be the final reason not to support some sort of IDL for web services. There may be other, better reasons, but I have not seen them yet.
Since Jim is taking the awesome Cocoa class at Big Nerd Ranch SF, and I can't (Waaahhh), I want Aaron's book instead.
I've started reading Andrew Sullivan's website pretty much daily. He's a fairly prolific blogger, now we just need to get him to make his posts linkable. Doc agrees.
"Jim" Roepcke, my current WebObjects mentor and all-around great guy, is bragging about the blog he built in an hour with WebObjects. We won't mention who put him up to it...
At Macworld SF, Steve Jobs layed out Apple's vision for itself and the future of the Macintosh. In a 15 minute section of his keynote, he described the digital lifestyle, where our Macs become "Digital Hubs" that route information and media between the new generation of digital devices that are becoming more and more commonplace.
#item1413"='href"http://jim.roepcke.com/2000/12/03None#item1413"' 12="" 2000="" href"http:="" jim.roepcke.com="">Jim points out that Radio Userland, once promised to be a free distribution, will actually have a moderate price once officially released.
Dave has put the Userland Discussion Group on pause, and is re-instituting the "Mail Pages", which ran '96..'98. To help ease the time burden is Radio Userland, Dave's üautber-content-tool.
← first ← previous page 60 of 61 next → last →