Aye, I run a large on-prem GitLab for my org.
GitLab's CI Runner stuff is light years ahead of GitHub's, who just brought something similar online in least year or so. It's works fine, but I've found it more fiddly to setup. GitLab's runner setup is trivial at this point.
Running on-prem, where people are pushing and pulling multi-gigabyte repos over the 1Gbps LAN in a couple seconds is such a huge win.
MTA to try to deliver mail to.
I frequently have to fill out a form to try to get my mail server's IP off their naughty list. And in every case it's been, "Hey your IP is kinda close to someone else's that was naughty". Really? In world of exhausted ipv4 allocations, when I get to rent a single IP from my VPS provider, you're going to play that game? Give me a break.
Most recently, I had to give up on IPV6 all together has SpamHaus has decided that blocking entire ipv6
As much as I hate Google for innumerable reasons, at least they're transparent in how they process incoming mail and subsequently I've NEVER had a problem delivering to a gmail address.
Well, as I remember it, you were trying to commercialize the site. Not a single other person working on it was interested in that, lest it fall to the same fate as our beloved Slashdot. We were pushing hard to incorporate as a non-profit.
Regardless, you're right about one thing, He was ill suited for the role he took on.
30 Million! My AM environment is serving barely 5K. I'd love to get some details on your infrastructure. How many IDPs and AGs are you running?
Access Manager is an extremely capable enterprise class single-sign-on product (It's the current incarnation of Novell's iChain SSO product). I'm using it here to protect about 30+ backed web-applications. I can do access restrictions based on LDAP group memberships, inject identity information in http headers, do behind the scenes form-fill login for applications that wouldn't know what SSO was if it fell on them and so much more. Currently just finished a Radius server integration for 2 factor auth. It's one of the two best pieces of enterprise software I've ever used. (Riverbed's Stingray appliance being the other).
Yes, in the effort to make trucks more economical, they've really engineered out a of ruggedness. I can flex a body panel on any new truck by leaning on it. I can lean hundreds of pounds against my '81 Ford with no visible deflection in the panel. Its possible this is a way to actually address these concerns of people who use trucks have. Can we make things stronger and lighter at the same time? I'm cautiously optimistic that this won't suck and will actually make the trucks better.
Of course there is always the view that the language you "learn" with in school is largely irrelevant, learning how to develop software and solve problems is the skill. The underlying concepts are what's important, not that you understand the specific syntax of the language -- My undergrad program was taught *entirely* in Java -- I haven’t written a single line of Java code since graduation.
Second is that it is MUCH easier to control emission at the generating station than it is to try to do it on every tailpipe out there. Would you rather have one big filter or millions of small ones?
Of course it's much easier to control one point than many, but until the EPA gets serious about a carbon cap or other controls on the dirtiest power plants -- I'll stand by my argument.
Instead of coal you can power it with natural gas or even oil.
You *can*, but many folks don't have the option of choosing where their power comes from.
'based on a Lotus Elise' would be the Tesla *Roadster* - which they haven't produced for a couple of years now. the car everyone is talking about in this story is the Model S, which is built from the ground up by Tesla as a pure electric vehicle, and is therefore a much more optimal solution.
you're right, mea culpa.
Oh, I don't doubt that it's a fine electric automobile, based on a Lotus Elise, it would be hard to make it bad, however; the very concept of a battery car is what I take issue with, as a gear-head I have just a have a personal prejudice against.
Personal prejudices and preferences aside, my biggest issue with electric cars is that you're really just shuffling the emissions around. Instead of the source of pollution being from a very tightly regulated source (tail-pipe emissions), they are now likely to come from a largely unregulated and dirty power plant -- 42% us power came from coal in 2011. Until we get a point of 100% clean renewable energy, I'm not sure the trade-off is worth it.
I'm sorry, I just don't care for battery cars, just like I don't care for iDevices -- perhaps the (dumb) analogy is more accurate than the author intended.
Really?
Verizon has all but abandoned the copper infrastructure around here. It's FIOS or nothing. No new TP copper installs. No TP copper repairs! The "repair" for being on a bad pair was the FIOS installation guy showing up my door. No thanks.
Oh for a Mod point. This is exactly it.
Among the employees of a University, Faculty are the 1st class citizens. Us staff folks are not. We are subject to all the normal stuff that you would expect of any employer. Faculty just have a different relationship with their employer. Not making a judgment call on this, I'm just stating the reality of the situation.
As faculty, I would expect that my email would not be ready without my knowledge and that there would be some sort of committee to determine if HR had the right or reasonable cause to search my email before it happened.
As staff, every bit I generate is subject to search and inspection...including these made on "company time".
Around here I pay $0.18 per kWH. My Server draws about 90W -- That's about $11-12
Leveraging always beats prototyping.
