4,371 karma · joined November 16, 2013
Given the NZ flag's Union Jack and very close resemblance to the Australian flag I can understand why people don't feel too strongly about the current state of affairs. There's nothing evocative, nothing that feels distinctive to NZ. How many NZ flags do you see being waved at sporting events compared to silver ferns and the like? Almost none. Based on that alone I think it's high time we shrugged off the flag's colonial roots and changed it to something that's uniquely NZ. It might take a while for people to adjust to the change (after all, people generally don't like change), but in the long run people will support it just because it's truly ours.
[1] https://www.techdirt.com/articles/20150702/00134231524/david...
This isn't the point though. A general purpose programming language shouldn't impose arbitrary restrictions on data structures like this. Even if such a restriction was in place it would have to be enforced at runtime which doesn't sound like a trivial problem from a performance point of view.
http://metaist.com/blog/2010/02/disease-screening-base-rate-...
[1] https://play.google.com/store/apps/details?id=com.mrnumber.b...
Centralia on Google Maps: https://www.google.com/maps/@40.8006547,-76.3428604,287m/dat...
I spent many hours trying to write games in gw-basic but quickly realised that the performance was atrocious, to say the least. Eventually I stumbled across a magazine that had a two-page article about debug.exe and it was my gateway to a whole new hidden world. I went on to learn 8086 assembly with debug.exe by trial and error and from stepping through other programs. Eventually I figured out I could write little 8086 assembly routines in debug.exe myself, take the sequence of bytes that made up that routine, declare them as a DATA statement in a BASIC program and then just make call that DATA line to run the machine code directly [2]. It wasn't until many months later I finally managed to get my hands on some compilers and assemblers (Borland Turbo Pascal and Turbo Assembler being my favourites back then) which of course made my life a whole lot easier! I continued to use debug.exe for many years though, primarily for reverse engineering.
I've just managed to dig up an obfuscated "Hello World" batch file I wrote many years ago that makes use of debug.exe, see [3] below (If you actually want to run it you'll probably need an MS-DOS emulator [4][5] or an older version of Windows that still has debug.exe).
[1] http://en.wikipedia.org/wiki/GW-BASIC
[2] http://www.antonis.de/qbebooks/gwbasman/appendix%20d.html
[3] http://www.redyeti.net/extra/hello.bat
I built this without giving much thought to whether anyone else had attempted something similar. Presumably they had though I do remember being disappointed when researching the various open source caching libraries, they didn't offer much help at the time. Overall I was pretty happy with the way it all worked and the performance boost it provided was like night and day.
Sadly the company is no longer operating, presumably the CMS codebase is long lost.
> It's just a swipe down or a swipe up.
That's why I prefer a widget (or lockscreen), there's no swiping required at all. As for getting push notifications for the subway... No thanks, I don't want a notification every time some subway line is running a little slow. I only want notifications for events I care about, with few or no false-positives.
Given the way the Android community has picked up on these sorts of things in the past, I wouldn't be too surprised if someone creates a launcher that implements this relatively soon.
- Weather info. Before heading out for the day I can see instantly if I might need a jacket or umbrella later.
- Tube status. I can see at a glance if there are any problems on any underground lines. If there are, I can click on the problem line to get more detailed information with a single touch.
- Calendar. Shows me my schedule for the day.
- Music. Control playback without having to launch an app.
I also have widgets I tend to only use when I'm travelling, showing currency and timezone information.
[edit: on the plus side, Flickr make it very easy to delete your account entirely. The only obvious side effect is that the screen name you had is now unavailable for any further users]
1) High level languages are easier to refactor and maintain than lower level languages (changing the algorithm in the assembly's a big job).
2) For performance, the algorithm used is almost always more important than the language you choose to implement it in.
Both of those points back up the author's assertion, it's a shame he didn't specifically discuss them.
I used to hand-code assembly (or generate it, eg "compiled bitmaps") back in the 8086 days. For many situations there were easy gains to be had that couldn't be achieved so easily in high level languages. These days I wouldn't dream of attempting it other than perhaps for vector code in an inner loop. I'd far rather spend the time profiling and optimising the algorithms and data structures because that's where the big gains are going to be. To go ahead and implement something in assembly when the algorithm clearly isn't yet optimal is perhaps fun but also kinda insane.
Interestingly, there is some redundancy with this encoding meaning you can't represent a full 2^12 unique values. Eg 0x1 could be represented by 0x1 and 0x0 in the rotate field, 0x4 with 0x1 in the rotate field, 0x10 with 0x2, or 0x40 with 0x3. The same applies for every other combination - this means that there are only (2^12)/4 = 1024 unique values that are representable in total.