@Sʨɠɠan Why not just reply "Okay, we'll change it"? I doubt that he cares what name we actually land on, as long as it doesn't make it look like we're running an official AoC tie-in.
@RadvylfPrograms i.e python would be map(lambda i: i + 1, nums). in that case, id clearly prefer [i + 1 for i in nums]. but in java its a simple .map(i -> i + 1). so it depends on the language
I'm kind of not sure how to deal with tuples and structs in general in Tundra, since I want to avoid the JS-style "structs and dicts are the same data type", but I also don't necessarily want to have static typing for tuples/structs and nowhere else
yes, of turning on my raspberry pi and seeing some shit like panic: init exited with code -19987: failed to inititalize device /sys/waterjet/alice/packages/HOT_BUSTY_ANIME_GIRLS_VIEWER.jet.d/aviewer/main.py: unknown device type "import requests"
I actually intend to make a little disclaimer along the lines of "software from the internet can screw your computer up, please don't install things you don't trust" that shows up when running waterjet for the first time
well in that case can you make it so that waterjet's pakdef for tundra can do the dependency resolving and downloading by itself and then shell out to taiga for installation? that's what it does with pip
You'd just install the software the same way you would ordinarily. If it was from an OS packaga manager, you would probably include the dependencies rather than delegate that to Taiga
Or more likely, use some sort of compiling or minifying functionality which I hope to include in Tundra so that some sort of chaotic thing like JS has doesn't show up
I'm not fully decided on how I want Tundra programs to be run, or what their scope would be
If it'll be intended for finished software, I will include compilation as an option. If it is intended for web stuff, I'll include JS or Wasm transpilation. If it's intended for small scripts used mainly by other programmers, it'll be purely interpreted
well, the OS manager then has absolutely no clue what packages are being installed because it can't see what the other manager is doing, which kinda misses the point of a package manager
waterjet's whole goal is to be a universal package manager but if you do stuff like that than it can't do that