Python/Jupyter developer in Boston. I build data tools and I start by talking to the people who'll use them, because code that doesn't get adopted is wasted work. My main thing is Buckaroo (github.com/paddymul/buckaroo, ~680 stars), an open-source data table for Jupyter over Pandas/Polars. I built both the data layer and the React frontend. Looking for a team building data tooling (as a product or in house).
Ted Turner won the America's cup there in 1977. His team named Courageous was legendary. Robbie Doyle was a team member, and got a degree from Harvard in applied physics. In the middle of the trials to see which team would defend the cup for the US, he remade the sails to be more competitive. Doyle went on to found a racing sailmaking company.
I used to live in Newport, RI. I love sailing and introducing people to the world of sailing. When I had guests I asked them to watch this NBC video about Ted's 77 campaign [1]. It really captures the history of Newport, sailing, and Ted
Sounds great. I'll watch it with the kids. We've recently done this podcast about the history of the cup and it was funny and fascinating. https://www.youtube.com/watch?v=hUZmk_G6rFE
Ted Turner won the America's cup there in 1977. His team named Courageous was legendary. Robbie Doyle was a team member, and got a degree from Harvard in applied physics. In the middle of the trials to see which team would defend the cup for the US, he remade the sails to be more competitive. Doyle went on to found a racing sailmaking company.
I used to live in Newport, RI. I love sailing and introducing people to the world of sailing. When I had guests I asked them to watch this NBC video about Ted's 77 campaign [1]. It really captures the history of Newport, sailing, and Ted
I think another factor is that people are rejecting the rounded corners and excessive padding of modern web design, you can't do that in a TUI, so you don't have a designer or standard practice encouraging you to do it. As implemented TUIs have greater information density than GUIs. Make no mistake though, TUIs are a decided step backwards from GUIs. Everything that you can express via text, you can also do in a text area on a GUI app.
The sgi stuff was also engineering focused. The net result was it was not really that fast, powerful sure, but my understanding is the early consumer cards(voodoo) could run rings around them. The game cards did not have the z-buffer depth, fill rate, 3d texture support, line drawing, that sgi's had(cad features), but they could keep the frame rates high and had more features that made the games look pretty.
My personal favorite sgi from the mid 90's was the o2. It had a unified memory model so it was the slow red headed step child of the sgi ecosystem. But because of that unified memory you could effectively pack it with close to a gigabyte of texture memory, whatever the OS and app did not need. This was an obscene amount in 1996. For comparison the top of the line sgi desktop system at the time had 8 mb of texture memory. It does not hurt that the o2 was probably the best designed and engineered computer I have ever seen.
Slightly related to the article. I have a personal cargo bike. The most fun that I have with it is giving friends a ride home from a party. People instantly start giggling and laughing. It's goofy, you get stares and people curious
Python/Jupyter developer in Boston. I build data tools and I start by talking to the people who'll use them, because code that doesn't get adopted is wasted work. My main thing is Buckaroo (github.com/paddymul/buckaroo, ~680 stars), an open-source data table for Jupyter over Pandas/Polars. I built both the data layer and the React frontend. Looking for a team building data tooling (as a product or in house).
reply