ときどきの雑記帖 RE* (新南口)

Why Do I Feel Like This?

中吊り広告

金曜日(7/1)の帰宅時に乗った電車の中吊り広告が全部メイドインアビスだった。

flagged

Vのリリース Release 0.3 · vlang/v があったのだけど、 それにあわせて立ったであろうHNの V 0.3 | Hacker News が

[flagged]

となってて…と書こうと思ったが 再度確かめてみたらなくなってる?

ませまちか

新しいバージョンのリリース(ローンチ?)があったようで Launching Version 13.1 of Wolfram Language & Mathematica 🙀🤠🥳—Stephen Wolfram Writings

Launching Version 13.1 of Wolfram Language and Mathematica | Hacker News というスレッドがあったのだけど

The saddest thing about Mathematica is that despite the incredible level of effort invested into it by some of the smartest people on the planet, it will inevitably be relegated to the dustbin of history.

As a proprietary language and kernel, it can never compete long-term with open source alternatives.

この辺を読んで、Mathematica すげえよなあ。と。 何年か前にもクローンじゃないけど 似たようなものを作るという話を見た覚えがあるけど どうなったんかね。あれ。

スタンドアローンなだけではなく クラウドでも…となると さらに難度が上がるだろうなあ。

Mahjong tile

Hugoで麻雀牌の絵文字出すにはどうすればいいんだ?

🀀 🀁 🀂 🀃 🀆 🀅 🀄 🀇 🀏 🀙 🀡 🀐 🀘

(これは直接コードを書いた)

gnu make

にわか管理者のためのLinux運用入門(338) GNU Makeでいく - 関数を知る（変数の種類を表示する） (1) | TECH+ で、知らなかった機能(関数)が紹介されていた。

origin関数は指定された変数が「何」であるかを表示している。ここで表示されている「何」とは、 undefined、default、environment、environment override、file、command line、override、automaticだ。

そこで過去の記事は、と 【連載】にわか管理者のためのLinux運用入門 | TECH+ を見ていくと他にもいくつかそういう機能(関数)があった。 たとえばこれ。

にわか管理者のためのLinux運用入門(336) GNU Makeでいく - 関数を知る（ファイル読み書き） (1) | TECH+

GNU makeには、ファイルのデータの読み書きを行うために「file」という関数が用意されている。 これは、GNU makeに独特の機能と考えて良いかもしれない。

便利は便利だけど覚えて活用するような場面、あるかなあ…🤔

copilot

どうなるんですかねえこれ (日本ではあまり話題にならない(盛り上がらない)気がするけど)

Give Up GitHub: The Time Has Come! - Conservancy Blog - Software Freedom Conservancy

「あなたが客でないとすれば、商品だ」は

if you aren’t the customer, you’re the product.

この部分ですね。 ここだけ切り出してもアレなのでその前後も合わせて見ると

Specifically, GitHub profits primarily from those who wish to use GitHub tools for in-house proprietary software development. Yet, GitHub comes out again and again seeming like a good actor — because they point to their largess in providing services to so many FOSS endeavors. But we’ve learned from the many gratis offerings in Big Tech: if you aren’t the customer, you’re the product. The FOSS development methodology is GitHub’s product, which they’ve proprietarized and repackaged with our active (if often unwitting) help.

「原則」はどうなんだろうという気もするけどまあ。

ということでこれは元記事を「きちんと」読まねばと思ったものの 全部読み通すのきつそう… GitHubに対する質問(主張) だけを抜き出しても

Give Up GitHub: The Time Has Come! - Conservancy Blog - Software Freedom Conservancy

