Photoshop was ported to IRIX using Latitude, Quorum Software's implementation of Mac OS System 7. Apple later acquired the Quorum's code and it became part of Carbon.
One big problem is that Python's semantics make it difficult to implement the language efficiently. When I translate the sieve code into safe Common Lisp, I get a speedup of 15. After adding a few declarations, making the code as unsafe as C, the speedup factor is 30. Those improvements are possible because the compiler can assume many things about the functions and operators used in the code. For instance, that the Lisp equivalents of range() and len() have not been redefined.
There's a big difference between the complexity of setting up Bazel and the experience of using Bazel at a company where Bazel has been set up for you. As a user I love Bazel. When working with Java, I use the java_binary and java_library rules. When coding in Go, there's nothing new to learn regarding the build, just use go_binary and go_library instead. Everything is repeatable, builds and tests are cached, it's easy to query the build dependency tree, etc.
A few startups are offering "Bazel build/test as a service." It's one way to eliminate the work involved in setting up Bazel for an organization.
The best way to acquire a quality sofa is to purchase a used one made by a furniture maker known to create high quality pieces. It requires a bit of research. You need to figure out which builders around you produced excellent furniture 50 or more years ago. In the USA, Dunbar is an example. Buy an old Dunbar sofa from the 1950s and reupholster it. It will easily last another 100 years.
When I was about ten, Chi Corp., which was associated with Case Western, had an open house. I keypunched my name on a card and fed it to a Univac 1108, which output a large image of my name on a line printer. I think an image of Snoopy was also output. I was hooked.
In middle school wrote Basic code on an HP-2000E. High school summer job writing C code on a PDP-11/70? running Version 6 or 7 Unix. Later, spent a summer at Bell Labs. Bjarne was working down the hall on C with objects. Rob Pike demoed a wire-wrapped Blit prototype. I wrote an assembler for an Ikonas frame buffer in Turner Whitted's graphics group for a C compiler port.
Having broken a couple of kingpins at high speed on roller skates, it's definitely no fun. Unfortunately, the kingpins are under a lot of stress and they're threaded. Invariably, the break occurs on the threads.
Titanium kingpins are available for skates and skateboards, and are much lighter. I don't know if they help with breakage.
Good quality roller skate truck pivot pins end in a spherical ball and the pivot pin cup on the truck is also spherically machined. There's no bushing in the cup.
Good quality skates have pivot pins whose length is adjustable. I don't know if skateboard trucks generally have this feature.
You tighten and loosen the pressure on the kingpin rubber bushings by shortening and lengthening the kingpin in order to adjust resistance for cornering. When you do that, you also need to be able to adjust the length of the pivot pin. Otherwise, lengthening the kingpin results in a pivot pin that's not resting properly in its cup. You want it just touching, not floating out of the cup or exerting a lot of pressure on the cup.
Roller skating plate trucks are similar to skateboard trucks.
Kingpin angle affects cornering ability. Kingpins at higher angle from vertical corner more sharply, so skaters doing figures tend to prefer more vertical kingpins than dance skaters, who want to be able to do deep curves. For instance, kingpin angle is the major difference between Snyder Super Deluxe and Imperial plates.
Durability is a serious consideration for roller skating kingpin angles. It's painful when a kingpin breaks and more common with less vertical kingpins, so most skaters doing freestyle will choose a plate with kingpins closer to vertical. Roller skate plates also often have a "jump bar" connecting the two trucks to decrease the chance that a kingpin will break when a jump is landed. Sometimes even a jump bar breaks.
I code my personal projects in Common Lisp because I like the language and because the code I write today will likely execute without modification 20 years from now.
Yes. At the end of the following Usenet post, the developer of a Python implementation compares the language features of Common Lisp to those of Python in order to explain why Lisp code can be compiled to run much much faster than Python. The same kind of comparison can be done for JavaScript. The problem is a collection of Python features, each of which saps performance.