universities in the 1980s: writing the majority of internet standard RFCs and their implementations
universities now: moving away from Microsoft cloud is really hard okay? 🥺
universities in the 1980s: writing the majority of internet standard RFCs and their implementations
universities now: moving away from Microsoft cloud is really hard okay? 🥺
or we could say now that the organizational level overpower the individual one. Universities are gigantic structures sometimes for good reason and most of the time bad ones.
@edbilodeau @eloy There was a ton accomplished my #MIT Project Athena / IS&T (and Project Andrew at CMU) by staff members in the 80s and 90s, with things like Kerberos coming out as a result. Lots of this was to fill niches in Workstation software. Ironically some of these underly some Microsoft protocols. Student groups like MIT's SIPB were also tightly coupled into this
Lots of that staff left for various reasons, and universities shifted to using off the shelf products. Sadly MIT as a whole is now way behind (eg, very little IPv6) and I suspect the same is true of other schools.
That said, the people leaving schools to go work in industry had a huge impact on how many large Internet companies operate. Aspects of the MIT network certainly influenced how #Akamai was architected in the early days, and some of those patterns seeded how some of the other largest tech companies designed things.
@eloy this one dropped several classes that used some kind of "test browser" that had zero Linux support. Several professors would say "it's ok, I give paper tests", some were bamboozled.
The bamboozlement is mostly from a handful of departments. You'd never guess which :|
@eloy @gnomon Also universities in the 80s: one of the biggest places computer stuff was happening, especially Internet/networking stuff. Universities today: a lower-paid backwater for exciting Internet, networking, Unix etc stuff.
In the 70s and 80s, a university job looked like a decently paid place you could continue interesting work after a CS degree, and better than many outside computer programming jobs (hello IBM mainframes). Today, the exciting jobs are outside of academia.
@eloy @gnomon I came up through the CS to university sysadmin pipeline (and currently work at a CS department). Even back then I don't think it was a majority pipeline¹ and it kept shrinking over time as outside jobs got better (both pay and work). Today the university can't really compete; what highly technical new people we can recruit have to really, really like the environment.
¹ people might start as university sysadmins but they leaked out unless they liked the environment.
@maswan @eloy @gnomon My view is that management is somewhat forced by what staff they can recruit and what that staff can operate (which at a large scale is forced by budget, which is forced by politics¹). Increasingly I think universities (and lots of other places) will be forced to rely on existing solutions instead of building their own.
¹ as mainstream tech salaries get ever higher it becomes ever-harder for 'second tier' organizations like universities to pay competitively.
@cks
@eloy @gnomon Yeah, but this is also a geographical issue. While we can't match US tech giant salaries, we're not far behind the local IT sector (but with some better benefits like 7 instead of 5 weeks vacation etc).
The bigger challenge for us lately is how to sell the position, gotta call it devops and not sysadmin, and stuff like that. Operations seem to be very low-valued in the modern world.
@eloy Also universities in the 1980s: We're training the best & brightest, we offer them permanent contracts e.g. in the IT department and try to hold them.
Also universities now: Get your degree and get lost! Why can't we find good staff? 🥺
RE: https://hsnl.social/@eloy/116003176888188762
To be clear, I HATE the current state of things, but there's a hint of truth to this.
I don't have the blog post handy, but someone tried to roll their own alternative to TCP, UDP, etc for fun recently. They discovered that carriers will refuse to reliably route anything that's doesn't set the IP proto to TCP/UDP.
So even if Unis wanted to create a new proto, it _sounds_ like the social aspect of getting non-Uni middlemen to play nice is a lot more difficult.
@eloy There used to be just a CS / Engineering department. There was no university IT. So it was far easier to make decisions.
Now there has to be a uni-wide IT team, with business goals, compliance, etc, often competing for resources with department specific IT groups. That's not necessarily a problem but makes it much harder to build and deploy new stuff if it always needs approval from higher up.
The worst though is when individual departments IT get folded into to main uni IT, then it's impossible to trial any innovations.
@LonM
@eloy Hmm. That's not the case here, central IT is older than the CS dept (uni IT is where the applied math folks handed in their stacks of punch cards for programming classes, before they split out into CS and had computers of their own). They just used to be more focused on technical expertise and innovation rather than process management and billing.
The CS and/or HPC dept running their own infra still happens, but is under political and financial pressure.