Our three primary questions for Microsoft/GitHub (i.e., the questions they had been promising answers to us for a year, and that they now formally refused to answer) regarding Copilot were:

  1. What case law, if any, did you rely on in Microsoft & GitHub’s public claim, stated by GitHub’s (then) CEO, that: “(1) training ML systems on public data is fair use, (2) the output belongs to the operator, just like with a compiler”? In the interest of transparency and respect to the FOSS community, please also provide the community with your full legal analysis on why you believe that these statements are true.

    We think that we can now take Microsoft and GitHub’s refusal to answer as an answer of its own: they obviously stand by their former CEO’s statement (the only one they’ve made on the subject), and simply refuse to justify their unsupported legal theory to the community with actual legal analysis.

  2. If it is, as you claim, permissible to train the model (and allow users to generate code based on that model) on any code whatsoever and not be bound by any licensing terms, why did you choose to only train Copilot’s model on FOSS? For example, why are your Microsoft Windows and Office codebases not in your training set?

    Microsoft and GitHub’s refusal to answer also hints at the real answer to this question, too: While GitHub gladly exploits FOSS inappropriately, they value their own “intellectual property” much more highly than FOSS, and are content to ignore and erode the rights of FOSS users but not their own.

  3. Can you provide a list of licenses, including names of copyright holders and/or names of Git repositories, that were in the training set used for Copilot? If not, why are you withholding this information from the community?

    We can only wildly speculate as to why they refuse to answer this question. However, good science practices would mean that they could answer that question in any event. (Good scientists take careful notes about the exact inputs to their experiments.) Since GitHub refuses to answer, our best guess is that they don’t have the ability to carefully reproduce their resulting model, so they don’t actually know the answer to whose copyrights they infringed and when and how.

こうだからなあ。

We expect this particular blog post will generate a lot of discussion. We welcome you to interact with SFC staff on our public mailing list about this effort.

Amazon(のCodeWhisperer)が云々というのはこの部分ですね。

While Microsoft’s GitHub was the first mover in this area, by way of comparison, early reports suggest that Amazon’s new CodeWhisperer system (also launched last week) seeks to provide proper attribution and licensing information for code suggestions0.

でその脚注。

However, we have not analyzed CodeWhisperer in depth so we cannot say for sure if Amazon’s implementation is compliant with the respective licenses. Nevertheless, Amazon’s behavior here shows sharp contrast with Microsoft’s GitHub: Amazon acknowledges the obvious fact that there are license obligations that deserve attention and care when building AI-assisted programming solutions.

追記

“Atari Was Very, Very Hard” Nolan Bushnell on Atari, 50 Years Later

HTG: So let’s go the opposite way now. What did you do “wrong” at Atari that people could learn from today?

Bushnell: I think that I - how do I put this without sounding like an asshole? I put up with incompetence more than I should have. I should have been quicker to fire.

この部分からかな。ただ、インタビューにヒッピー(hippies)という単語は何回か出てくるけど 原文のここには見当たらない。訳に混ぜ込んだ意図はなんだろう?

FORTRAN II

先日Kindle本で

というのを見かけ、面白そうな題材と思ってすぐに買ったがちょっと期待外れだった (レビューで☆☆つけたのはわしじゃないがそんな感じ😄)

call by reference が現在のプログラミング言語でどうか (call by shareingと混同されがち) というのはさておいて、 なぜそういう手法が使われたのかは 当時のコンピューターのアーキテクチャに依存する部分が大きかったんじゃないかと思うんですね。

だって、FORTRANが最初に実装されたIBM 704や その後のIBMのメインフレームってスタックないですからね? (前述の川俣さんの本でも引数はスタックに積むのが当然みたいな記述もあったような)

別件で Transcription of Smithsonian IBM 704 Fortran II source code. — Software Preservation Group というのを見つけて これはと読み始めたはいいがまるで分らん😄

370互換機のアセンブラはちょっといじったことあるけど IBMのメインフレームっつても大違い(当たり前)

MS221  SXD ABAR,4                                                       4F13594 
       TRA MS020                                                        4F13595 
MS230  LXD ABAR,4            PERFORM LEVEL ANALYSIS FOE ENDMK,          4F13596 
       TXI MS231,4,3                                                    4F13597 
MS231  TXL MS232,4,0         FINISHED, HAS LEVEL BEEN REDUCED TO ZERO,  4F13598 
       TSX DIAG,4            NO, ERROR.                                 4F13599 
