Consider the possibility that without the first 2 problems, the latter 2 examples would be no problems at all. That tells you what to focus on and what to ignore =)
I could be wrong here culturally tho... I've never been in Kathmandu.
3,253 karma · joined January 16, 2008
I could be wrong here culturally tho... I've never been in Kathmandu.
Minimalist fast native (not browser-based) code editor for Windows, Mac, Linux, BSD. Both a terminal TUI and a native-GUI version for each. First-class (ie. by same author) LSP package. Fully Lua-scriptable for needs beyond LSP. Succinct C & Lua code-base. FOSS, and matured & maintained ever since 2007. All the basic table stakes (syntax coloring, multi-select-and-edit etc).
Woulda skipped on Sublime back when, had I known about it then.
But just my interpretation here =)
"For that server" is the other number-of-requests..
> Procedural generation can't be used as an excuse to do less work
> So people going into procedural generation thinking it'll save them work are already destined to fail
Consider the possibility that nobody really picks up proc-gen in the hopes they can laze out a RDR3 or such over the weekend.
Another thing is, this applies to indies and AAAs alike: while a big world has to have interesting unique things in it, by definition not every square meter can/should be chockful of another "interesting truly unique thing" because if the whole world is filled like that, it's just another kind of sameyness in that the novelty factor would wear out just as quickly once you're getting that there truly is true novelty in absolutely every little square meter, which kills the novelty sensation in a heartbeat. Novelty delights us in a backdrop of routineness, sameyness, same-old-same-old-ness. So in between interesting things, the thusly necessary slightly-"duller" in-between areas are to pace and prep and make one anticipate novelty "hopefully almost just around the corner". Ideally it's so spaced to appear just in time before the player resigns such hopes.
And so if you're going to have slightly-duller "filler areas" (and let me posit that any real-world say forest (in a biome one has traversed before), without the physical air and smells and winds (or friends/pets stringing along) is quickly "proc-gen dull-ish" within minutes — even in reality — or call it "meditative"/calming) — so again, if you're going to have slightly-duller "filler areas" just to connect and space apart the unique content things to good effect, then procedural placements/scatterings/variations are going to beat manual placement not just in "effort time" but because manual would swiftly look much more repetetive (being inevitably eventually effectively copy-paste driven) given the scale of environments under discussion, even if it would not take a human months of menial clickery.
Rockstar gets it right imho but their approach would also get your "many caves in Skyrim" right because they manifest little novel uniquenesses not in scattered objects or env textures/models but via lively interactive interludes, whether it's animals frolicking or chasing each other or attacking towards you or "random stranger" incidents etc. That's the right kind of "filler but not boring", nobody cares about the variety of the rocks, only noticing them if nothing seems to be happening.
Also of interest, hosting game assets is a whole other price category than just source code. =)
Last quarter I made a 20GB (when packaged) open-world 3rd-person game in Unreal, but the whole project folder itself was 160GB. That's basically "the source". All kinds of assets were dumped in there for experimentation & exploration & try-outs, and untangling that to strip down the project to only-what's-used-in-the-Level-file is not just not a one-click action as it should be, UE's weird reference tracking very quickly opines that everything depends on everything and nothing can be "just deleted". Would you host that whopper? I can imagine even Github wouldn't. (Haven't checked tbh — probably should have =) Because I wouldn't untangle that just to post "the source". Nobody even cares about the free downloadable ZIP (executable + content) for Linux and Windows that I made (mostly as a fun b-day gift to my bro, not per se for any other audience or any kind of adoption) and put on itch.io, who'd even care for "the source". Plus in this space it's never (at the indie level) Rocket Science, so whoever is in the coding game keeps it all home-grown self-engineered and tailored to size, and whoever isn't will forever try & fail to "plug-and-play with 3rd-party snippets".
Also of interest, many solo gamedevs or non-team creators without an artist at hand keep a vault of dear-to-their-heart pro-calibre high-quality game art assets that they may well have once received for free or very little money in the ever-coming-and-going gamedev-specific Humble Bundles, Epic / Unity / etc. store sales or freebie specials. They have thusly acquired a valid license for using them in their packaged games, but not to publish those assets' sources (if even included) with their work. Now some may stick religiously to Creative Commons / FOSS-licensed assets, but if Their Work is their chief & foremost priority rather than sporting-and-supporting "only certain types of licenses" out of some conviction — their works won't partake in your network.
This is not to rain on your parade or discourage your enthusiasm, just some things that come to mind, "to be accommodated" / considered in your pursuits. =)
> There is one other convention — sometimes we repeat a key point to emphasize it. In addition, we sometimes repeat a key point to emphasize it.
One more quote and I'll stop:
> ctime() converts its argument into local time, which will vary from GMT, depending on where you are. California, where this book was written, is eight hours behind London, and several years ahead
Also: software that works like molasses on the developer's high end workstation
Not sure that's so very true for most langs / stacks other than Python. Go LSP & vscode extension is Go-owned, C++ you have clang LSP+ext and can really skip MS' offering(s) there. TypeScript LSP+ext is most likely OSS (dunno) or else MS-owned anyway; dotnet same. Niche langs own their LSP+exts anyway. The builtin HTML / CSS stuff is bare-bones IIRC, if there aren't richer OSS alternatives out there yet there sooner-or-later will be. Python, I wouldn't know, but let's face it, if a lang is a big FOSS project it can and will mobilize their own owned and ever-more-excellent LSP + ext if and when necessary / desirable — and if it's niche and small-scale, MS won't anyway, proprietary or not.
In the audience space of meet.hn, defaulting to github/gitlab/sourcehut/etc profiles instead would have been just more apt =)
There's also downloadable CSV lists of the world's place names at https://geonames.org (and stably have been kept available and updated for many years by now) — if you already have a DB (likely in your case), script up some csv-to-dbtable dumping and thus you save on networked API call overheads just for querying the world's existing place names.
(It's regularly updated so best to keep the convert-and-dump script or logic around if you go that route.)
On the one hand, this has always bugged me slightly. But on the other hand, every time when it came down to it in practice, I realized two things: first, a VSC extension that does nothing but wire up the LSP language clienting library is a tiny project with no major maintenance burden; and secondly, more importantly you usually want additional language-extension client-side features that are editor-specific by nature and either couldn't or shouldn't be abstracted-inside / covered-by the language-server / lang intel / IntelliSense realm. Syntax-coloring and other grammar-describing meta-data come to mind, or custom Notebook, or rich & productive build or debug or pkg-mgmt etc. helpers & tooling UX, etc. Stuff that arguably belongs in one's "language extension" but is mostly editor-specific and thus at the same time doesn't truly belong in one's "language intelligence serving".
https://www.cell.com/current-biology/pdf/S0960-9822(24)01027...
But there's a lot more movies coming to mind that deserve a 2nd watching imo, just haven't done so yet. Eg. most Coen Bros ones come to mind.
Too bad we can't anthromorphize evolution, else I'd say: maybe that was evolution's "idea" / "gamble" to begin with. Evolve the being that evolves everything "evolution" (nature) itself hasn't. Pyramids, skyscrapers, suburbs, machinery, poetry, computation, computation devices.. entirely abstract pure-thought-stuff machines aka programs.. abstract machines that "evolve" new ones.. and whatever stems from that when we/they get there.
But.. evolution doesn't have ideas or plans. Right? Nevermind that we, a self-proclaimed product of evolution, do. Did we even invent (create / evolve) .. the idea of "ideas" and "plans" there? Who could tell, other than some big overseer of it all =)
What does "outpacing natural evolution" even mean once non-random-mutation-based change makers .. just naturally evolved via the natural evolutionary mechanisms? Everything they (we) do then is "natural evolution" by extension / implication. Genes and fitness "came up with" (or randomed up) us doing all that, even us wondering and worrying whether we're "outpacing natural evolution".
Curious food for thought!
It's called TextAdept. Much of it is itself built on its own Lua extensibility story, which runs on a fairly compact C core. Both native GUI and terminal versions, using the same user config (keybinds etc). Linux, Mac OS, Windows builds. LSP support built in. Plenty of community-produced extensions around (but of course not as vast a range as VSCode's VSX eco-system furnishes).
Here's JS string interpolation:
`OK ${10+20} == 30` // result: "OK 30 == 30" — a JS string
Here's a quasiquote-unquote:
`(OK ,(+ 10 20) == 30) ; result: (OK 30 == 30) — a list of 4 atoms
In my toy Lisp I used $ instead of comma, which I found a tad "more readable" coming from today's JS, Perl, Bash world. (And makes quasiquote... "the money quote"? =)
I'm still a happy camper on VSCode but if it ever begins to crumble/rot/overbloat (by subjective criteria), I'd hop onto that. Lua is (for my purposes here) no better/worse than JS/TS. Save for those darned 1-based array indexings!
LSP-capable too, last I heard, else it'd be a non-option for me in 2024. https://orbitalquark.github.io/textadept/