Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Re:Sugar *substitute* (Score 1) 67

Fact check: Haribo Sugarfree Gummi Bears contained the following:

Hydrogenated Glucose Syrup (LYCASIN), Gelatin, Citric Acid, Natural and Artificial Flavors, Artificial Colors: Yellow 5, Blue 1, Red 40, Fractionated Coconut Oil, Beeswax, Carnauba Wax, Starch

Lycasin is a brand of maltitol sweetener.

The gummy bears of which you speak did not contain xylitol.

Comment Case study in the virtues of profit motives (Score 1) 49

While it's not yet clear why the board did what they did, it increasingly looks like they were acting out of anger. Altman lied to them, they got mad, and fired him.

If that's what really happened, I don't think I've seen a clearer case study arguing in favour of profit motives. Taking away the financial profit motive (as per the non-profit board), what you may be left with is not superior rational decision-making in the collective interest, but nothing more than basic human emotional knee-jerk reactions.

Cutting off noses to spite faces.

Comment Re:It has nothing to do with being open source (Score 2) 142

It has to do with huge numbers of developers and companies all using the same code/framework as everyone else. It is a single point of failure.

For some libraries you might have a point. But this is about logging. Most people don't choose a logging library, they stick with what's already in use. You don't want logging from different components going to different files, and you don't want confusion around how to write 'logger.info(...)' because different logging libraries have different APIs. You don't want JAR hell because you use logger X but also library Y that depends on logger Z.

And there aren't a lot of viable alternatives in this space anyway.

A lot of frameworks should maybe be more broken up with few dependencies between the pieces, allowing developers to omit more code that they might not need.

I wrote a blog post Log4j vulnerability: What the FAQ happened? and didn't quite get to this point, but reading between the lines in this section, a likely reason why the problematic feature was so poorly documented was that log4j was broken up into separate API and backend libraries - leaving no obvious place to document the backend features, where API users could clearly see them.

Comment Re:38% is “Lion’s Share”? (Score 4, Funny) 79

TFS said "the lion's share", not "the Lions' share" - note the capitalization and position of the apostrophe.

38% sounds about right for Mr Lion alone. Then there's Mrs Lion and the rest of the pride. Any leftovers go to the hyena pack with the biggest marketing budget.

Comment Re:GIT? (Score 1) 238

Yes, but my experience was that merge conflicts in Word docs were frequent and painful to resolve. So we introduced a 'lock before edit' convention for Word docs (and same could be said for any file not edited as text).

Merge conflicts in tables are bad enough, and that's fairly basic functionality. Good luck with merging changes to embedded media.

Slashdot Top Deals

Promptness is its own reward, if one lives by the clock instead of the sword.

Working...