Recent submissions

Comment · 2 months ago
when i'm feeling blue i go read and toy with geoworks source.. it's kinda weird to read TODOs from 1900 :)

and one wonders what could have been if there were not incompetency of microsoft etc..

Comment · 4 months ago
depends on artillery.. i mean canon:

F5 is for save game

F9 is load :)

Comment · 4 months ago
hmm, yes it's interesting but honestly - not much of the stuff is usable IRL

the only thing i was regularly using (Loki library) for was the assoc_vector

Comment · 5 months ago
this compatibility sucks sometimes.

for example you want to add nice feature to c++ with nice syntax, but there is a similar syntax somewhere in C that nobody uses, but you have to support it. you end up with nice feature with horrible syntax.

Comment · 6 months ago
> It's a magical feeling.

hehe working with this TV library scratches my nostalgia itch :D

it probably saved me from futile efforts like writing apps for GEOS or joining the one person Hurd team.

Comment · 6 months ago
i mean: for example you have a problem 'how do i create scrollbars two squares wide' (not a real problem, can't think of something now)

if you work with qt for example so these days you ask google/stackoverflow/qtforum and you have multitude of responses if it's a common problem and sometimes you have whole solutions ready to copy&paste.

when you work with TV and ask google - you usually get... not much. so you have to take the longer route: study the doc/books (you mentioned), study the code, examples... or be friend with the author of this library or those two or three people who actively use this library these days ;)

-- edit: btw those books (there's a c++ one as well) you mention are good, but, sadly, no book is detailed enough when you have very specific problem :)

Comment · 6 months ago
it is still very well usable - i used TV 2.0 year ago to do some prototype. i wanted (and mostly succeeded) to create turbovision front end for LLDB debugger... you know, that would behave like Borland's Turbo Debugger.

few quick notes:

- blimey it was like it where i left it 199x :) you can even compile/run code from 1993 without major issues.

- there's even a better internal TV editor based on scintilla, so with syntax highlighting and such. although i was trying to mod it without success, i'll have to ask author for help, probably.

- there's no documentation (in the sense of common wisdom), so you can't ask stack overflow or AI. you have to do it like in old days: learn from examples (that have bugs in them ;) and read those few books on turbo vision again and again.

- manual 'layouting' is kinda annoying, some auto layout like qt would be handy

- i miss splitters, but that should not be hard to implement

- tbh i am kinda surprised how small and compact TV really is. it felt ginormous in the 90ies :)

overall - the author did very good job modernizing the library and i love it.

Comment · 8 months ago
i gave up on stacking - no matter what i do, i get passive-aggressive comments from my wife

'raccoon on cocaine' she calls it :)

Comment · 9 months ago
MUDs were the fentanyl of university students :D
Comment · 10 months ago
cool, i was looking for something like this to try on my own puny hw - thanks!
Comment · 11 months ago
'We have D at home' :)

c:\> subst d: c:

Comment · 11 months ago
Stacker compressed volume ;)
Comment · 11 months ago
LOL :D somebody has high opinion about himself
Comment · 11 months ago
heh, i have seen programmers using virtual everywhere, because they were lazy to use declspec(dll_export) on windows system :)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton