wicket

It's not so hard, the author is just using the wrong OS. VMS saves new files versions for every disk write and now that it runs on x86 [1], there is little excuse to not use it. :D

[1] https://news.ycombinator.com/item?id=26169179

A very well written comparison of XMPP and Signal, but one thing that the author seems to overlook is the significance of Signal using phone numbers as user IDs. This is what users have come to expect and what makes Signal a drop-in replacement for WhatsApp.

Leave your comfort zone. Move to another country, learn a new language and embrace another culture.

Strenuous? Not in the slightest. The ISA and the original chip design is from Arm and is licensed to Apple. There would be no M1 without Cambridge.

>Also, they should insist to change "Made in China, designed in California" into "Made in China, High-tech from Taiwan, rest of the design from California".

Cambridge, England (Arm) should also be in this mix.

Over the years, I don't think I've ever been able to explain to anyone that their memory error could have been caused a cosmic ray without being laughed at.

Not really surprising that they are recommending SHA-1. It's well known that the UK is a nanny state that hates encryption.

I'm seriously struggling to think of a use case for why I would want to use web browser to use a CLI tool.

As far as I'm aware, if you go for Orka Cloud, you only pay for the physical Mac, not the VMs. I've no idea about the hobbiest market, I've only used MacStadium for a large company. I didn't personally make the purchase but that's the information that has been relayed to me.

> Yes it does. The Xcode GUI only allows one build at a time, but you can run multiple `xcodebuild` command line builds using the same or different versions of Xcode in parallel, even under the same macOS user.

This isn't true. "xcode-select" forces you to set a system-wide Xcode version. If you have a job that uses one version and a concurrent job selects another version, it will potentially break the first job.

Okay, so it should be possible then. That brings me back to me original question of why isn't there a XNU hacking community?

> And it's not like you can re-compile your changes to xnu back into a working MacOS machine

Wow, that's just awful, but it would it explain it. Thanks!

> For comparison, you can rent an equivalent Mac Mini from MacStadium for $139/month, $1,668/year. Or you can rent their cheapest model for $59/month, $708/year.

> You can also buy the equivalent Mac Mini for $1,899.

Not only that, but MacStadium lets you run multiple VMs on a single Mac at no extra cost. Amazon's offering is seriously underwhelming.

The more I use or learn about MacStadium, the less impressed I am with it (3 layers of virtualisation is overkill in my opinion!), but it beats the hell out of what Amazon has just announced.

The big problem with CI/CD on Mac is that Xcode does not allow you to run builds in parallel, so you need one Mac per build unless you use virtualisation.

To be honest I'm surprised that no one has added namespace/jail support to macOS yet. The XNU kernel is open source so this should be possible. In fact, can someone explain to me why there doesn't seem to be any sort of XNU hacking community?

> Private and secure.

As long as it's sending data to Apple, it's anything but private.

I don't know what desktop environment/window manager you are using, but in i3 I can just press $mod+f to exit fullscreen and it will appear as a normal desktop app.

As far as I can tell, kiosk mode does pretty much the same thing.

firefox -kiosk [URL]

It's worth noting that there is also the hilarious PonyOS which is based on ToaruOS. The main website[1] seems to be down right now, but you can check it out on GitHub[2].

[1] http://www.ponyos.org/

[2] https://github.com/klange/ponyos

For those interested in the story behind this, there's this interview with the developer Randy Linden:

https://www.youtube.com/watch?v=P5PknJvplKg

Maybe next time they could include mini laptops such as those from GPD, One Netbook, Chuwi and Topjoy.

And now we've gone full circle. One of the proposed use cases for containers when Solaris Containers came about (and probably also FreeBSD Jails before it) was that you could easily give a software developer a full OS instance to play about and break stuff or to do whatever they desire, instead of restricting them to the confinement of their home directory.

I appreciate your sentiment, but I don't know, I'm not convinced. You can have all the GUIs and WYSIWYGs you want, but as I said, email replies should default to the same format as that of those received. Thunderbird (a modern email client) does this, if I recall correctly. It's very easy to avoid this mess.

I don't think it's hyperbolic. If someone has sent you an email in plain text with wrapped lines, your mail client will know this and it would be reasonable to assume that perhaps the sender may be using a mail client not capable of rendering HTML emails nor autowrapping long lines. It would be a sensible choice to format the reply in the same format as that of the email received.

By stating "HTML email has features that most people actually want. The world has moved on...", you seem to be implying that the primary method of communication of Linux kernel developers is irrelevant and their use-case for email is not important. In fact, the more I think about this, this is a classic example of Embrace, Extend, Extinguish.

It looks like they are already at the "Extinguish" phase for email. Try reading this:

https://lkml.org/lkml/2020/5/19/1527

:(

Is this a library or an SDK? Why on earth would you install an SDK on an end-user's phone?

Well this really confused me as I thought Microsoft had discontinued the Windows RT operating system. It turns out that they also have a platform-agnostic application architecture, ingeniously named WinRT.

When I picked up Docker, I had already been using other container technologies for several years so I personally don't know of any modern or complete learning resources that I can recommend. However I would recommend starting out by understanding what namespaces are, i.e. how container isolation works. You should also be aware of what cgroups are and how they are used, but you won't need profound knowledge of them when starting out. The man pages [1] [2] might be a good place to start.

[1] http://man7.org/linux/man-pages/man7/namespaces.7.html

[2] http://man7.org/linux/man-pages/man7/cgroups.7.html

> If you’re trying to learn Docker you will first have to master its various terminal commands.

This is completely the wrong way to go about learning Docker. The biggest problem with Docker is that there are too many people using it who claim they know Docker because they learnt a few commands they read on the internet, but they don't actually understand what a container is. In reality, this leads to all sorts of problems, like the deployment of insecure containers in the wild. Guides like this are recipe for disaster.

I found it interesting to compare the four chown manuals (POSIX, GNU, FreeBSD and OpenBSD) and can see why the author may have been confused about the -h switch.

The POSIX manual is the only one that explicitly states that -h applies to each file operand (as opposed to files encountered during the traversal from -R). The SYNOPSIS section also makes it clear how it differs.

FreeBSD kind of gets it right, but without the word "operand" it could easily be misinterpreted.

GNU uses the word "referenced" which could also be open to misinterpretation.

The OpenBSD manual doesn't really make it clear at all, but kind of implies it with the comment about -h and -R options being mutually exclusive.

I hope the pizza arrived in a SPARCstation! ;)

I don't dispute the triviality of setting up your own log bot; I was merely pointing out that Freenode is not solely used for informal chat.

You bring up an interesting point about GPDR and aggregate logging. The same probably applies to mailing list archives.