apk17

> Well, to nitpick, the reason anyone becomes professional is to make money, kind of by definition.

The definition only includes the making money part, not the reason. Many people do take money for what they do simply so they can do it full time.

Mine is called cdx and includes 'env' functionality and a bit more. (https://github.com/apk/c-utils/blob/master/aenv.c)

I still wonder why `cd` doesn't have a form `cd dir command...`, as in `cd dir tar xf -`.

In this day and age it's not that fun anymore. You need to prepare what to do when there is a lot less snow around.

'mesh network' popped up here exactly because we want to avoid the fat links in that mesh.

And getting substantial data (including transit) routed through a heap of wifi devices in a city isn't easy. To the next city - hard. Over the big pond - well...

Disabling 3rd party cookies breaks functionality, e.g. tweetdeck.

They could tell local authorities; this usually gets things done.

Unless, of cource, $activity isn't even illegal in that other country.

> This is not about the government ... "removing news articles that are politically unacceptable".

That's actually part of the problem. The government should close down illegal establishments, and not just be blocking access to them.

The other part of the problem: Once the gov can tell the ISPs what to block (a) the block list must be secret and (b) the process can be very easily abused, with 'overblocking' being the standard excuse.

I doubt that. With 6502 you have so much byte fiddling to do; x86 (or 6809) is much easier once you need more than 8 bit pointers.

(I probably still have a turing-complete set of Z80 opcodes in my head.)

Correct - but the starting point here was already 'take this path', not 'go to that location on the grass'.

Come to think about it - even 'just park somewhere' is remarkably complicated. I don't quite understand why self-driving cars should need external high quality maps and can't make do with onboard cameras as human drivers do.

But then the parking requires either a high-quality database of valid and off-limits parking locations, or the ability of the car to read the signs on parking lots and generally be able to distinguish private from public parking.

I doubt that. Cars are, besides being a transportation means, also a moving trunk, and that makes them non-interchangable to a degree.

Not that people actually driving cars off the road are capable of this now. I'd often wish for a remote control when parking in constricted spaces.

Depending on the context, 'turn the wheel left two degrees' can be a non-rampant, a very rampant, or a rampage-compensating action.

The last two sentences seem contradictory. If the system cannot detect by itself when it is safe to be used, the driver will as well have to react when it becomes unsafe to use?

Ruby takes the seed for rand() from /dev/urandom, according to doc. That's good enough for a single use.

ruby -e 'rand(34*10).to_s(34)'

I prefer not to have to use the shift key in passwords, and the 34 instead of 36 ([0-9a-z]) solves my german/us layout problem in a very golfy way.

You make the modifications and store those hashes as well.

Can't have a new 'similar' algo for past pws, obviously.

The blue light were brighter - they have a mechanism different from the old LEDs that is much more efficient. I guess the designers just dropped in the blue leds, and voilá, terrible bright lights.

The other colors later followed suit - the brightness you now get with a few mA is amazing when you know the old LEDs.

I wish. Flashlights tend to have all sorts of strange UIs, just like television firmware are just exploring the possible ways of being annoying.

None of mine have both a way of getting full power fast /and/ deterministically turning it on on the lowest setting.

(Except for the one that only has 'very bright' and where I first wondered why there is no rebound when I turn it on.)

I don't understand the general use of PWM anyway - you want to use switching regulators anyway, and it is actually slightly easier to do (almost) constant current than PWM.

And PWM lighting is annoying in a lot of ways.

> It's so naturally a two-case problem that I'd be really surprised if anyone came up with the one-case answer first.

[Raises hand] I always did it Linus' way in C (way before him); I don't remember if I ever had the need in assembly before.

'cleverness for its own sake' often makes it into standard practice later.

And I seriously fail to see the 'for its own sake' here. This cleverness reduces the number of moving parts, does the 'dont repeat yourself' and thus reduces ways modifications of the code could break it due to overseeing a case.

I just shuddered to think how this would be done in java - with a LinkUpdater interface, and a RootLinkUpdater and ElementLinkUpdater, and one instantiation per iteration, and suddenly we have a lot of code around to keep the active code's function simple - to a point where it is completely pointless because of adding a lot of machinery. (And java does collections differently anyway.)

In the original pascal pointers/refs came only out of new (AFAIR), you couldn't point into structures or to local variables. That makes this trick impossible.

'Modern' 'pascals' were different.

Actually, I find the double pointer version easier to understand, and incidentally it is also the way always wrote this in C. And I pitied the pascal programmers who had to use the original version.

'Simplify so a fool can understand your code, and you will have fools editing it.'

Even 'dumb pipes' aren't equivalent. Here it's either IPv4 only (telekom.de), CG NAT IPv4 plus IPv6 (Kabel), or the small ISP I'm with (/28 static IPv4, /48 IPv6).

Since 9/11 the US already states very explicitly that it doesn't want me as a visitor - I'm not going to go through the (visa) hoops they hold up to me.

It was actually administratively much easier to cross the iron curtain in the form of the berlin wall back then than it is now to get into the US (me being german).

(This is a bit unfair because there were special regulations for germans inside berlin, and US visas weren't that easy back then either.)

According to a journalist who gave a talk here (Stuttgart, Germany) last week, there is a speed radar and license plate scanner at the local NSA installation, and going by too slow gets you on the 'suspicious people' list.

In mine, not quite. All forms of merges are simple: resolve, add, commit. Inside a rebase I find it harder to memorize whether I need to to the add and/or commit or rebase --continue does it for me.

And conflicts from 'stash pop' are somewhat counterintuitive to handle.

...and having commits that are not referenced by any branch.

And (c) lose the entire subtree the repo is in.

Yes, git-svn is probably the reason why the mutiny didn't happen yet in some departments. You can identify their users by having several SVN commits in as many seconds.

(I used git in an cvs-to-svn migration, and stayed since.)