wyufro

Even if you go with one IPv4 per household + 1 per company you're going to be hard stretched to find room for that in 32 bits, at least after you add the routing infrastructure.

That's very elitist and unfair to people who previously struggled to form their words but now have a better chance at doing so.

It doesn't pass the file contents at all, it passes the file path.

I think "oh this looks like it could be made generic" is the wrong time to convert to generics.

You should convert when you reach the point "I wish I had that code but with this other type". Even then, sometimes interfaces are the right answer, rather than generics.

Only if the salt is kept secret. There also needs to be a different salt value per ip, obviously. But given those conditions, it works.

Of course, it would be just as simple to use the salt as-is, in that case, since you have to look it up anyway.

IMO, while their use cases do overlap, LXC is more geared towards a user installing things while Docker is more geared towards a developer creating a ready to use package.

LXC creates environments, while Docker creates apps, is another way to say it.

In languages with closures it would be easy to set a variable to the lambda while that same variable is also captured by the lambda. In fact, this seems to happen once in a while in Go, since closures are always lambdas.

I believe you're thinking of the AppleDouble files with name ._file. Those haven't really been used for the past 10 years or so (unless you run software older than that, obviously).

Indeed, direnv and asdf integrates, such that PATH is set to the values exposed by your .tool-config. This avoids the asdf shim and makes executing the tools slightly faster. Good when you have to run them over and over in a script.

Before I learnt what it really means I always imagined it as a blowtorch heating things up, which sort of fits the original but obviously has a much wider scope. So maybe GP has the same idea I had.

Right. Neither am I, so take this with a grain of salt. But I'd use "committee decision" in this case.

It was using IPv6 in IP, just like 6to4, protocol 41.

I haven't heard it called a political issue before though. It just had problems, like being blocked in firewalls and security problems where the encapsulated packet wasn't checked properly, etc.

What, no. It's not GNU/Linux if there's no GNU software present.

Hasn't there always been a 10 user limit? That's what I remember at least.

A string, ISO 8601, https://en.wikipedia.org/wiki/ISO_8601 Preferably RFC3339 (which is a specific profile of ISO 8601) but, as noted in a sibling comment, it isn't always appropriate for future dates.

Ubuntu supports Google Drive out of the box, it appears in the file manager. Probably it's Gnome doing the actual work, I haven't really bothered to learn it well.

Coffee cups as measured on the brewing machine is only about half that size.

OTOH, the researcher says 1-2 cups is the normal amount in the article. To me that implies a larger cup size.

I wrote an Entity-Container system that really could've benefitted from a generic Get function. Instead I had to write on for each entity-type, even though they were the same except for different types.

Most places where the empty's interface is used now could benefit from it. Eg. the json package could state it always uses float64 for numbers (except when you tell it to use Number).

Dystopian Sci-Fi being anti-capitalist? Wow, what a crazy idea.

As someone who doesn't know Rust yet I feel there's a "do this instead" missing to point 8. It's not clear to me how to do it instead.

In my experience the hardest part of using parser generators is to have them create understandable errors.

Also it's questionable that they add very much. Parsing text isn't all that difficult. The hard part is to get the tree structure of the AST right.

All in all the parsing is a quite small part of a compiler. I've converted from a parser generated to manual code in two different projects and they actually ended up with less lines of code after the conversion, if just barely.

Primarily disk access is a lot slower, even with Hyper-V. Eg. Compilation suffers from this. But tasks that don't use the disk too much shouldn't be that bad.

MacPorts is sponsored by Apple, or at least used to be.

Just that the prompt automatically goes on a new line makes iTerm2 so nice though. As well as the built in timing of commands, jump to previous prompt, double click selects matching parentheses, etc. it's those little details.

I'm speculating, but sizeof(bool) == 1, sizeof(struct{}) == 0 and sizeof(interface{}) == 8, so might be as simple as that.

https://play.golang.org/p/5acy87JLD3i

And Finland is in UTC+2. The thing regulated is probably when DST starts and stops, not the timezones.

I think the key thing that makes my microwave easier to use is that it has a big dial to choose the function. No clicking through menus, you just turn the dial to the function you want, then the second dial to adjust the settings, or press start to start and add time.

He really should've told near the end. Anyway, I assume you press the power button, because that is the established standard for microwaves in the last 10 years or so. Probably there might be a timeout and then it starts automatically.

This is indeed something you have to learn though, first time I encountered this kind of microwave it baffled me as well.

I really feel it doesn’t make much sense to generate assembly any longer. It’s much more reasonable to generate IR (for example for llvm). Then you get free optimizations and at least some portability. It’s probably easier as well to not keep track of registers.

Their point, which I agree is fairly unclear, is that the fat is not converted to energy, it's converted to CO₂ and water. That conversion releases energy, which you then use to move, but the total mass of the process is constant (conserved).