zwerdlds

2 things:

- IMO, having owned a couple readynas(es) in the past, FreeNAS is a good compromise between ease of setup and functionality. To me, it does not feel over-engineered. In fact, it feels like it gives you enough to do everyday stuff easily through the UI, and drop into ssh if necessary. I've only had to do this a few times. To wit: I would take a stock FreeNAS over manual setup anyday.

- The 2 disk failures I've experienced were independent of each other. I have not experienced a simultaneous failure of 2 drives. I have preventative measures in place, namely in the form of a hot-spare for the pool and an aggressive resilver schedule that runs weekly.

Programmer's opinion here: I'm not a sysadmin, just like to do light HomeLab style hobby work at home.

I can't provide a counterpoint for why you might consider a proprietary NAS, but I can tell you that I'm 90% sold on FreeNAS. I've built two servers running them from commodity hardware and never once had a problem with it.

I use rsync to backup to my older NAS no functioning specifically for that purpose. It's a ReadyNAS x86. I moved away from that because I wanted more functionality and redundancy.

I've had 2 drive failures on 5-disk setup. Live rebuild in degraded status worked as well as it should have. I also use the SSD caching feature which sped things up a bit for frequently used files.

My only qualm about the product is that whole versioning fiasco. I actually almost got bit by it while building a server for my parents, but the install wouldn't take so we used the older version. But by the grace of luck we didn't use the bad version.

I use separate hardware for my service host which talks over NAS. I just use the FreeNAS boxen for storage. Learned that lesson!

I was going to take issue with you're "this is the answer" description but sure enough, on the featured snipped "About this result", Google interchanges the word "answer" and "result" pretty arbitrarily:

When a user asks a question in Google Search, we might show a search result in a special featured snippet block at the top of the search results page. This featured snippet block includes a summary of the answer, extracted from a webpage, plus a link to the page, the page title and URL...

Just to offer a contrary pov, I have a gigabyte brix that I use as a headless VM cluster workhorse - worked fine with the headless HDMI dongle.

Not having worked with COBOL in about 10 years, the critiques I have of it (from memory) are virtually identical to some modern languages I still have to work with daily.

It's - Too structured. - Poor tooling. - Whitespace sensitivity. - No first-class functions.

But the article is right - if these same standards were applied to today's languages, things would be a lot louder.

Additional reading: https://www.hanselman.com/blog/DarkMatterDevelopersTheUnseen...

You can buy certain OEM android devices not only rooted, but with unlocked bootloaders.

It'll be a cold day in hell when Apple does anything remotely similar.

I hope you're right. Time will tell.

If it can't happen to Transocean after Deepwater Horizon; If it can't happen to PG&E after San Bruno; It's not happening here.

I had this exact feeling as well.

Complexity comes about when systems integrate too closely. If you're running multiple systems in the same environment, eventually, they have to work around each other, or it leaves the temptation to take advantage of what's there anyways. Docker establishes firm boundaries and reduces the cognitive load of the developer and ops teams.

Pedantic, I know, but the projected beam was it's power source. It had no _built-in_ power source, which is pretty cool, all the same.

Oi... XML wasn't the first format to be used for data interchange and encounter these problems either. At least JSON is designed for data interchange in the first place...

Too many tools? Are you not selective about what tools you use anyways? The field is decades old. Do you program in assembly? Fortran?

Yes, that was my point.

Not a genuine answer, but JavaScript has a great ability to inspire respect for type systems, due to that duck typing.

I suppose the GP enforced it manually?

The repo has updates from just a few days ago, and IIRC, v2 just came out at the beginning of last month.

So I'd say no to "Is it dead?" Is it dated? Well I stopped using it once I found Docker (years ago), but can't say much for others. I'd be using it if I targeted other hosting platforms than Linux.

https://github.com/hashicorp/vagrant

Sorry, not my numbers - as noted in the comment, I took them from the press release.

Let a thousand 'Markup Language's bloom.

No offense intended, but you may want to start with WCAG 1.4.6 as a baseline. It's entirely possible to create a modern, compelling UI in conformance to basic accessibility guidelines.

It's been a while since I used these UIs, but usually what happens is you click on the knob and it turns into a vertical slider. Not so bad really.

The skeumorphic UI lets you move between the physical panel and the GUI pretty seamlessly. Not saying there isn't a better option, but this at least is pretty nice for beginners.

for anyone else interested in the actual stats, I grifted this from their pr on the image:

The minideb image currently weighs in at around 50MB uncompressed. For comparison the debian library image is 123MB, the alpine image is 5MB, and the newly released amazonlinuximage is 328MB.

I was trying to rationalize it this way:

1980's - first decade

1990's - second decade

2000's - third decade

2010's - fourth decade

I guess, technically, the third decade of age for this paper ended in 2016, making 2017 the fourth.

But this seems like silly ways to rationalize it. Genuinely seems like a typo.

See also regardimg the Gerasimov Doctrine: http://www.politico.com/magazine/story/2017/09/05/gerasimov-...

Anyone who has to work with the clowns in the credit reporting biz knows that this data is probably sitting on some COBOL-backed shimmed-out VAX talking to drum memory storage.

Hey now. Accenture is a totally different company. They have reliable analysts who do good work.

/s

Having done big and small consulting work, I think part of the issue is that waterfall still has quite a large buy-in. Smaller shops tend to go more agile, but when you have a team of analysts chomping at the bit to document your processes and say "yes, we can do this" (regardless of if they actually can) that builds confidence.

And that confidence is what moves the project forward, until the customer sees dates slipping, at which point it's too late.

Unfortunately, the title is correct. The product being launched here is called "Chrome Enterprise".

I'm slowly losing my sanity between this and the .Net Core.

The question of whether he is guilty of this particular crime is what this particular trial is about.

Concessions regarding past behavior are usually saved for the sentencing portion of the trial.

Anyone care to give a first blush comparison vs protobuffs/json schema?

Tough crowd.