Ahhhhhhhhh!
20 years on giant enterprise codebases. And any enterprise worth their salt at this point will be scanning these servers and flagging eosl software.
My experience the last five years of the 20 - security and service life trumps all fucking complaints about complexity.
To the point where it’s the opposite and I’m fielding weekly questions about why we’re still running an older 3.7.9 version. Among 50 other things.
Meh. I’ve ported a fair many py2 projects to 3. At this point just bite the bullet. Even from a security standpoint. Trying to not let my bias seep through - but it’s been so long.
That’s fucking heart breaking. Thank you for sharing. Thank you for doing what you did. What a good person the boss was.
Love all the ideas. Was an avid subscriber on the platform I won’t name - and support them here.
One opinion though - and not a ride or die opinion - just a thought. What if you made tags to categorize certain options. #vintage for things that are old and outdated but may still be obtained.
So still allow it - just make sure it can be quantified and understood by readers/posters.
I’m not a fan of certain days - that just discourages participation - but tagging is a great option to allow posts at any time but allow others to filter.
Couple of tag ideas
- vintage for older items
- promotion for self promotion
- diy for posts that encourage instructional material
This way you don’t push off posters and allow a gentle path to posting and categorizing that will help others later on to filter and search. If I ever went to a sub-thing and saw a rule to not post until x day - I just ignored it and moved on to other communities.
Others have already replied with this info but I’m just spelling it out for anyone who is not familiar like me:
They fucking named the brand new game mk1. Is it a remaster? No. It’s not a remaster. Is it a recreation of mk1? No. It’s an alternate timeline game given the worst name in the history of naming things. It’s genuinely a brand new game.
Just a plain tailor. Plain. Simple. Garak.
Docker containers in programming are reusable environments. Basically instead of manually setting up an operating system environment from scratch - you give your program this extra layer where you specify each and every thing that will be on the environment.
If your program was always tested on windows 10 instead of windows 9 - you basically have a way to guarantee it always has windows 10. If your program always used x version of Linux a boom, guaranteed. It adds some complexity but reduces and removes randomness from the concept of deploying applications you’ve created.
Team Memmy. It’s freaking great. And the amount of updates they post to the test channel. Fantastic. It’s nice logging in once a day and seeing some cool functionality pushed out.
It’s an exceptionally rare thing — in life or in business — that you get a second chance to make another big impression," the chief tweeted. "Twitter made one massive impression and changed the way we communicate. Now, X will go further, transforming the global town square."
Yes yes. Indeed. I love referring to a company by a single letter. Think about all of the great SEO will come from this! Think about the great way this will unite us all!
Agree on stack overflow. And part of learning how to program is trying to structure logic into thoughtful questions.
With R specifically I’d recommend looking into the tidyverse library for R. Or at least understand the libraries your work environment will be specifying to make sure you’re on the same page.