@morbiuswilters said:
I thought mercurial was better overall, although like most VCSs, it lacks good GUI tools.
I've recently discovered "SourceTree", which so far seems to be the king of Git and Mercurial GUI tools.
@morbiuswilters said:
I thought mercurial was better overall, although like most VCSs, it lacks good GUI tools.
I've recently discovered "SourceTree", which so far seems to be the king of Git and Mercurial GUI tools.
@Ben L. said:
Okay, so...
- you don't understand how to use a tool
- therefore the tool must be broken
Seriously, there's good documentation readily available. READ IT. If you don't understand how ssh works, READ THINGS ABOUT SSH OR STOP USING SSH. If you don't understand how
git remote
works, typegit help remote
. If you have a merge conflict, you did something wrong. It is not a bug with Git.Stop making these idiotic threads.
In the case of most tools, I would agree. However, I make an exception for Git. Git was just made to make your brain hurt.
Every time you expect it to do something according to accepted conventions, or according to basic understanding of the english language, it does something subtly different, or outright wrong. It then turns out that you missed some obscure parameter, some esoteric branch definition, or something equally unexpected.
Sure, that could be fixed by reading the documentation. However, there are better tools available where that is not necessary, because they simply work as expected all the time (Mercurial, SVN).
Anyone whom dislikes this interface is taking too much trouble writing each email (you really don't need any more than this for most of your emails).
Anyone whom is unable to figure it out within the first 5 minutes of using it is either a retard, or just old.
@Lorne Kates said:
Godfuckingdamnit, Gmail. I didn't want to spend my afternoon writing ANOTHER Stylish userstyle to fix your fucking stupid UI decision to fuck up things that have been working and stable since the inception of webmail interfaces!
The conservatism is strong in this one.
@joe.edwards said:
You're talking about the misuse of whom, right? eye twitch
@Lorne Kates said:
Sorry, we took Trolling off Easy Mode a while back. You're welcome to try again.
I don't really care. I just couldn't help the feeling that you must be incredibly set in your ways if you can't deal with Gmail changing their compose interface. You don't have to deal with all that useless clutter when composing an email anymore. I personally think it's quite refreshing.
Seriously, if you dislike change, don't use Google.
Use this
DIscourse is awesome! Haters gonna hate. Either way, it's better than all the other shit out there.
EDIT: Clippy was, and Pegman is, fucking awesome :D
DIscourse is awesome! Haters gonna hate. Either way, it's better than all the other shit out there.
EDIT: Clippy was, and Pegman is, fucking awesome :D
Interesting, how did you actually end up there?
I work for an American company in Japan and they're quite sane. Not hiring right now though.
The only plus I can see to the Japanese system of seniority is that you can be quite safe in your job as long as you do what you are told. At worst, you'll just have to sit it out until _you_ are the senior. Sadly, as westerner you'll probably always remain a bit of odd guy out, so I'm not certain it'll work that way.
Lastly, just one thing I wonder about, can't you write PHPDoc comments in Japanese?
@joe.edwards said:
You're talking about the misuse of whom, right? eye twitch
@Lorne Kates said:
Sorry, we took Trolling off Easy Mode a while back. You're welcome to try again.
I don't really care. I just couldn't help the feeling that you must be incredibly set in your ways if you can't deal with Gmail changing their compose interface. You don't have to deal with all that useless clutter when composing an email anymore. I personally think it's quite refreshing.
Seriously, if you dislike change, don't use Google.
Use this
Anyone whom dislikes this interface is taking too much trouble writing each email (you really don't need any more than this for most of your emails).
Anyone whom is unable to figure it out within the first 5 minutes of using it is either a retard, or just old.
@Lorne Kates said:
Godfuckingdamnit, Gmail. I didn't want to spend my afternoon writing ANOTHER Stylish userstyle to fix your fucking stupid UI decision to fuck up things that have been working and stable since the inception of webmail interfaces!
The conservatism is strong in this one.
@Matt Westwood said:
Now we don't know the details of European law from squat, we're not lawyers, but we do know how to keep the customer happy and (importantly) paying us money. If they've misinterpreted the laws, why do we care?
Because it might just be nice to actually solve the customers problem instead of blindly doing what they request? Because it feels horrible to implement features you know are going to frustrate people? Because you'd hate using the website yourself? What you saying is you don't give a shit about your customer or their success as long as they keep paying you money.
@El_Heffe said:
God Bless You. This should be tattooed onto the forehead of every programmer who touches the source code of any browser.
That would be incredibly useless, as none of them would be able to see it...
It's a network and I just poisoned one really good reference/connection.
Well, I understand you wanting to keep a good reference, but I think it's a pretty sad reference if the fact that you dislike their logo is going to matter more than the fact that you worked without issue there. I mean... It DOES look slightly ambiguous. Anyone whom cannot see that... Meh.
@leganza said:
anyways, i thought this is a real forum with decent people, but all i see here especially posting on my topic bunch of sikddies and people who have nothing to do, only bash other people without even knowing them
Oh, you got real people with real skills alright, it's just that any request here (as stated above), is going to not be taken seriously. At least, when no effort is taken towards basic punctuation and capital letters, and an explanation of the issue.
@leganza said:1 thing for the admins of this site, this kind of people right here in this topic, are the ones who ruin this forum, bunch of kids. i guess the people that call others criminal they are the real criminals :)
I'm afraid the admins are part of the problem :P
That said, if you really want people to help you find SQL vulnerabilities on your website, you should've just posted the link here, and I'm certain all kinds of vulnerabilities would be made fun of, which incidentally would also tell you what and where they were :P
@Ben L. said:
Okay, so...
- you don't understand how to use a tool
- therefore the tool must be broken
Seriously, there's good documentation readily available. READ IT. If you don't understand how ssh works, READ THINGS ABOUT SSH OR STOP USING SSH. If you don't understand how
git remote
works, typegit help remote
. If you have a merge conflict, you did something wrong. It is not a bug with Git.Stop making these idiotic threads.
In the case of most tools, I would agree. However, I make an exception for Git. Git was just made to make your brain hurt.
Every time you expect it to do something according to accepted conventions, or according to basic understanding of the english language, it does something subtly different, or outright wrong. It then turns out that you missed some obscure parameter, some esoteric branch definition, or something equally unexpected.
Sure, that could be fixed by reading the documentation. However, there are better tools available where that is not necessary, because they simply work as expected all the time (Mercurial, SVN).
@morbiuswilters said:
I thought mercurial was better overall, although like most VCSs, it lacks good GUI tools.
I've recently discovered "SourceTree", which so far seems to be the king of Git and Mercurial GUI tools.
Extracted from some code I'm working on
1 2 3 4 5 6 7 8 | function shutup(i) { var o = document.getElementById(i); if (o) o.style.display = "none"; } function shutup2(i, j) { document.getElementById(i).style.display = "none"; document.getElementById(j).style.display = "none"; } |
I just don't understand what prompts people to do these things... Can anyone think of a good reason for someone to do something like this?
Also interesting to note that the second version does not check for the existence of the element, and that the check in the first function will probably result in an exception anyway.