It is more fun to use a handheld ham radio when you can tell it to scan different frequencies and stop there if it hears anyone. Whatever your location there are places to hang out on certain frequencies. For example here are some of them around Milwaukee Wisconsin. The trouble is that wherever you go those places will change and it is hassle to program your handheld to know about them. Fortunately it can be done easily:
CHIRP makes it easy to program your handheld radios.
Whether not you play guitar, or do custom software development, you ought to pay homage and respect to Line6 for supporting their gear for years and years after the release date with excellent software drivers and tools. Surely their excellent long-term gear support and quality eats into their profits a bit, but they create life-own Line6 fans with nearly every purchase.
My reason for posting here is that setting up my old POD XT on Windows 7 required accepting just a couple of oddities, and then everything worked fine, and I can’t be the only one facing this. Here is how I did it in order.
Ran [Line 6 Drivers v220.127.116.11 Installer].exe with PODxt support. This was a battle because the POD wasn’t getting detected. Finally I remembered that I had always used the front USB port, not the back. Plugged it in there and the installer detected it just fine. This was major blocker until I remembered that (my fault).
Ran [Line 6 License Manager v1.07 Installer].exe.
Ran [Line 6 Monkey v1.65 Installer].exe.
Ran [Line 6 Edit v3.06.0 Installer].exe.
At my preference, I reinstalled the firmware and patches, because I forgot what was even on there and why.
Bought the Bass Expansion pack. Downloaded the PDFs for it to make sense of what is on there. Line6 Money will install the plugin and that worked flawlessly. The only oddities were two things. The first was that the new amp models for the bass didn’t show up. Literally amps #79 to #104 were gone. Rebooting the POD fixed this. The second was that in Line6 Edit, when you go to edit the amps, the tool complains that I don’t have support for those amps. Not sure what to do but things seem to work fine.
That is my story.
Pharo is a fork from the Squeak open-source Smalltalk. We decided to start Pharo because as active Squeakers, and responsible for Squeak 3.9, we felt the need to reconsider choices made. We want to create a better Smalltalk and be free to enhance it without fear of backwards compatibility to Squeak.
Looks pretty fun!
Via the homepage:
The 4th ACM International Conference on Distributed Event-Based Systems (DEBS) builds on the success of first three editions from 2007. DEBS Conference success is rooted in five editions of the DEBS workshops held from 2002 to 2006 in companion with major conferences such as ICDCS, ICSE, and SIGMOD/PODS. The conference has received full ACM sponsorship since 2009.
The objectives of the DEBS Conference are to provide a forum dedicated to the dissemination of original research, the discussion of practical insights, and the reporting on relevant experience relating to event-based computing that was previously scattered across several scientific and professional communities. The conference also aims at providing a forum for academia and industry to exchange ideas, for example, through industry papers and demo papers.
-------------------------------------------------------------------------- Event-based systems are rapidly gaining importance in many application domains ranging from real time monitoring systems in production, logistics and networking to complex event processing in finance and security. The event based paradigm has gathered momentum as witnessed by current efforts in areas including event-driven architectures, complex event processing, business process management and modelling, Grid computing, Web services notifications, information dissemination, event stream processing, and message-oriented middleware. The various communities dealing with event based systems have made progress in different aspects of the problem. The DEBS conference attempts to bring together researchers and practitioners active in the various subcommunities to share their views and reach a common understanding. The scope of the conference covers all topics relevant to event-based computing ranging from those discussed in related disciplines (e.g., coordination, software engineering, peer-to-peer systems, Grid computing, and streaming databases), over domain-specific topics of event-based computing (e.g., workflow management systems, mobile computing, pervasive and ubiquitous computing, sensor networks, user interfaces, component integration, Web services, and embedded systems), to enterprise related topics (e.g., complex event detection, enterprise application integration, real time enterprises, and Web services notifications). The topics addressed by the conference include (but are not limited to): Models, Architectures and Paradigms - Event-driven architectures - Basic interaction models - Event algebras, event schemas and type systems - Languages for event correlation and patterns, streaming and continuous queries, data fusion - Models for static and dynamic environments - Complex event processing - Design and programming methodologies - Event-based business process management and modeling - Experimental methodologies - Performance modeling and prediction based on analytic approaches Middleware Infrastructures for Event-Based Computing - Federated event-based systems - Middleware for actuator and sensor networks - Algorithms and protocols - Event dissemination based on p2p systems - Context and location awareness - Fault-tolerance, reliability, availability, and recovery - Security issues - (Self-)Management - Mobility and resource constrained device support - Streaming queries, transformations, or correlation engines Applications, Experiences, and Requirements - Use cases and applications of event-based systems - Real-world application deployments using event-based middleware - Domain-specific deployments of event-based systems - Real-world data characterising event-based applications - Benchmarks, performance evaluations, and testbeds - Application requirements for next-generation event-based solutions - Relation to other architectures - Enterprise application integration - Event-driven business process management - Information logistics - Seamless integration of event-based mechanisms into middleware platforms
Don’t design everything you will need in the next 100 years, but design the ability to create things we will need in 20 or 100 years. The heart of the Perl 6 effort is the extensibility we have built into the parser and introduced language changes as non-destructively as possible.
with that of [R3RS] Scheme in 1986:
Programming languages should be designed not by piling feature on top of feature, but by removing the weaknesses and restrictions that make additional features appear necessary.
(via R3RS, referenced in R5RS)
In other words, language implementers ought to accept that they aren’t going to “get it right” on the first try, and they should leave the language extensible for additions.
Are you as excited about Perl 6 as I am! 🙂