Are You Prepared for a World Without Flash
-
@scottalanmiller said:
XML is very straightforward. There is no programming involved (unless your site is completely dynamically generated.) It's just markup. So like editing a CSV or a Word document manually. Just look for the line and delete. I have to edit XML by hand so often for so many different things, how do you avoid that?
Because I don't manage any websites except our Wiki.
-
@Dashrender said:
@scottalanmiller said:
XML is very straightforward. There is no programming involved (unless your site is completely dynamically generated.) It's just markup. So like editing a CSV or a Word document manually. Just look for the line and delete. I have to edit XML by hand so often for so many different things, how do you avoid that?
Because I don't manage any websites except our Wiki.
I said XML, it's used broadly outside of web pages. I didn't suggest that you would know how to modify the website because you have lots of websites, just because XML editing is such a common task for so many things. Many applications require it, for example.
-
Either my situation is really rare, or SMBs don't have to deal with it that much.
-
I've always had to deal with XML Configs. a lot.
-
@thecreativeone91 said:
I've always had to deal with XML Configs. a lot.
You also work for a HUGE company!
-
@Dashrender said:
@thecreativeone91 said:
I've always had to deal with XML Configs. a lot.
You also work for a HUGE company!
Now. But I haven't always. I worked for government localities with under 300 employees before.
-
@Dashrender said:
Either my situation is really rare, or SMBs don't have to deal with it that much.
I've had to deal with it everywhere since XML came out in the early 2000s. It's so common. Been working with it all this week.
Do you use a lot of JSON or YAML instead?
-
@Dashrender said:
@thecreativeone91 said:
I've always had to deal with XML Configs. a lot.
You also work for a HUGE company!
This really is not a factor. If anything I would think that it was the opposite since XML is old now and generally not favoured but retained by Microsoft more than most major vendors and modern app design tends to use YAML or JSON.
-
@thecreativeone91 said:
Now. But I haven't always. I worked for government localities with under 300 employees before.
And I run into it working for tiny companies, not the big ones.
-
@scottalanmiller said:
@Dashrender said:
Either my situation is really rare, or SMBs don't have to deal with it that much.
I've had to deal with it everywhere since XML came out in the early 2000s. It's so common. Been working with it all this week.
Do you use a lot of JSON or YAML instead?
I guess my job is just that much below you and yours - almost bench work more often that IT work as you'd put it...
No I have almost never edited a JSON file and never heard of a YAML file.
I have seen and edited XML files before, but... what... maybe 4-6 times ever... is so rare I couldn't tell you the last time I did it.
-
Correct me if I'm wrong here, I think the point you're getting at hear is that it's no different than editing INI files - OK - I'll look into it and see if I can find the files and get rid of this prompt on my own (damn I'd just rather get rid of the software
) -
I find that it is in all the "little places." Third party apps, for example, running on Windows often need it. IIS configs use XML so it is super common in the Windows world.
-
YAML = Yet Another Markup Language
It was designed to replace XML because it is so much simpler than XML for humans to look at and edit. You find it heavily in Ruby applications but anything might use it. I believe that Spiceworks uses YAML.
-
I think NGinx uses YAML, now that I think about it.
-
@scottalanmiller said:
@thecreativeone91 said:
Now. But I haven't always. I worked for government localities with under 300 employees before.
And I run into it working for tiny companies, not the big ones.
Yep. I wouldn't deal with for the most part here even if we had it. I manage the servers and the network/routers and MPLS as the Systems Engineer. We have people that handle most of the applications. some of the SQL management falls on me but, very little.
