1. 2

    In a similar vein, I wrote something in golang to grab news articles and dump them to stdout (based on the original arc90 readability): https://github.com/bcampbell/arts/tree/master/scrapetool

    disclaimers: about the first golang I ever wrote, part of a bigger project, totally undocumented and un-idomatic and will probably make your computer explode if you run it.

    1. 3

      I’ve got a few cross-platform GUI apps I work on (eg evilpixie, a pixel-art app). My primary requirement is that stuff looks (reasonably) native on each platform.

      I’ve settled on Qt, and it’s great… but I do find it too big and overbearing for my tastes. I’d love to use libui for such things - it’s light and uses native widgets and all that, but there are still crucial bits missing for me - decent menu support, a bitmap wrapper, table widget… I’ve got high hopes for it though (and have contributed the odd patch here and there).

      1. 4

        I tried to do some pixel work in Gimp recently and found it a nightmare. Specifically managing an 8 bit palette in a nice way (editing a palette entry and having the image update accordingly, that sort of thing). I abandoned what I was doing and when I return to it I might fire up deluxe paint iv in an emulator, or PSP7 under wine.

        1. 9

          Just going to plug EvilPixie, my own dpaint-inspired pixel editor: http://evilpixie.scumways.com/

          (There’s been a load of changes since the last release - the “layers” branch is where it’s all happening right now: https://github.com/bcampbell/evilpixie/tree/layers)

          1. 1

            Looks fab, thanks! I’ll check it out

        1. 36

          I was the second developer working on TortoiseCVS, so I imagine there’s at least a few fragments of my code remaining in there after all this time :-)

          Back in the late ‘90s I was chatting at work one day with Francis, a friend & colleague of mine. We were transitioning off sourcesafe(!) and bemoaning the state of CVS clients for windows. I said “wouldn’t it be great if you could see the a files status directly in windows explorer and right-click to do CVS stuff?”. Francis came back into work the next morning and said “Done it.” And that was the very first version of TortoiseCVS, which ended up being used by embarrassingly large numbers of people.

          1. 3

            I don’t use Windows nor CVS anymore, but when I did, I used TortoiseCVS (and later TortoiseSVN), so thank you for working on such an excellent tool!

            1. 2

              Here’s a random anecdote: I work on a desktop app that shows overlays on files in Windows Explorer. TortoiseSVN shows like 6 or 10 overlay icons (I forget exactly.) But Windows only supports a max of 15 overlays. So my app’s 3 overlays fight with TortoiseSVN’s however-many to compete to show overlays. Our customers who use both can’t get all the overlay functionality. An the coup-de-grace is that the overlays that get shown are based on the ones registered in alphabetical order in the Windows registry. We added some spaces to the beginning of our keys to get to the top. Sorry!

              1. 1

                Ha! Don’t let the TortoiseSVN devs hear about that one, or they’ll be prefixing their overlays too… I can imagine that escalating quickly :-)

                1. 1

                  Another company added two spaces, so we’re at three spaces now!

              2. 2

                I prefer CLI tools, but nonetheless I am/was one of those users. Neat! Hi. :)

                1. 1

                  Thanks for making CVS a bit more bearable back in the days.

                  1. 1

                    Wow, while I haven’t used TortoiseCVS I have used many Tortoise* clients that were influenced by it!

                    Thanks so much for helping get this line of tools started!

                    1. 1

                      Fun fact: my first tech job was at a place that transitioned from SourceSafe to SVN in 2009, and only switched because they could no longer run SourceSafe on a supported OS. We used TortoiseSVN, of course.

                      Amazingly, we switched to git in 2018, and the SourceSafe guys hated it.

                      1. 3

                        TortoiseCVS is a direct result of a transition away from SourceSafe.

                        The games company where I worked at the time, we were using SourceSafe for code. Everything else was just on network drives. I wanted to extend VCS use to other stuff (ie art assets, design docs etc etc). I inquired, and discovered that SourceSafe licenses would cost 800GBP each. No way in hell the company was going to fork out that for everyone. So I suggested CVS (no svn in those days!). Despite some management objections - “How can it possibly be any good if it’s free?” - we rolled it out. And quickly decided we hated having a separate stand-alone client. Hence TortoiseCVS.

                        Fun fact: the first versions of TortoiseCVS used Tor Lillqvist’s mindblowing and then-very-recent win32 GTK+ port. And ran the GUI directly from the shell extension DLL. So when the GUI crashed (profusely often), explorer would die, killing any file windows you had open. And the desktop.

                    1. 3

                      “256 full-time staff”

                      I like how they stuck to a nice round number.

                      1. 23

                        I was appalled at the scarcity of static site generators out there. So I wrote my own: Glod, the new glod standard in static site generation.

                        1. 4
                          1. 14

                            I suspect @bcampbell was waxing ironic.

                            1. 6

                              Aaah I see… woosh

                              1. 3

                                Indeed :-)

                                Actually, the ironic bit was that I wrote it because I found Hugo too complex - I’d have to relearn it every 6 months, so Glod’s aim was to be short and stupid (well under 1000 lines of golang) - but in the process I ended up submitting a patch to Hugo too…

                              2. 1

                                I use the Clojure one.

                            1. 4

                              Oh, I remember these from my time at Just Add Monsters/Ninja Theory! We had a couple of these Xenon kits for developing Heavenly Sword (which ended up being a PS3 exclusive). I thought it was a good way to prep people before the real devkits were available - big-endian PPC chip, comparable GPU, and an early version of whatever NT Kernel + DirectX variant it ran.

                                1. 3


                                  • a webgl-based menu system for someone’s website (it’s flash time, all over again!)
                                  • a phone app to help kids track and manage/monitor their medical condition
                                  • a Zombie shooter/puzzle game in VR


                                  • finishing up my old-school retro arcade shooter game (coding is done, just setting up for online sales. I’m aiming to sell the latest version, with the previous version under GPL.)
                                  • writing a browser extension to detect and flag up sponsored content in news articles
                                  1. 1

                                    Job hunting. Not the most creative and spiritually-uplifting way to spend my time - I’d rather be coding.

                                    Need a coder? My CV/github/various project links are here: http://scumways.com

                                    1. 8

                                      I really like this list!

                                      Sometimes, you have a small problem, and you just want a small solution. Some might argue that these libraries shouldn’t be used for production because they’re too small, or not enterprise strength, or whatever. I completely disagree. I think that too much code is often a liability. Having just enough simple code to solve your problem and nothing else can be a great benefit.

                                      Shameless plug: three of my projects are on this list: Genann, TinyExpr, and Minctest.

                                      1. 1

                                        My Happyhttp code made it on there too! I’m always amazed where it pops up.

                                      1. 4

                                        Oddly enough, the N64 version was 3D. There were a couple of places where corridors crossed, at different heights. I’ve no idea why they bothered - the original 2D level layouts were great.

                                        1. 2

                                          I can see 3D rendering to ease the load on the anemic CPU, but overhauling the engine enough to be “true” 3D? That’s pretty neat!

                                          1. 3

                                            It needed to be a totally different engine in any case - the N64 had something that was starting to be a modern GPU, with a real depth-buffer rendering pipeline. In the three years between the original Doom release and the N64’s release, that kind of specialized hardware had started to be a thing. The original Doom was doing everything in software.

                                            1. 2

                                              If your primitive is triangles, drawing only scaled lines is wasting at least two vertices (xy and uv) for every column / row

                                              1. 2

                                                That’s why I thought the N64 version was really odd: why bother storing the extra coordinate for all your map data, and doing all your player movement in full 3D when 2D would be just fine (as evidenced by the original PC version)? From memory there were very very few places where corridors crossed over, so it wasn’t exactly a core gameplay enhancement…

                                          1. 3

                                            But obviously it was all a cunning ploy by @DefuseSec to obtain peoples bitcoin/paypal details ;-)

                                            1. 2

                                              $work: ongoing work on my news-collection-and-analysis set of tools. Feel a bit like a duck - not much going on above water, but underneath, paddling like the clappers ;-) The visible, above-water bit is our ongoing analysis of the media coverage of the UK election:


                                              Currently improving my tools for feeding in twitter data to the mix and analysing the twittersphere (is that really a word?). Looking forward to the election being done and dusted. Got to start thinking up how to further fund this stuff ;- )

                                              $nonwork: slowly (very slowly!) hacking away at a prototype sort of ‘shared clipboard’ kind of thing that I’ve been wanting and has been kicking around my head for a good few years now. Trying really hard to keep it pared back and simple. Hopefully have something to show over the next couple of weeks.

                                              1. 3

                                                $work: The news-analysis tool I’m working on (Steno) has yielded its first public results - an analysis of the coverage of HSBC coverage in The Telegraph, in the wake of their chief political commentator resigning. We got mentions on the BBC and in the FT, which was nice. Currently working on tools to analyse twitter traffic for the upcoming UK election. Currently hating how twitter auth is so hostile to server-based apps :-( PIN numbers? really?

                                                $home: Worked through the intricacies of OSX package bundling to get a Mac build of my retro-arcade-shooter game available for people to try out. Download links for mac and windows over on the TIGSource forums. I’d love some feedback btw (like, does it even run? ;-)

                                                1. 2

                                                  $work: More on the news-article collection & analysis tools I’m working on. Lots of golang. We’re planning to use it to analysis coverage of the upcoming UK general election. We’ve got a landing page up now for anyone interested in receiving reports on said coverage, as they happen: http://electionunspun.net/

                                                  !$work: finally started making some progress on releasing one of the games I’ve had kicking around for a while (ie 15 years or so). I even started a devlog over at Tigsource to keep me motivated. Actually, motivation isn’t the problem, it’s just finding the time to work on it.

                                                  1. 2

                                                    $work: I’m working on tools to grab UK news articles from the national papers and broadcasters (works out to around 3000-5000 articles/day) and tools to help my non-techy colleagues analyse said articles. Aim at the moment is to monitor the media coverage of the upcoming UK general election, with an eye to producing regular reports on how things are being reported. I’ll post some links when we get some results to show. The larger goal is to produce tools which can help analyse the media coverage of any particular issue or event. Development mostly in Go, at the moment. I’m starting to nibble away at the corners of some NLP techniques, but really, we’re still at the ‘stupid’ phase - lots of hand-crafted keyword rules to identify articles about various people and topics.

                                                    $home: utterly failing to make any headway in getting a game I started writing about 15 years ago out the door. It’s 95% done, so there’s only the other 95% to do :-)