from wikipedia:
Quibi (/ˈkwɪbi/ KWIB-ee) was a short-lived American short-form streaming platform that generated content for viewing on mobile devices. It was founded in Los Angeles in August 2018 as NewTV by Jeffrey Katzenberg and was led by Meg Whitman, its CEO. The service raised $1.75 billion from investors.[1] It launched in April 2020, but shut down in December 2020 after falling short of its subscriber projections.[2][3][4] In January 2021, Quibi's content library was sold to Roku, Inc. for less than $100 million.[5][6][7]
Languages spread when there is an obvious advantage to using the language. Java, in the beginning, was obviously better because it was multi platform, free, was sort of object oriented, and had an interface to C (to connect to existing libraries). It was finally possible to write once, and run on windows, apple, Unix. I worked on a DARPA project, and we snapped up the first public release because we needed to support all three. This was about 1995.
The next winning language will implement correct programs. There will be a specification language (assertions, type invariants, API contracts), and an implementation language. In the middle, massive semantic checking tool.
"Easy to learn" is a red flag. Arguments about ; and {} are silly.
1. AR glasses with face recognition. See the coded reputation / reviews / truthfulness / relationship status / political views of the person.
2. Software for computers / smart TVs / cell phones that completely blocks ads and tracking. Software that generates tons of fake ad views, and ad clicks. Software that sends nasty messages to the cell phones of CEOs of advertising companies, ad networks, and ad carrying media, ad servers.
3. Software for cell phones that spoofs location tracking.
4. Auto dashboard camera plus GPS plus software for drivers to instantly report traffic violations that they observe.
5. Software that tracks real time location of politicians, full time Doxing.
6. Add on software for Metaverse so that the end user can change the local appearance of avatars of other players. Your co-workers are clowns.
1. How to select a programming language. What features are important to develop correct programs. This is a very emotional topic. Formal specification languages.
2. How to certify great programmers. Finding the 10Xer. Not hiring the weak. Developing certification / licensing for software developers.
Build an effective solution for remote work for developers. Then expand the solution to other employees that are not 'hands on' in a particular place.
Something better than zoom and slack. Use multiple displays, cameras, speakers. The most environmentally friendly commute is no commute. The most environmentally friendly office building is no office building.
In the beginning there was the command line. A keyboard input to a type on paper output. Then UNIX. The first editor was 'ed' (edit). It was line based, designed for a keyboard onto paper output. It was enhanced to become 'ex'.
When the happy hackers at UC Berkeley were porting UNIX onto VAXen (becoming BSD Unix), CRT terminals were available, notably the DEC VT-100 and other less expensive ones. These terminals had commands that would move the terminal cursor around the screen, allowing a editing program to modify the 24 (or 25) lines of 80 characters on the display. But the terminal commands were DIFFERENT. So the configuration file TERMCAP and the C library libcurses were created.
Then 'ed' / 'ex' was expanded to become 'vi' (visual, not six). Note that the 'ed'/'ex' commands are still there, invoked by the ':' command. Now there was a full screen text editor that worked on different CRT terminals.
This was all before UX design existed. It evolved. 'vi' was a giant leap up from a typewriter editor.
I recall there also was em which displayed a single line as it changed. With ed I used to invoke the 'p' command constantly to confirm that my changes were correct. With em it was done for me automatically.
IMO Unix utilities evolved along with the concurrent advances in technology. If anything, the pioneers were far more concerned about functionality than aesthetics. The earliest UX principles only emerged from the work on Smalltalk at Xerox PARC.
With stack ranking, team members compete, not cooperate. They will make other members look bad, with trash talk, not responding to slack and email, ans actual code sabotage. Some team members act like the chariot race in Ben Hur.
Remember that EVERY PLAYER in the winning Super Bowl gets a ring. At the Olympics, EVERY team member gets a metal (Ice Hockey, Basketball, Soccer).
Some managers will hire someone incompetent just so they can stack rank fire them.
