horusthecat
> In my experience, the most technologically savvy F100's are all VERY familiar with utilizing in-house dev, and as recent releases from AWS/Azure might suggest (SQL Server on linux, Aurora support for postgres/mysql, etc) OSS is a key part of this as well.
Ding ding ding fries are done! Oracle is deeply concerned with losing customers to PaaS and Saas providers. Part of Oracle's current model is to push its mixed and private cloud offerings for their customers--AWS and Azure have a huge share of that market already.
It's Oracle, though, and they have a huge presence in the gov't sector... They're trying to reclaim that as much as possible by moving in on the Trump Administration's transparent give-aways to favored parties.
1. I work in a backwards enterprise shop where "no one ever got fired for choosing Microsoft" and it would be easier (read as "possible) to get IT here to support it than Postgres. (That said, they do support Mongo internally but won't admit that to software teams)
2. It's much cheaper than Oracle, which is the other "enterprise" database where it's easier to get an install done
3. It's not Oracle
A few millenia from now archaelogists and historians will be pontificating about Hollywood the way we do about the Pyramids.
Power 32 bit is dead. Apple never ventured into other architectures. macOS (and OSX 10.whatever plus since the mid 2000s) are running on x86 and stumbling towards ARM; iOS runs on ARM. It's still commodity hardware, just like Windows and Linux.
I understand that Apple supports a much smaller set of hardware and drivers, but in my mind it's not really 'integration' the way, say, dinosaurs like SPARC + Solaris or POWER virtualization under AIX is integrated hardware with software. I'm really just being cranky here and splitting hairs.
But with the current administration as well as Congress (we're likely to see a Federal gov't shutdown over the budget even though the Republicans control the legislature and White House), I wouldn't anticipate seeing any regulation down the pike because of this.
They mention the Struts vuln, but not which one... did an attacker access the info directly via a naive attack, or was this a campaign? Having worked on Enterprise-Ready(tm) systems I wouldn't be surprised if Equifax had an unsegmented network...
Additionally you're assuming the only motive behind mining bitcoin is the value of bitcoin, effectively ignoring realities like, e.g., that entities use it to avoid capital flight regulations.
It's basically a field day for consultants and for appliance vendors. I'm not a huge fan of NIH but it's really demoralizing to see money get spent on toys that immediately get locked up in the attic.
I will co-sign to this every day of the week and twice on sundays. In our org chart, developers are not "IT" and getting nearly anything done that requires involvement from IT borders on impossible.
I honestly will probably never work for this sort of Microsoft/Oracle/IBM shop ever again unless I get a blood promise I can use a Mac or Linux workstation, get on-demand development VM creation, and have absolutely 0 Oracle product I'm required to integrate with.
The org I work at is so old that it still has groups with "Wintel" in their names, but the UNIX guys (the majority of our non-windoze stuff is AIX) aren't any better. It literally feels like I'm in a time warp back in the 1990s.
Some horror stories:
- having a systems engineer tell me to put in a ticket for the purpose of making a phone call to discuss something that had no pending action needed on his part
- having a DBA tell me the same thing
- having a DBA not know how to turn on query logging
- getting told we had to put together a hardware acquisition plan to do an in-place upgrade of database modules
- having a ticket to get log rotation turned on ignored for months and then told (when logs filled up the disk) that they'd have to turn off the service
- tediously going through change control to alter permissions, elevation rights, etc., only to have "implemented" changes mysteriously disappear the next time security patches were applied
- requesting and getting access to some very nice and expensive commercial applications only to be told that our use case was unsupported
- a half-dozen vendors' antivirus clients on windows machines
- unplanned outages during non-brownout/storm conditions corrupting databases
Ironically enough, some of the PMs (who are generally non-technical) we've talked to in IT literally complain about the exact same sort of problems.
The upside is I can take two or three hour lunch breaks whenever I have to wait on these guys, which is a couple times a week.
If I was in ops I would not use btrfs on anything but lab experiments... if i can get hardware RAID, then I can blame the vendor and the equipment
Of course it cuts both ways. A better headline would have been "Nuclear: sure it's dirty but are you really trying to tell us coal is safer".
You work in software right?
You never ever "just" replace a system with an improved feature-alike product, you go apeshit crazy with cool stuff you wanted for the past 5 years but couldn't get approved, until you run out of budget. Duh.
Here is the only solid criticism of systemd I've read that focuses on design (as opposed to bugs that surface from the sprawling throw-it-over-the-wall approach to development): http://blog.darknedgy.net/technology/2015/10/11/0/
Notably, darknedgy hosted/hosts uselessd, which was a lightweight version of systemd. On the whole i think the idea underlying systemd, of graph-based management of services and system state makes more sense that wonky initscripts garbage.
Technical discussion aside, I rarely see mentioned is that, what in my opinion, systemd resembles a lot of "politics-driven-development" i've worked on before. It's sprawling and ambitious--which means bugs--and like a high-politics project there's a certain incentive i perceive to downplay bugs--which also means it's a great way for RHEL to centralize control over things they didn't have say in previously as well as standardize, etc.
I'll go ahead and beat up on it more by saying that if the project is going to be used cudgel-like, I wish it would more loudly start talking about stuff like formal analysis, fuzzing etc., because it would be a great opportunity to promote research-y stuff in the "email your patches" world of OSS development.
Which is fine, but running Arch workstations for nearly ten years now, there's been a lot of gore with systemd... more than i'd like to see in PID1.
Of course, I hate writing C code with a passion so I'm just a whiner really.
you must not work enterprise much
I'm consistently amazed that the response is always that "Windows sucks" even as it's gotten better than the 95/XP/Vista experience. It's 2017, .NET runs on Linux now and VS runs on macOS, can't we all just get along? Of course, that sentiment exists for good reason even as Microsoft improves its product offerings. Every stable Windows install is just one third-party enterprise shitware deployment from automating BSOD reboots.
Tooling aside--VS is great if you add "finally" and "for some tasks" and if Powershell ever reaches a finished state that'd be good, but I still don't use either--regardless of how slap-dash and inconsistent Windows (lol X11) can be, the part of Windows that sucks the most is working at companies that require its use. If you haven't worked somewhere where people aspire to be "Sharepoint Administrators", where people "fix" prod data in Access and where >25% of your CPU cycles go to black-box antivirus vendor apps that had unpatched CVEs discovered in the past month, you really should so you can remember why you left.