HN user
There is fairly new Zeiss camera that implemented the whole "camera OS" with Android and even included mobile Lightroom editing capabilities. I guess it's as close as it gets right now. My theory is that the main Japanese companies are extremely conservative and they don't pick up such changes easily - see how Canon and Nikon completely missed mirrorless and suffered huge market loss to Sony.
But of course they have - every major smartphone manufacturer is eating the whole consumer camera market alive for quite few years now.
One of very important reasons why FreeBSD haven't incorporated the patches from HardenedBSD was that their code quality was disputed and historically the author had issues with undergoing reviews and applying requested changes. HardenedBSD may do a very good job for the PR about their "superior security" but one may wonder if a system without badly implemented feature isn't more secure than the one with it.
You need to be aware that while pledge is a security technology, linux containers aren't. Pledge was designed as another security layer, while containers were designed as "management" or "separation" layer, but not strictly as security measure - read up on how bad is to run things as a root in a container.
You may not be aware, but recently Uber drivers have been recognised as actual employees in UK by the court.
I wouldn't be so hasty in saying that Jails implementation doesn't suffer either - there are dragons there too, it wasn't all just designed and written in one go, there are layers upon layers and it is not all pink and unicorns as it perhaps initially was ;)
RunC isn't "their own implementation" but rather an OCI (Open Containers Initiative) standard that world seems to be adopting and I wish FreeBSD Jails would be a part of it.
No, it doesn't and this is where an initially "superior" technology (Jails existed years ago, I was using them at least 15 years back in time) gets overrun by "inferior" tech (Linux containers), because the latter gets a user oriented tooling, packaging and so on (no flame war intended at all). Now the Linux container is much more "superior" as it catch'd up and exceeded Jails in many areas, especially user oriented readiness and integration.
Actually, you don't need another copy of userland. You merely need a dedicated space for the jailed OS (assuming we're talking OS-style jails, not process-style ones) to write the things OS writes to (devices, logs, etc.). You could get away with null mounting your host filesystem and then mounting writeable space on top of it. Once I've had read-only mounts for my jails, for funsies.
While I agree it's easy in hindsight, you're not comparing apples to oranges here: comparing the comment author to a person running a business, with very high expertise in particular subject (chip making) and general subject (technology), having access to information not accessible to others (Apple plans and visions about the product, tech specs required, price asked, etc.) is not even close to being the same thing. I can see how a much better decision could be made very realistically given that expertise and information no one else had and yet the worst possible was made.
What's the point of using Pi 4 when it is also ARM cpu? You can use the Docker beta on your M1 mac and it's going to be a better experience.
I've experienced something like that as well. Depending on what you can do, try a different monitor and/or different cable and/or different dongle. I've managed to find a combination that doesn't do that anymore.
They don't let engineers design and implement UX/UI's but instead have them create properly designed UX/UI by UX/UI people who know what they're doing? It does make sense, I have no idea where does the notion of engineers doing UX/UI came from, would we want UX/UI people to actually code the software delivering their designs? ;)
Out of pure curiosity, what's wrong with him? I don't feel his vibe so I never got into listening to him, but I was under impression he's popular and quite liked.
Your mileage may vary - I've got plenty of Amazon support staff blatantly telling me I've got no consumer rights (both national and EU) "because Amazon rules", no matter how high you try to escalate it.
Not if it runs NetBSD.
One could say that you're mixing Thinkpads from IBM era, where they were really well made (my first A21m holds a special place in my heat till this day), Thinkpads from Lenovo that are plastic piece of garbage and MacBooks from Apple post keyboard change, that was indeed faulty, but it isn't anymore. There you go, I've fixed it for ya ;)
I think I could say my workflow isn't Mac OS specific, but for my own use, I think it is. I require 1st class Unix userland tools (which WSL isn't), fast native terminal (which nothing on Windows and most on Linux aren't) and due to me not being 20 anymore, an OS that "Just Works" (which Linux isn't for sure and Windows most often isn't either) that doesn't actively spy on me (which Windows does) and runs on a well made hardware (which Mac OS does only on Apple machines). I've talked about that at lengths, feel free to check my comments, for me Mac OS is the only viable OS right now.
They are "solid" in the context of hackintosh community (not to mention non-Intel hackintoshes are considered to be less solid and more risky even by the community). I would dare to say they are not solid in the understanding and expectations of anyone else, and I'm saying that from a perspective of hackintosh user, one of the most recommended "golden builds" with components carefully selected to be as close to real Mac as possible.
And it is still full of issues, intermittent, persistent, every OS update is a stress, every Clover/drivers update is a stress and risk and so on. Yet, for a hackintosh, it is solid.
I wouldn't recommend it to anyone and I regret spending money on it ;)
Mind, I've said nothing about operating systems or platforms nor have I said about abandoning them if you don't like one thing about them. I have said, that if you don't like something and if you do come up with a better standard/protocol and convince companies to use it, it will show up on all of them (just like Bluetooth is on macOS, BSD, Linux, Windows, iOS, Android, etc.).
Until better solutions are available all companies are free to and most likely will try to find better solutions themselves and to do it in a way that will give them an edge over competition. Some more than others, and Apple here is known for being in exactly that type of business.
One could argue, that you can create an experience as good as AirPods or even exceeding it. All you need to do is to develop a 'protocol' better than the horrible Bluetooth, make it an industry standard and convince companies to adopt it.
The only reason why Apple had to (and could at the same time) work on that aspect of headphones is because Bluetooth sucks and Apple is in a business of taking things that are widely used and suck, making them suck much less and selling them for a premium price.
I think you're missing the point where I treat the "top class desktop operating system with top class unix environment support and tools" as a whole, and not as two separate things. To me MacOS is the top class desktop operating system with top class unix env support, nothing else gets close to this definition. Other operating systems could get close to other definitions, maybe even surpass it, but not to this one.
Except they aren't. I need a top class desktop operating system with top class unix environment support and tools. Windows10 might be getting close to a top class desktop os, but sadly WSL is years behind and simply feels like forced afterthought. Linux fills the unix env/tools box, but doesn't even gets close to desktop operating system quality bar of MacOS.
MacBook Air still has the physical F keys.
Not even close. All plastic, much worse touchpad and coil whine in all models I cared to check up on.
Laugh as much as you want but to me (and many others) it actually is. I would look at other manufacturers for their hardware, but sadly it's all non-MacOs and I value this operating system above anything else for my needs (work and personal).
It's Windows 95.
I know how to solve this problem, so I wasn't commenting on his comment, but rather on the fact that none of these tutorials so far solve this problem for new users that they target.
Aside from that, I don't think what he proposes is a great solution, because what we'd need is the automated way for deployments to get that DNS created (or announced) for their IP when they get it or when it changes. Having it done manually and being static is vastly different in usability from k8s does with ingress/cloud controllers.
That's exactly what I meant. I know how to do it myself, but then again I'm not the target for these articles, but when I read them with the mindset of someone who is supposed to have a use of them, that's always the big missing bit for me.
What I miss from all of these tutorials is one very important piece - how to handle network routing and dns automation within your home network, that's in typical scenario is being handled by the ingress/cloud controller. Without having automated (or easy enough) way of reaching the apps you're deploying there, each of these clusters is pretty much useless for users except for maybe learning basics of k8s, what's easier done with minikube.