I run zfs as the storage pool for my incus (next lxd) services. It is the ideal fit. Here is a list:
- Instant, zero-copy container cloning from images via Copy-on-Write. If you boot a new image like the existing ones it's seconds.
- Atomic, millisecond-level instance snapshots regardless of storage size
- Block-level container migration using native 'zfs send' and 'zfs receive', very short command lines and seems to work perfectly.
- Granular dataset nesting (every instance, image, and custom volume gets its own ZFS dataset). You can see every filesystem even on the host.
- Transparent, inline data compression (LZ4/ZSTD) enabled automatically per dataset. For services that don't change much, you might as well use a compressed image to make them even smaller.
- Mirroring / Raid
- Sub-volume sharing and direct management via native ZFS administration tools. If my home directory has a build area and a million files, I can just save time and put my home, pre cooked into a new machine and not copy or even rebuild on my new machine.
- Dedup keeps blocks with the same data as a reference. This costs a lot of memory and has not saved much for me as a lot of my images are similar and already shared I think, but it's cool.
I have a 15 year old Mercedes. I got the old integrated CD player and radio pulled out and Alpine makes a nice dash surround and canbus support module for the steering wheel controls.
It has a 7" display where the old stuff was and wireless Android Auto.
It's pretty much like any new car as far as entertainment and maps. Plus, it's got physical buttons for everything else. I think recent cars may well be coming back to what I have on my old car.
ps. not mentioned, Anrdoid auto and Carplay are H264, later H265, video players with touch control and buttons in a return channel. The phones render the display internally and project it as video to the display. That's all. This is why much older generation displays with at least reasonable SOCs can run them near perfectly. They are not running Anrdoid themselves. In fact some of them are operating system-less SOCs that have nearly no firmware but a video player and the support for the touchscreen and buttons. Much like that crappy video player built into old TVs ten years ago.
I have them on my motorcycles too. It's way better than a phone, in that the user interface is designed to be less interactive and more focusses with larger buttons.
> Only extremely wealthy people participate in stock markets, in general. Other people use one of those wealthy people as an intermediary.
This confuses a retail investor with a Clearing Member.
Anyone with a phone and a $10 brokerage account has direct, sub-millisecond execution access to US equity markets. Brokers are not wealthy patrons acting as gatekeepers, they are licensed utility providers providing the technical pipeline to the exchange, just like the power distributors who cable and sell you power. They are providing a managed service, being a direct link to the exchange. There are some platforms that are not DMA, direct market access, but there are numerous brokers who offer DMA. I personally don't trust non DMA access, but maybe for larger orders, it might be good to have a man in the middle as a service.
The graph on Google is a trade feed, the last traded price, not buys and sells. If you sign up to one of those discount brokers you have a feed of those buy and sell orders, the order book, live, not delayed like the google trades. No one gets the names of the people buying and selling until settlement. (How I know, I write that code that builds the order book and matches the orders for a living). Not even the brokers.
True large firms trade large orders amongst themselves so they can get a more stable price, but US regulators explicitly mandate real-time reporting for off-exchange and private trades. Once they trade a listed instrument they must report the trade within 10 minutes. Yes they do, this part is highly regulated, if they don't they will be penalised. It's also in their interest as the more pricing, the better the prices. (No conspiracies here, some people have broken the rules but the code is pretty easy to write to make sure this happens, I've worked on that too)
This is all false in modern days. What you are saying was pretty true 100 years ago, except the google bit. I'm pretty sure you didn't take your meds today.
This is exactly why I call it 'resume++'. You have to use it to attract talent. People want to use it to expand their employment pool. This is not justification to using it.
To use it is a whole different question, and not in any way related to job interviews. I have worked in places that are crazy for not using it and others where using it was even crazier.
A power function seamlessly maps 0 to 0 and 1 to 1, easy for black to white.
An exponential/log function requires arbitrary clamping or offsets because you cannot represent pure black, 0, on a pure log scale without hitting negative infinity.
Basically, it fits better, aside from a good map of human perception
I've been a developer for 40 years. Used VC since rcs. If only people had such pedantry for the actual code, the world would be a better place. I look at the author way more than I read a commit message, next the date and then the code. Never much else.
I have tried one. It has no torque. For what looks like an awesome product, it does not have the power to drive a peristaltic pump. I used the same motor on a TMC stepper controller and it's completely silent and works. It's open loop, so comparing apples to oranges but I am not sure what the MKS servo driver on a motor could actually do, aside from spin unloaded.
It's not me. I actually work for a living and I receive a salary.
Many people I know with their own business plan to hopefully get out of it some day. They all make less than me but own a business of their own.
Let's say this works and those people who already have assets get taxed a bit more, when they are gone, there would then now very little incentive to work hard and start a business.
Such short term thinking will pretty much destroy the economy in the long term. You can't tax an economy to health and fairness.
ps. Australia uses a progressive tax system. If you earn very little money, you pay a very low tax rate (or many zero). If you earn a massive corporate salary, you pay the top rate.
The new 30% floor completely throws that out the window for capital gains. It means even if your total income for the year is low enough that your normal tax rate should be 16% or 0%, the government steps in and forces a flat 30% tax on the asset sale anyway.
So, contrary to what the government is saying, this new regime taxes the poorer even more.
I'd assume, as an Australian, who works for a HK company and has travelled for work all their life, the long term lifestyle in Australia is probably better than those countries. I love HK and Singo but I am not sure I'd want to live there. But for working, most people here would not work in an iron lung and the socialist government pretty much supports the idea that, if you don't like to work, you shouldn't have to as long as there are a few who will work. And, that number is fewer and fewer.
Never to feed the trolls ... but, how does my carpenter deserve $100 an hour when he is using an electric drill and power saw I can get at Home Deepo for $100 bucks?
Most good developers are not employed because just because they can code well.
What is over is: fizzbuzz and trivial CS algorithm regurgitation as a gate.
- Instant, zero-copy container cloning from images via Copy-on-Write. If you boot a new image like the existing ones it's seconds.
- Atomic, millisecond-level instance snapshots regardless of storage size
- Block-level container migration using native 'zfs send' and 'zfs receive', very short command lines and seems to work perfectly.
- Granular dataset nesting (every instance, image, and custom volume gets its own ZFS dataset). You can see every filesystem even on the host.
- Transparent, inline data compression (LZ4/ZSTD) enabled automatically per dataset. For services that don't change much, you might as well use a compressed image to make them even smaller.
- Mirroring / Raid
- Sub-volume sharing and direct management via native ZFS administration tools. If my home directory has a build area and a million files, I can just save time and put my home, pre cooked into a new machine and not copy or even rebuild on my new machine.
- Dedup keeps blocks with the same data as a reference. This costs a lot of memory and has not saved much for me as a lot of my images are similar and already shared I think, but it's cool.