Since we're in the EU, as is Hungary, in fact, yes, we do!

Not that Akamai's State of the Internet is worth a damn anyway, with the throttled shit we have to deal with in the nordic countries. Seriously, Akamai is crap here. Steam, Limelight Networks etc etc, I can max out my 100/100 connection. If it's Akamai, it slows down to like 20Mbit/s.

Personally, I like the quieter cars, both in everyday traffic and in racing. Unlike many others, I enjoy the new turbo V6's in Formula One for example, and it would be interesting to see how much faster the turbo V6's would be than the previous eras if they were allowed to use the aerodynamics regs of those eras(That's what actually slowed down the 2014 F1 cars, the greater restrictions on aero).

I also enjoy the LMP1 hybrids that are much quieter than their spiritual ancestors, the Group C prototypes.

For me, within a given engine type, more noise=less impressive, since it shows that it's badly engineered and wasting energy.

There is a way to work around that. Create a VHD on your network drive, mount that VHD as a drive via disk manager, point backup to that drive.

6 WD Red 2TB disks split over 3 VDEVs, sector size is set correctly etc. No encryption, no compression. And it makes no difference whether I use NFS or Samba.

ZFS is something with which I have yet to familiarize myself with the internals so I can only guess, but my initial impression is that it's similar to older unix filesystems(and why Silicon Graphics developed XFS) in that it is not that good at handling many large files simultaneously. So I have the original video clip, then I have individual folders with the RBG channel images, the alpha channel images, the shadow maps, etc etc etc, meaning that for each second of 3D animation there's hundreds of images.

I've recently gone back to my roots and started dabbling with 3D animation and compositing again. My fileserver is a FreeBSD machine running on a decent 64-bit CPU with 16GiB RAM, with ZFS. And let me tell you, ZFS is dog slow for some uses, without it being anywhere near full. In my case, lossless-encoded video, and directories with thousands of 4MiB+ images, and working against that in realtime(or trying to), the filesystem stalled out at 80MiB/s, while my old fileserver running Linux and XFS easily saturated the gigabit link

The mainframe people I know, when they rarely refer to transactions, have a slightly different meaning from when windows or unix people do it. The mainframe people more often rever to messages, which is a whole discrete task, which can often require multiple database transactions, some computational passes etc. They usually talk about hundreds of thousands of messages per hour, so if it's 2.5 billion mainframe-style "transactions"(messages), it's pretty damn impressive.

Let's not forget something as simple as debugging. Someone who understands the hardware and knows Assembler will always have an advantage when it comes to debugging.

Hardware should always be a concern, because hardware is the reality that implements the abstraction of a program. No matter how efficient something is in purely mathematical terms, it's the hardware that determines the actual performance, complexity and problems. ISA, I/O capabilities, amount of RAM etc all matter in deciding what will be the best way to implement something.

No matter how many layers of abstraction you put in to provide the illusion of being able to ignore the hardware, the reality of hardware will always matter.

Nono, like other big IT projects in the UK, it will be using "the very latest in Agile know-how", and cost 3 times as much as any clusterfuck that involves Oracle, take 50% longer, and spread 300% more blame on "old fossiles"....

Disclaimer: Had to interface with a EU project under UK IT auspices last year.... Painful....

While your faith in the religion of liberretardianism sounds fun, history empirically proves you 100% wrong.

Except that the Xbox One runs Shadows of Mordor at 720p and 30FPS. An el-cheapo PC built now can run Shadows of Mordor in 1080p and above 60 FPS stable, and with better details etc.

Something I wish I could have in a workstation again is a full-fledged crossbar switch like the Octane and Octane 2 had.

Even with emergency shutdowns, you can still get massive damage

Data invariance, even if you can somehow implement it properly on a hardware level, does not protect you if it's the execution pattern that is the attack method for example.

As an example, rapid power cycling/power state change due to a program swiftly being shunted between CPU intensive and idle threads, etc can cause power surges that can damage the PSU or the motherboard or even the CPU(as voltage regulators etc move onboard, they become ever more vulnerable to this), and for all intents and purposes the data input to the program will be fully valid and unchanged. Excessive head parking on a mechanical HD can cause the HD to become faulty. Frequent standby/active cycles on monitors can kill them fairly rapidly.

As for the emergency shutdown, nowadays, with modern equipment, the big red button and the emergency shutdown button in the control program do the same thing: Send a signal to the correct circuit and halt all operation. In some heavy machinery that means just cutting all power, in others it disengages pneumatic valves and thus engaging mechanical brakes etc etc. It depends on what kind of machinery it is.