Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Manishearth
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
91.
▲
by
Manishearth
9y ago
It is now! (we had some issues with GH pages)
92.
▲
Rust 1.25 released
(blog.rust-lang.org)
252 points
by
Manishearth
9y ago
|
53 comments
93.
▲
by
Manishearth
9y ago
> Same deal with English. > > Which is similar in complexity to English, just the order of speaking is reversed. Yes, I was mentioning these to paint an accurate picture, not to contrast with English :) ----- As a native Marathi &#
94.
▲
by
Manishearth
9y ago
No, for English the thirty series is always "thirty-foo", and numbers ending in three are always "foo-three". It is true that you don't use the same word for the number when it's in the tens place (like Chinese
95.
▲
by
Manishearth
9y ago
Might be enterprise.
96.
▲
by
Manishearth
9y ago
(Native Marathi, competent Hindi speaker here. Marathi has the same problem) So, it's not like each number has a different name. However, it's almost like that. Basically, the numbers can be broken down into a logical tens and o
97.
▲
by
Manishearth
9y ago
Hindi/Marathi are not easy, you almost have to memorize the numbers 1-100. Hindi and Marathi both have dedicated names for the tens (11, 12, 13, ...) and after that numbers are named in the reverse order of their digits. E.g. 45 wi
98.
▲
by
Manishearth
9y ago
The problem is that there's a buggy u2f library out in the wild distributed by Google that depends on Chrome-specific impl details. This means that while the pref works for sites like Github, it doesn't work for Duo or Google logi
99.
▲
by
Manishearth
9y ago
FWIW Firefox does support WebRTC (which is used for web calling), however sites like Meet sometimes filter for Chrome anyway (IIRC Meet may use Chrome-only proprietary features?). Hangouts is now available on Firefox though, after years of
100.
▲
by
Manishearth
9y ago
I think for such things it's preferable to just have a `clamp` method as a static method, i.e. you call it with `Ord::clamp(foo, bar)` instead of `foo.clamp(bar)`. But yes, it could. Generally the trend seems to be to still try to avoi
101.
▲
by
Manishearth
9y ago
Currently: - new keywords https://internals.rust-lang.org/t/keywords-to-reserve-for-ru... . There are a lot, but not all of them may end up being used, this is conservatively reserving them. In case a crate on a previo
102.
▲
by
Manishearth
9y ago
This particular series is more of a toy OS for learning purposes (and through which they can teach things). At least, that's my impression of it. Redox ( https://github.com/redox-os/redox ) is a Rust OS project that
103.
▲
by
Manishearth
9y ago
It's not just old sites that depend on these quirks. Seriously, web compat is very tricky.
104.
▲
by
Manishearth
9y ago
I'm not sure what you mean by team velocity. We're still working on standards compliance, but we may focus more on the bits that are actually useful within VR.
105.
▲
by
Manishearth
9y ago
You still need webcompat for VR stuff. Focusing on VR means that we may not be working on some kinds of webcompat things (the standard example is "IE6 table layout quirks") but there's plenty of webcompat work that needs to b
106.
▲
by
Manishearth
9y ago
We're still working on web compatibility; that's not changing. But I don't think we've ever had a concrete goal to have a standalone Servo browser. Parts of servo in firefox? Sure. Trying out new ideas? Sure. Embedding s
107.
▲
by
Manishearth
9y ago
> I think the amount of users you can win back from Chrome with a Servo browser is much larger than any VR audience you can hope to gain in the near future. A Servo browser product is not possible in the near future. That is very much
108.
▲
by
Manishearth
9y ago
There's a tool called cbindgen ( https://github.com/eqrion/cbindgen ) that generates header files from rust code . It's a bit experimental. The reverse tool, bindgen ( https://github.com/rust-la
109.
▲
by
Manishearth
9y ago
This will not work with password fields.
110.
▲
by
Manishearth
9y ago
This isn't a CSS feature, CSS does not let you select on the value of a password field (it lets you select on the value of the `value` attribute , which doesn't change when you type) This is a React feature, where React apps sp
111.
▲
by
Manishearth
9y ago
This is incorrect. The [value=foo] selector does not work for the actual value of the field, only the `value` attribute (used to set the initial value). This means that both: - typing the password - setting the password via element.value=fo
112.
▲
by
Manishearth
9y ago
I think your wording there is incorrect and very misleading, even if you do understand it. You say > Cargo selects the latest version of a new dependency and its own new dependencies but that's not true; it selects the "latest
113.
▲
by
Manishearth
9y ago
I think this oversimplifies the problem. OpenType basically requires you to operate on a glyph buffer. What you can do, is try and make all glyph buffer operations throw an error that makes you hit a fallback case.
114.
▲
by
Manishearth
9y ago
Imagine if dereferencing a null pointer in C was defined to segfault. Currently, it's UB, which means the optimizer assumes it's not null, and when you break that assumption, weird things happen, the least scary of which is a segf
115.
▲
by
Manishearth
9y ago
http://www.cloudscan.me/2018/02/coretext-crash-osx-10133-lld...
116.
▲
by
Manishearth
9y ago
This isn't any different from what happens to pronunciation in English. The difference between English and Indic languages is simply that this has happened a lot more with English (also English kinda gets its words from all over the
117.
▲
by
Manishearth
9y ago
Yeah, and because it's reliable, you don't need to worry about security issues -- the worst this can do is abort the application. Whereas for this bug it's quite possible that it may be exploitable. Especially given that the
118.
▲
by
Manishearth
9y ago
Huh, that's an interesting theory.
119.
▲
by
Manishearth
9y ago
> Congratulations, you can now pronounce (almost all of) Telugu (and almost any Devanagari script using this same play book). It is because these scripts are deterministic, and there is a single pronunciation unlike English and many othe
120.
▲
by
Manishearth
9y ago
Not Korean, but the Korean case is different, a bit. Korean syllable blocks are viewed as syllable blocks -- a new concept, whereas Indic consonant clusters are simultaneously viewed as letters of their own and fundamentally composed of mor
More ›