I am not sure why this old news is surfacing here today but I can give my 2 cents, since I sold speedchecker.com last year and were directly competing with Ookla.
The main business is selling the data. You use Speedtest.net to troubleshoot your connection but metrics captured with the test alongside location data give telcos invaluable insights on where they should improve their networks. Telcos pay 6 figures annually for this data and we have a few hundreds of of those big MNOs globally. This market is pretty big. Accenture is in trouble with their main consulting business due to AI so acquiring data business is one of the smart strategies they can implement to stay relevant.
To all commenters who think they can code it over the weekend, yes you are right. I coded my first speed checker over the weekend in 2008 but it took me 18 years to grow the user base , figure out entreprise sales strategy and exit. Its not easy as it seems.
Sadly the website is offline, but if you like a hard copy cloud book I can heartily recommend the following. During my spell in Antarctica, I had to act as a meteorological observer (clouds are still manually encoded into METOBS that are entered in by WMO stations). This required learning the 10 types and being able to characterise the full picture of the sky.
It made me a total cloud addict, and spurred a far deeper interest in the role of the atmosphere in environmental science which has persisted ever since.
I heartily recommend looking up at the sky, dividing into oktas (eighths) and trying to classify how much of the low, medium and high clouds there are. If you do it regularly enough, the changes begin to astound. Getting your kids to do it too is also wonderful, because it's always there as an activity... :)
If there are any Dropboxers here (drew—I emailed you a few weeks ago, but I imagine you're busy):
I went to prison for 18 months, my digital and physical life was stolen from me: https://news.ycombinator.com/item?id=45451567 applies to my Dropbox account (and Apple but separate problem); I just received the "your account will be going bye-bye" email. I have very important dead-mom-club stuff in there, and support is useless. :(
Edit: Thanks unofficial Dropbox support channel; thanks Drew :)
Edit edit: Try my luck with my Apple account now, I guess—Tim Cook, you busy?
In 1979, I made a program called VisiBase in this BASIC.
It's a visual database modeled after VisiCalc.
That won me a joystick in at a competition by the local computer store. :-)
Still have the source, that works in an Apple 2 emulator. It's 13 K in ASCII (untokenized).
I own a reasonably well performing indie bookstore. I've noticed for the model to work you need a critical mass of other local shops clustered to make the trip an experience for families and diverse tastes. My working theory is that three of such small businesses are sufficient and could operate well with a common inventory strategy and manager (e.g. a bookstore, a toy store, and a tea or candy shop...nothing that spoils in the very short term). When I've got a bit more time I want to try that idea and see if it works as a way to revitalize otherwise charming old downtown areas with vacant retail space and communities wishing to bring back their main street. Giving this idea away in case anyone else has tried or wants to try sooner than me and report back.
• He had already published the first editions of Volume 1, 2, 3, and the second edition of Volume 1, by 1973. It was in 1977 when the publishers sent him galley proofs for the second edition of Volume 2, having switched to phototypesetting (away from hot-metal typesetting a la Linotype, though IIRC it was actually Monotype) that he was disappointed with the results. And he had some back-and-forth with them and they did improve their fonts (https://tex.stackexchange.com/a/367133/48), but he was still dissatisfied.
> I didn't know what to do. I had spent 15 years writing those books, but if they were going to look awful I didn't want to write any more.
• At this time he came to know of the existence of digital typesetters. Typesetting with computers had existed before, but it had always seemed a crude toy, rather than something suitable for “real books”. But he saw Patrick Winston's Artificial Intelligence that had been just published (I think he got an early proof copy to review or something), and he realized for the first time that digital typesetting was an option (apparently Winston's book was printed at >1000dpi, and Knuth later got his hands on a machine that claimed a resolution of 5333 dpi: see this wonderful comment from Knuth's student and “right-hand man”, David Fuchs: https://news.ycombinator.com/item?id=20009875)
• In fact it was the fonts that he was dissatisfied with rather than the typesetting, so METAFONT was in some sense the primary/motivating project and TeX was only written in order to be able to use METAFONT.
• Actually his first idea was to simply take the old fonts, get high-resolution scans of them (not easy to obtain at that time) and use them directly. He approached Xerox Research Center but:
> I asked if I could use Xerox's lab facilities to create my fonts. The answer was yes, but there was a catch: Xerox insisted on all rights to the use of any fonts that I developed with their equipment. Of course that was their privilege, but such a deal was unacceptable to me: A mathematical formula should never be "owned" by anybody! Mathematics belongs to God.
• So he went home and (after trying a bit with TV cameras) tried projecting photographs of the pages onto the wall and tracing the outlines, and it was while staring at these images that he realized that the shapes of letters were not arbitrary but there was some logic to them (e.g. in the font he was using, the spacing between the vertical strokes in 'm' was equal, and equal to that in 'n'), and he decided (as a computer programmer) to capture this design in code — something that had never before been done. The hardest letter to capture this way is S, hence the paper in the OP.
> Finally, a simple thought struck me. Those letters were designed by people. If I could understand what those people had in their minds when they were drawing the letters, then I could program a computer to carry out the same ideas. Instead of merely copying the form of the letters my new goal was therefore to copy the intelligence underlying that form. I decided to learn what type designers knew, and to teach that knowledge to a computer.
• This is also why METAFONT never really caught on among typographers: as Charles Bigelow (quoted by Richard Southall, https://luc.devroye.org/Southall-METAFONT1986.pdf) observed, “the designer thinks with images, not about images”. Knuth did not want crude “geometric” constructions of letters (as some prior 16th century typographers had attempted: https://www.ams.org/journals/bull/1979-01-02/S0273-0979-1979... and as some typographers only passingly familiar with METAFONT think!). He wanted actual real typographically beautiful shapes, but to be able to generate those shapes with code. This is obviously much harder than simply drawing the shapes using visual intuition, even if it enables variation. (See “The Concept of a Meta-Font”: https://gwern.net/doc/design/typography/1982-knuth.pdf — again, many people in the typography world confuse the abstract concept of a meta-font introduced in this paper with (their incorrect impressions of) the METAFONT program, and omit crediting Knuth for variable fonts).
• The second edition of Volume 2 was not printed with Linotype. Yes the machines still existed in Europe and he talked to typesetters (he mentions in particular a person from Belfast), but it was in fact published using TeX (the first version, TeX77 and MF78). He was still unhappy with the results, though, and spent a few more years learning more about typography and working with people like Bigelow and Hermann Zapf, before the rewrite into the current TeX82 and MF84 (and current version of Computer Modern). I think it's only with the third edition (1997) that he's finally satisfied.
I wasn't in this class myself, but one prof at my alma mater started his "Programming 201" class with the simplest assignment: write a C program that accepts two integers from the user and prints their sum. It actually was the only assignment for the rest of the semester, since he has a test suite that would humiliate the students gently at first, but would ultimately pipe a billion nines into stdin as the first argument.
PSOS. Now that was something I never expected to see again.
I'd worked on the previous system, KSOS, mentioned in the article. I wrote the file system and all of the drivers, while at an aerospace company. We'd used formal specifications in SPECIAL.
Nobody could prove anything about SPECIAL yet, but I wrote a compiler-like syntax and type checker, so it was at least type valid. It was a good language for writing down invariants. I used it to
describe file system consistency and recovery.
Another group started work on PSOS, but never got past the design stage.
I managed to avoid getting sucked into that, because it looked like a death march.
SRI, which was a think tank, just did abstract designs. It was extreme waterfall.
One group wrote a spec, and a contractor implemented it. This did not work too well.
They did have Boyer and Moore, and those two made real progress on proof systems.
I used their prover for another project, and talked to them a lot.
But they were not closely associated with PSOS. Specifications in SPECIAL, which is quantifier-oriented were not
compatible with Boyer-Moore theory, which uses constructive mathematics and recursive functions.
The big problem in that era was that the hardware wasn't ready for secure operating systems. KSOS was for the 16-bit PDP-11 line, and it took a cram job to make it fit. The Modula I compiler wasn't very space-efficient. Optimizations had to come out to make it fit, and the result was too slow.
Microprocessors weren't quite ready yet. Neither Intel nor Motorola had a decent MMU.
The suitable target machines were all minicomputers, which were on the way out.
PSOS never got far enough to pick an implementation target.
Capability-based systems work, but they create a new problem - ticket management. You have lots of tickets which let some piece of software do something, and now you have to track and manage them. It's like physical key control. It's the same reason that Windows access control lists are little used.
You also still have the delegation problem - A can't do X, but A can talk to B, which can do X. Most modern attacks involve that approach.
Most of the early secure OS work was funded by NSA. NSA had an internal division in those Cold War days - the important stuff was at Fort Meade, and the less-important stuff was some distance away at FANX, an annex out by Friendship (now BWI) Airport. FANX had personnel ("HR" today), training (including the cryptographic school), safe and lock testing and evaluation, networking, and computer security. Being exiled to FANX was bad for careers. This set back the computer security work.
There was also industry pushback. The operating system testing criteria were borrowed from the safe and lock people. Something submitted for testing got two tries. First try, the evaluators told the vendor what was wrong. Second try was pass/fail with no feedback. That's how locks for vaults were evaluated. Computer vendors (there was not much of a separate OS industry yet) hated this. They eventually got a testing system where "certified labs" did the testing, and a vendor could have as many tries as they were willing to pay for.
Some good secure OSs came out of that, and passed testing. But they were obscure, and for obscure hardware - Prime, Honeywell, etc. If you dig, you can find the approved products list from the 1980s.
What really killed all that was the growth of the computer industry. In the 1960s and 1970s, the government was the biggest purchaser of computers and electronics. As the industry grew, the government became a minor purchaser with a slow update cycle, and could not get design-level attention from major vendors.
There was much grumbling about this from military people, especially the USAF, as they were sidelined during the 1980s.
That's a tough problem - distinguishing wet pavement from deep water.
Humans make that mistake frequently.
Autonomous vehicles should probably be equipped with a water sensor. (We did that in our DARPA Grand Challenge vehicle back in 2005). Then they can enter water very cautiously and see if it's too deep. This may make them too cautious about shallow puddles on roads, though.
There's more history than this. Disclaimer: Xoogler (2010-2017).
When I first started the environment you used depended entirely on language. In the C++ and Python space, there was the vim and emacs divide. With Java it was more complicated. Some still used vim/emacs but a lot of people used Eclipse.
Now Eclipse was a real problem at Google because of the source control system. Java IDEs are primarily built to import binaries, specifically jars. In the outside world, these dependencies are managed via Ant (very early days), Maven/Gradle or the like.
At Google there's a mono-repo (Perforce/Piper) and you check out parts of it locally and rely on the rest via a network connection (to SrcFS IIRC, it's been awhile). This was neat because you could edit a file locally and the dependencies would just recompile (via Blaze).
So for Eclipse a whole lot of initialization had to be done and the IDE would fall over. A lot. It had a team of ~10 working on it at one point. Then somebody did a 20% project called magicjar. Magicjar took a Perforce client and built all the dependencies as jars that could be imported directly without parsing the entire source tree (which was usually huge). This made it possible, even preferred, to use IntelliJ, which is what I did. Magicjar was great.
Other people actually made CLion work reasonably well with C++ too. That was nice. This was a much bigger undertaking with many more corner cases just given how C++ works (ie headers and templates).
So checking out a client was relatively heavyweight, even with a minimal local tree. And, if you worked on Google3, you had to do this a lot. You might need to do a config file change. This was the real starting point for Cider because it was way nicer to do config file changes with it.
Obviously I don't know where all this went from there. VS Studio as a Cider frontend? Ok, that was news to me. Engineers being unhappy when things change and when the slightest thing works differently is the least surprising thing I've ever heard.
Oh it's worth adding that in my time many people didn't use Perforce (P4) directly. They used somebody else's project, which was a Git frontend for it, called Git5. I believe it was already being deprecated while I was still there. But Git5 modelled a P4 change as a branch so you could play around with your Git commits locally and then squash them into a single P4 change. I actually liked this a lot.
I think my Grandpa worked on the mentioned classified experiments in the late 1950s and throughout the 1960s. He was a Naval Academy graduate with a degree in electrical engineering and spent several years on submarines. He then spent several years working at the Pentagon in late 50s and throughout the 60s (my mother was born in Bethesda in 72).
He took those secrets to his grave. I could never get it out of him what he did that was classified. Although I did find several books and research papers in his basement about sonar and radio communications…
Anyways, great article that gave me a bit more insight into what my Grandpa might have been up to.
Decades ago, I worked a mission that went up on a Titan IV, and I spent a few weeks at Pad 41 working in the IUS clean room. Riding up and down the tower in the rickety (self operated) elevator was frightening. Walking the gantry and looking out at CCAS, you could see for miles in all directions. Standing under the thrust cones was an amazing experience. Unfortunately, no photos were allowed because it was a classified mission. All I got were a few stupid tee shirts.
About 15 years earlier, I had done some work at the VAB and walked around the Saturn IV that was laying on its side there, just as James Burke had a few years earlier. It wasn't there when I worked the above referenced mission. I'm not sure when they moved it, or where it ended up (but it's not in the "rocket garden" at the Visitor Center).
No wait, you think I'm being silly so that's why you're being a bit sarcastic back.
But seriously, you can put a shebang on an english text file now (if you're sufficiently brave), or feed it through something that spits out code on the other end (so you can proof read the consequences before executing them).
It's crazy, but this is 2026, and that actually ... just works. You can even do it locally, if you don't mind running a space heater.
Thing is, when you have the expressiveness and power of a full natural language (and you're already paying for it), why would you want to constrain yourself to a subset? That's not very practical. Why not use all of it? Computing was never about typing code into machines anyway. "Computer" used to be a human profession, until it got automated.
On the upside, there's thousands of years of documentation. On the downside, a lot said documentation is underspecified and/or straight wishful thinking. It's certainly an interesting avenue to explore.
I was a great admirer (and later friend) of Barlow, and I'm still very deeply influenced by the Declaration and many adjacent phenomena. I agree with some fraction of this post in terms of seeing many people shelving these principles when it gets inconvenient for them.
In the past few months, I've been troubled by one specific part of the Declaration, in the final paragraph:
> We will create a civilization of the Mind in Cyberspace. May it be more humane and fair than the world your governments have made before.
Specifically, I think the cyberspace civilization, to the extent that it exists, has been a failure lately on "humane" in the broad sense. The author of the linked post might say that this has to do with the need for moderation (indeed this is a big surprise from the 1996 point of view, as there were still unmoderated Usenet groups that people used regularly and enthusiastically, and spam was a recent invention).
I think there are lots of other things going on there over and above the moderation issue, but one is that the early Internet culture was very self-selected for people who thought that the ability to talk to people and the ability to access information were morally virtuous. I was going to say that it was self-selected for intellectualism but I know that early Internet participants were often not particularly scholarly or intellectually sophisticated (some of our critics like Langdon Winner, quoted here, or Phil Agre, were way ahead on that score).
So, I might say it was self-selected in terms of people who admired some forms of communicative institutions, maybe like people whose self-identity includes being proud of spending time in a library or a bookstore, or who join a debate club. (Both of those applied to me.) This is of course not quite the same thing as intellectual sophistication.
People were mean to each other on the early Internet, but ... some kind of "but" belongs here. Maybe "but it was surprising, it wasn't what they expected"? "But it wasn't what they thought it was about"?
Nowadays "humane" feels especially surprising as a description of an aspiration for online communications. It's kind of out the window and a lot of us find that our online interactions are much less humane that what we're used to offline. More demonization of outgroups, more fantasies of violence against them, more celebration of violence that actually occurs, more joy that one's opponents are suffering in some way. (I see this as almost fully general and not just a pathology of one community or ideology.)
I'm troubled by this both because it's unpleasant and even scary how non-humane a lot of Internet communities and conversation can be, and because it's jarring to see Barlow predict that specific thing and get it wrong that way. Many other things Barlow was optimistic about seem to me to have actually come to pass, although imperfectly or sometimes corruptly, but not this one.
We are in the South Pacific with our sailboat, and are using Meshtastic every day to talk between ourselves and with various buddy boats. The boat has a solar-powered repeater (CLIENT_BASE) on the mast that increases communications range significantly.
This all works great with no local SIM cards or other subscriptions or infrastructure needed.
We plan to run experiments with Reticulum when we stop for the cyclone season. Reticulum would open a lot more possibilities with both LoRa and internet-based comms. The Columba app seems to do a lot to bridge the usability gap, but work will need to be done to integrate Reticulum with our boat systems the way we have with Meshtastic (alerting, telemetry, digital switching control).
I’ve done this for a couple years now, cool to see it pop up here. I believe the scale is a touch larger; 3935 acres in 2025, plus a small amount outside the fence line.
On the technical side, we not only log but photograph everything, down to each clump of toilet paper. We check our progress by doing hundreds of tests identical to what the BLM does, both ahead and behind our main crew; bagging up any debris to be photographed on green screens where the pixels are counted to ensure we’re under the 2.29×10^-3 percent limit.
It’s a stupendous amount of walking, with no shade, a moop stick and a bucket. But it’s a hell of a feeling to be part of making sure we remain undefeated against an impossible task that the future of burning man depends on.
Ha ha! I worked in one of these matchbox factories as a kid. My dad had dropped me off at my grandpa's for summer vacation in the village. I was not a particularly good kid. So my grandpa took me to the match factory in the morning and told me to make myself useful. You sit around in a circle on the floor. There is a small hill of matchsticks piled in front of you. You count 50 sticks and stuff them into a matchbox, push that matchbox into the center of the pile. If you stuff 100 matchboxes you get 10 paisa or some such...was in the 1970s, I don't recollect exact amount. I do remember I came out in the evening with enough money to buy a stick ice-cream.
I remember around 2000 I read about how Ted Turner started his empire: he bought podunk local TV stations that had loose contracts with media owners that allowed them to broadcast shows as often as they wanted, with no restrictions. In the those days, local TV stations were broadcast just like radio and so the assumption was the contract only concerned the audience the TV station's antenna could reach. But the contract didn't specify this. Recognizing the loophole, he bought multiple stations and combined that content into its own cable channel(s) that played old movies and TV shows: https://en.wikipedia.org/wiki/Ted_Turner This was the basis that allowed him to branch into CNN and more.
When I learned about this, the story was very applicable to me at the time, as my startup had acquired licenses for content that was historically sold directly to libraries by a salesman who would negotiate with each library individually. He used a standard contract. When we contacted the company to license content for display on the internet, they gave us a ridiculous contract with a small one time fee and access to display the content forever. Only after reasoning through their business model and history did we understand how this occurred, which was exactly the same type of gap that Ted Turner had exploited.
My TI-85 story. While I was in prison, around 1996 or 1997, I found out a friend had a TI-85 calculator. I realized it was programmable, so I borrowed it over the weekend and wrote a program to track his stock portfolio. It was the first time I had programmed anything in 2 or 3 years.
Then I learned that the US Bureau of Prisons had a rule against any calculator (or device) that was "programmable". So I programmed the TI-85 so its startup screen read, "TI-85 NON-PROGRAMMABLE CALCULATOR". Problem solved.
I worked on geothermal control systems a decade or so back. There are some less obvious applications for geothermal that reduce electric use (as opposed to generating electricity).
The systems I worked on were for cooling larger structures like commercial greenhouses, gov installations and mansions. 64° degree water would be pumped up from 400' down, run thru a series of chillers (for a/c) and then returned underground - about 20° or 25° warmer.
I always thought this method could be used to provide a/c for neighborhoods, operated as a neighborhood utility. I've not seen it done tho. I've seen neighborhood owned water supplies and sewer systems; it tells me the ownership part seems feasible.
Fun fact, while Trower was the manager who got Windows moving, it was Gabe Newell who served as the lead developer of Windows versions 1, 2, and 3. Win95 was the first version he wasn’t really involved with. By that time, he was working on porting Doom to Windows.
Up until a year ago I was regularly using a Massy Fergusson 135 [0] (Perkins Diesel version), made sometime in the 1970s. It was wonderful! So amazing to drive and use. Clunky and heavy, but you really really felt like you were using a machine. In low gears, if you put you foot down on the accelerator the engine would roar, and your speed would barely change!
And there was no fancy technology in it at all. If I was in the forest and had forgotten the key, I'd just reach behind the dashboard and hot-wire it. The air filter was basically a shisha-pipe that bubbled the incoming air through wire wool and engine oil.
Its fuel gauge didn't work either. You just had to take a look in the tank, or quickly react as soon as the revs started dropping. I ran it dry a few times and had to sit there with a spanner in one hand and YouTube into the other, while trying to bleed all the fuel lines. But they were all on the outside of the vehicle, which made it comparatively easy I imagine.
I've never actually driven a modern tractor, so don't know how it compares. I imagine the clutch is easier on the knees these days!
Anyway, this just felt like the place to share this.
> “When we work on making our devices accessible by the blind, I don’t consider the bloody ROI.”
I just have to call out how much this impacted my mom’s life. She’s 100% blind and has access because of her iPhone and iPad. Yes she learned JAWSs and literally took classes to do it. Every single windows update has made it so she’d have to retake this class. The iOS updates a rocky but she isn’t literally hamstrung.
My dad, damn near 80, is still happily using his 2012 i7 Mac mini I set him up with before moving away.
I've told only a few people about my near death experience, and most of them were polite, but obviously didn't believe a word I was saying. To be honest, I wouldn't believe it either if I had not experienced it myself.
I did not "see" anything other than a bright light, but I was overcome with an incredible feeling that I was in the presence of, and communicating with somebody who was conveying a message of absolute love for, and total understanding of everything that I was. The feeling of euphoria is impossible to fully describe, because of the absoluteness of it.
I wanted to stay where I was. It was the best feeling I'd ever experienced, and I was content. Somehow, I was "shown" some bits of what I had to live for -- people I had not yet met, and amazing places and things that I had not yet seen or done. I don't really remember making a choice to return, but I woke up in a hospital with a broken back and other injuries. I later learned that I had been hit by a car while riding my bicycle, and was given CPR by a passing stranger.
It makes me uncomfortable to talk about this because it's all just so unbelievable, but there it is.
As the years have gone by, I've met the friends and family that I had in my visions, and I've also been to the places and done the things that I saw myself doing in the vision.
My whole perspective on life was changed by this event, and I have no fear of death whatsoever.
When I was a teenager I was friends with an extremely poor kid who literally lived on the wrong side of the tracks. He couldn’t afford a microphone and used an old pair of busted headphones to rap into as a microphone. He had recorded and produced a whole album like this with Fruity Loops on an old computer he found discarded at the side of the road.
I am this very term teaching 18-year-old students 6502 assembly programming using an emulated Apple II Plus. They've had intro to Python, data structures, and OO programming courses using a modern programming environment.
Now, they are programming a chip from the seventies using an editor/assembler that was written in 1983 and has a line editor, not a full-screen one.
We had a total of 10 hours of class + lab where I taught them about assembly language and told them about the registers, instructions, and addressing modes of the chip, memory map and monitor routines of the Apple, and after that we went and wrote a few programs together, mostly using the low-resolution graphics mode (40x40): a drawing program, a bouncing ball, culminating in hand-rolled sprites with simple collision detection.
Their assignment is to write a simple program (I suggested a low-res game like Snake or Tetris but they can do whatever they want provided they tell me about it and I okay it), demo their program, and then explain to the class how it works.
At first they hated the line editor. But then a very interesting thing happened. They started thinking about their code before writing it. Planning. Discussing things in advance. Everything we told them they should do before coding in previous classes, but they didn't do because a powerful editor was right there so why not use it?...
And then they started to get used to the line editor. They told me they didn't need to really see the code on the screen, it was in their head.
They will of course go back to modern tools after class is finished, but I think it's good for them to have this kind of experience.
JOVIAL had been in use within the US Air Force for more than a decade before the first initiative for designing a unique military programming language, which has resulted in Ada.
JOVIAL had been derived from IAL (December 1958), the predecessor of ALGOL 60. However JOVIAL was defined before the final version of ALGOL 60 (May 1960), so it did not incorporate a part of the changes that had occurred between IAL and ALGOL 60.
The timeline of Ada development has been marked by increasingly specific documents elaborated by anonymous employees of the Department of Defense, containing requirements that had to be satisfied by the competing programming language designs:
1975-04: the STRAWMAN requirements
1975-08: the WOODENMAN requirements
1976-01: the TINMAN requirements
1977-01: the IRONMAN requirements
1977-07: the IRONMAN requirements (revised)
1978-06: the STEELMAN requirements
1979-06: "Preliminary Ada Reference Manual" (after winning the competition)
Already the STRAWMAN requirements from 1975 contained some features taken from JOVIAL, which the US Air Force used and liked, so they wanted that the replacement language should continue to have them.
However, starting with the IRONMAN requirements, some features originally taken as such from JOVIAL have been replaced by greatly improved original features, e.g. the function parameters specified as in JOVIAL have been replaced by the requirement to specify the behavior of the parameters regardless of their implementation by the compiler, i.e. the programmer specifies behaviors like "in", "out" and "in/out" and the compiler chooses freely how to pass the parameters, e.g. by value or by reference, depending on which method is more efficient.
This is a huge improvement over how parameters are specified in languages like C or C++ and in all their descendants. The most important defects of C++, which have caused low performance for several decades and which are responsible for much of the current complexity of C++ have as their cause the inability of C++ to distinguish between "out" parameters and "in/out" parameters. This misfeature is the reason for the existence of a lot of unnecessary things in C++, like constructors as something different from normal functions, and which cannot signal errors otherwise than by exceptions, of copy constructors different from assignment, of the "move" semantics introduced in C++ 2011 to solve the performance problems that plagued C++ previously, etc.
Since there’s a lot of assumptions on personality here, I’ll toss my perspective here.
Worked at Atlassian for 5 years, had plenty of interactions with Mike. I wouldn’t categorize him as a jerk. I have plenty of disagreements about decisions he’s made, and I think he heavily over-hired (and is paying for it now), but a jerk he is not.
The reality is Atlassian has mechanisms, for better or for worse, that reward social discontent - Hello (their internal Confluence instance which has Reddit-like upvoting on blogs) and their karma bot on slack. Both of which tend to result in people gamifying these to boost their social status, which as you’ve seen with Reddit, often results in a subset of people realizing negative comments get more attention than positive ones. This got out of hand and they’ve been trying to dial it back, leading to cuts like these. It’s been a problem at Atlassian for a while.
Oh wow, I used to work on Excel Add-Ins about 10 years ago. Even got a patent for it. I'd be curious to see how they implemented the calls.
We came up with what I still consider a pretty cool batch-rpc mechanism under the hood so that you wouldn't have to cross the process boundary on every OM calls (which is especially costly on Excel Web). I remember fighting so hard to have it be called `context.sync()` instead of `context.executeAsync()`...
That being said, done poorly it can be slow as the round-trip time on web can be on the order of seconds (at least back then).
The main business is selling the data. You use Speedtest.net to troubleshoot your connection but metrics captured with the test alongside location data give telcos invaluable insights on where they should improve their networks. Telcos pay 6 figures annually for this data and we have a few hundreds of of those big MNOs globally. This market is pretty big. Accenture is in trouble with their main consulting business due to AI so acquiring data business is one of the smart strategies they can implement to stay relevant.
To all commenters who think they can code it over the weekend, yes you are right. I coded my first speed checker over the weekend in 2008 but it took me 18 years to grow the user base , figure out entreprise sales strategy and exit. Its not easy as it seems.