If I had any faith in American school systems, I would suggest bringing back computer classes instead of just trusting "digital natives" to run into every toll booth unhindered. But they will be taught by old people who are even more computer-illiterate than the students...
What do we do about this? How do we teach people computer literacy? What would the lesson plan even look like? I'd really like to hear some suggestions from someone more experienced with computers than myself.
Would the final exam be installing Arch Linux? ... I mean, knowing the software stack of a computer in-and-out is kinda useful, perhaps, and the nitty-gritty of all the packages does that well... But the average person never has to worry about partitions, and there's nothing about an Arch install that tests your knowledge of browser cookies and adblockers.
Are you commenting only for the sake of commenting?
This is not a very substantive addition; I'd say it's pedantic to say a divide that is "not [just] between smart and stupid people" does, in fact, divide smart and stupid people at SOME point.
Your other comment [1] is only slightly better, but I can't help but feel that you're presenting it as a contradiction where there is none. Yeah, us Americans are concerningly illiterate, but we're concerned in the first place because we all agree that we believe reading and writing is not a useless skill.
So ultimately, in both cases, the article is correct, and you're... also correct, but not actually adding anything to the conversation.
Since we've stepped from interpreted language (Lua) to compiled-to-VM language (C#), let's go all the way down to compiled, low-level language (C) with Raylib!
I'm curious as to how you came to that conclusion. Did you run any tests, or is it just a general observation? What's your computer hardware like? This isn't an accusation of anything, I promise I'm genuinely curious.
I've not done proper scientific comparisons, but had to reimplement some games as websites to make them reliably perform on Raspberry Pi's we used embedded.
This is a bit of an apples to oranges scenario, because the algorithm and architecture is not exactly the same, despite the game functioning identical.
The main weak points of LÖVE that we hit were mainly around embedded video playback though, which is probably very well optimized in chromium.
As the open source author in question, I'd politely ask everyone to not draw overly-generic conclusions from an ancient discussion in some third-party forum, which links to a (now) resolved bug report.
Open source is not a one-way street. By publicly disparaging open source projects, you're actually harming the ecosystem you rely on.
There are a lot of free-as-in-freedom alternatives to (and clones of) PICO-8, but TIC-80 is indeed the most popular one, by far. And popularity is important for any software ecosystem. I really like that it supports other languages, even if that kinda inhibits its ability to be embedded into small hardware.
Apparently the nightly release supports DCPM samples now. Dunno why.
The fantasy computer by 100 rabbits? I love their philosophy, I'm glad Varvara exists, but I'm personally not up to program assembly for a 4-color screen, and I'm sure many others are the same.
For a small while I've had the idea of a [game engine/fantasy console/Scratch clone?] that comes packed with a bunch of example games. The example games should be good enough that people download it just to play them, but they are also encouraged to peek into their source code. I'd hope for it to be a sneaky gateway into programming.
For that, I'll keep this in mind: "Unlucky players may look at the source code of a chance-based effect to check if the odds are actually as stated."
If I recall correctly, there was also the issue that a Nintendo 64 ROM of their game would be fundamentally incompatible with Steam, which (as many forget) is technically their DRM solution. I could be wrong, of course.
You are free to publish any ROM to any system, it's a basic right against both monopolies and freedom of speech restrictions. What you can't do is to ilegally pull propietary dependencies without permission.
The problem I'm pointing out is that it's a work based on a Valve property that fundamentally cannot be tied to the DRM because it's "just" a ROM.
I believe this came up when the creator was talking about libdragon-- Valve has been more forgiving of other games like Hunt Down the Freeman and whatnot because they're native executables with the Steam DRM, which video games based on Valve properties necessarily must have. Portal 64 simply cannot do this, because Steam is not a Nintendo 64 application.
Yeah, it seems to only be a problem when you're a human being remixing the culture you grew up with.
Meta can admit to soullessly scraping books they don't own for their for-profit AI datasets [1], and it's not a problem because they're Meta. But if you're an artist? Nope. Sampling in hip hop songs, for example, is in a "complex legal gray area" (translation: "it's illegal but we don't want to admit that out loud") [2].
What do we do about this? How do we teach people computer literacy? What would the lesson plan even look like? I'd really like to hear some suggestions from someone more experienced with computers than myself.
Would the final exam be installing Arch Linux? ... I mean, knowing the software stack of a computer in-and-out is kinda useful, perhaps, and the nitty-gritty of all the packages does that well... But the average person never has to worry about partitions, and there's nothing about an Arch install that tests your knowledge of browser cookies and adblockers.
reply