Github still holds quite a lot of nines in terms of uptime. It's just that it's extra visible when something big like Github goes down.
The important part you should consider is to switch go git. I'd recommend starting to use Github, and if you find that it's down too much, look at alternatives or at hosting a solution yourself.
The initial code work was probably not even an hour from initial idea to actually having random colored strings and a test shibe. Then I spent some time tweaking the image to be better, as already mentioned.
I never felt it looked complicated. The code is not even 300 lines, and at least I feel that the abstraction is all right. I wrote the code to be flexible, and because of that, adding piping to stdout was really simple. What parts of the code do you find complicated?
The hardest part was getting the Python packaging right, haha. It was difficult to get the doge.txt file distributed in the package in a path that would work both when installed to site-packages and that would work whilst developing. I have since started doing more Python packaging for my other projects (I'm on a contribution streak, so I do a lot right now) and it's gotten a lot easier.
It's pretty easy to use. The problem is usually to create good input for it. I spent roughly an hour in GIMP just tweaking the original doge.png and trying to get good dithering for the colors.
I was afraid I wouldn't like it, but after using it for a couple of weeks I am very pleased with it. I think the island style mainly was implemented to allow for the keyboard backlight. That's a bonus for me since I work in low light from time to time. Backlight really helps then.
Also, the six rows things is no issue for me. I rarely se the extra keys anyways. The PrtSc placement perplexes me though.
Heh, cute. This means Github could probably do some automated means of informing these people that their code is insecure and would be a danger to themselves and their users. I'm not sure if they should, but it's interesting that they could.
I've been a Lenovo man for the longest time, and I am currently running a T430s. I find it to be the best balance of physical size and computing power there is to find.
It would be an interesting move from Oracle to even try. Nothing would say corporate desperation as much as trying to buy the project that sprung out when you first bought the project.
Can't use XFT fonts. Doesn't set 256 colors properly. The blinking cursor is retarded and seemingly cannot be disabled. Those are kind of dealbreakers for me.
On the plus side, it feels really snappy. Impressive speed indeed.
Exactly the same here. I really wanted to like Ember, since I liked the documentation and read a bit about how the project started and how it works on a higher level. However, since I couldn't get through the Get Started tutorial, I gave up and went into angular instead, and I haven't looked back.
I'd like to give Ember a second chance, if only so I could be the only person on the internet that has tried both angular and Ember on a deeper level, but right now I'm not sure I'd do any better should I actually try again.
I'm not sure I instantly see the use of this, but I am really impressed about the way GitHub is improving their discovery tools. Every new way opens up new possibilities for collaboration, and I love it!
That's a really bad thing in my eyes. Why teach a beginner that consistency is something that does not exist?
Also, non-english variables are an abomination! I've worked with code with some finnish variables. Not only is it harder to grok, it's actively distracting.
Awesome app! Already loving it! As others, I would gladly pay for it!
A tip for the Chrome Extension: A majority of the times I have wanted to push a link (the default) I want to push the page I am on. I suggest that you prefill the "Link title" and "Link URL" field, if possible!