111–120 of 122 posts
What's the Unicode codepoint of the character? Is it a single Unicode codepoint or multiple? (I tried to search for info on the web, but Chrome kept crashing.) Supposedly it's a normal Telugu character, but how could that have gotten past even minimal testing in Hyderabad? Or is it some strange combining corner case? Telugu script is kind of unusual in Unicode, since it is syllabic but has separate codepoints for vow…
Multiple codepoints. U+0C1C U+0C4D U+0C1E U+200C U+0C3E
Here's a link to the character if someone wants to test it themselves https://pastebin.com/9Tr8ytTr
Earlier quoted context omitted.
What causes this to be an issue in C but not in other languages?
It is in other languages just to be clear. C++ for one example could suffer from it. But largely the issue is, when an error occurs, can the state change to [undefined]. In some languages, like C/C++, it is possible through bugs to enter an undefined state. In many higher level languages, all states are defined even if not all states are actually handled by the developer's code. If all states are defined you can use…
There is absolutely no such thing as "all states are defined". This has nothing to do with the language. There is nothing magical about a "higher level language" to safeguard from failures. At best you could be referring to managed languages, where memory access and exceptions are controlled and the extent of a aborted execution is predetermined - but still not immune to just closing a process when they misbehave. That is precisely what a process should do. Nonetheless, nothing in this bug report indicates that the system is acting in an undefined manner. The library that failed may have, by design, been programmed to close when font rendering reached these conditions. We don't know if this was a signal abort or an intentional if (bad_outcome) close()
Any level from the most managed sandboxed level to the most host level process may fail, regardless of the language used.
Earlier quoted context omitted.
> Without this information, it's pointless to talk about how things feel or seem. Au contraire! Without this information we can only talk about how things feel or seem .
Exactly. One can discuss and imagine all they want without full information and it's very normal and socially and personally productive. I'd refrain from issuing final judgements unless you have "all the info" but that's pretty obvious.
I don't see how that's productive, what has been "produced" here? Even the reddit comment from an (alleged) Apple employee was contradicted by other (alleged) Apple employees.
Gathering any insights into Apple's quality issues does not seem to be possible at all from internet comments... that makes the whole thing misleading and pointless to me.
Earlier quoted context omitted.
You're just making assumptions. All we know is that there's a failure. We don't know what kind of and how many errors triggered the failure, nor do we know what the faults causing the errors were. We certainly don't know what kind of hazard analysis they did and what kind of mitigations they have in place, nor do we know whether they accepted a specific amount of residual risk for e.g. economic or market pressure rea…
> Without this information, it's pointless to talk about how things feel or seem. Au contraire! Without this information we can only talk about how things feel or seem .
Earlier quoted context omitted.
also crashed firefox on mac and chrome somebody should just paste them here in the comments seeing the % of people here who run macos
HN is no fun allowed zone - it strips all unicode.
本気ですか？
Earlier quoted context omitted.
Choose Rust. It has zero-overhead memory and data race safety.
I suppose so. As an embedded developer it appeals to me, but I haven't looked too much into it TBH. Do you know of any analysis done on the bugs in servo or any other large-ish project?
>Mozilla made two previous attempts to parallelize its style system in C++, and both of them failed. But Rust’s fearless concurrency has made parallelism practical! https://blog.rust-lang.org/2017/11/14/Fearless-Concurrency-I...
Earlier quoted context omitted.
Exactly. One can discuss and imagine all they want without full information and it's very normal and socially and personally productive. I'd refrain from issuing final judgements unless you have "all the info" but that's pretty obvious.
One can gossip about Apple's technical problems, but it's neither interesting nor a good use of the time of most of the people on HN I'd imagine. I don't see how that's productive, what has been "produced" here? Even the reddit comment from an (alleged) Apple employee was contradicted by other (alleged) Apple employees. Gathering any insights into Apple's quality issues does not seem to be possible at all from intern…
Earlier quoted context omitted.
I suppose so. As an embedded developer it appeals to me, but I haven't looked too much into it TBH. Do you know of any analysis done on the bugs in servo or any other large-ish project?
I haven't studied this extensively, but Mozilla made the following claim: >Mozilla made two previous attempts to parallelize its style system in C++, and both of them failed. But Rust’s fearless concurrency has made parallelism practical! https://blog.rust-lang.org/2017/11/14/Fearless-Concurrency-I...