mrbadguy

Arranged marriages are not the same as forced marriages. Your family simply plays matchmaker and it’s up to the prospective couple to decide whether they want to be together.

Man you got me on readability. Just yesterday I had to input a random string WiFi password in a printer with only arrow keys to select each character. The password had an upper-case I in it but the moronic designers of the little password label that came with the router selected a font where “I” and “l” are indistinguishable. Took me like ten minutes to get the damn thing connected.

I only got it right because I looked up the password on my Mac, whose keychain app displays them in gloriously readable monospaced font. FFS

You’re right. My point was more about the idea that “higher frame rate = better movie because the number is objective” rather than “all art is subjective”. In other words, I don’t think we should try to value art on narrow physical axes. I’d like to think that the people you’ve mentioned would agree on that. The traditional notion of “objectively beautiful art” isn’t tied to technocratic things like that and, for what it’s worth, I agree with it.

If people don’t report crime then we have to leave it. The answer can’t be just to invade everyone’s privacy looking for crimes (before they’re even committed!)

Agreed, the idea that there’s anything “objective” about art is kind of hilarious. Yes, it may be technically better in that there are more frames but does it make a more enjoyable film?

Your film, too?

Yeah bone conduction headphones are awful, I don’t know how people tolerate them.

For now

Keep at it, friend. You are not alone.

It’s even worse than that: someone else shipped the bug and you have to work without pay to fix it.

Yeah the comments here are slightly surreal; the issue was that they didn’t have an off-site backup at all, not that it wasn’t on AWS or whatever.

Agreed, a single thread is painful if it’s actually spawning off multiple sub-topics. I suppose the better answer is to start a separate thread in Slack in that case but it can flow weirdly where the topic originally arises in one place but is continued elsewhere; it relies on someone linking on the original thread to keep context. In a mailing tree, that context is still there.

All of this depends on having a sane email client though, doing it via outlook or gmail is a nightmare and I suspect this is the root of many people’s aversion to email.

Maybe you should try it

Their latest sham is the bag sizing box that has one side open. So, even if your bag would actually fit into a volume of the required size, if any of it is loose (often the case with soft bags)then it’s “too big”.

I recently saw a lady try to make this point to them, only for the staff to keep repeating “but it sticks out”. In the end, the lady had to take the belt off her jacket and wrap it around the bag just to make the point. What a waste of time.

People who defend this airline “because it’s cheap” are just degrading themselves quite frankly. It’s awful and we shouldn’t be accepting of it.

Nailed it. All of the “progress” in the last, say, 20 years is exactly this. They call it “disruption” and wear the title “disruptor” as a badge of honour.

Well said. There’s a noticeable lack of judgement in many places these days; people think they can abdicate it to metrics and data but this is mistaken.

That’s simply untrue. The old way was definitely better because, with OTA, the manufacturers will succumb to the usual web-software bullshit of “we don’t have to sell them something that actually works now, we’ll just push the update later”. I mean, it’s a car, I can easily take it to a garage and do so for anything else that might be wrong (if I can’t fix it myself) so I don’t see the problem in doing so for software patches. OTA doesn’t solve many issues for me but it sure as hell will create new ones.

These kinds of announcements are quite misleading IMO. It’s not like smoking a single cigarette immediately takes off 20 minutes, it’s a cumulative effect caused by years of heavy smoking. It’s not particularly meaningful to average that out over the number of cigarettes smoked.

What?

This is an odd complaint. It’s not a waste of anything to update a record on an official document. Indeed, it’s more frustrating when they don’t because now I can’t see my full travel history by looking at my passport. Yes that exists somewhere in a DB but I don’t have access to that.

How’s that not true for just about any country?

I’m not American and I totally agree. Y’all and all y’all are brilliant!

It’s fairly mindless boilerplate for sure, but it does mean that when something happens that causes a change like this protobuf update, the change in your codebase is isolated just to the interface between it and your code ie your dumb conversion funcs. Otherwise you end up with the problem the original commenter had.

It’s good to isolate your dependencies within the code :)

Oh I see, thanks for the clarification! Personally, I'm fine without that and with something like

  func Foo(r io.Reader) {
      var m MyStruct
      binary.Read(r, binary.LittleEndian, &m)

  }

but we may be operating in different contexts where the underlying copy is or isn't a problem. That said, depending on the implementation of the reader passed in, the bytes might be being streamed from elsewhere, in which case the copying is minimised.

Can you please give me an example of what you don’t like? I’m not sure I understand the “write the code manually to do a struct” bit.

You have to define the struct for sure, but beyond that you just pass it to binary.Read and it comes back with the fields populated. I don’t see how you’d avoid defining the struct.

I don’t know about the padding (certainly it never inserted any when I’ve used it) but you can definitely state the byte order upon reading or writing. That would definitely be an oversight. Take a look at the encoding/binary package:

https://pkg.go.dev/encoding/binary

I’m not sure I understand the packed structs complaint. I have used Go to read binary data and it’s quite easy. You just need to ensure that all of your struct fields have fixed sizes e.g. int32 or [4]int64 or whatever. Unless I’ve misunderstood what you mean?

This made me actually laugh out loud.

This is an unbelievably ignorant comment. As someone else pointed out, Swiss German is not the same as German and there are many (widely spoken) languages that are spoken in many different countries as there are many countries where many different languages are spoken.

The entire point of TFA is that there isn’t a simple mapping between flags of countries and languages so we should probably stop trying to create one.

> Back in my day we all had to use ASCII, etc etc.

And it turned out that this assumption was a bad one hence the need for Unicode. Why make the same mistake again?

Gah! Don’t give them ideas!