home.social

#borland — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #borland, aggregated by home.social.

  1. Well this sure brings back memories.

    It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.

    Disk Images
    archive.org/details/borland-tu

    User and Reference Manual:
    archive.org/details/bitsavers_
    archive.org/details/bitsavers_

    If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.

    #Borland #TurboC

  2. Well this sure brings back memories.

    It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.

    Disk Images
    archive.org/details/borland-tu

    User and Reference Manual:
    archive.org/details/bitsavers_
    archive.org/details/bitsavers_

    If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.

    #Borland #TurboC

  3. Well this sure brings back memories.

    It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.

    Disk Images
    archive.org/details/borland-tu

    User and Reference Manual:
    archive.org/details/bitsavers_
    archive.org/details/bitsavers_

    If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.

    #Borland #TurboC

  4. Well this sure brings back memories.

    It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.

    Disk Images
    archive.org/details/borland-tu

    User and Reference Manual:
    archive.org/details/bitsavers_
    archive.org/details/bitsavers_

    If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.

    #Borland #TurboC

  5. Well this sure brings back memories.

    It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.

    Disk Images
    archive.org/details/borland-tu

    User and Reference Manual:
    archive.org/details/bitsavers_
    archive.org/details/bitsavers_

    If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.

    #Borland #TurboC

  6. Finally done with my #coding escapades related to coding a virtual terminal inside a terminal using #Borland C++ 5.02 and #Win9x. It is a fun project to code with especially when I did not use any AI at all. For those who are interested, you can get the source here: gitlab.com/ShinAska/terminal-b

  7. For so many years I’ve been wondering but never really knew what happened to Borland and Delphi.

    I hated Pascal due to how discouraging our lyceum teacher was and how ancient TP felt in the early 2000s. Plus I learned QBasic at school and then logically moved on to Visual Basic 6.

    Though I remember that indeed Delphi was better than VB in many ways, including not needing to provide a runtime.

    youtu.be/Ubie5xxfdzE?si=lYYWW6

    #delphi #programming #coding #history #visualbasic #microsoft #borland

  8. I just realized something.. I used to love learning new things, i could get engrossed in something because it was simple to learn and easy to use.

    New "tech stack" doesn't seem to be like that anymore. It feels needlessly complex and invents a new 'standard' every time. It makes me angry and I hate learning, cause its no longer fun.

    Learning #borland #TurboPascal #pascal was fun and easy in High School. Moving to #C and #Perl in university was great and easy enough as well. Not that I was any kind of competent in C, but I felt I learned enough that it set me up on a trajectory to learn the finer details and gotchas.

    Things like #Python are annoying AF. Oh, your python program only works on 3.11 and not 3.12 or 3.13? That shouldn't be at all. From 2->3 sure I expect changes, 3->4, i would expect great changes as well. But not a minor change!

    Dabbling in #Go was fine actually, it didn't anger me much, and #Rustlang / #rust I'm still doing rustlings so I can't say much there.

    CLI tools are weird today too. Do they want to be a TUI, a true CLI tool or what?

    The #Unix philosophy made learning new tools nice and easy, at least I think so. Do one thing, do it well, make it so your output can be used as the input to another program and great!

    Things don't seem to follow that idea anymore.

    Or am I just old and biased cause my brain lost its elasticity?? I don't want to think i'm so egocentric as to not rule that out.

    #programming #OldManYellsAtClouds

  9. IBM 5150 и разработка под самый первый PC

    Есть много интересных способов провести новогодние праздники, но поскольку я уже старенький — вместо классических алкогольного угара, ведра оливье и просмотра «Иронии судьбы» выбрал себе более редкое и необычное занятие.

    habr.com/ru/articles/982954/

    #5150 #pcdos #borland #си #эмуляторы #dosbox #pce #freebsd #8080

  10. IBM 5150 и разработка под самый первый PC

    Есть много интересных способов провести новогодние праздники, но поскольку я уже старенький — вместо классических алкогольного угара, ведра оливье и просмотра «Иронии судьбы» выбрал себе более редкое и необычное занятие.

    habr.com/ru/articles/982954/

    #5150 #pcdos #borland #си #эмуляторы #dosbox #pce #freebsd #8080

  11. IBM 5150 и разработка под самый первый PC

    Есть много интересных способов провести новогодние праздники, но поскольку я уже старенький — вместо классических алкогольного угара, ведра оливье и просмотра «Иронии судьбы» выбрал себе более редкое и необычное занятие.

    habr.com/ru/articles/982954/

    #5150 #pcdos #borland #си #эмуляторы #dosbox #pce #freebsd #8080

  12. IBM 5150 и разработка под самый первый PC

    Есть много интересных способов провести новогодние праздники, но поскольку я уже старенький — вместо классических алкогольного угара, ведра оливье и просмотра «Иронии судьбы» выбрал себе более редкое и необычное занятие.

    habr.com/ru/articles/982954/

    #5150 #pcdos #borland #си #эмуляторы #dosbox #pce #freebsd #8080

  13. Modula-2, UCSD P-System, and the birth of Scala

    I stumbled across this tidbit from Hacker News.

    I never liked that #Borland stuffs. And used to program in #Pascal in #UCSD P-system (my alma mater). When I got to the US Department of Defense they wanted me for my #C and #COBOL skills and then they sent me to an Air Force School where I studied Modula-2 and Ada.

    I did a lot of work in Modula-2, which doesn't exist anymore. Modula-3 does, but in the meantime Scala was in the works. #Ada is still actually a thing. We didn't want clever, like those one liner #Perl challenges that folks use to put in their signature lines to demonstrate how clever they thought they were through obfuscation.

    Clever is bad. Clever opens up a whole universe of unexpected behavior and potential vulnerabilities. Maybe that's why #Rust became so organically popular - because it's safe by design and nowadays it's included in the Linux kernel more and more.

    When you're designing software for missle guidance systems you most certainly do not want clever. The job is simple and ambiguity is potentially catastrophic in warfare.

    Anyway, I really enjoyed this interview, I can identify with the #Timex_Sinclair - my dad bought me one and that membrane keyboard was horrendous, but I was persistent and eventually I was writing code in cutting edge languages on mainframes and #Vaxen.

    Many of the stories about how one thing or another came about were through frustrations; like the impetus for #Linus the #Linux kernel coz #MINIX just didn't cut it, and who wants to trodge through snow drifts in #Helsinki to the computer lab when you can be warm and cozy, drinking beers in your dorm room?

    This story is kinda like that too, which I can really appreciate, even though I've never played with #Scala.

    I hope you enjoy it too.

    https://www.artima.com/articles/the-origins-of-scala

    #tallship #FOSS #Modula_2 #Modula_3

  14. Modula-2, UCSD P-System, and the birth of Scala

    I stumbled across this tidbit from Hacker News.

    I never liked that #Borland stuffs. And used to program in #Pascal in #UCSD P-system (my alma mater). When I got to the US Department of Defense they wanted me for my #C and #COBOL skills and then they sent me to an Air Force School where I studied Modula-2 and Ada.

    I did a lot of work in Modula-2, which doesn't exist anymore. Modula-3 does, but in the meantime Scala was in the works. #Ada is still actually a thing. We didn't want clever, like those one liner #Perl challenges that folks use to put in their signature lines to demonstrate how clever they thought they were through obfuscation.

    Clever is bad. Clever opens up a whole universe of unexpected behavior and potential vulnerabilities. Maybe that's why #Rust became so organically popular - because it's safe by design and nowadays it's included in the Linux kernel more and more.

    When you're designing software for missle guidance systems you most certainly do not want clever. The job is simple and ambiguity is potentially catastrophic in warfare.

    Anyway, I really enjoyed this interview, I can identify with the #Timex_Sinclair - my dad bought me one and that membrane keyboard was horrendous, but I was persistent and eventually I was writing code in cutting edge languages on mainframes and #Vaxen.

    Many of the stories about how one thing or another came about were through frustrations; like the impetus for #Linus the #Linux kernel coz #MINIX just didn't cut it, and who wants to trodge through snow drifts in #Helsinki to the computer lab when you can be warm and cozy, drinking beers in your dorm room?

    This story is kinda like that too, which I can really appreciate, even though I've never played with #Scala.

    I hope you enjoy it too.

    https://www.artima.com/articles/the-origins-of-scala

    #tallship #FOSS #Modula_2 #Modula_3

  15. Modula-2, UCSD P-System, and the birth of Scala

    I stumbled across this tidbit from Hacker News.

    I never liked that #Borland stuffs. And used to program in #Pascal in #UCSD P-system (my alma mater). When I got to the US Department of Defense they wanted me for my #C and #COBOL skills and then they sent me to an Air Force School where I studied Modula-2 and Ada.

    I did a lot of work in Modula-2, which doesn't exist anymore. Modula-3 does, but in the meantime Scala was in the works. #Ada is still actually a thing. We didn't want clever, like those one liner #Perl challenges that folks use to put in their signature lines to demonstrate how clever they thought they were through obfuscation.

    Clever is bad. Clever opens up a whole universe of unexpected behavior and potential vulnerabilities. Maybe that's why #Rust became so organically popular - because it's safe by design and nowadays it's included in the Linux kernel more and more.

    When you're designing software for missle guidance systems you most certainly do not want clever. The job is simple and ambiguity is potentially catastrophic in warfare.

    Anyway, I really enjoyed this interview, I can identify with the #Timex_Sinclair - my dad bought me one and that membrane keyboard was horrendous, but I was persistent and eventually I was writing code in cutting edge languages on mainframes and #Vaxen.

    Many of the stories about how one thing or another came about were through frustrations; like the impetus for #Linus the #Linux kernel coz #MINIX just didn't cut it, and who wants to trodge through snow drifts in #Helsinki to the computer lab when you can be warm and cozy, drinking beers in your dorm room?

    This story is kinda like that too, which I can really appreciate, even though I've never played with #Scala.

    I hope you enjoy it too.

    https://www.artima.com/articles/the-origins-of-scala

    #tallship #FOSS #Modula_2 #Modula_3

  16. Как Borland просрали все полимеры

    Первая встреча с Turbo Pascal Начать стоит с самого начала, когда я впервые увидел Turbo Pascal 5.0. Тогда для меня это было что-то на грани чуда. Ведь как в те времена делалось "в норме": Читать далее...

    habr.com/ru/articles/949956/

    #delphi #c# #borland

  17. Retro geek t-shirt 🤓 unfortunately it's an M and does not fit me, especially with these #poledance shoulders. 💪
    #borland #TurboC #retrocomputing

  18. Retro geek t-shirt 🤓 unfortunately it's an M and does not fit me, especially with these #poledance shoulders. 💪
    #borland #TurboC #retrocomputing

  19. Retro geek t-shirt 🤓 unfortunately it's an M and does not fit me, especially with these #poledance shoulders. 💪
    #borland #TurboC #retrocomputing

  20. Retro geek t-shirt 🤓 unfortunately it's an M and does not fit me, especially with these #poledance shoulders. 💪
    #borland #TurboC #retrocomputing

  21. Retro geek t-shirt 🤓 unfortunately it's an M and does not fit me, especially with these #poledance shoulders. 💪
    #borland #TurboC #retrocomputing

  22. Recuperiamo un mio vecchio programma del 1993 per MS-DOS realizzato con il Turbo C++ della Borland: il classico insieme di Mandelbrot in grafica VGA a 16 colori. Questa volta per il recupero ho usato i dischetti originali. #clanguage #programming #borland #mandelbrot youtube.com/watch?v=Bp5h-AMeRf

  23. I know, many have been asking for this and even more out there didn’t even dare to ask.

    But finally, the wait is over:

    You can now use your #PinephonePro running #FreeBSD to do all your #Borland C++ #OS2 development while waiting for 1997 to arrive.

    #RetroComputing

  24. Как Microsoft задушил Delphi, создав .NET: история одного программиста и одного чемодана

    Личный взгляд программиста с стажем на то, как Microsoft переманил Хейлсберга, создал .NET и вытеснил Delphi с технологической сцены. История предательства, перехода эпох и чемодана, который до сих пор скрипит в углу. Как Microsoft задушил Delphi читать далее

    habr.com/ru/articles/902476/

    #turbo_pascal #delphi #net #microsoft #borland #codegear #программирование #история_технологий

  25. [Перевод] Ещё раз о моделях памяти, применявшихся в DOS

    Некоторое время назад я написал несколько статей о различных трюках, применявшихся в операционной системе DOS, чтобы вписаться в те жёсткие лимиты памяти, которые действовали в реальном режиме на архитектуре x86. Постоянно возникал и оставался без ответа один вопрос: а каковы были различные «модели», которые предлагались компиляторами тех времён? Взгляните, как выглядело меню для генерации кода в Borland Turbo C++. Tiny (крошечный), small (маленький), medium (средний), compact (компактный), large (большой), huge (огромный)… Что означают эти опции? Каковы их эффекты? Ещё важнее… а так ли важен весь этот антиквариат сегодня, в мире 64-разрядных машин и гигабайтных ОЗУ? Чтобы ответить на этот вопрос, сделаем небольшой обзор архитектуры 8086 и тех двоичных форматов, которые поддерживались в DOS.

    habr.com/ru/companies/timeweb/

    #timeweb_статьи_перевод #c++ #dos #озу #8086 #x86 #com #exe #microsoft #borland

  26. [Перевод] Ещё раз о моделях памяти, применявшихся в DOS

    Некоторое время назад я написал несколько статей о различных трюках, применявшихся в операционной системе DOS, чтобы вписаться в те жёсткие лимиты памяти, которые действовали в реальном режиме на архитектуре x86. Постоянно возникал и оставался без ответа один вопрос: а каковы были различные «модели», которые предлагались компиляторами тех времён? Взгляните, как выглядело меню для генерации кода в Borland Turbo C++. Tiny (крошечный), small (маленький), medium (средний), compact (компактный), large (большой), huge (огромный)… Что означают эти опции? Каковы их эффекты? Ещё важнее… а так ли важен весь этот антиквариат сегодня, в мире 64-разрядных машин и гигабайтных ОЗУ? Чтобы ответить на этот вопрос, сделаем небольшой обзор архитектуры 8086 и тех двоичных форматов, которые поддерживались в DOS.

    habr.com/ru/companies/timeweb/

    #timeweb_статьи_перевод #c++ #dos #озу #8086 #x86 #com #exe #microsoft #borland

  27. Spending some of my #christmas #vacation #geeking around with #vintagecomputing and getting reacquainted with developing software for #msdos. Last time I did that must have been in the early #90s before I discovered #Linux.

    So far I've given the #djgpp C compiler a go, but it seems a little messy and keep throwing internal errors. #OpenWatcom v2 seems promising, but has a horrible way of doing interrupt calls. The #borland suites seems outdated, but does come with a lot of libraries that the others don't have. I don't believe it can generate protected mode executables though.

    Im actually only looking to do a couple of simple tools, and perhaps some sort of menu/launcher that can scan recursively for configuration files. For the ladder, word around the campfire is that #pdcurses is pretty good at drawing menus and other components in text mode. I'll investigate! Would be a new experience NOT starting by writing my own library for addressing the text mode screen directly.. AGAIN.. 😜

  28. @nixCraft
    My high school didn’t have enough fancy 286 computers so some of us used original 8086 with just 384kb of ram? IDE (had to use #WordStar key bindings) was Turbo #Pascal 3.0 and I’d exit back to DOS to compile.

    I volunteered to use the worst computer so the following semester I’d get first dibs on new (for the school) computers: 386 w/4MB ram. 😎

    #Borland

  29. Here's something I wish would be open sourced.

    The #TopSpeed C #compiler is an integral part of the #Psion SIBO C SDK.

    Old timers might remember JPI as a group of developers who left #Borland in 1987, after Borland decided not to use the team's new compiler technology. They took their code with them, and it became the TopSpeed compiler.

    From what I gather, the TopSpeed compiler IP is now owned by #SoftVelocity, the company who now also owns Clarion. I emailed them about 6 years ago, asking them if they would consider open sourcing the compiler code. I got no response, which I guess is to be expected.

    I even found someone who had a copy of the source code (written in Modula-2), but they understandably wouldn't give it to me without the IP owner's approval.

    This is the situation with so many bits of software (including the SIBO C SDK tools) from this time. We are lucky that copies of the applications still exist, otherwise the job of building C software for #EPOC16 would be significantly more difficult. But it is likely that the original source code, along with many other codebases, will disappear thanks to copyright laws that don't support digital preservation.

    #retrocomputing #vintagecomputing #digipres

  30. Here's something I wish would be open sourced.

    The #TopSpeed C #compiler is an integral part of the #Psion SIBO C SDK.

    Old timers might remember JPI as a group of developers who left #Borland in 1987, after Borland decided not to use the team's new compiler technology. They took their code with them, and it became the TopSpeed compiler.

    From what I gather, the TopSpeed compiler IP is now owned by #SoftVelocity, the company who now also owns Clarion. I emailed them about 6 years ago, asking them if they would consider open sourcing the compiler code. I got no response, which I guess is to be expected.

    I even found someone who had a copy of the source code (written in Modula-2), but they understandably wouldn't give it to me without the IP owner's approval.

    This is the situation with so many bits of software (including the SIBO C SDK tools) from this time. We are lucky that copies of the applications still exist, otherwise the job of building C software for #EPOC16 would be significantly more difficult. But it is likely that the original source code, along with many other codebases, will disappear thanks to copyright laws that don't support digital preservation.

    #retrocomputing #vintagecomputing #digipres

  31. Here's something I wish would be open sourced.

    The #TopSpeed C #compiler is an integral part of the #Psion SIBO C SDK.

    Old timers might remember JPI as a group of developers who left #Borland in 1987, after Borland decided not to use the team's new compiler technology. They took their code with them, and it became the TopSpeed compiler.

    From what I gather, the TopSpeed compiler IP is now owned by #SoftVelocity, the company who now also owns Clarion. I emailed them about 6 years ago, asking them if they would consider open sourcing the compiler code. I got no response, which I guess is to be expected.

    I even found someone who had a copy of the source code (written in Modula-2), but they understandably wouldn't give it to me without the IP owner's approval.

    This is the situation with so many bits of software (including the SIBO C SDK tools) from this time. We are lucky that copies of the applications still exist, otherwise the job of building C software for #EPOC16 would be significantly more difficult. But it is likely that the original source code, along with many other codebases, will disappear thanks to copyright laws that don't support digital preservation.

    #retrocomputing #vintagecomputing #digipres

  32. Here's something I wish would be open sourced.

    The #TopSpeed C #compiler is an integral part of the #Psion SIBO C SDK.

    Old timers might remember JPI as a group of developers who left #Borland in 1987, after Borland decided not to use the team's new compiler technology. They took their code with them, and it became the TopSpeed compiler.

    From what I gather, the TopSpeed compiler IP is now owned by #SoftVelocity, the company who now also owns Clarion. I emailed them about 6 years ago, asking them if they would consider open sourcing the compiler code. I got no response, which I guess is to be expected.

    I even found someone who had a copy of the source code (written in Modula-2), but they understandably wouldn't give it to me without the IP owner's approval.

    This is the situation with so many bits of software (including the SIBO C SDK tools) from this time. We are lucky that copies of the applications still exist, otherwise the job of building C software for #EPOC16 would be significantly more difficult. But it is likely that the original source code, along with many other codebases, will disappear thanks to copyright laws that don't support digital preservation.

    #retrocomputing #vintagecomputing #digipres

  33. Here's something I wish would be open sourced.

    The #TopSpeed C #compiler is an integral part of the #Psion SIBO C SDK.

    Old timers might remember JPI as a group of developers who left #Borland in 1987, after Borland decided not to use the team's new compiler technology. They took their code with them, and it became the TopSpeed compiler.

    From what I gather, the TopSpeed compiler IP is now owned by #SoftVelocity, the company who now also owns Clarion. I emailed them about 6 years ago, asking them if they would consider open sourcing the compiler code. I got no response, which I guess is to be expected.

    I even found someone who had a copy of the source code (written in Modula-2), but they understandably wouldn't give it to me without the IP owner's approval.

    This is the situation with so many bits of software (including the SIBO C SDK tools) from this time. We are lucky that copies of the applications still exist, otherwise the job of building C software for #EPOC16 would be significantly more difficult. But it is likely that the original source code, along with many other codebases, will disappear thanks to copyright laws that don't support digital preservation.

    #retrocomputing #vintagecomputing #digipres