Remember the "One Laptop Per Child" project, that developed a low-cost computer for children in developing countries?
-
Remember the "One Laptop Per Child" project, that developed a low-cost computer for children in developing countries? I was always amazed by a certain feature: The "View Source" button.
When you pressed it, the source code for the currently running application would open. This was supposed to encourage tinkering with the software on your device!
I've been pondering what it would take to build that button on modern machines. Has anyone seen something like that?
(Prototype in next toot.)
@blinry Negroponte took Epstein funding. Say what you will, but I'd rather have my hands be clean.
-
@raymaccarthy @agowa338 @blinry yeah, J++ was an attempt to EEE Java, especially for “applets” in IE, that got shut down by the court ruling. dotNET and C# were the subsequent attempt to build a better mousetrap, which largely succeeded in terms of capabilities, but failed to replace Java in adoption because it was closed-source and windows-only
@ShadSterling @agowa338 @blinry
And if C# had been crossplatform and more liberally licenced, Android might have used it instead of Java. Then Oracle would not have sued Google.
But Symbian devs were using Mobile Java and Google wanted them.
Sun had the odd idea that Mobile Java was free-sh, Desktop Java was free-ish, but it was forbidden to use the Desktop version on anything else. It never made sense. -
@blinry I think the OLPC project failed because they foolishly rejected my implementation suggestion
@th Aw
Still have it? -
Remember the "One Laptop Per Child" project, that developed a low-cost computer for children in developing countries? I was always amazed by a certain feature: The "View Source" button.
When you pressed it, the source code for the currently running application would open. This was supposed to encourage tinkering with the software on your device!
I've been pondering what it would take to build that button on modern machines. Has anyone seen something like that?
(Prototype in next toot.)
@blinry Could work if the system compiles the executable from source but also stores the source to reference the executable.
And changing and saving the source would trigger it to recompile? Idk.
-
@blinry Not sure if I'm thinking too complicated here, but doesn't it get ever more complicated what exactly to show there?
If I'm currently looking at a web app that shows some data retrieved from a server-side backend in a browser whose UI is written in (say) Python calling one of the dominant rendering engines and one of the dominant Javascript engines, which of the sources do I show on “View Source”?
It could be anything from the operating system kernel via the CPython or the Javascript runtime to the web app or its server-side counter-part that could be considered most interesting and answering the question: “Oh, I wonder how this works.”
it's both true that that's more complicated, but because of that more important that people understand where "it's coming from". And what "it" is. Yesno?
Well, this is why pedagogy is really hard!
I feel like the simplified, one-app-at-a-time Sugar style was meant to narrow down the possible contexts to make this easier, but also that limited screen space and trying to have a unified design language blurred it again.
-
It's been fun, it feels like a new superpower to "quickly fix something and send a PR". It's also a super dangerous rabbit hole generator, because now that it's easy to fix stuff, it's very tempting to do so…
My prototype has some rough edges:
It clones the latest commit, which doesn't always compile using the #nixpkgs setup (but it seems reasonable to check whether the bug is still there).
And invoking the phases of the nixpkgs stdenv manually can be tricky. https://nixos.org/manual/nixpkgs/stable/#sec-building-stdenv-package-in-nix-shell
@blinry This is such an awesome idea! When I read your first toot I thought immediately "that'd be near impossible for non-interpetted language programmes" but I love this because you've converted it into essentially a search problem!
Such a clever way to take stuff from "almost impossible" to "super achievable" almost instantly!
-
-
Remember the "One Laptop Per Child" project, that developed a low-cost computer for children in developing countries? I was always amazed by a certain feature: The "View Source" button.
When you pressed it, the source code for the currently running application would open. This was supposed to encourage tinkering with the software on your device!
I've been pondering what it would take to build that button on modern machines. Has anyone seen something like that?
(Prototype in next toot.)
-
You'd roughly need to:
- Figure out which program is currently focused
- Figure out the Git repo of this software
- Clone it into a temporary directory
- Set up the required tools to start hacking on it and compile itAs a quick prototype, I wrote a li'l Bash script that does some of these things. It makes heavy use of #nix and #nixpkgs:
https://codeberg.org/blinry/view-source-button
I enters a "dev shell" with the required tools already in the PATH, and even sets up a Git remote to start contributing.
@blinry@chaos.social With some jumping through hoops and applying very dirty heuristics it should also be doable on Debian.
<img class="not-responsive emoji" src="https://pleroma.envs.net/emoji/drgn/drgn_think.png" title=":drgn_think:" /> Isn't this exactly the kind of mapping that appstream should provide? (In theory it could provide at least a link to the source code repository cleanly tagged as such)
-
N necrosis@chaos.social shared this topic
-
Remember the "One Laptop Per Child" project, that developed a low-cost computer for children in developing countries? I was always amazed by a certain feature: The "View Source" button.
When you pressed it, the source code for the currently running application would open. This was supposed to encourage tinkering with the software on your device!
I've been pondering what it would take to build that button on modern machines. Has anyone seen something like that?
(Prototype in next toot.)
@blinry You know where this will lead to? Combined with „agentic AI“, people will create millions of personal improvements to office programs, mail, browsers, etc. Probably with enormous incompatibilities and security issues to each other.
