482794793792894

As I understand it, English is your mother tongue. If so, that's probably why you don't have this issue.

For me, French is my mother tongue and I live in France. So, there's lots of things that I'd want to research that are specific to France (laws, culture, geography etc.) and then obviously, if you speak French fluidly, you get much more precise and detailed information for these in French texts.

If you're lucky, the English text is just a bad translation, but more often than not, the English text assumes that you must be some guy from a foreign country that really doesn't care about specifics and instead just wants an overview.

On the other hand, if I need to look up technical information or most international science, then English is the lingua franca, what gives you the best results in most cases.

In some cases, I'll even try both languages, just to make sure I'm not missing any useful information or to gauge which language gives better results (for example when a globally usable technology happens to be exceptionally popular in France).

While that would also be a somewhat useful measure in this context, there's very little correlation between the size of the codebase and the size of the binary.

Programming languages and styles can vary in verbosity a lot. For example, if UEFI is written in some form of assembler code, then you quickly get a lot of lines of code while the binary doesn't grow particularly. On the other hand, high-level programming languages like Java, or even moreso functional and logic programming languages like Haskell and Prolog respectively, can generate huge binaries out of even just a few lines of code.

This is a notion that sounds great at first, but it's entirely shallow.

- There are tons of information pieces that functionally need to be private, for example passwords, and tons of information pieces that better just should be kept private for your own benefit, like medical records.

- You're not helping us customers. If every company knows everything about us, then every company can exploit our mental vulnerabilities to get us to buy more things we don't need.

- Privacy is a basic human need. Lack of privacy can lead to severe mental issues, as illustrated by Panopticons.

Well, you can just as well be best friends, even if you're wanting to mold each other. Both parties just have to be open-minded about it.

You might even see it as positive to be challenged in your ways, as it helps you to move yourself forward. For example, if you're a couch potato, you might actively look for a sporty partner in hope of being motivated to do sports.

Alright, but it really doesn't seem to me like fixing this issue for you would require breaking the search for bilingual people. There's gotta be so many better ways to resolve that.

Yeah, it definitely feels like Google has gotten into this phase of a monopoly where you just stop trying. It was specifically Google that used to have all kinds of advanced user thingamabobs, now they actively make it harder on advanced users.

The problem with X11 is that it's everything-and-the-kitchen-sink. You can't solve that by making another everything-and-the-kitchen-sink. You need to cut down in some places and modularize the other things.

One perfectly legitimate way of doing that is to do one of those things and ask others to do the other things. Development would not go faster, if they put those other aspects at the end of their To-Do List as well.

Last weekend, my dad needed new printer cartridges and so we went sifting through the internet for different offerings. By chance, we got onto a page on the manufacturer's website, which had images of all their cartridge packs. Among those, we also found an XL version of what we initially thought to buy.

So, there we were, needing exactly this feature. If I didn't know that it's impossible for them to have developed this in such a short time, I'd be a little freaked.

Thankfully, though, TinEye served the exact same purpose...

That's not the point they're making. What they mean is that if they consider side projects as potential criteria for being hired or not, they'll lose the fun in those side projects.

Because they'll then try to make every part of the code perfect and with complete documentation for everything, probably spending more time trying to present it rather than working on it.

> Instead of seeing a dollar amount associated with their purchase, app developers show the purchase amount as coins. This could take the sting out of spending cash, Amazon has believed.

I'm fully aware that Amazon is not the first company to be doing this, but does this not break contract law? They're actively trying to trick people into spending more cash for a product than they rationally would.

Like, where's the line between this and just offering people a joint before they sign your contract, so that they feel easier about spending money?

> Note that there is no picker for <input type=time>. We decided not to support it since we think it’s easier and faster to enter a time using the keyboard than selecting it from a picker.

I've thought this so many times, even on my phone where typing is less accessible, I still prefer it over those analogue clock face inputs.

With such a clock input, I'll often hit the wrong time, either an hour/minute too late/early, due to my apparently fat fingers, or 12 hours wrong, because I live in a 24-hour-format region where normally on an analogue clock you read things in 12-hour-format and so my brain thinks "8 pm" and enters "8" when it should have chosen "20". That doesn't happen with typing, because digital clocks almost always display 24-hour-format.

And even worse, in an attempt to speed things up, someone came up with the ingenious idea of directly advancing from hour input to minute input as soon as some input has been made. So, my first few wrong inputs then mean that I have to find the way to get back to the hour selection multiple times.

Nah, it's been on Mozilla's To-Do list for years already, just realistically not ever really a priority.

And I'm also pretty sure they've already been actively working on the implementation prior to talks with those companies. I think, I remember reading about first design steps at the start of the year already.

Well, Firefox is not Chrome. Firefox usually supports things more completely than Chrome, partially because that's just what they do, they safeguard webstandards, so delivering a standards-compliant browser is a main-goal, but in large parts also because the community will make Mozilla go the extra mile with code contributions, if they don't do it themselves.

And a Mozilla dev, Manishearth, has commented above that he is in fact currently looking into making it configurable.