Pabloski80

Was extremely important for someone who learned as a native to read Polish around age of three. First part was learning a mapping grapheme to phoneme for single symbol. Then came a second part - for a day or three picking out that symbol from raw text of newspapers, trying to pronounce its sound every time it was found. Then as more and more symbols were learned, looking up one symbol for a while, then another for some time, then when nearing learning a whole alphabet mixing the patterns to lookup wildly. After memorizing some 20/26 symbols, learning the connecting the sounds, and you could read simple words by then. But again polish is extremely regular language in that sense but a very few of irregular short symbol sequences.

For some languages (like Polish) it is nearly sufficient. I imagine for others it will basically suffice (perhapes e.g. Malay and Indonesian). Good luck with Chinese and other tonal languages, as well as Japanese (no word borders), Korean (dual and triple phonemes on a single grapheme and the order of phonemes on them), and Hebrew without nikud (little friendly smirk).

As of English, we come to funny question here, as in it the mapping from graphemes to phonemes is extremely irregular.

That feels certainly right on both points.

Another point of contention that perhaps shall be left out for later discussion (i might have got some preconditioned view, but perhaps would like to hear others first) is whether the third category should be considered "equal" to the 0 and F.

Science around that tiny area is profoundly broken. This event is just another instance of evidence of this sad fact.

Shademaps for the applucation for FV planning and optimization sounds cool.

Could they be helpful for agriculture planning, for example vineyards etc?

Another bunch could perhaps be the mobile bots which need to follow the sun or the shadow, either way.

WASM surely could be an improvement over js, especially for kind of BigData-ish/repetitive jobs, and where load on clients might become the next wall after we optimized the cloud/server part, or when we try to use js on cloud leafnodes.

You're not anymore "the weirdest", You two are unique still though. Share and exchange, and try to support each other. All gonna be good.

I need to learn more where lies the issue with GeoTIFF format. Perhaps "pure conversion" pipeline infrastructure shared between your two projects could help.

If there are two of You, perhaps there are more hitting the same wall.

I think I would try to use cloud first, or for completely non-profit projects - the crowdsourcing/distributed_computation, perhaps with help of people from projects like OpenStreetMap.

Hmm, those regions sound much like a construct from Cyclone language.

Make C Safe Again.

UBs in C language are the asleep plague just asking to get triggered into a głos bal disaster. Oops, too late.

There is another class of those there, described in some papers for CSmith. Milder but still quite bad.

Both got quietly not acted upon, when C++ got made.

Lets go back to Pascal/Modula/Oberon.

Could it be possible to build a kind of wikipedia around it?

As for text, be creative with leetspeak and diacritics or Unicode and other funny characters.

As for image it shall be easier. Try out a few filters after which the Meth RoboCop will give up. This one is roughly comparable to uncrackable so far caotcha problem.

I would advise him to present his work to someone who could estimate the value if his research and suggest a kind if mentor at least or optimally a sponsor for visa. There happen to exist offers for positions of visiting student+researcher etc.

If roughly an area of research isn't a secret, could You provide it?