I guess you aren't seeing what I'm seeing, but then again, you probably aren't even looking at it. I haven't seen this number of job reqs, contracts, and new work in some time. Perl is having a renaissance, and I'm loving every minute of it.
And this is why there is a big push back to Perl for new development. It's fast, proven, plenty of tricks for speed, and a very fast database framework. Even with DBIx::Class on top of it, it's insanely fast.
If you haven't looked at Perl in a while, now's the time. Between Moose and Catalyst, developing in Perl is fun again.
I'm on a Lenovo ThinkPad X61 Tablet. As far as I can tell, they are still being sold, and it's a standard 12.1" display on the Tablet and the standard model.
From what I understand, Opera Mini's servers deliver a package containing the html and other viewable content in one compressed bundle. All the well-designed name resolvers and browsers can't help the fact that latency generally sucks on low-power mobile networks, EDGE and below. The fewer requests you have to make (resolve > request > deliver), the better your experience will be.
You'll have everything you need. You may want to consider PC-BSD, a.. friendlier edition of FreeBSD. It uses KDE by default, and as you're a Fluxbox user, you'll know how to swap that out as needed.
The only gotcha is that nVidia's binary drivers are just as finicky as in Linux, and you're SOL if you want to use the amd64 version of FreeBSD, unless I'm out of touch. You can find their binary driver here.
Articles like this really annoy me. There are indeed tools best suited for each job. Most people are not going to write an end user application with a GUI in Perl, because it's just not normally suited for it. Needless to say, with wxPerl, I've done it. Fancy that, it's readable, too. But, I'm aware it's not good for that.
What people tend to forget is how extensible a language can be, especially Perl. Blanket statements like "Perl should not be used for the web" is misinformed at best. No one wrote web scripts in Ruby before Rails -- it's all about the framework. Go give the Catalyst framework a try, and tell me again not to use Perl for the web.
As for high performance computing, remember that the perl interpreter does a few things very well, very fast. We ended up rewriting our web crawling infrastructure at $WORK from Nutch and Lucene in Java to a custom distributed Perl architecture against Xapian. Not only is it much more 'pluggable' than the original solution, we ended up getting a huge increase in speed out of the deal, even putting it up against 64-bit Java. It's anecdotal, and mileage will vary, but there are times that Perl is just better at crunching text than anything else.
Too many people write off Perl as a relic of the past. What people fail to see is the new Perl renaissance that is quickly approaching. It's a good time to be a Perl developer, judging by the job market.:)
I think Linux needs better power management before I can consider it for an ultra portable. Ubuntu Gutsy ran great on my Vaio TZ, except for the fact that my battery life went from 6 hours to 3, even after shutting off the cd drive, lowering lcd brightness, and turning on SpeedStep.
So close, but so far away. Even hackintosh did better with power.
It is easy to work with, and it doesn't stop me from using it. As I said, we have a few tens of servers, and they're all running Ubuntu Server Edgy or Feisty. But, if you compare what Ubuntu Server provides, compared to FreeBSD, CentOS, or Windows Server, it comes up very short. If you're using it on 2-3 machines, it's no big deal.
As a user of Ubuntu Server on a 60+ machine deployment for $work, Canonical is seriously going to have to take the server distro up a notch before this could possibly work. The server distro, in stark contrast to Desktop, is a horribly hacked together mess that gives off the impression that it isn't really studied much at all. While Desktop shows the best and brightest of Linux integration, the server distro is just as barebones as the alternative distro, and manages to screw things up in terms of out of box experience.
Am I looking for a UI? No. I want a few basic things.
1: A proper, usable deployment system. debian-installer is good for the basics, but it's a pain in the behind to set up, and doesn't support scripting a RAID/mdadm install, or LVM. This "sucks". Take a look at Redhat or CentOS for a little inspiration. 2: A boot screen that doesn't look like vomited output. Why does the login prompt appear before services have finished loading? I support being able to use the machine before services have stopped. I do not need "Starting PostgreSQL" appearing as I'm entering my login credentials locally. 3: A server kernel that always installs. Why does the installer give me the generic kernel when I'm installing the server distro? Why do I have to manually install the server kernel on boot up, and then remove the generic kernel? 4: Easily add services. You get 'LAMP server' or 'DNS server' or nothing. I had to create a custom installer just to have openssh-server install by default on first load, without apache or MySQL, or other crap floating around in there as well.
It sounds whiny, I know, but we really like the debian-style package management system with the modern services Ubuntu provides. It's great for that purpose. As a real server distro, though, long way to go yet.
I hope this lights that fire under Canonical to pay some attention to Server.
There's a tad of a failure in logic there. There are high profile sites written in Lasso as well, but that doesn't make it a serious tool, it just makes it a functional tool. PHP was designed to create pages with logic very easily, and it's being bent in a lot of ways now, which is cool in a way, but there's really no reason why anyone should work that freakin hard. At this point, creating an AJAX enabled site is far easier, and still scalable for a competent admin, with Java, or Perl with Catalyst, or Ruby with Rails.
The scheduler on FreeBSD never locks me out of the system, never takes down the kernel under high load, and always gives me a chance to save a system without hard powering it. I'm using mostly Linux here at work now, of both Debian and Red Hat varieties, and I can't say the same for it at all. If given the choice, I would move everything here to FreeBSD for just the scheduler.
I'm also ticked that I am now Flamebait, but I guess it makes sense.
Most people choose the iPod for that. Kinda like how the Zune locks you into the Zune store. You could get a WM player, which allows you access to... a lot of stores with the same pricing and content. *twirls finger* It's all about making it easy.
Some people like iTunes better.:) The linux players are getting quite good, but iTunes has spit and polish that can't be touched by any of them, especially AmaroK.
Depending on your view of the GPL in general. Each iteration of the GPL seems to further limit the use of the source and binaries that it covers, so in many ways, it is 'restricting'.
Slashdot Mirror
Mason makes me want to cry. :)
I guess you aren't seeing what I'm seeing, but then again, you probably aren't even looking at it. I haven't seen this number of job reqs, contracts, and new work in some time. Perl is having a renaissance, and I'm loving every minute of it.
And this is why there is a big push back to Perl for new development. It's fast, proven, plenty of tricks for speed, and a very fast database framework. Even with DBIx::Class on top of it, it's insanely fast.
If you haven't looked at Perl in a while, now's the time. Between Moose and Catalyst, developing in Perl is fun again.
I'm on a Lenovo ThinkPad X61 Tablet. As far as I can tell, they are still being sold, and it's a standard 12.1" display on the Tablet and the standard model.
Just what I wanted, an operating system with no devices and no users! Can it play ogg vorbis too?
From what I understand, Opera Mini's servers deliver a package containing the html and other viewable content in one compressed bundle. All the well-designed name resolvers and browsers can't help the fact that latency generally sucks on low-power mobile networks, EDGE and below. The fewer requests you have to make (resolve > request > deliver), the better your experience will be.
You'll have everything you need. You may want to consider PC-BSD, a.. friendlier edition of FreeBSD. It uses KDE by default, and as you're a Fluxbox user, you'll know how to swap that out as needed.
The only gotcha is that nVidia's binary drivers are just as finicky as in Linux, and you're SOL if you want to use the amd64 version of FreeBSD, unless I'm out of touch. You can find their binary driver here.
Articles like this really annoy me. There are indeed tools best suited for each job. Most people are not going to write an end user application with a GUI in Perl, because it's just not normally suited for it. Needless to say, with wxPerl, I've done it. Fancy that, it's readable, too. But, I'm aware it's not good for that.
:)
What people tend to forget is how extensible a language can be, especially Perl. Blanket statements like "Perl should not be used for the web" is misinformed at best. No one wrote web scripts in Ruby before Rails -- it's all about the framework. Go give the Catalyst framework a try, and tell me again not to use Perl for the web.
As for high performance computing, remember that the perl interpreter does a few things very well, very fast. We ended up rewriting our web crawling infrastructure at $WORK from Nutch and Lucene in Java to a custom distributed Perl architecture against Xapian. Not only is it much more 'pluggable' than the original solution, we ended up getting a huge increase in speed out of the deal, even putting it up against 64-bit Java. It's anecdotal, and mileage will vary, but there are times that Perl is just better at crunching text than anything else.
Too many people write off Perl as a relic of the past. What people fail to see is the new Perl renaissance that is quickly approaching. It's a good time to be a Perl developer, judging by the job market.
Except that the query has to be made on the web site, and you also did the program with more code. To each their own.
I think Linux needs better power management before I can consider it for an ultra portable. Ubuntu Gutsy ran great on my Vaio TZ, except for the fact that my battery life went from 6 hours to 3, even after shutting off the cd drive, lowering lcd brightness, and turning on SpeedStep.
So close, but so far away. Even hackintosh did better with power.
Reliability in numbers. If you have 30 machines running your website, no one will notice if one goes down.
Yes, because then I wouldn't need a driver just to use a drive.
You can finally script md in feisty and gutsy, but it's broken -- doesn't work most of the time, and completely fuzzes over if anything changes.
It is easy to work with, and it doesn't stop me from using it. As I said, we have a few tens of servers, and they're all running Ubuntu Server Edgy or Feisty. But, if you compare what Ubuntu Server provides, compared to FreeBSD, CentOS, or Windows Server, it comes up very short. If you're using it on 2-3 machines, it's no big deal.
As a user of Ubuntu Server on a 60+ machine deployment for $work, Canonical is seriously going to have to take the server distro up a notch before this could possibly work. The server distro, in stark contrast to Desktop, is a horribly hacked together mess that gives off the impression that it isn't really studied much at all. While Desktop shows the best and brightest of Linux integration, the server distro is just as barebones as the alternative distro, and manages to screw things up in terms of out of box experience.
Am I looking for a UI? No. I want a few basic things.
1: A proper, usable deployment system. debian-installer is good for the basics, but it's a pain in the behind to set up, and doesn't support scripting a RAID/mdadm install, or LVM. This "sucks". Take a look at Redhat or CentOS for a little inspiration.
2: A boot screen that doesn't look like vomited output. Why does the login prompt appear before services have finished loading? I support being able to use the machine before services have stopped. I do not need "Starting PostgreSQL" appearing as I'm entering my login credentials locally.
3: A server kernel that always installs. Why does the installer give me the generic kernel when I'm installing the server distro? Why do I have to manually install the server kernel on boot up, and then remove the generic kernel?
4: Easily add services. You get 'LAMP server' or 'DNS server' or nothing. I had to create a custom installer just to have openssh-server install by default on first load, without apache or MySQL, or other crap floating around in there as well.
It sounds whiny, I know, but we really like the debian-style package management system with the modern services Ubuntu provides. It's great for that purpose. As a real server distro, though, long way to go yet.
I hope this lights that fire under Canonical to pay some attention to Server.
I think it's really cute that you believe that's the case.
So what did you encode with? Ogg or WMA?
There's a tad of a failure in logic there. There are high profile sites written in Lasso as well, but that doesn't make it a serious tool, it just makes it a functional tool. PHP was designed to create pages with logic very easily, and it's being bent in a lot of ways now, which is cool in a way, but there's really no reason why anyone should work that freakin hard. At this point, creating an AJAX enabled site is far easier, and still scalable for a competent admin, with Java, or Perl with Catalyst, or Ruby with Rails.
You do have an excellent point.
PHP is what kids write My First Sites with. Sorry, next.
The scheduler on FreeBSD never locks me out of the system, never takes down the kernel under high load, and always gives me a chance to save a system without hard powering it. I'm using mostly Linux here at work now, of both Debian and Red Hat varieties, and I can't say the same for it at all. If given the choice, I would move everything here to FreeBSD for just the scheduler.
I'm also ticked that I am now Flamebait, but I guess it makes sense.
The solution there would be 'FreeBSD'. :)
*eyeroll*
Most people choose the iPod for that. Kinda like how the Zune locks you into the Zune store. You could get a WM player, which allows you access to... a lot of stores with the same pricing and content. *twirls finger* It's all about making it easy.
Hoser.
Some people like iTunes better. :) The linux players are getting quite good, but iTunes has spit and polish that can't be touched by any of them, especially AmaroK.
Depending on your view of the GPL in general. Each iteration of the GPL seems to further limit the use of the source and binaries that it covers, so in many ways, it is 'restricting'.