You can either install Amarok 1.4 directly (I use Arch, and there's a pkgbuild for it), or use one of the forks that are around. I am aware of Pana and Clementine.
Your statement reminds me of novices who avoid ?: in favor of if/else because it's 'cryptic'.
It's not about being cryptic. I use if/else and I've been cutting code for decades. if/else and ?/: do the same thing, while one is easier to read while you're scanning through lines of code (it's just English after all). That the novices can understand what's been written is a bonus.
Personally, I find that the conditional operator is easier to get meaning from, which is more important. For instance, in
foo = isBar() : bar
? isBaz() : baz
: qux
the fact that you are determining the value of foo (and only determining the value of foo) through this logic is obvious (to someone who understands the conditional).
Aside: forgive my poor formatting; it appears that/. doesn't like my pre tag:/.
You can fit the menu bar, navigation buttons, address bar and search bar or even Google toolbar (don't ask) on one horizontal section saving tons of vertical space.
Install vimperator and you don't even need those any more. I have a bar for bookmarks and the command bar at the bottom (no UI window dressing, either, but that's due to my choice of window manager). It gives me a fantastic amount of space without distractions.
You should participate in Global Game Jam. It's like what you're doing, but simultaneously with a few thousand other people. My club participated this year, and it was much fun.
If VP8 really is as good as On2 claimed, Google could save some pretty good money by serving up YouTube videos in VP8 format instead of H264. And even better, Google would not have to worry about the H.264 patent owners changing the rates or changing the rules.
I don't think Google really wants to re-encode their entire YouTube catalog in yet another codec, but V8 serves a very particular role in this picture.
Google is basically keeping ISO/IEC MPEG in check by basically stating "if you do something stupid, we'll do everything possible to use V8 to make your life harder". So we may see some PR work and posturing, and V8 will likely end up in Google Chrome as well.
Whether everyone will jump to using V8 is still questionable at this point. But having it around will keep H.264 more accessible to everyone, which is good news.
Not a lot, admittedly, but the fact of the matter is that I generally just decide that I want a list of things to do [whatever I'm actually thinking about],
Yep, you want to have everything quickly without planning and thinking long term. Chances are your code will be less easily maintainable. I simply use bash scripts for throw away code to do a job quickly. You seem to have a throw away code coder attitude.
Admittedly, I do, since quite a few of the things I write *are* throwaway. I tend to use perl/python/ruby rather than bash, though.
I don't understand your logic here at all. If anything, I'm more likely to write more documentation when I'm writing less code (to do the same thing), since I'm not all tired out from typing. It's not like once I get my fingers flowing they just keep typing on their own.
Indeed, you do not understand ! Nicely written Java code with meaningful variable names needs almost no documentation. The code self-document itself, this is the idea.
Nicely written Python code with meaningful variable names also needs almost no documentation.
Having to write less is only a minor argument, and is related to being able to spew out your thoughts quickly - it's annoying when your train of thought gets interrupted because you're too busy typing lots of boilerplate crap.
You mean your thoughts are so clear that you need to write them right away in fear of forgetting them ? This seems illogical to me. It sounds like a music jam session, of course you ain't going to stop for thinking when you are jamming. Are you jamming when you write code ?
I most certainly am.
You could use bash scripts for everything then, do you begin to get the idea ?
I would if bash didn't suck so much. The languages I use are much faster to write than bash scripts.
Also, if you were fluent at Java, you would realize that with auto-complete and modern development tools, you can write Java code just as fast. (auto-imports etc..). As a bonus, modern tools will hint you when you do something that might be stupid so, at least you get a warning.
Eclipse/NetBeans/IntelliJ won't turn my
for city in ('austin', 'atlanta', 'albuquerque'):
into
String[] cities = {"austin", "atlanta", "albuquerque"};
for (String city : cities) {
Admittedly, that's just a poor implementation of for loops, rather than boilerplating, but it still stands that I am forced to think about things that I don't wish to (or at least, in a different order than is natural for me).
I use an almost-IDE (Komodo Edit) for all of my code, so I am quite aware of (and appreciate!) the niceties of a modern editor. That's no excuse for being overly verbose (see: json vs. xml).
I find no appeal in dynamic typing. It just makes programs harder to read and debug. Have you tried Scala? With type inference, it manages to get the type-safety of static typing along with the reduced verbosity traditionally associated to dynamically typed languages.
If you merely use it as a way to avoid typing types, then yes, dynamic typing is fairly worthless.
IMO, dynamic typing is only useful in duck-typed languages, because then you have the flexibility to do all sorts of crazy shit that you can't otherwise, or even to just DRY things up a bit.
More seriously, how much time does a developer spend typing compared to what he should be spending thinking ?
Not a lot, admittedly, but the fact of the matter is that I generally just decide that I want a list of things to do [whatever I'm actually thinking about], and I don't want to have to wonder if I actually want an ArrayList, or a LinkedList.
The fact that java forces you to type more also forces you to type basic documentation as you code
I don't understand your logic here at all. If anything, I'm more likely to write more documentation when I'm writing less code (to do the same thing), since I'm not all tired out from typing. It's not like once I get my fingers flowing they just keep typing on their own.
I have never understood developers saying that a language was superior because you can write code using less key strokes using it.
Having to write less is only a minor argument, and is related to being able to spew out your thoughts quickly - it's annoying when your train of thought gets interrupted because you're too busy typing lots of boilerplate crap.
More importantly, though, is that there is much less to read. When I look at most Java code, it's difficult to quickly parse what's going on, whereas a smaller language like Python or Ruby tends to be much more easily grokkable. Note that terseness is not everything, as Perl has proven.
You know, everyone keeps complaining about all this "control" apple has on the iphone. And now, to read how they are worse than Microsoft.
First, Flash sucks for me as a user so I am thrilled it's going to die. Sorry if a few developers love it, but that's not my problem nor do I care if they have to learn new things. Thank you Apple.
The reason we're so angry is because the use of nice cross-compiling tools like PhoneGap and Appcelerator Titanium is also banned. Users should care because we're the ones making the apps.
That being said, pick up your local paper (or go to Seek - also bleh) and look at the proportion of jobs advertised these days that require Java. It's quite significant. That's the sort of thing that you should be looking at when making your decision. Sure, you'll find a few that require any of your listed languages. And sure, when these kids have finished UNI and want to work in IT (poor bastards) Java will be dead and buried, but there'll be a million and one "Legacy" systems lying around that use Java.
There will also be a shitton of "Java programmers" churned out by the current schooling system. There's more than enough competition to go around.
Still, the best steps are check the pedal, try neutral, try cutting the engine (tap tap tap, hold, or whatever it takes if it is a button), and use the brake forcefully and completely, before the pads have a chance to heat up. Assuming you have the/!right/ pedal.
Bill went on to lament that had PP played its cards right, Smalltalk would have been the language used by Sun and the language that would have ruled the Internet.
In case you haven't noticed, the language that rules the internet is not Java, but scripting languages (one of which that is growing particularly rapidly pulls quite a bit from Smalltalk).
I used to be really anal about how many windows I had open and how they were positioned, simply to avoid the problem of clutter and trying to find what window I wanted. Then I started using a Mac, with Expose, and now I have windows opened all over the place and don't care. Finding the one I want is either F8, F9 or F10 away. I don't know how I functioned without Expose, before.
You still have to visually identify which window in your Expose list you want. That's why I'm a heavy user of virtual desktops (usually have windows across at least 8 of them while I'm coding) and a tiling window manager. I understand that it's not the workflow for a great number of people, but it works really well for me (and I can't stand using a floating wm).
I'm currently a J2EE (and C, but predominately Java J2EE) programmer, familiar with Hibernate, Spring, as well as the old school EJB 2 mess.[snip]
Here's the core of the problem: The web is a horrible platform. I went from Rapid development drag and drop screen design in the late 90s to the abomination that is hand crafted JSP against shitty state based environments. Sure our applications are more scalable now, but I'm still hand crafting code to talk to a database object.
Your problem is that you're trying to rapidly develop web applications in Java. I took a fairly challenging class in web development that went through the various available tools that the Java world uses, and god, I was wishing to go back to my Django, or even just raw PHP.
Then you take a look at the GUI layer. Hand writing CSS and JSP? Really? In 2010? SHIT.
If by "hand writing CSS" you mean "using SASS and blueprint", then sure. Oh, and JSP? Yeah, the rest of us have been using good templating systems since, oh, 2005 at least.
And then you have to deal with having to redeploy your application to see simple changes OR using exploded views that don't update properly and leave you debugging a problem for 4 hours that should take 4 minutes.
When I make changes, the development server in whatever framework I'm working with automatically restarts and the changes are visible by the time I can switch desktops over to my browser. As far as actual deployment, there are several really cool tools that do things like automatically update and reload the server when you push commits to your repository. Pretty sweet.
From experience, trying to get designers to use a VCS is more trouble than it's worth. They're used to dealing with file locks, and they'd prefer to continue with what they know, rather than use this new thing that the sysadmin is trying to force on them.
Why not just create an alternate account with sudo for them? Why give them root?
Give them sudo and they can grab root whenever they want:
sudo -i
passwd
[input new password twice]
exit
That assumes that you're giving them permission to run any command using sudo (which, granted, is how most sudoers files are set up). Just allow them to use the things that you think they'll need (which doesn't include visudo or a text editor, else they can change it;) ).
Slashdot Mirror
I'm not sure if you're aware of it, but the Transitive Grace Period Public License requires releasing of source code after 12 months. It's an interesting idea that I've seen around a few places.
You can either install Amarok 1.4 directly (I use Arch, and there's a pkgbuild for it), or use one of the forks that are around. I am aware of Pana and Clementine.
Also, I appear to not be able to write ternary ifs correctly >. .
Your statement reminds me of novices who avoid ?: in favor of if/else because it's 'cryptic'.
It's not about being cryptic. I use if/else and I've been cutting code for decades. if/else and ?/: do the same thing, while one is easier to read while you're scanning through lines of code (it's just English after all). That the novices can understand what's been written is a bonus.
Personally, I find that the conditional operator is easier to get meaning from, which is more important. For instance, in
foo = isBar() : bar
? isBaz() : baz
: qux
the fact that you are determining the value of foo (and only determining the value of foo) through this logic is obvious (to someone who understands the conditional).
Aside: forgive my poor formatting; it appears that /. doesn't like my pre tag :/ .
You can fit the menu bar, navigation buttons, address bar and search bar or even Google toolbar (don't ask) on one horizontal section saving tons of vertical space.
Install vimperator and you don't even need those any more. I have a bar for bookmarks and the command bar at the bottom (no UI window dressing, either, but that's due to my choice of window manager). It gives me a fantastic amount of space without distractions.
I think he's talking about JavaScript missing critical language features. You know, things like proper namespaces, exceptions, static typing,
Wait, static typing is a "critical language feature"? What the hell are you smoking?
Now, Javascript is weakly-typed, which many people see as an issue.
You should participate in Global Game Jam. It's like what you're doing, but simultaneously with a few thousand other people. My club participated this year, and it was much fun.
If VP8 really is as good as On2 claimed, Google could save some pretty good money by serving up YouTube videos in VP8 format instead of H264. And even better, Google would not have to worry about the H.264 patent owners changing the rates or changing the rules.
I don't think Google really wants to re-encode their entire YouTube catalog in yet another codec, but V8 serves a very particular role in this picture.
Google is basically keeping ISO/IEC MPEG in check by basically stating "if you do something stupid, we'll do everything possible to use V8 to make your life harder". So we may see some PR work and posturing, and V8 will likely end up in Google Chrome as well.
Whether everyone will jump to using V8 is still questionable at this point. But having it around will keep H.264 more accessible to everyone, which is good news.
V8 is quite a different thing from VP8.
Not a lot, admittedly, but the fact of the matter is that I generally just decide that I want a list of things to do [whatever I'm actually thinking about],
Yep, you want to have everything quickly without planning and thinking long term. Chances are your code will be less easily maintainable. I simply use bash scripts for throw away code to do a job quickly. You seem to have a throw away code coder attitude.
Admittedly, I do, since quite a few of the things I write *are* throwaway. I tend to use perl/python/ruby rather than bash, though.
I don't understand your logic here at all. If anything, I'm more likely to write more documentation when I'm writing less code (to do the same thing), since I'm not all tired out from typing. It's not like once I get my fingers flowing they just keep typing on their own.
Indeed, you do not understand ! Nicely written Java code with meaningful variable names needs almost no documentation. The code self-document itself, this is the idea.
Nicely written Python code with meaningful variable names also needs almost no documentation.
Having to write less is only a minor argument, and is related to being able to spew out your thoughts quickly - it's annoying when your train of thought gets interrupted because you're too busy typing lots of boilerplate crap.
You mean your thoughts are so clear that you need to write them right away in fear of forgetting them ? This seems illogical to me. It sounds like a music jam session, of course you ain't going to stop for thinking when you are jamming. Are you jamming when you write code ?
I most certainly am.
You could use bash scripts for everything then, do you begin to get the idea ?
I would if bash didn't suck so much. The languages I use are much faster to write than bash scripts.
Also, if you were fluent at Java, you would realize that with auto-complete and modern development tools, you can write Java code just as fast. (auto-imports etc..). As a bonus, modern tools will hint you when you do something that might be stupid so, at least you get a warning.
Eclipse/NetBeans/IntelliJ won't turn my
for city in ('austin', 'atlanta', 'albuquerque'):
into
String[] cities = {"austin", "atlanta", "albuquerque"};
for (String city : cities) {
Admittedly, that's just a poor implementation of for loops, rather than boilerplating, but it still stands that I am forced to think about things that I don't wish to (or at least, in a different order than is natural for me).
I use an almost-IDE (Komodo Edit) for all of my code, so I am quite aware of (and appreciate!) the niceties of a modern editor. That's no excuse for being overly verbose (see: json vs. xml).
I find no appeal in dynamic typing. It just makes programs harder to read and debug. Have you tried Scala? With type inference, it manages to get the type-safety of static typing along with the reduced verbosity traditionally associated to dynamically typed languages.
If you merely use it as a way to avoid typing types, then yes, dynamic typing is fairly worthless.
IMO, dynamic typing is only useful in duck-typed languages, because then you have the flexibility to do all sorts of crazy shit that you can't otherwise, or even to just DRY things up a bit.
ArrayList myList = new ArrayList();
More seriously, how much time does a developer spend typing compared to what he should be spending thinking ?
Not a lot, admittedly, but the fact of the matter is that I generally just decide that I want a list of things to do [whatever I'm actually thinking about], and I don't want to have to wonder if I actually want an ArrayList, or a LinkedList.
The fact that java forces you to type more also forces you to type basic documentation as you code
I don't understand your logic here at all. If anything, I'm more likely to write more documentation when I'm writing less code (to do the same thing), since I'm not all tired out from typing. It's not like once I get my fingers flowing they just keep typing on their own.
I have never understood developers saying that a language was superior because you can write code using less key strokes using it.
Having to write less is only a minor argument, and is related to being able to spew out your thoughts quickly - it's annoying when your train of thought gets interrupted because you're too busy typing lots of boilerplate crap.
More importantly, though, is that there is much less to read. When I look at most Java code, it's difficult to quickly parse what's going on, whereas a smaller language like Python or Ruby tends to be much more easily grokkable. Note that terseness is not everything, as Perl has proven.
You know, everyone keeps complaining about all this "control" apple has on the iphone. And now, to read how they are worse than Microsoft.
First, Flash sucks for me as a user so I am thrilled it's going to die. Sorry if a few developers love it, but that's not my problem nor do I care if they have to learn new things. Thank you Apple.
The reason we're so angry is because the use of nice cross-compiling tools like PhoneGap and Appcelerator Titanium is also banned. Users should care because we're the ones making the apps.
There already is, run FreeBSD. After all something can't crash that isn't available.
I'd think it'd be easier to just uninstall Flash on his current system...
Please, for the love of God, somebody come along and write a test suite for my project. I'm sick of breaking code by accident! ;)
That's the real advantage of TDD - it forces you to write a good test suite.
That being said, pick up your local paper (or go to Seek - also bleh) and look at the proportion of jobs advertised these days that require Java. It's quite significant. That's the sort of thing that you should be looking at when making your decision. Sure, you'll find a few that require any of your listed languages. And sure, when these kids have finished UNI and want to work in IT (poor bastards) Java will be dead and buried, but there'll be a million and one "Legacy" systems lying around that use Java.
There will also be a shitton of "Java programmers" churned out by the current schooling system. There's more than enough competition to go around.
For Python, can they use: Psyco as a library? That would help being practically a Just In Time compiler.
Or they could use the recent release of Pypy. I haven't used it myself, but the benchmarks look appealing.
Still, the best steps are check the pedal, try neutral, try cutting the engine (tap tap tap, hold, or whatever it takes if it is a button), and use the brake forcefully and completely, before the pads have a chance to heat up. Assuming you have the /!right/ pedal.
Why would I want to tap hard on the wrong pedal?
Speak for yourself. Some of us like the mouse and window for code editing.
I use a laptop for a significant portion of my coding (as I would guess many people do), and going from my vi-keybinded Komodo to Eclipse is painful.
Trackpads have made me appreciate keyboard-controlled window managers, vimperator, and the aforementioned editor so much more.
Bill went on to lament that had PP played its cards right, Smalltalk would have been the language used by Sun and the language that would have ruled the Internet.
In case you haven't noticed, the language that rules the internet is not Java, but scripting languages (one of which that is growing particularly rapidly pulls quite a bit from Smalltalk).
I used to be really anal about how many windows I had open and how they were positioned, simply to avoid the problem of clutter and trying to find what window I wanted. Then I started using a Mac, with Expose, and now I have windows opened all over the place and don't care. Finding the one I want is either F8, F9 or F10 away. I don't know how I functioned without Expose, before.
You still have to visually identify which window in your Expose list you want. That's why I'm a heavy user of virtual desktops (usually have windows across at least 8 of them while I'm coding) and a tiling window manager. I understand that it's not the workflow for a great number of people, but it works really well for me (and I can't stand using a floating wm).
You are assuming that whoever wants to break the encryption is doing a brute force attack.
Well, yes, because he was responding to:
You don't think someone, given enough time, would be able to brute-force your password?
I'm currently a J2EE (and C, but predominately Java J2EE) programmer, familiar with Hibernate, Spring, as well as the old school EJB 2 mess.[snip]
Here's the core of the problem: The web is a horrible platform. I went from Rapid development drag and drop screen design in the late 90s to the abomination that is hand crafted JSP against shitty state based environments. Sure our applications are more scalable now, but I'm still hand crafting code to talk to a database object.
Your problem is that you're trying to rapidly develop web applications in Java. I took a fairly challenging class in web development that went through the various available tools that the Java world uses, and god, I was wishing to go back to my Django, or even just raw PHP.
Then you take a look at the GUI layer. Hand writing CSS and JSP? Really? In 2010? SHIT.
If by "hand writing CSS" you mean "using SASS and blueprint", then sure. Oh, and JSP? Yeah, the rest of us have been using good templating systems since, oh, 2005 at least.
And then you have to deal with having to redeploy your application to see simple changes OR using exploded views that don't update properly and leave you debugging a problem for 4 hours that should take 4 minutes.
When I make changes, the development server in whatever framework I'm working with automatically restarts and the changes are visible by the time I can switch desktops over to my browser. As far as actual deployment, there are several really cool tools that do things like automatically update and reload the server when you push commits to your repository. Pretty sweet.
And why not use revision control?
From experience, trying to get designers to use a VCS is more trouble than it's worth. They're used to dealing with file locks, and they'd prefer to continue with what they know, rather than use this new thing that the sysadmin is trying to force on them.
Why not just create an alternate account with sudo for them? Why give them root?
Give them sudo and they can grab root whenever they want: sudo -i passwd [input new password twice] exit
That assumes that you're giving them permission to run any command using sudo (which, granted, is how most sudoers files are set up). Just allow them to use the things that you think they'll need (which doesn't include visudo or a text editor, else they can change it ;) ).
Heck, America doesn't protect it's whistle blowers. Why should Latvia?
Because they know the difference between its and it's.