Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

XML is the future

bitecode.dev

Post reply on HN
Print view View original

401–408 of 408 posts

Re: XML is the future

#401

Post by datavirtue »

WJW wrote: post #298
goodpoint wrote: post #266

Earlier quoted context omitted.

Maintaining old stuff is way more sensible than rewriting everything every few years. Companies tend to measure costs of maintenance vs rewrite. Edit: there's always a tradeoff but I wrote "every few years". Cobol is an odd example. Many banks have been going back to Cobol because they found it less expensive than the alternatives and are there is an influx of new graduates learning the language right now.

Sensible for who? Companies may try to estimate costs of maintenance vs rewrite, but individuals need to make the final call and for them the benefits usually go the other way. Maintaining some existing project is going to get you nothing if you do it right and will bring you problems if it breaks despite your best efforts. Rewriting an existing system in a new tech stack counts as exciting innovative work for promot…

A stack that goes down all the time is a ripe opportunity for career advancement, if you are in to that.

Hell, I have seen the creators of the problems get endlessly promoted for constantly solving problems they created.

Small or medium company, critical systems going down a lot...give me that shit. Easy money and reputation.

Re: XML is the future

#402

Post by datavirtue »

edejong wrote: post #179
shocks wrote: post #172

Earlier quoted context omitted.

Here’s another perspective: A decade ago you could deploy an internal PHP app to a box and forget about it for a few years, then fix a minor bug by sshing in, viming a file, and hacking it a few times. These days, if you leave the app untouched for six months that 10 minute fix becomes 2 hours of fixing a broken docker build. :)

In the meantime, your PHP app had 40 major security flaws, no meaningful monitoring, a DB that wasn't backed up and major data consistency problems. Also, when your box's hdd crashed, you lost all those minor changes you had vim'ed over the years. But for the rest, yeah, all is fine.

Shiney new app has no monitoring, 40 security flaws, and a ultra-modern cloud database that promotes data consistency issues. But all the devs you can hire act like they might know something about this mess. They really don't.

Re: XML is the future

#403

Post by [deleted] »

WJW wrote: post #298
goodpoint wrote: post #266

Earlier quoted context omitted.

Maintaining old stuff is way more sensible than rewriting everything every few years. Companies tend to measure costs of maintenance vs rewrite. Edit: there's always a tradeoff but I wrote "every few years". Cobol is an odd example. Many banks have been going back to Cobol because they found it less expensive than the alternatives and are there is an influx of new graduates learning the language right now.

Sensible for who? Companies may try to estimate costs of maintenance vs rewrite, but individuals need to make the final call and for them the benefits usually go the other way. Maintaining some existing project is going to get you nothing if you do it right and will bring you problems if it breaks despite your best efforts. Rewriting an existing system in a new tech stack counts as exciting innovative work for promot…

[deleted]

Re: XML is the future

#405

Post by spiralx »

mcv wrote: post #117
gnulinux wrote: post #7

I've been working in the tech industry in the US for about 5 years. Ever since I knew myself I've been coding. From middle school to high school, given any problem, like Sudoku, or keeping up daily chores, my solution was Programming! Programming wasy homebase. Then I studied it in uni, thought I was kinda good at it, and loved it. But when I started working in the industry, I realized that it's absolutely exhausting…

Yeah, you can't jump on every hype. I started in web dev almost 20 years ago (did some Visual C++ before that). First job was everything XML. We had our open source CMS that stored all documents as XML and used XSLT to transform it into the HTML we needed. Was pretty cool, but there's always something that didn't fit that paradigm. Some coworkers went a bit overboard and used XSLT to generate the XSLT to create the H…

> First job was everything XML. We had our open source CMS that stored all documents as XML and used XSLT to transform it into the HTML we needed.

Docato/XHive? Been there as well.

Re: XML is the future

#406

Post by gofreddygo »

manvillej wrote: post #367
DarkCrusader2 wrote: post #245

Earlier quoted context omitted.

I am in the exact opposite,but equally frustrating boat. In last 5 years, I have worked at 2 Faang and a large hedge fund and everywhere they had extremely outdated stack or undocumented in-house stack or outdated undocumented in-house stack. Already derecated dependencies were pinned years ago and management won't let you modernize anything since there "no business value in it" and we need to ship a feature instead…

In both of your cases, I think there is this massive disconnect in decision making. Software development is a constant game of economic decision making. Which investment returns the greatest value. Agile worked because it spread risk and allowed for reaction to new opportunities. CICD/devops worked because it drastically reduced the risk & expense of defects, the cost of development, time to market, etc. But the chas…

The decision makers themselves are couchsurfing.

You'll consistently notice obviously idiotic decisions rooted at decision makers who aren't around to own up to the mistake.

The other end has decision makers never change, they waited too long, were too risk averse to stagnate and the cost of change just keeps rising.

The ones who end up surviving this churn, have both kinds of decision makers in equal powers, mistakes are made, but things keep moving sometimes in leaps, sometimes backward steps.

Re: XML is the future

#407

Post by collinmanderson »

otabdeveloper4 wrote: post #393
edejong wrote: post #292

Earlier quoted context omitted.

In the 27 minutes after you wrote your comment, our CI/CD rebuild two containers from a latest snapshot. No manual work involved.

Good for you, some people can do automatic unattended OS updates too. There's no benefit to using containers here, only more pain.

One benefit of containers is easy rollback.

Re: XML is the future

#408

Post by cowoder »

rerdavies wrote: post #385
xdennis wrote: post #379

Earlier quoted context omitted.

They no longer want you to create a React app by itself[1], but instead use Next.js, Remix, Gatsby, or Expo. [1]: https://react.dev/learn/start-a-new-react-project

None of which are static. How are you supposed to create a static React app?

You can use vite for that
Post reply on HN