A long time ago, when I started building my first video game server for
Double Cluepon, my video game company, I did a bad
thing. I looked at the AMF library for Perl and Python and decided that
Python's looked better. I had always meant to learn Python, and this felt like
the perfect opportunity. It had cooperative multitasking (Twisted) and it had
an ORM (SQLAlchemy), so along with the messaging format (PyAMF), I had
everything I needed to build a server for a Flash MMO (later migrated to AIR).
Let me reiterate my mistake: While under time constraints, I chose to learn a
new programming language. I didn't realize my mistake until it was too late.
As YAPC::EU draws closer, here are some ways to stay informed about the latest news and views about the conference, talks, venue, and city:
- all major news items will be announced here
- we are tweeting as @yapceu
- all news items will be posted on the front page of our main website
- all registered attendees should shortly be added to a mailing list for important announcements
- you can see what other attendees are discussing and join in on our wiki
- ... and if you still can't find the information you need, then Contact us!
We're very happy to announce a fantastic selection of talks: Perl in industry and the media, web frameworks new and old, new syntax, the Perl job market, and of course, the latest on Perl 6!
If you are now kicking yourself for not submitting a talk, fear not AND SUBMIT!
We are juggling the schedule at http://act.yapc.eu/ye2014/wiki?node=Schedule and will release the timetable over the next weeks. We will do our best to squeeze in some more speakers, and having extra talks really helps us plan!
- we'd love to see more talks from new speakers! (20 minute or 5 min lighting talks are best)
- (and of course we always love talks from veteran speakers)
- YAPC::EU is an inclusive conference (race, gender, sexuality, ability, faith, etc.) We're already delighted to have a good selection of talks by female speakers, for example, but We Can Do Better, so please help us by submitting a talk!
If you have submitted talks, you should have received an email from us listing which ones have been accepted. Please confirm that you will give the talk as soon as possible!
YAPC::EU is taking place from Friday, August 22nd till Sunday, August 24th in Sofia, the capital of Bulgaria.
A long-time user of Data::Dumper, here. I have seen several talks about using Data::Printer in cases when you want the output to be readable by humans, not machines. I've always meant to eventually get around to checking it out. Today was that day.
I had a huge data structure at work, nested many layers deep and full of repetition with slight variances. My job was to find out what was wrong with it. After looking at the Dumper output for about 10 minutes, I became aware that I had actually stopped looking at the Dumper output a few minutes prior and my mind had wandered somewhere else (squirrel!) So, I decided to see if Data::Printer made the job any easier.
(This blog post will serve as a document that I point to for people to read when I suggest people renaming their third-party-API modules [although not necessarily always from Net:: to WWW:: or WebService::]. I'm currently on a Questhub quest that does exactly this.)
Perl being a glue language, people write many modules to connect to third-party API services. These days, most public API services are web-based. What namespace should you pick for your module?
A lot of people still use Net:: as a namespace. For example: Net::GitHub, Net::Amazon::Glacier, Net::Backpack.
This namespace is not recommended by PAUSE module naming guideline because it's supposed to be used for modules that implement various network protocols, e.g. Net::DBus, Net::Ping, Net::DNS.
We have received two proposals for this round. Take a look and give them feedback. Your input is important for us to determine how to use the community money.
If you have a grant idea but missed this round, you can still submit a proposal now. We will review them in the Septermber round.
We managed to get Peter Rabbitson also known as ribasushi as guest speaker for our conference in October.
Peter is very famous for being the master mind and release manager for DBIx::Class, the most popular ORM in the Perl world. He also plays an important role in the Perl community and goes long ways to help people.
Getting experts to the conference isn't possible without sponsors, please check if you can support us. Every contribution will be helpful, please checkout our sponsoring page and/or contact me by email.
Please note that amount of tickets for the conference are limited, better register now and save money with early bird prices!
If you want to hear about a specific subject from Peter, please let us know and we will pass your suggestion on to him.
Some months ago i wrote how to (ab)use your database as a messagequeue in order to distribute tasks among worker-processes.
"From your code, it also looks like having more than one demon will put you at risk of processing the same jobs more than once." (Jerome Eteve)
"Abuse" is the right word. The moment you hit more than three concurrent jobs, you will see a nasty slowdown ..." (rob.kinyon)
The comments made pretty clear that this was not a good idea and I promised to clean up. (Note: it worked pretty well but only as long as you didnt upscale the system)
Here we go!
I decided to go with ZeroMQ as a messagequeue and ZMQx::Class + AnyEvent.
Processing tasks takes some time in my project (5 seconds up to 20 minutes) and are of varying priority. So I cannot have some low priority task delay incoming high priority tasks.