frign

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.

Thanks for recommending libgrapheme. I am honoured, being the author of this library.

Thank you! I'm using just an editor and the terminal, nothing fancy. :)

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.

It could be even simpler. A presentation tool by the suckless folks with minimal dependencies but several features:

http://tools.suckless.org/sent/

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.

"simple"

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! :)

If you are passionate about coding, work on free software or build a team with which you work on stuff.

This is much more rewarding than doing unpaid work for your boss on code that will probably never see the light of day anyway.

There is a lot to learn by collaborating with other people on code projects of this nature.

   "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.

Exactly. The mess glibc is is giving C a bad name. Look at the musl libc for how it should be done.

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.

Now we can at least explain with code examples why Electronic Arts Games suck so much.

Using the term "net worth" already uncovers the fact that you are a business rat. Let the real engineers do the work and stop stealing their guts.

All those business school people ruined the corporate sector to a degree that I find it truly despicable.

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.

It's a system built to fail.

The broad scope of this topic won't be justified in a short comment like this, but it's general knowledge that the economy goes in cycles.

My special area are rare earth metal bonds and EU government bonds. The derivative markets are not a good direct indicator for stability (because they are unstable), but they set the bar for what one can expect. If you look at the M1-data by the FED [0] (M3 is _censored_), you'll see how large the bubble really has become. And this is consistent across all global markets.

Call me an apocalyst, I don't even care. Invest, crash and burn, have fun!

[0]: https://research.stlouisfed.org/fred2/series/M1

I'm preparing for a crash in 2016. Unlike back in 2008, when the FED was able to "balance" it out by dropping the interest rate to almost 0%, we now won't have an airbag to save us.

The crash will come, sooner or later, and compared to that, 2008 was only a road bump, with all of us sitting in a big oil truck heading at a steel wall of a nuclear plant.

In Germany, a "study" is often cited saying that men were better paid than women. However, peer review uncovered that the media covering this study omitted the fact that the women also worked less hours than men and thus got less money (obviously).

This however does not stop "female-rights-activists" from citing it over and over again. I'm sick of it.

I also don't like the notion that women are portraied as victims here. Most women I know don't want to go into tech-jobs because they think it's fucking boring. Live with it, people!

I know it's also due to socialization, but do we really want to change the entire society just to shoehorn exactly 50% in our employee statistics? Who benefits from this?

I know no woman who is sad because she just can't get hold in a tech job. If a woman is passionate about something, and pursues it, it will work out for her. Same with men of course.

Oh, and why don't people go berserk because we have like 96% women as educators (kindergartens, pre-schools, ...). Oh yeah, right, I know, because you can't earn as much money with that.

That is a very good point. It's easy to cite studies to support one's position. I could easily find studies which show that diversity actually decreases the mean IQ of the population.

Now, evaluating these studies, we might then rightfully say, that IQ evaluation is erroneous and discourages minorities, and that social status has a huge impact on the IQ. However, when diversity leads to a lower social status and poverty, doesn't this defeat the purpose of arguing for more diversity? Just to give you an insight into my thought process on this.

Another point is: Did the lack of diversity really hinder the creative minds of the last millenia?

It's the american notion that in politics there can only be liberals and conservatives.

In my opinion, it's a more liberal notion to actually choose people based on their skills and knowledge rather than skin color or in the interest of "diversity", even if it only yields in a 100% white or 100% negroe or 100% asian team.

I could even understand the notion of those who propose "diversity" if they wouldn't shut up when a team is devoid of white people. I won't recite the extremist clause that "Anti-Racism" means "Anti-white", however, judging from what I've heard in my years of experience as a software developer and entrepreneur, we're getting closer and closer to that if we keep on shutting those people up who question this.

I bet it's part of where we had our experiences. In Germany, it's almost exclusively leftist. It doesn't get in my way, because I care about the technology and don't think politics have a place there, but many people do strongly put both in one bin (if you allow me, I noticed that these are mostly people who do not really shine with their code contributions and want to "contribute" in other ways instead of improving their skills).

I'm with you brother. It's a hard fact to accept that the majority of the tech-world is leftist.

And for those who think I'm wrong: Imagine company X sent 4 white blond-haired blue-eyed women on the stage with a "message" of this kind. Double-standards anybody?

Also, somebody has to explain to me how exactly the products of a company magically become better when more minorities worked on it. When I engage in work with people, I don't care what their skin color is or if they are male or female. People embracing this culture of unfairness (because it's unfair to favor minorities over better-qualified non-minority applicants) should rethink what they are doing and who they are cheering at.

I've investigated this topic for a while. I've been thinking about adding a mandated wide gamut color space. Even though the wide color spaces "destroy" accuracy in small gradients, it doesn't matter when using 16-Bit. And because farbfeld is 16 Bits, it would definitely be an option.

Care to hit me with a mail (you can find it at the bottom of the page) so I can write you in a more sensible way what I've been thinking. Maybe you can help me decide on which color space to use (Adobe RGB, ProPhoto RGB, ...).

What do you need custom headers for? I think this problem is better solved with tagging file systems. BIP/BSQ Image Encoding can be done just well (you have (2^16)^3 colors), but you need to leave the interpretation to the outside. It is definitely not in scope of this format to handle that internally. Compression is external, so yeah, it definitely can be used.

All the things you presented are useful to have, but the question is: For which percentage of people is it useful to have? Is it solved by something else in a better way? You can never please the 1% without making everything harder for the 99%.

You can also use AdobeRGB with Farbfeld, but from my experience, those photographers shooting and printing in AdobeRGB with late CMYK export have Photoshop/PhotoRAW as their pipeline. If you fuck one thing up trying to handle AdobeRGB in farbfeld, everything is fucked up, but that happens anywhere.

On the other hand, most photographers shoot their stuff in sRGB (for a fact, because sRGB is by far the most widespread). I don't want to insult the professionals or something, I'm just acknowledging the fact that for the 1% using AdobeRGB there's no reason to complicate the format.

Nowadays, most computers use Little Endian, however, that might change in the future. Also, there's no justification to write software only for one endianness due to speed(tm) or something. Learn to use the interfaces provided by the system (htons(),htonl(),ntohs(),ntohl(),...) and when you specify interchange formats, specify an endianness.

Which one it actually is doesn't matter, there's not too much magic happening in the background anyway. Those people claiming "Little Endian Master Race" might probably jump on the Big Endian bandwaggon as soon as it became the majority for some reason.

In fact though, writing endian independent code is the way to go.