Posts tagged with ‘Open Source’
In light of continuing threats we should build it ourselves.
Initial design (not for kids)
£20,000,000 for more detailed plans and enough chicken wire to protect reactor exhaust ports.
£543,000,000,000,000,00 ($850,000,000,000,000,000) to secure full funding for actual construction.
To keep costs lower the entire project will use open source hardware and software.
FJP: Make it so.
Investigative Reporters and Editors has a nice rundown of free production tools for journalists. These include old standbys such as Gimp for images and graphics, Audacity for audio editing and Open Movie Editor for video editing.
Multimedia production can get pretty pricey pretty quickly, of course. There’s a lot of gear and software needed so knowing what alternatives are out there is important.
If money’s tight, a great place to start is Open Source Alternatives. For example, if you need Adobe’s Photoshop but don’t have (or want to spend) the $699 to buy the standalone version, OSA lists Gimp and Krita among others as alternatives.
There are Web-based alternatives out there as well. For example, Aviary has a swiss army knife of audio and image editing applications that sit in the browser. In 2010, Google purchased the Web-based image editor Picnik and now you can crop, enhance and perform other basic edits in Picasa/Google+.
Other important browser-based tools are plugins and add-ons. For example, if you’re working with large files you’ll eventually need to get them somewhere which you’ll often do via FTP (although I come across more and more people who are using shared folders in Dropbox). Use Firefox? Try FireFTP. Chrome more your flavor? Try FileZilla. Want a desktop FTP client instead? Try Cyberduck.
Sometimes though, what’s already on your computer can bring you where you need to go. For example — and using a Mac because that’s what I have and know — iMovie, Garage Band and iPhoto all come pre-installed and are perfectly fine for editing video interviews, creating radio pieces and organizing and lightly editing your photos. Are they as robust as Final Cut, Pro Tools and some sort of Adobe Bridge/Photoshop amalgam? No, but they’re tools immediately available to you once you actually have the computer. Besides, the tools we need don’t always have to be the latest and greatest model of something.
There are good reasons to have the software that have become standard across the industry. This is especially true when collaborating with others. But when money’s tight, or you just want to try things out before diving deeper into a particular format, play with what’s low cost or free before making the plunge.
Besides, it’s the end result that matters. Once you publish your amazing audio, video or interactive piece, your appreciative audience isn’t going to care what you used to get there.
Wikipedia joins a growing list of high profile organizations leaving Google Maps and moving to the open source Open Street Maps. The move comes after Google announced in March that they would begin charging Web sites that receive more than 25,000 requests per month for use of their maps.
Previous versions of our application used Google Maps for the nearby view. This has now been replaced with OpenStreetMap - an open and free source of Map Data that has been referred to as ‘Wikipedia for Maps.’ This closely aligns with our goal of making knowledge available in a free and open manner to everyone. This also means we no longer have to use proprietary Google APIs in our code, which helps it run on the millions of cheap Android handsets that are purely open source and do not have the proprietary Google applications.
OpenStreetMap is used in both iOS and Android, thanks to the amazing Leaflet.js library. We are currently using Mapquest’s map tiles for our application, but plan on switching to our own tile servers in the near future.
Also, via Techspot, a look at mapping economics:
In March, Google announced it would be charging high-volume users for its once gratis Google Maps service. Developer accounts which pull in fewer than 25,000 requests per month are not considered high-volume and thus have remained free. However, for accounts that exceed 25,000 views, developers must pay between $4 to $10 for every additional 1,000 views generated. For popular websites and apps that rely on Google Maps APIs, this can add up pretty quickly…
…Although some may be quick to call out Google for its decision to charge a premium, Google Maps has really been the only mapping service to offer its product to everyone without cost. Traditionally, companies like NavTeq and TeleNav have always licensed their map data to third parties. It costs a lot of money to put together accurate maps and Google took some risk offering theirs free of charge. As a result, Google Maps has become the go-to place for many companies and users alike. In fact, comScore found that over 71% of Americans had used Google Maps in February.