Novel. A similar approach could be taken by other SaaS tools to comply with age verificaiton laws. Just write an entry to the client's hosts file that points to a subdomain corresponding to a particular birth year. Simple enough for legislative representatives to understand.
It's possible their spokesperson was not informed about SimStudio being the basis for Delve. Lots of people in sales and marketing do not know little about how open source software works.
I'm not sure "Person who answered a question didn't actually know the answer" is such a good defense, almost worse than "We didn't understand the license", because the implications of having such people in your company seems way wider then.
That is very much true. Lack of knowledge in a legal context is a very weak defense.
Generally speaking, open source ecosystem knowledge is not something that shows up in job descriptions, interviews, or regular training for non-technical staff in most software companies. Hopefully that will one day be the case but until then there is a high likelihood that misleading statements can be made accidentally.
Yes, great response. But is the failing here an individual one 'This person is bad at their job and needs more training/be replaced' or a company one 'This company only hires bad people and we shouldn't use them'
Every company of non-trivial sizes will eventually hire someone who is a bad hire.
Understandably it can be difficult for the machines of HN to truly understand, but humans don't normally have that kind of exacting control over what comes out of their mouth. Those who have carefully developed the skill of having that control don't waste their time working at struggling startups.
No, it is. Humans understand that to err is human and thus have compassion for other humans. Human expectations are placed on full timelines, not instants in time. A human saying the wrong thing simply doesn't matter to other humans as they know that words are part of a larger dialog and surrounded by a vast array of other context.
Looks good overall, but that huge seamless trackpad looks like it will be a nightmare for touch typists. It blends in so well with the palm rest that it will be hard to avoid accidentally moving the cursor if you type with your palms resting. Dell will need that extended battery life to make up for time spent correcting typos.
I have employer-provided XPS 14 9440 and it's never unplugged from the dock because this annoying touchpad issue is too much trouble.
Why would they target professionals with a laptop that has such an anti-feature? I can understand it makes it easier to clean, but wouldn't that be more important for non-computer enthusiasts who don't care for their laptops?
Anecdotally, Bhyve has worked in FreeBSD for a decade now. Eventually it got ported to Illumos because it was better than their implementation of QEMU.
Without looking at the Sylve docs, I'll conjecture that it has deeper integration with ZFS. With a foundation on FreeBSD, there is a likelihood Sylve can support ZFS-on-root rollbacks better than hacking it into Proxmox. A rollback capability is why I'm looking for Proxmox alternatives. In the Linux world, Talos Linux and IncusOS provide A/B updates which achieve a similar rollback capability. With something based on FreeBSD, your "immutable" OS and all of it's data can be treated equally as ZFS datasets. There's also a higher risk that a Linux kernel update will break ZFS.
Regardless of the number of drives available, you gain an advantage when your file system can leverage snapshots to roll backwards or forwards. There are other Linux-native filesystems that can provide this capability too, but many admins prefer ZFS because the full range of capabilities is unparelleled.
Perhaps I'm missing your point, but proxmox+lxc on zfs storage works fine in proxmox? If just looks like any other storage in proxmox and on commandline you've got all the usual zfs tools
I think it comes down to the standard argument against ZFS on linux -- uncertainty. It works *now*. Will it continue to work? Will any upstream changes in the Linux kernel cause issues with the ZFS modules bolted on top?
It is unlikely for there to be issues with ZFS and Linux. It's too common now, but it's not included in the main Linux tree, so it's not explicitly tested.
So, it's a low risk, but not zero risk.
More to the point here, when working with FreeBSD, ZFS is a first-class citizen (moreso even), so working with it *should* be more integrated with a FreeBSD solution than Proxmox, but how much more (and is that meaningful) is probably a qualitative feel than quantitative fact.
Folks using TrueNAS or unRAID for backup instead of safe keeping, and then get mad when everything goes sideways and the data is gone. Your NAS must have a backup elsewhere, snapshot and what not won't save you if everything goes RIP.
ZFS is redundancy and redundancy only, but people see ZFS as some sort of backup. That is silly and wrong.
>A rollback capability is why I'm looking for Proxmox alternatives.
Your VMs and LXC container should have an automated backup. Proxmox itself takes a second to clean install it.
I had to change the motherboard and had to literraly install Proxmox 9.1 from scratch. BUT.... before doing that, I checked the LXC backups sent to a TrueNAS spool in mirror for safe keeping.
Reinstalled Proxmox, mounted the NFS share on Proxmox and voila, all the LXC containers were restored and started like nothing happened.
I wonder if my grandmother had heard of this book. She lived 10 minutes from the German border in the Netherlands
During this time, she mentioned there were radioactive clouds flying in from Chernobyl.
Isn't it more plausible that she mentioned there were radioactive clouds flying in from Chernobyl, because there were radioactive clouds flying in from Chernobyl? After all, it were the even further away Swedes who discovered the fall out from Chernobyl first and alarmed the world.
reply