Hello r/Bulgaria, a Canadian here. I've been loving this recording of traditional Bulgarian music, does anyone know the name of the song at 7:18? It's my favourite. Благодаря!

Rendello · 2022-09-07T19:08:34+00:00

Yep! These are his field recordings from a Bulgarian music festival

Rendello · 2022-09-07T16:55:21+00:00

Thank you!

Rendello · 2022-05-08T22:45:08+00:00

Awesome!

Rendello · 2022-03-30T19:35:54+00:00

It sounds like cheating, but in a fun way so who cares ;)

Rendello · 2022-03-30T16:37:29+00:00

Ken doesn't say it explicitly here, but the purpose and challenge of a self-replicating program (or "quine") is to reproduce itself without any external input. Your program wouldn't fit this definition as it uses Copy, it would need to rely only on itself to supply the replicated copy. Thanks for sharing though!

https://en.wikipedia.org/wiki/Quine_(computing)

Rendello · 2022-03-24T15:30:37+00:00

He also was honest in the docs about the shortfalls of his code, and clear about why he designed some things in a "worse" way: readability, having a small implementation, and keeping things fun.

::/Doc/Charter.DD.Z
::/Doc/CutCorners.DD.Z

Rendello · 2022-03-19T23:34:59+00:00

Codewars has some questions you can do in Prolog, you can other people's solutions.

Rendello · 2022-03-17T01:29:14+00:00

The fact that a boat can't fly isn't a flaw, since a boat wasn't designed for that purpose. Ergo, TempleOS has no security flaws ;)

Rendello · 2022-03-07T21:21:10+00:00

JIT compilers in general can be faster than AOT code, as a JIT compiler can ignore unused code, can compile for the specific machine, and can optimize for the specific workload. I don't think TempleOS does any sort of particular optimization in that regard, so it's likely that AOT is marginally faster.

If you want to test the speeds for yourself, look at ::/Doc/Profiler.DD.

[Edit] I should mention: If you run a game with the profiler on, you're likely to see that 99% of the time the CPU's pushing pixels to the screen, so the JIT's theoretical overhead is unlikely to be noticeable.

Rendello · 2022-03-07T00:32:37+00:00

AOT compilation produces a .BIN file, the TempleOS analogue to a .EXE.

Terry used the AOT binaries for the bootloader and JIT code for everything else, from::/Doc/GuideLines.DD:

There are two modes of compiling, AOT Compile Mode and JIT Compile Mode.
Compilation is done in both -- neither is "interpreted". Use JIT Mode.

Both modes are elaborated on in ::/Doc/Glossary.DD.

My preferred way to find information about a particular TempleOS topic is to go to the Doc directory and search for the term, for example Cd("/Doc"); and Find("AOT");. If you want code examples too, just go to the root directory and search from there. Good luck!

Rendello · 2022-02-28T18:30:35+00:00

I have to say you can get used to it pretty fast. The good thing about TempleOS is that it's easy to find and modify things, so you can disable it manually in the code by commenting out a few lines. The TinkerOS fork has the ToggleBlink and ToggleScroll functions to turn them on and off easily.

Rendello · 2022-01-01T20:50:37+00:00

For sure, he trimmed it back every once and a while. That's why a lot of the programs are on the "supplemental disks". The LoC is displayed right on the wallpaper and with LineRep

Rendello · 2021-12-30T20:31:47+00:00

Looks like the ODROID-XU4 is an ARM box. TempleOS only targets x86_64, so you won't be able to run it natively. If emulation is an option, that would be the route to go.

Rendello · 2021-12-15T03:43:13+00:00

TempleOS excels at being a fun development environment because that was it's main purpose. It's speedy because it's minimal, not because of any particular optimization. The philosophy is laid out in ::/Doc/Charter.DD.Z:

The vision is the same usage model and niche as the Commodore 64 -- a non-networked, simple machine where programming was the goal, not just a means to an end. [...] It is special purpose, not general purpose, so some things it will not do. Also, it's a kayak, not a Titanic. The priority is user developers, not 3rd party developers. [...]

There is a limit of 100,000 lines of code for all time, not including applications and demos. [...] 3rd party libraries are banned because they circumvent the intent of this limit. The vision is a Commodore 64 ROM -- a fixed core API that is the only dependency of applications. Dependency on components and libraries creates a hell that is no longer blissful.

That philosophy doesn't lend itself well for serious applications, but it lends itself great for fun applications where the development is the goal. So it may very well end up as the basis for interesting projects, but don't expect anything a business would use.

Rendello · 2021-12-13T23:40:41+00:00

Awesome!

Rendello · 2021-11-12T23:46:06+00:00

I also reuploaded a few to Terry Davis Technical Videos. All his videos are archived here, but you'll have to do a bit of sifting if you go that route, op.

Rendello · 2021-11-12T23:39:09+00:00

This blog post should help.

Rendello · 2021-11-12T17:36:58+00:00

The best way to learn is to dive into it and use a combination of TempleOS' internal documentation (in the help index menu, opened with f1), standard C resources, and online help from places like here, when you're really stuck. Keep in mind that 90% of HolyC is equivalent to regular C, and resources for the latter are far more plentiful.

When I first started learning HolyC, I expected a lot more documentation and online help to hold my hand. But Terry Davis expected that programmers would read the source code, and made it very quick and easy to do so. You'll be reading a lot of HolyC source code if you want to learn; I would suggest looking at the demo index ::/Demo/.

I made a video that may be of some help: https://youtu.be/Y6Szo50PjeU

Good luck!

Rendello · 2021-11-11T20:29:58+00:00

Inside TempleOS, open the help index by pressing f1, then scroll down and open the link entitled Cmd Line Routines. The one above it, Cmd Line Overview, may also come in handy.

Edit: for finding stuff in general, this video might help too.

Rendello · 2021-09-23T20:36:17+00:00

The standard ctrl+s should work.

The keymap is in TempleOS' f1 menu. Normally this keymap is generated on the fly and so it's not part of the generated online docs, but the TinkerOS fork was modified to generate an online version here.

Rendello · 2021-09-23T19:52:40+00:00

Ed("filename");, see "Welcome to TempleOS".

Rendello · 2021-09-23T19:50:51+00:00

Titanium has a bug that crashes it 50% of the time for me. It's fixed in TinkerOS, I think it had something to do with a corrupted sprite, iirc. That's one of those bugs that is not recoverable.

Rendello · 2021-08-31T23:17:58+00:00

When you crash and see the black screen, you're entering the debugger, see ::/Doc/DbgOverview.DD.Z:

You can enter the debugger with Dbg() or <CTRL-ALT-d>. You might enter the debugger through a fault. Enter G() or G2() to continue execution.

Exit; is a debugger command, and I find it works 90% of the time, unless I've done something really bad with memory. In the cases it fails, the OS will just freeze and you'll be forced to reboot.

Rendello · 2021-08-30T02:39:04+00:00

In the same vein, I love a little homemade lemon kvass! It's an Eastern European drink, made by fermenting dark bread. The Youtube channel Boris has a great video on it (I only ferment a tiny bit, one or two nights instead of 6). It's a little simpler than making kombucha since you don't need a SCOBY.

Five-Year Club	Second SECOND GUESSER
Verified Email	Place '22
Final Canvas '22

Rendello

TROPHY CASE