Rounin

I wonder what it would take to swap out the top layer for a FUSE layer? After all, ten thousand lines is comparatively small, but still a lot of work. On the other hand, having at least one modern file system with most of the bells and whistles that worked everywhere would benefit a lot of people.

A lot of articles and videos are reporting on this, but so far there's very little comprehensive information about what brands don't do this.

Clearly, the 25 major brands examined by Mozilla collect a ton of data. Allegedly, BYD does so as well.

What about the Slate truck? Was that even released? What about some of the Indian brands? Surely there's some useful car being produced somewhere that's just a car?

As far as adoption is concerned, I'm not sure it should be that big of a concern.

After all, D is supported by GCC and Clang and continually being maintained, and if updates stopped coming at some point in the future, anyone who knew a bit of C / Java / insert language here could easily port it to their language of choice.

Meanwhile, its syntax is more expressive than many other compiled languages, the library is feature-rich and fairly tidy, and for me it's been a joy to use.

Many projects have taken longer and been more stressful and had worse outcomes than needed. A lot of the work being done hasn't even been intended to deliver any business value, but to provide an opportunity for one or more people to be seen to be doing something. Actual value creation does occasionally take place as well, but more as a happy accident or a side effect than anything else. I'm very glad I'm not a major shareholder in any of these corporations.

Problems with scaling have been the biggest timewaster in my career:

1. In some large businesses I've worked in, so many people have been hired that some systems and processes have wound up being controlled by entirely different people from the people who need them. So coordination between people and waiting for people who have little to no incentive to do the thing they're being asked to takes up a large part of the working day.

2. In other businesses, a large fraction, or even a large majority of the employees have had no discernible job except to talk and write about the job performed by the few people doing an actual job. So a lot of time in these businesses would be spent dodging meeting invitations, rejecting grand ideas about revolutionizing the business with AI on the blockchain, saying no to "if you could X, that'd be great" and generally reminding people that they're not in charge.

The great thing about these problems is that you're not very likely to have them in a small startup, but if you decide to grow the organization later, you'll need to be very vigilant about how you scale.

I forgot that there's an "11.0.0" as well. Perhaps others have been added since.

You should be able to make it think you have another card: export HSA_OVERRIDE_GFX_VERSION=10.3.0 The possible values are said to be: # gfx1030 = "10.3.0" # gfx900 = "9.0.0" # gfx906 = "9.0.6" # gfx908 = "9.0.8" # gfx90a = "9.0.a"

D. It's quite C-like, but more concise, has a richer standard library, garbage collection, threading, etc. etc.

For looking at the commit history rather than the files, apparently one can use git-ls-remote .

Perhaps something like this to get just one commit with no large files: git clone --depth 1 --filter=blob:limit=100k

Recompressing an already lossily compressed file is almost guaranteed to produce information loss, whereas storage media is getting cheaper and cheaper over time. An 18TB hard disk is now within the budget of many people, and they're likely to get cheaper still.

So if your purpose is to archive these files because they're worth keeping, buying a bigger disk may make even more sense.

Retirement?