eek04_

I like plastic in that I prefer the lower cost and lower pollution and lower weight and lower breakability compared to glass.

Back in the day, my father worked as a researcher for a large, old dairy company. He was tasked with finding out what was environmentally friendly for packaging milk; whether they should start offering milk in washable glass bottles instead of their current cartons, for environmental reasons.

He found that the environmental impact created by the washing of the glass bottles was worse than the impact of the entire production and disposal cycle for the cartons. If you added in the production of the glass, the recycling of glass when it broke, and the extra impact from transport (less space due to not being able to pack as well, heavier) there was no competition at all - glass was way, way worse.

Plastic was a bit better than glass, and carton was the best available option. So they stayed with carton.

This was ~30 years ago, mind, so the equation may have changed. But I still find it important to check before deciding "Let's go glass" is the right option.

> A huge company is using unpaid artist's labour to create tools that will reduce the potential for these and all future artists to get any paid work at all in the future.

"Will" is a strong claim. If the Jevons Paradox (https://en.wikipedia.org/wiki/Jevons_paradox) applies in this case - and it may well do so - the new technology will lower costs, and the increased productivity will increase demand. If so, it will require artists to work in a different way but they'll earn more.

The Baumol Effect (https://en.wikipedia.org/wiki/Baumol_effect) may also lead to increased wages.

While I've not played with k8, I did run stuff in Google's Borg for a very long while, and that has a similar architecture. My team was petabyte scale and we were far from the team with the largest footprint. So it is clearly possible to handle large scale data in this type of architecture.

> Random perturbations are a parsimonious explanation, but a deeply unsatisfying one.

Why? I've always found it satisfying - it matches with how a lot of other things in biology has happened.

> So, this is just number rearranging. The public pays either way.

"The public" isn't one person. Denmark has progressive taxes; getting rid of subsidies so prices of food increases changes who among the public pays.

> Or do you just want to ignore this externality until we pay it all at once?

> So, this is just number rearranging. The public pays either way.

"The public" isn't one person. Denmark has progressive taxes; getting rid of subsidies so prices of food increases changes who among the public pays.

> Or do you just want to ignore this externality until we pay it all at once?

I'm in favor of the carbon tax. I also think that it has complicated side effects and we should try to understand those effects, and see if we need to change something else to compensate for them.

> programs are written much less frequently than they are run, so surely developer keystrokes are laughably unimportant compared to runtime performance and other user-facing concerns.

Taking this to its logical conclusion all programs should be written in assembly.

The reality is that there's a tradeoff: Programmer time vs performance, and which parts of performance matter. I've worked using anything with performance from assembly to shell scripts (including C, C++ and Java). It is all tradeoffs. Do users want more features, or more speed? Are we running at a scale or situation where ultimate usage of hardware matters, or not?

Saying we should do ultimate amounts of investment in performance when there's three users and one programmer doesn't make sense. They'd typically rather have more features and adequate performance.

If we can, and it works out to less harm vs benefit than otherwise: Yes. But it turns out we can't for alcohol and cigarettes (except regulation). We fairly much can for workaholics - Norway has laws that stop working overtime except in certain situations, and they actually work fairly well. I don't know if we can for social media, though I see California is trying to stop some of the addictive forms of social media.

There's at least one bit that's missing here, even if the claim is entirely accurate:

Both the total pie and the total number of creators has increased. Hollywood feature film production is [estimated](hhttps://www.quora.com/How-many-people-work-in-the-film-indus...) to be 3000-7000 people. There are [approximately 61.1 *million* YouTube creators](https://explodingtopics.com/blog/youtube-creator-stats), or approximately 10,000 times more. There could easily be 100x more money flowing to the total visual entertainment creator community and the old guard film creators could still get less than they used to.

I don't know exactly what to search for to get similar numbers for music production, but I suspect it is similar: There's a lot more creators and they get less each even though it's more in total, and this is especially hitting "old timers" that used to get the bulk of the old total and get less with the new setup.

Scientific libraries categorise into *several categories*.

They effectively use hierarchical tags, with the set of tags very carefully curated.

The better candidate is spending more on the evaluation.

E.g, for my company's twice-yearly evaluation, everybody writes up a short report on the most impactful stuff they've done including evidence, this is evaluated by their manager to give a score, and then there's a series of group meetings between managers to make sure that the scores are calibrated, including looking at all types of metrics that can be dug up and comparing to our written role descriptions for different levels. It takes a lot of time but creates fair scores.

This is extremely labor intensive, but that's the thing: To create anything resembling fair evaluation of a large group of people that do a large set of different things, you need to do things that are labor intensive. Using a simple set of metrics don't cut it.

I've lived in Norway (>30 years), Ireland (>10 years) and in California (3.5 years). There's extreme differences in culture around dog ownership in different areas. In the time I lived in Norway, nobody I knew had abandoned a dog. Getting a dog is a commitment for the lifetime of the dog; the only cases I've heard of relocation of dogs from anybody I knew has been for medical reasons (e.g. discovering somebody in the family has an allergy). In Ireland, it is similar, though people don't seem to take quite the same commitment (based on known several people that got dogs from shelters). In my relatively small social circle in California there were two families that got and handed off dogs in the 3.5 years I was there. It was just not seen as a big deal.

An A3 (11-3/4" x 16-1/2") poster here in Ireland starts at around 7 euro ($7.50). 80 euros is presumably for the aluminium dibond print - which sounds like an extreme quality print material, and those gets expensive fast. An A3 on that starts at about 50 euro (and it sounds like the author got an A2 - twice the size of an A3.)

I spent a decade or so of my life writing assembly, and a few years as a performance specialist for a programming team. What you're describing is a specialist skill. There's nothing wrong with it - it's a good skill to have - but there is no need to have everybody in the team have it, and you can expect better results by having some people develop that skill and other people develop other skills.

I have a problem with the leadership. OpenBSD does good technical work, but I don't want to deal with deraadt again.

Back in the 1990s, I was a FreeBSD guy, and at some point I looked over the code for a few of the popular Linux ISA networking drivers for some reason and was shocked at the low quality. The code quality of the core Linux kernel is generally excellent - the code quality of these drivers was at the level of "lowest passing undergraduate's second C program". I'd not be at all surprised if this turned out bugs giving bad performance; drivers are often considered finished when they produce the expected result, and network protocols have enough recovery mechanisms that you can get the expected result with a fair number of bugs.

The NE2000 clones worked fairly well in FreeBSD at the same time all the complaints were coming over in Linux-land. To be fair: You'd usually have less support for hardware in FreeBSD than Linux at the time (and almost certainly still.)

> If this loophole exists it probably goes against the intention of the lawmakers and would be struck down by supreme court.

It's Common law not French/European law. The intent of the lawmakers is, in common law, more or less completely assumed to be present in the text of the law. French/European courts looks to the context the law was made in and other documents produced; common law judges mostly don't (but do look much more to precedent.)

And there is of course the problem of judges in the US being fairly strongly partisan politicised (since all power in the US is partisan politicised), so the interpretation will depend on which party has lately stuffed the supreme court.

You can dual-license if you own the full copyright ownership but if you include GPLed stuff (and don't have the full copyright ownership) you'll have to GPL the result.

As for "at least as permissive" - it requires no further restrictions, but it adds a bunch of restrictions itself. And there's no other license that doesn't add restrictions - MIT adds restrictions to reproduce the MIT license, which is an extra restriction. The restrictions are attempted excused by the FSF under the "attribution" clause of the GPL, but it is not clear to me that is valid and it has not tested by any court.

For speed-architected C compilers/linkers lexing time is typically a very significant part of compilation time. The Unix compilers typically hasn't been speed-architected, instead having a focus on simplicity and ease of porting.

Where did Linux enter into it? I just don't typically use GUIs much, and I use the Mac GUI much more than I use Linux GUIs. But I've used command lines since I started with computers (before GUIs were common.)

It actually wouldn't be the same music. DJs typically adapt their set to how the crowd reacts.

See e.g. https://www.digitaldjtips.com/2011/05/dj-getting-people-to-d...

Let's not presume the development would happen if the code was copylefted.

As somebody that used program on the Amiga, using SAS C: GCC is/was terrible, speed-wise. We're talking 10-20x slowdown. Sounds like ack is on the same level as SAS C, and clang is on the same speed as GCC.

This had NOTHING to do with

> those last 8-10% of features (performance, safety, etc...) have come at an absolutely staggering price

SAS C had better generated code and more features.

It was purely a question of architecture - SAS C was architected for speed, and actively used caches (especially precompiled header files) to avoid re-doing work. GCC didn't, and I've seen no hint of that appearing in GCC since.

MacOS has been a pain for me with this; in some of the later revisions it's always a pain to get around to the right place. I don't spend time learning Mac in depth; I'm mostly a Unix person, using a Mac as just a terminal to the stuff I actually deal with (which mostly is web based or run on a datacenter somewhere.)

It's certainly fine if you work a lot locally with the Mac; but for me, the cost-effective thing has been to fumble around each time (since I only do this a few times a year) rather than memorize handling that I use so seldom.

> If the authors of software X or Y chose the GPLv3 as license I imagine they were completely aware and agreed to the terms of the license they used, including the limitations it enforces.

That is certainly not universally true. It is common, but not universally true.

And we should assume that the authors were NOT aware of real ecosystem implications of licenses - because nobody understands these in detail. I've been trying to understand them since the mid 1990s when I started contributing in a BSD environment, and I won't say that I properly understand them. I understand parts of them, but I don't understand all of them.

There is a certain total of income for salary available in a country; e.g, the US is spending about 44% of GDP on salaries/compensation[1]. The difference in income for software engineers is partially (and possible mainly) because the US is very income-inequal - ie, because there are more poor people to prop you up. If you look at income inequality before taxes and transfers[2], the US is the most income-inequal of any of the OECD countries. If you look at it after taxes and transfers[3], Chile, Turkey and Mexico manage to do worse.

[1] https://fred.stlouisfed.org/graph/?g=2Xa

[2] https://en.wikipedia.org/wiki/List_of_countries_by_income_eq...

[3] https://en.wikipedia.org/wiki/List_of_countries_by_income_eq...

> I'm pretty sure most people are in agreement that racist caricatures are bad.

I'm pretty sure most people are in agreement that wiping out history and culture is bad.

The question is what is the appropriate tradeoff. Should new editions of these books be published, targeted to children? Probably not. Should they be effectively banned from being sold (used)? At least not without due consideration to the alternatives, like marking them.

You're right - $18/1000 is 1.8, I was just copying the number from the article. So that's off by me.

However, as far as I understand, Google pays out the ads for premium customers, so you shouldn't count just the "to Google" portion. That's off in your calculation, to a factor of about 3. Using $4 (the average in $3 to $5) and 9 videos per day, we get 0.4cents * 9 * 365 = $13.14/year - a bit over a month of premium. Still devastating to my argument, of course.

I don't, but I collaborate with people that work in search, and regularly hear detailed presentations about aspects of it.

> Also, never use Google’s CDN for loading fonts or icons — always self-host them. The CDNs are used to track your users.

Any evidence of this claim? Also, given that the Google CDNs allow caching for 24h, it seems extremely ineffective even if it was done.