Author of libgrapheme here: Both collation and normalisation are non-trivial and have many gotchas thanks to the way the Unicode consortium likes to write their specifications. I sometimes get the feeling that they don't even care about implementers and just document what is done in the reference implementation ICU.
The only sensible normalisation one can implement is the full decomposition (NFD), and maybe the full composition (NFC). You rely on the full decomposition if you want to collate correctly, which is a problem because the amount of memory needed to store the decomposition is unbounded in general. I don't want to make the libgrapheme users jump through hoops, and I also don't want to do any memory allocations in libgrapheme either.
There is an idea floating in my head on how to solve this, but I'm currently busy finalising Unicode 15.1 support (Unicode 16.0, released on the 10th, will be trivial to upgrade to) and releasing my already fully-compliant implementation of the Unicode bidirectional algorithm.
Thanks for your work on packaging my library. Please let me know if I can make the process simpler for you; I take great care to make packaging as simple as possible for the packagers. Likewise I have no sympathy for those writing software that is almost deliberately hard to package.
Look at sndio if you want to see how sound should be done. Excusing the horrible mess pulseaudio is with the horrible state of Linux Audio doesn't cut it, when OpenBSD has been offering a superior and simpler alternative for years!
It doesn't reinvent the wheel and for anything more complex you can always use JACK, like if you really want to go low-latency.
When I saw the new Ghostbusters trailer in the cinema (yes, I still go there), I thought it was a parody film. I'm not kidding.
Nowadays, people always try to find ways to be offended. A women-led movie got bad ratings? It must be the patriarchy!
Nobody wonders if it might have been just a bad movie, as I, as a man, also enjoy women-led movies (I mean movies in the cinemas, not what you think :P). Hoewever, the new Ghostbusters just looks like a big horrible painful joke, and that's why the ratings tanked.
Given it's so hard to even assess statistically, how many men are among movie raters, this entire article stands on weak feet.
Yeah, I agree. Though, Vulkan is meant to be low-level, kind of like an ASM for Graphics Cards.
The euphemism of the article's title is too much though imho.
So can one assess this is a racial problem after all?
For years, liberals tell us the high poverty of negroes and hispanics was due to lack of education. If it's not education, what is it then? And why are Asian-Americans not facing the same issues?
I suspect it's a racial identity issue. The best way to understand this point is looking at the mainstream media and how the different races are portraied. Only an idiot would ignore this influence on people, especially because the USA are by far the biggest TV consumers.
If you start judging me for asking these questions or downvote me without giving a reason, you should be ashamed of yourself. Reasons for downvoting are welcome though, so keep them coming! :)
"What about other areas and under-the-covers code that just
needs rework? Just do what I do, and work on it on your own
time."
Yeah because doing unpaid work for your company is the way to go.
Get a life and learn to leave work at work.
It's not the developer's fault if the manager is not dedicating enough man-hours to finish something, only to find out later on that messy code eats up many more man-hours than having it written cleanly the first time with much lower maintenance costs later on.
If developers don't man up and let the managers crash and fail for it, they will be supporting greed and exploitation in the workplace and probably make it worse.
> Note: When Spike originally released this list, many noted the lack of female filmmakers. Lee accepted that critique and released an updated list.
Thanks, I'll stick with the original list. Given the small number of female filmmakers in Hollywood an only-male list is not unlikely. Political Correctness is a bitch.
LFTR's are very safe, but the current technical challenge is actually building containments that can handle heat + flouride salts.
The tritium formed during the nuclear reactions is also challenging to handle, as it passes through those walls via diffusion.
Until we find materials that can cope with these situations, it will remain a dream. Advances in nanotechnology will bring us further here, I totally agree with you though that LFTR's by far get too little attention, as today's nanotechnology could solve it for us.
The waste coming out of LFTR's has to be stored ~400 years (which is actually a sane timespan and it's easy to find places underground that stay stable for 400 years).
Another bonus is the fact that Thorium is much easier to find than Uranium, and that an LFTR can be built more or less failsafe.
I totally agree with you my friend. Same applies to companies literally hoarding lawyers and economists.
I don't understand that they do not realize these people bring no benefit to a company other than laying off key people and filling their sentences with "big" buzz-words.
I know companies where more people analyze the company's work rather than people actually working.
When it gets hot, the FED prints money (they call it quantitative easing) (for 5-year-olds: throw money at the problem).
Look at 2008, where they ramped up the money stock like crazy. And afterwards, all these upward bumps were quantitative easing steps to "stabilize" the markets.
However, just realize this is exponential growth. You don't need a maths degree to realize that you can't keep on printing money like crazy and expect the markets to stay stable for much longer.
It takes one person to dig into the matter and ask the question: "But what covers this money?" and bang, you got a stock market crash.
And let's not call it money. What the FED "prints" is currency, sheets of paper. Money has inherent value (gold is money for instance), but not this FED-Dollar lie we live in every day.
Since 1914, America has been tricked into believing into this system. When Nixon turned off the Gold standard in 1971, the entire Bretton-Woods-System (built on top of the Dollar) sort of went Berserk.
The only sensible normalisation one can implement is the full decomposition (NFD), and maybe the full composition (NFC). You rely on the full decomposition if you want to collate correctly, which is a problem because the amount of memory needed to store the decomposition is unbounded in general. I don't want to make the libgrapheme users jump through hoops, and I also don't want to do any memory allocations in libgrapheme either.
There is an idea floating in my head on how to solve this, but I'm currently busy finalising Unicode 15.1 support (Unicode 16.0, released on the 10th, will be trivial to upgrade to) and releasing my already fully-compliant implementation of the Unicode bidirectional algorithm.