From: "David Bray, PhD" <david.a.bray@gmail.com>
To: dickroy@alum.mit.edu,
"Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] public service website slowness
Date: Mon, 19 Aug 2024 10:40:24 -0400 [thread overview]
Message-ID: <CA+aeVP8K_ht3S8mSTrrx1txU1Q7yd61Wg=QuzJ4weiVAbR0p3Q@mail.gmail.com> (raw)
In-Reply-To: <4CFA1F4CC17A444EAFF9A96F1D7CDB2B@SRA6>
[-- Attachment #1: Type: text/plain, Size: 2567 bytes --]
Part of the challenge is that several government websites usually only have
a budget allocated to launch them - and then they collect dust (the O&M
long-tail). So the lament is that a website that was made 18-25 years ago
is slow to load nowadays (keeping in mind that client-side javascript
wasn't really an option back then either).
A much bigger problem is making sure legislators when they appropriate
funds for a project that is intended to continue for multiple decades -
those appropriators need to also include in that budget continuous
refreshes to both the web UI/UX as well as the security posture. That's the
other side of the issue, when legacy technology isn't funded IT security
postures get progressively worse as sites get more and more out of date.
Meanwhile we also need to encourage ways for continuous updates to both the
UI/UX and the security to be done that aren't captured by incumbents who
use this knowledge of the ins and outs of both the technology systems and
associated human systems to charge inflated prices to keep things updated
too?
... and this isn't only for government organizations.
Ask Delta about their IT infrastructure and how when Crowdstrike/Microsoft
Cloud hiccupped, how that created a ripple effect for them and their UI/UX
too. O&M tied to legacy IT does have substantial impacts.
On Mon, Aug 19, 2024 at 12:03 AM Dick Roy via Nnagain <
nnagain@lists.bufferbloat.net> wrote:
> Speed is not the problem … it’s how information to be transmitted is
> encoded and more importantly, how much redundant info is being sent. It’s
> the MS mindset … give me a faster processor and more memory and I’ll give
> you more bloated code to fill it up! When you put kindergarteners in
> charge, you get a kindergarten solution! JJJ
>
>
>
>
>
>
> ------------------------------
>
> *From:* Nnagain [mailto:nnagain-bounces@lists.bufferbloat.net] *On Behalf
> Of *Dave Taht via Nnagain
> *Sent:* Sunday, August 18, 2024 7:03 PM
> *To:* Network Neutrality is back! Let´s make the technical aspects heard
> this time!; bloat
> *Cc:* Dave Taht
> *Subject:* [NNagain] public service website slowness
>
>
>
> This was a damning analysis of many government websites' speed.
>
>
>
> https://infrequently.org/2024/08/object-lesson/#the-golden-wait
>
>
>
>
> --
>
>
>
> Dave Täht CSO, LibreQos
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>
[-- Attachment #2: Type: text/html, Size: 6211 bytes --]
next prev parent reply other threads:[~2024-08-19 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 2:02 Dave Taht
2024-08-19 4:02 ` Dick Roy
2024-08-19 14:40 ` David Bray, PhD [this message]
2024-08-19 14:48 ` Steve Crocker
2024-08-19 14:57 ` David Bray, PhD
2024-08-19 15:31 ` Dave Crocker
2024-08-19 2:42 Hal Murray
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+aeVP8K_ht3S8mSTrrx1txU1Q7yd61Wg=QuzJ4weiVAbR0p3Q@mail.gmail.com' \
--to=david.a.bray@gmail.com \
--cc=dickroy@alum.mit.edu \
--cc=nnagain@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox