elFarto

It sounds like you should probably just go the whole hog and give each user their own network namespace and bridge them to the main network. Then they can run DHCP and get their own address and do with it what they like.

Wouldn't really work for Internet accessible IPv4 addresses, but IPv6 would be fine.

I've had this with someone who I emailed (completely separate from Facebook) being recommended to me. The only logical conclusion I could come to is that Facebook was mining their emails for contacts.

NVIDIA have Linux 32-bit ARM drivers available on their download page, right next to the x86 versions.

I was slightly confused by the claim of the article saying:

"Memory mapped files are new feature in Java nio package"

They were introduced in Java 1.4, 15 years ago.

I'm not quite sure what Apple were expecting, when they have shown a clear contempt for OpenGL by leaving it at version 4.1 (while everyone else is up to 4.5, even Mesa).

But to the people saying use Vulkan for the web API, that wouldn't be a good idea. Vulkan is a very verbose low level API.

Here[1] is a sample for the most basic of renderers (renders a single triangle). That's 1,000 lines of (commented) code. It's not a good fit for web development. A far better solution would be to evolve the current WebGL API, than shoehorn Vulkan into somewhere it was never meant to be.

[1] https://github.com/SaschaWillems/Vulkan/blob/master/triangle...

There's a video[1] that has some history of the calculator in Japan that kind of mirrors this. There's a race to get the smallest and thinnest, but it ultimately ends with the calculator not being particularly good to use.

[1] https://youtu.be/1_GVkR0SITo?t=17m25s

As far as I know, there's nothing that will render them. There used to be a web based renderer, but I can't seem to find it now.

One of my favourite dark corners of Unicode is IDS, or Ideographic Description Sequence. It's allows you to describe characters that are not encoded in Unicode, but can be described by a combination of existing ones.

For example, the Chinese character for the word Biang[1] can be describe with:

⿺辶⿳穴⿲月⿱⿲幺言幺⿲長馬長刂心

[1] https://en.wikipedia.org/wiki/Biangbiang_noodles#Chinese_cha...

An actual music möbius strip: https://www.youtube.com/watch?v=3iMI_uOM_fY

I'm amazed how many people get their email address wrong. I have <firstname>.<lastname>@gmail.com, which is fine, and hardly gets any mail meant for someone else. <firstletter><lastname>@gmail.com however, is basically unusable. Funny thing is, the latter was the one I created first, but I forgot the password so had to create the other. I managed to recover it later and I'm glad I have the former.

I've been using Enpass[1] for a while now and it's great. Free desktop clients (Windows, macOS and Linux), and $10 for the mobile app. Supports a bunch of cloud services for sync.

[1] https://www.enpass.io/

What I find funny about this comment is that Hello Games' office is about 2 miles away from the former office of Lionhead Studios.

Here's the link to where he talks about AMD on that stream https://youtu.be/lThX7UovKCc?t=34m

How about:

  Iterator<String> it = names.iterator();
  while (it.hasNext())
  {
    if (it.next().startsWith("B"))
    {
      it.remove();
    }
  }

I found http://journal.stuffwithstuff.com/2011/03/19/pratt-parsers-e... really useful as well.

This page has the best implementation I've seen: http://www.daemonology.net/blog/2008-06-05-faster-utf8-strle...

It basically counts continuation bytes (which all start 10xxxxxx) and substracts, rather than trying to count characters.

Additionally, if you know how many bytes are in the string, you can remove the check for the null terminator.

Your right, I did miss it, I apologize. That'll teach me to read code so early in the morning.

Actually, that's not correct, and it's the exact same mistake I made when using that API. codePointAt returns the codepoint at index i, where i is measured in 16-bit chars, which means you could index into the middle of a surrogate pair.

The correct version is:

  for (int i = 0; i < string.length(); i = string.offsetByCodePoints(i, 1))
  {
     int codepoint = string.codePointAt(i);
  }

Java 8 seems to have acquired a codePoints() method on the CharSequence interface which seems to do the same thing.

But this just adds to the fact, proper Unicode string processing is a pain :).

I don't understand Bengali at all, but the character ৎ does have it's own Unicode codepoint (U+09CE, BENGALI LETTER KHANDA TA). It was introduced in Unicode 4.1 in 2005.