Hacker Newsnew | past | comments | ask | show | jobs | submit | McMiniBurger's commentslogin

same here. solution: press 'rotate screen' button 4 times...


could you elaborate on the "bad news" part?

Is there something rust inherently can't do but c/c++ can?


Exist 20 years ago when the OS was written.


Even ColorSync, which the top of this thread mentioned, is older than that. It was first released in 1993 (https://en.wikipedia.org/wiki/List_of_macOS_components#Color...)

The work to remove all AT&T code from BSD started in 1989, so other parts of MacOS probably are over 30 years old, too.

I don’t think anything of the original Mac OS remains, lots of it being written in 68k assembly and pascal.


Yea, rust doesn't already exist. Rewriting a whole OS is an impossibly high ask.


> Knowledge is knowing you might be wrong about it all

that's not a great definition... I know I might be wrong about flying UFOs, but that doesn't count as 'knowledge', does it?


but don't password fields only recognize ascii?

it seems i just can't type korean to password fields


Most competent websites I know accept general UTF8 characters like emoji perfectly fine. There are a lot of crappier websites that don't even have proper unicode support for usernames or profile descriptions out there, though, so your mileage may vary.

As far as I know, there's nothing preventing a password field from containing any valid unicode string. The problem may be IME support or servers stuck in ASCII, but the textbox itself will just work.


Even surprisingly big names are surprisingly bad at this. Don't know recently, but Hotmail/Outlook used to have a rule of only using letters, numbers, and a handful of symbols, also limiting you to at most 16 characters or something. You couldn't even type a space!


They're not necessarily "bad" at it; there's a good chance they just want to make sure that the least competent of their users doesn't make a password that they have trouble with later. They don't care that security-conscious people get frustrated with it.

So I guess that could also be "bad," but not incompetent "bad" or Michael Jackson "bad."


This is much more excusable for email providers to prevent phishing. There are a ton of unicode points that indistinguishable from ascii letters. There are other security issues that can arise as well. Here is an example from spotify https://engineering.atspotify.com/2013/06/18/creative-userna...


I should have specified - this was (is?) for passwords, not usernames. I'm much more sympathetic to limited character sets in usernames, but I don't see much valid reason for doing so with passwords


Honestly, that stuff only proves that big name websites aren't necessarily competent. PayPal used to let you register an account with a password longer than the maximum password length used in the authentication code, for example, essentially allowing you to set a password you could never use with your account again. Being worth billions doesn't mean you've got all the basics down, it just means you've tricked many people into giving you their business.

Even good websites that will accept any valid password string will sometimes cut off the last part of a long password because their hashing algorithm throws that data away. Bcrypt, for example, supports a maximum input length between 50 and 72 bytes, depending on the library you use to hash your passwords. That's bytes, not characters!

More primitive systems used to have problems with non-alfanumerical passwords and once those algorithms have been unleashed upon the unsuspecting public, you need to support them in your login flow for years to come.


For what it’s worth the “big” company I work for stores usernames in MySQL. 15 years ago when the username column was created it was set for ASCII (or whatever legacy charset it was). Changing it to utf8 would be a royal pain in the ass, requiring all kinds of testing and crazy updates across the entire company.

So while we’d love to make it utf8, it is just too much work to justify doing over other things.


I should have noted - i was talking about their restrictions for passwords, not usernames. Since those are hashed before storage, i think there are far fewer excuses for such limitations.


can humans use those teeth as replacement?


Not. Even if we could solve the rejecting issues (and we have fully solved the technology for breeding sea breams since decades), they are too small. Not really suitable for adult people.

And not useful for children, that would lost and replace their teeth in any case.

The structure of the teeth root is also different, and the mandible is much more acute triangular than ours. Not useful to replace part of a missing mandible in my opinion. Specially when you can just made a ceramic piece of the right size and shape and do a bone self-transplant.


but not anyone's OK with spending $1250 upfront

if you earn $250 a month in a developing country, $1250 is like 9-month pay (* calculation may be wrong --- gotta sleep?)


Sure, but it is just an extreme example of the TCO of the OLPC being comparable to a high end professional grade laptop. It was just a very hard problem to solve, and the technology was not quite there yet.

Definitely not suggesting kids in Africa should just buy macbook pro's, but $100 is also a lot of upfront cost for a product that's actually not that useful and destined for the wastebin within a year or two.

I do hope I'm wrong and it brought some cool technology too some kids far removed from the big cities.


hm... "keep your friends close but your enemies closer" ...?


But try to make sure your enemies don't end up surrounding you?


Yeah, that is tricky. I believe that Constantinople once found out the hard way, and thus is now Istanbul.


I guess people just liked it better that way.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: