setq

I can use all of those today or develop a new implementation if I want.

He who controls the spice....

Vendors come and go. Standards don't.

Isn't this the same principle google uses for their location services?

This sums it up nicely.

Also, if it's easy and you've done it a million times, charge an inflated fixed price. If it's new territory, charge by the hour.

Edit: before I forget, if you let them know how it's done then you need to charge for the several times they won't come back again afterwards.

One doesn't win a game of chess by moving all the pieces at the same time.

Excellent. Downloading now :)

I ran NetBSD and OpenBSD on old sun kit in the late 1990s and early 2000's followed by Debian and then CentOS. FreeBSD got a look in persistently on the side. I'd rather like a step back to the sensibility of times past when you chucked something out and it just did its job until something blew up :)

This is interesting and lines up with the time zone offset on my last rant a couple of years back. Peak in upvotes UK afternoon followed by downvote pummelling at around 4pm UK time. Without wishing to don the tinfoil hat too much, actively squashing critical discussion on your product is a dick move if it's true.

This has got so bad on some parts of reddit they removed the voting buttons.

Interesting. I haven't used slackware for many years, so far back in fact that it had to come on CDs because I had a dial up. Will take a look in that direction this evening.

That's really interesting actually. In the distant past I spent more time sorting the cards than playing the game so there is probably a good trade off on automating it.

I went and bought a duel deck the other day to play with the wife so this is going to become another issue in the future again.

Well no not really. Vulnerabilities exist outside the realms of the language implementations. There are poorly designed protocols and access controls to contend with as well. I'd argue there are a lot more of those classes of problems out there. The ones enabled by programming languages are merely easier to find as you don't have to understand the precise problem domain of the application for each one found.

It's not. There's a content about 11 screens down, not that you'd find it easily.

This is why we need standards and APIs which are immutable. It doesn't matter what the implementation is then.

The whole of systemd is a comedic fuck you to POSIX and the mentality of a system which is standardised.

I apologise. This is the first time I've criticised systemd on HN. I had a massive rant on another site a couple of years ago when CentOS 7 dropped about the catalogue of failures I had been through with systemd, completely backed up with evidence and bug reports and it was hammered by downvotes instantly.