MS232  LXD ARGCTR,4          WAS THIS AN ARITH FUNCTION STATEMENT       4F13600 
       TXL STATEC,4,0                                                   4F13601 
       CAL FSTYPE            YES, UPDATE FUNCTION TYPE AND              4F13602 
       ADD L(1)              COMPLETE FORSUB ENTRY BY ASSIGNING         4F13603 
       LXD BK,1              TYPE NUMBER.                               4F13604 
       STA FORSUB-1,1        X                                          4F13605 
       ORS ARERAS            ALSO SAVE FOR LATER REFERENCE.             4F13606 
       TRA STATEC                                                       4F13607 
       TRA MS230             ENDMK                                      4F13608 
       TRA MS260             (                                          4F13609 
       TRA MS210             ,                                          4F13610 
       TRA MS220             )                                          4F13611 
MSERR= TSX DIAG,4            =                                          4F13612 
       TRA MS250             -                                          4F13613 
       TRA MS250             /                                          4F13614 
       TRA MS200             ,                                          4F13615 
       TRA MS250             +                                          4F13616 
MS240  ALS 30                *    SAVE  *                               4F13617 
TRBLKA BSS 0                                                            4F13618

↑の真ん中あたりにTRA なんとか(TRAはアキュムレーター(≠レジスター)の内容をインストラクションカウンター (≓プログラムカウンター)に転送する命令 無条件ジャンプ命令)が連続している部分があって、 なんとなくサブルーチン呼び出しが連続しているように思えるけど 「戻り番地をスタックに積んでジャンプする」 命令なんてものではないので 少し上のラベルMS230 からの命令と合わせて見てみても 何をどうしているのかよくわからない😓

あと 引数をとるサブルーチンのアタマはこんな感じ。

       REM DRTABS(,4)/ CALLS RDRX,DIAG. CALLERS=C1200,SS000,ROYCNV,CMA, 4F10695
       REM VRA(VRD).                                                    4F10696
       REM DRTABS IS CALLED BY TSX ....IX,4 -WHERE .... IS THE NAME OF  4F10697
       REM THE DRUM TABLE REFERRED TO. DRTABS MAKES ENTRIES IN THE DRUM 4F10698
       REM TABLES, AND ALSO SEARCHES THE DRUM TABLES FOR INFOMATION.    4F10699
       REM DIMALT= ENTRY POINT FOR DIMENSION TABLES.                    4F10700
DIMALT CAL TXLOP                     PICK UP SWITCH CONTROL,            4F10701
       TXI DRTABS,0                  AND GO SET SWITCH FOR DIM TABLES.  4F10702
       REM ALT= ENTRY POINT FOR ALL OTHER DRUM TABLES.                  4F10703
ALT    CAL TXHOP                     PICK UP SWITCH CONTROL,            4F10704
DRTABS STP DIMSW                     SET SWITCH.                        4F10705
       CLA 0,4                       GET CALLER (TSX ....IX,4) IN AC.   4F10706
       SXD XR1,1                     SAVE THE C(XR1),                   4F10707
       SXD XR2,2                     SAVE THE C(XR2),                   4F10708
       SXD XR4,4                     SAVE THE C(XR4), AND               4F10709
       STQ MQ                        SAVE THE C(MQR).                   4F10710
       ADD L(1)                      PREPARE TO MOVE PARAMETERRS        4F10711
       STA MOVE                      INTO WORKING STORAGE.              4F10712 
       SUB L(4)                      PREPARE TO UPDATE                  4F10713 
       STA UPDATE                    PERMANENT PARAMETER.               4F10714 
       LXA L(5),1                    MOVE 5 WORDS                       4F10715 
MOVE   CAL **,1                      (....IX+1)                         4F10716 
       SLW TEMP,1                    OF PARAMETERS                      4F10717 
       TIX MOVE,1,1                  INTO WORKING STORAGE.              4F10718

メモ

まあわたしが使っているのはFirefoxなんだけど😄

year.half.days

≪ prev ふまんがあります
next ≫ 七夕の国