3 ms·
Heh, it's like http://dtrace.org/blogs/wesolows/2014/12/29/fin/ http://dtrace.org/blogs/wesolows/2014/12/29/fin/ but from a different angle. I personal, naive
by Ericson2314 10y ago
Heh, it's like http://dtrace.org/blogs/wesolows/2014/12/29/fin/ http://dtrace.org/blogs/wesolows/2014/12/29/fin/ but from a different angle.
I personal, naive as it sounds, beleive nix* (as in e.g. NixOS) could be a silver bullet here, but the market is so used to IT being inherently shitty I don't believe it will happen.
- deleted 10y ago[deleted]
- nickpsecurity 10y agoThanks for the link. I didn't know Cantrill basically imploded. His gripes on Pike's comment and industry mimicked my own. He's way overstating how much people ignore the system level as there's active projects handling it funded by NSF, DARPA, and EU with a practical focus. Most practical being ones with defense contractors (esp Galois) or actual engineers partnered in. Quite a few going from software to firmware to hardware with some to the gates. He could possibly enjoy himself and do some good getting hooked into one of those groups to cover pragmatic, real-world aspects plus spot opportunities as development goes on. "beleive nix* (as in e.g. NixOS) could be a silver bullet here" Come on, now. Try to avoid that trap. You need to look at what the market needs in compatibility/legacy, production worthiness, talent to aid deployment/support, security, and so on. Always consider these plus target markets when evaluating any software platform. NixOS at first glance appears to fall short in quite a few. Now, what I do like about NixOS is its declarative, transaction-oriented packaging. That's great if implemented well given my Linux distro's screw that stuff up to this day when I install an odd package with one incompatibility in it. Irreparably breaks system or appears to. (rolls eyes) Source-based is debatable but allows site-specific optimizations. I'm barely in the debate but lean against systemd, which Cantrill's post mentions incidentally, as it's too complex to be in critical position it inhabits. Critics pointed out a simple thing in its spot plus less privileged services doing management or whatever. Consistent with best practices from high-integrity & high-security engineering going back decades. So, I see it as a weakness albeit a small one in larger picture. So, there's my two cents on that link and claim.
- intherdfield 10y ago> Thanks for the link. I didn't know Cantrill basically imploded. That wasn't written by bcantrill. He hasn't imploded yet, as far as we all know. Unless that was when Oracle bought Sun and he's been operating in the imploded state since.
- nickpsecurity 10y agoOops. Part of the page didn't render on the device I was using. Couldn't see the name. Thought it was him with the illumos and joylent references. Thanks for the correction! Note: So someone else that worked there was imploding and could use some time at aforementioned projects clean-slating or improving HW/SW architectures. :)
- Ericson2314 10y agoYeah this is somebody else doing Fishworks->Oracle->Joyent. Original HN thread on the blog post btw https://news.ycombinator.com/item?id=8816055 https://news.ycombinator.com/item?id=8816055.
- nickpsecurity 10y agoAhhhh. Ok, all clear now. Thanks to both of you.
- jclulow 10y agoI sit next to Bryan, and to the best of my knowledge he has not imploded!
- Ericson2314 10y agoBTW original thread https://news.ycombinator.com/item?id=8816055 https://news.ycombinator.com/item?id=8816055 . > His gripes on Pike's comment and industry mimicked my own. Yeah I always found it funny that many of the ex-fishworks people don't like Pike's 2000 paper, which is essentially the same complaint as theirs but different specifics [s/(Unix|Windows)/Linux/ s/Plan 9/Illumos/]. As I think both are interesting, a set up the right direction, and not quite radical enough, I'm especially inclined to see the similarities. > He's way overstating how much people ignore the system level... I'm a huge fan of Galois too, I think there is a legitimate complaint that most of industry only look this far down the stack where they must, e.g.. embedded systems or real-time where desktop hardware and a mainstream linux won't do. From reading many of your past posts, I get the sense we both think different operating systems, or even hardware, should (eventually) get used all over. I get why for projects due in a year go the path of real resistance, but I think the economic argument that e.g. Google should be designed something post-unix for 15 years is pretty rock solid. And yet I don't see them or anybody else (since Midori was cancelled) doing that. > Come on, now. Try to avoid that trap. First of all, to be clear I responding to the OP more than what I linked. That I interpreted as infrastructure around Unix (or Windows? Haven't read up on OpenStack), not OS work or something lower level. Looking at innovation on the whole stack, I consider nix* more "silver ductape" than "silver bullet"---it made personally using Unix tolerable :). > compatibility/legacy So yes nix changes the way unix is administered---and if you use it without changing your ways you will miss most the benefit. At the same time nixpkgs demonstrates that it is feasible to shoehorn-in software that wasn't designed for this with few--no modifications. I think enterprise has sunk more money into their devs' Java monstrosities than ops' perl scripts, but I could be wrong here. Also if your are running some "pre-cloud" "pre-container" "ancient" setup---on a heterogeneous pile of old desktops in a closet even!---I think nix* would actually allow one to change well than some more popular technologies. > production worthiness, security I don't think anybody as really audited the nix* ecosystem to the degree that some users would require, but people do use it in production. > talent to aid deployment/support So Nix has great fundamentals with a crappy user interface. Now maybe i am a masochistic idealist, but I think that's better than the reverse because it's easier to rewrite a misdesigned UI than misdesigned foundation. > That's great if implemented well It is. Sandboxing for security is a little WIP, but assuming enterprise users wouldn't install things willy-nilly, the real risk is more shitty software than malicious software, and Nix for a long time has been fully capable of dealing with the former. [And by shitty software I mean the thing being packaged. I don't know how one would fuck up the packaging itself: that either works and properly encapsulates things or doesn't work.] > I'm barely in the debate but lean against systemd I am completely out of the debate, but do note NixOS doesn't need systemd (or Linux!) for any fundamental reason. Indeed if we had better CI and better delegation on code review and merging PRs (my biggest gripes with nix*), I'd have expected somebody to have fixed this by now. My personal goal (which I think is common in the community) is all the features, none of the policy. Support all distros' init etc decisions; support Linux Darwin, BSDs, Windows + MSYS2; and so on. [I actually think the Joyent people should be all over NixOS as a way to make moving between Unices painless, but they have gone with lx-branded zones for that.]
- digi_owl 10y agoWhenever i run into anything from ex-SUN people there seems to be a truckload of sour grapes towards Linux included. What this article complains about Pike doing can just as well be leveled at the article author (and colleagues) vs Linux.