pragmatic

Everything in that data center is depreciating as soon as they turn on the power.

AC, ups, generators not to mention the severs.

That's the thing with fiber it was still useful. The cards at either end are easy to add, waaaayyy cheaper and higher perf (they're were no cards on end of dark lines) 15 years later.

In 2005 telecom was a cash cow because of long distance charges and if your mechanical phone switch was paid off you were printing money (regulations guaranteed revenue)

This didn't last that much longer and many places were trying to diversify into managed services (data dog for companues on Orem network and server equipment,etc) which they call "unregulated" revenue.

Add written an things business, irrational exuberance can kill you.

At a "telecom of telecom" we (they) were still lighting up dark fiber 15 years later (2015) when mobile data for cell carriers finally created enough demand. Hard to fathom the amount of overbuild.

The only difference is fiber optic lines remained useful the whole time. Will these cards have the same longevity?

(I have no idea just sharing anecdata)

Can I ask why define these in json?

Devs aren't going to like that over c# and data engineers/biz folks want more of a graphical tool.

Who is your audience for this?

"Warm water ports"

Isn't this one of the goals of their Project 2025?

Pipe enters the chat.

For whatever reason, pipe seems to be support common in health care data.

Crocodiles

It does not.

This is why EXAMPLES in getting started pages are so important.

LLMs are making up for the lack of this.

It’s the Backus-Naur approach vs the Human approach.

Humans learn by example. IMHO this is why math education (and most software documentations) fails so hard - starting with axioms instead of examples.

What are “db guys” in this context?

There are two distinct job functions.

1) dba - maintain OS, db software/hardware - DBs are complex beasts you want experts setting up hardware or deploying into the clown in a smarter way (virtual machines in the clown will cost you a fortune and your sanity) 2) database developers- specialists in writing sql.

The two functions work together but are distinct.

Nowadays due to private equity and Stanford MBAs we have junior engineers doing all plus “dev ops”.

It’s an absolute circus.

IMO, this is why we end up with ask these crazy DB startups - routing around the damage.

RDMS in modern hardware are insanely fast and powerful.

95% it’s a missing/improper index but the insane workarounds “engineers” put in place actively work against the database.

Does your hotpath query have a covering index? Is it seek-able. Are you predicates SARG-able.

Seriously biggest bang for your buck is to understand SARG-ability and understand indexes in your database really well.

Indexed Views for Postgres but at the query level?

A fellow data swamp enjoyer.

Just dump it in Hadoop became an anti-pattern and everyone yearned for databases and clean data and not dealing with internal IT and the cluster “admins”.

Wow very indepth.

This used to be (and still is in some circles) a hot topic.

.net had the benefit of coning second and fixed a lot of java's design issues. It really use a better java.

Of course in the days of JavaScript desktop apps and python, people just don't need to pay attention to perf as much for better or worse.

Yes, and then you get the job there and regret it bc they’ll have either have an over engineered Rube Goldberg contraption or they have system envy bc they’ve read about this architecture in blogs and THINK they need K8s and they still fix all their problems.

What could go wrong!

Many such cases!

- a tool that happens to be much slower than google/ctrl-f/man-pages/poking around github

Excel on the desktop isn’t going any where.

Riiiigghhht.

Windows Forms are alive and well.

Still supported in latest .net versions.

Not half the country, not even a majority of voters.

However your punt stands.

I think a lot of those voted for the racism not the economic collapse.

But it's actually useful for scalability.

All modern IO is async. The fact that you get this easy to use API to make an app more scalable is a ridiculously good deal.

Now, if you don't really need that, then it just looks like pointless extra work.

The old fox and scorpian tale over and over again.

Aka it's Microsoft, this is what they do.

That’s not how modern societies/economies work.

We have specialists everywhere.

More fair comparison: Military grade killbot enters ring with boxer and proceeds to fire pneumatic hammer at boxer until KO?

They came with avcertain number of power cores, say 8 but you could start by only licensing 4 and then grow into them. Don't remember the exact specs on this but they were crazy powerful 20 years ago.

AIX on big iron.

Used for ex nightly batch processing at banks. Lots of horse power for your on prem needs. Moving this kind of horse power to the cloud would be insanely expensive and complex for the mid size banks relying on these systems.

They shipped these massive boxes out and connected them to massive SANs. You could license the processors later if your workload grew.

I spent a year as consultant to big customers building SOA, websites, SSO for whatever they needed. ATM networks with low latency etc.

Could you elaborate a bit on the tasks,languages,domain etc you’re using it with?

People have such widely varying experiences and I’m wondering why.