home.social

#delphi — Public Fediverse posts

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

  1. Как я писал трей-утилиту для управления sing-box на Windows

    Эта статья о том, как я хотел сэкономить несколько секунд при переключении системного прокси в Nekobox, а в итоге уже несколько месяцев пишу мини-программу для управления sing-box . Началось с того, что для прокси на Windows я стал использовать Nekobox. Про гибкое раздельное туннелирование я еще не знал, и приходилось постоянно включать и выключать системный прокси, чтобы зайти то туда (сайт заблокирован), то сюда (сайт блокирует IP прокси). Много раз в час: клик по значку в трее, режим системного прокси, отключить (а потом обратно). И я подумал, что было бы удобнее просто кликать по значку. Ничего сложного — почему бы не реализовать? Начал я, конечно же, с рисования значка. Решил, что хорошо подойдет портал из «Рика и Морти» как метафора беспрепятственного перемещения между измерениями. Провел целый вечер в Procreate на iPad, замучился, устал и отложил затею на потом. Что было дальше

    habr.com/ru/articles/1031978/

    #singbox #прокси #winapi #delphi #программирование

  2. People want AI characters shut down. I gave mine opinions instead — pro-human ones. My 1974 character sees it through Asimov and Ellison. My Delphi twin apparently found me annoying. Here's the full take: [url]
    #Delphi #AI #AIcharacters #CharacterAI #Asimov #SciFi
    substack.com/profile/15669779-

  3. Vollmondtreffen der ALIGN:

    Am Dienstag, den 05.05.2026 findet in Nürnberg wieder um 17:00 Uhr das Treffen der #ALIGN im Delphi, Innere Laufer Gasse 22 statt.

    #Linux, freie Software und andere Themen stehen auf der Agenda.

    Diese Info findet sich auch auf unserer Webseite unter Termine.

    Einfach vorbeischauen, auch "Neue" sind gerne gesehen. Wir freuen uns auf eine rege Teilnahme.

    Wegen der Tischreservierung bitte vorab eine Info an rqxzbader[at]gmx.de senden.

    Vielen Dank.

    #delphi #lpd

  4. Vollmondtreffen der ALIGN:

    Am Dienstag, den 05.05.2026 findet in Nürnberg wieder um 17:00 Uhr das Treffen der #ALIGN im Delphi, Innere Laufer Gasse 22 statt.

    #Linux, freie Software und andere Themen stehen auf der Agenda.

    Diese Info findet sich auch auf unserer Webseite unter Termine.

    Einfach vorbeischauen, auch "Neue" sind gerne gesehen. Wir freuen uns auf eine rege Teilnahme.

    Wegen der Tischreservierung bitte vorab eine Info an rqxzbader[at]gmx.de senden.

    Vielen Dank.

    #delphi #lpd

  5. Vollmondtreffen der ALIGN:

    Am Dienstag, den 05.05.2026 findet in Nürnberg wieder um 17:00 Uhr das Treffen der #ALIGN im Delphi, Innere Laufer Gasse 22 statt.

    #Linux, freie Software und andere Themen stehen auf der Agenda.

    Diese Info findet sich auch auf unserer Webseite unter Termine.

    Einfach vorbeischauen, auch "Neue" sind gerne gesehen. Wir freuen uns auf eine rege Teilnahme.

    Wegen der Tischreservierung bitte vorab eine Info an rqxzbader[at]gmx.de senden.

    Vielen Dank.

    #delphi #lpd

  6. Vollmondtreffen der ALIGN:

    Am Dienstag, den 05.05.2026 findet in Nürnberg wieder um 17:00 Uhr das Treffen der #ALIGN im Delphi, Innere Laufer Gasse 22 statt.

    #Linux, freie Software und andere Themen stehen auf der Agenda.

    Diese Info findet sich auch auf unserer Webseite unter Termine.

    Einfach vorbeischauen, auch "Neue" sind gerne gesehen. Wir freuen uns auf eine rege Teilnahme.

    Wegen der Tischreservierung bitte vorab eine Info an rqxzbader[at]gmx.de senden.

    Vielen Dank.

    #delphi #lpd

  7. Vollmondtreffen der ALIGN:

    Am Dienstag, den 05.05.2026 findet in Nürnberg wieder um 17:00 Uhr das Treffen der #ALIGN im Delphi, Innere Laufer Gasse 22 statt.

    #Linux, freie Software und andere Themen stehen auf der Agenda.

    Diese Info findet sich auch auf unserer Webseite unter Termine.

    Einfach vorbeischauen, auch "Neue" sind gerne gesehen. Wir freuen uns auf eine rege Teilnahme.

    Wegen der Tischreservierung bitte vorab eine Info an rqxzbader[at]gmx.de senden.

    Vielen Dank.

    #delphi #lpd

  8. La prossima edizione di ITDevCon Spring Edition è imminente! 🫡

    Quest'anno parteciperò a due sessioni:

    👉 Micro-SaaS + AI + Delphi
    Dall'idea al prodotto, passando per:
    • AI nel processo creativo
    • OpenCode
    • sviluppo rapido e pragmatico

    👉 Web Components con Lit
    Assieme al collega Marco Pollacci creiamo architetture disaccoppiate grazie ai Web Components integrandole con Delphi.

    Ci vediamo l'8 maggio a Roma! 👏
    itdevcon.it/home/itdevcon-spri

    #ITDevConSE2026 #TechConference #SoftwareDevelopment #Delphi

  9. Vollmondtreffen der ALIGN:

    Am Dienstag, den 07.04.2026 findet in Nürnberg wieder um 17:00 Uhr das Treffen der #ALIGN im Delphi, Innere Laufer Gasse 22 statt.

    #Linux, freie Software und andere Themen stehen auf der Agenda.

    Diese Info findet sich auch auf unserer Webseite unter Termine.

    Einfach vorbeischauen, auch "Neue" sind gerne gesehen. Wir freuen uns auf eine rege Teilnahme.

    Wegen der Tischreservierung bitte vorab eine Info an rqxzbader[at]gmx.de senden.

    Vielen Dank.

    #delphi #lpd

  10. Quando affidi la tua applicazione al cliente è un po’ come quando lasci il figliolo alla nonna: ti chiedi sempre "si starà comportando bene? e avrà digerito tutto il pranzo?". 🤭

    Mettere una microspia addosso al pargolo sarebbe inopportuno. Per l'applicazione le soluzioni ci sono! 😊

    Nella live di martedì 31 marzo alle 21:30 mettiamo alla prova #ExeWatch: un servizio di #monitoraggio real-time per app e servizi sviluppati con #Delphi, #csharp (#dotnet) e #JavaScript. 🕵️

    👉 twitch.tv/compilaquindiva

  11. vkcube running on 64-bit RISC-V Alpine Linux in my PasRISCV Emulator in turn with the Vulkan-based PasRISCVEmu UI backend. #riscv #vulkan #ObjectPascal #FreePascal #Delphi
    @riscv @vulkan

  12. [Перевод] 7 уроков от Андерса Хейлсберга: архитектора C# и TypeScript

    Работа Андерса Хейлсберга сформировала то, как миллионы разработчиков пишут код. Даже если вы не узнаёте его имя, вы, скорее всего, сталкивались с его работами: он создатель Turbo Pascal и Delphi, ведущий архитектор C#, а также разработчик TypeScript. Мы встретились с Хейлсбергом, чтобы обсудить его выдающуюся карьеру и то, каково это — наблюдать, как его инновации выдерживают давление реального мира. В подробной беседе Хейлсберг размышляет о том, как выглядит разработка языков программирования после того, как проходит первоначальный ажиотаж, когда проявляются ограничения производительности, когда открытый исходный код становится неизбежным, и как ИИ может повлиять на изначальную функцию инструмента. В итоге вырисовывается набор закономерностей для создания систем, способных выдерживать масштаб. Вот что мы узнали.

    habr.com/ru/articles/1011876/

    #javascript #typescript #c# #языки_программирования #история_создания #советы_разработчику #Андерса_Хейлсберг #turbo_pascal #delphi




  13. (1) Does the Apple MacBook Neo support virtualisation (Hypervisor)?

    (2) Can you do macOS/iOS software development on an Apple MacBook Neo?

    (3) Can you do software development on an Apple MacBook Neo?

  14. The irony: the entire RISC-V base ISA (RV64GC) is beautifully RISC: simple opcodes, fixed 32-bit instructions (+ compressed), load/store architecture, no flags, no implicit state. Then RVV comes along and throws all those principles out the window: global implicit state, microcode-like behavior, variable semantics of the same instruction.

    Because vsetvli changes the semantics of all subsequent V-instructions based on the current VLEN configuration. For a JIT compiler in an Emulator and for an Emulator in general, this means having to continuously track the vtype state and react to any changes, a fundamental contradiction to the principle of statically analyzable instructions. It feels like the RISC-V Foundation sacrificed the simplicity and elegance of the RISC principle to create a powerful but extremely complex "super-SIMD" that is difficult to efficiently map in a JIT. A more traditional SIMD extension with fixed vector widths and clearly defined instruction semantics would have been much more JIT-friendly. The upcoming P extension does go in that direction, but it is primarily targeted at embedded and low-power applications rather than high-performance computing.

    #riscv #riscv64 #emulation #pasriscv #object_pascal #delphi #free_pascal

  15. The irony: the entire RISC-V base ISA (RV64GC) is beautifully RISC: simple opcodes, fixed 32-bit instructions (+ compressed), load/store architecture, no flags, no implicit state. Then RVV comes along and throws all those principles out the window: global implicit state, microcode-like behavior, variable semantics of the same instruction.

    Because vsetvli changes the semantics of all subsequent V-instructions based on the current VLEN configuration. For a JIT compiler in an Emulator and for an Emulator in general, this means having to continuously track the vtype state and react to any changes, a fundamental contradiction to the principle of statically analyzable instructions. It feels like the RISC-V Foundation sacrificed the simplicity and elegance of the RISC principle to create a powerful but extremely complex "super-SIMD" that is difficult to efficiently map in a JIT. A more traditional SIMD extension with fixed vector widths and clearly defined instruction semantics would have been much more JIT-friendly. The upcoming P extension does go in that direction, but it is primarily targeted at embedded and low-power applications rather than high-performance computing.

    #riscv #riscv64 #emulation #pasriscv #object_pascal #delphi #free_pascal

  16. The irony: the entire RISC-V base ISA (RV64GC) is beautifully RISC: simple opcodes, fixed 32-bit instructions (+ compressed), load/store architecture, no flags, no implicit state. Then RVV comes along and throws all those principles out the window: global implicit state, microcode-like behavior, variable semantics of the same instruction.

    Because vsetvli changes the semantics of all subsequent V-instructions based on the current VLEN configuration. For a JIT compiler in an Emulator and for an Emulator in general, this means having to continuously track the vtype state and react to any changes, a fundamental contradiction to the principle of statically analyzable instructions. It feels like the RISC-V Foundation sacrificed the simplicity and elegance of the RISC principle to create a powerful but extremely complex "super-SIMD" that is difficult to efficiently map in a JIT. A more traditional SIMD extension with fixed vector widths and clearly defined instruction semantics would have been much more JIT-friendly. The upcoming P extension does go in that direction, but it is primarily targeted at embedded and low-power applications rather than high-performance computing.

    #riscv #riscv64 #emulation #pasriscv #object_pascal #delphi #free_pascal

  17. The irony: the entire RISC-V base ISA (RV64GC) is beautifully RISC: simple opcodes, fixed 32-bit instructions (+ compressed), load/store architecture, no flags, no implicit state. Then RVV comes along and throws all those principles out the window: global implicit state, microcode-like behavior, variable semantics of the same instruction.

    Because vsetvli changes the semantics of all subsequent V-instructions based on the current VLEN configuration. For a JIT compiler in an Emulator and for an Emulator in general, this means having to continuously track the vtype state and react to any changes, a fundamental contradiction to the principle of statically analyzable instructions. It feels like the RISC-V Foundation sacrificed the simplicity and elegance of the RISC principle to create a powerful but extremely complex "super-SIMD" that is difficult to efficiently map in a JIT. A more traditional SIMD extension with fixed vector widths and clearly defined instruction semantics would have been much more JIT-friendly. The upcoming P extension does go in that direction, but it is primarily targeted at embedded and low-power applications rather than high-performance computing.

    #riscv #riscv64 #emulation #pasriscv #object_pascal #delphi #free_pascal

  18. The irony: the entire RISC-V base ISA (RV64GC) is beautifully RISC: simple opcodes, fixed 32-bit instructions (+ compressed), load/store architecture, no flags, no implicit state. Then RVV comes along and throws all those principles out the window: global implicit state, microcode-like behavior, variable semantics of the same instruction.

    Because vsetvli changes the semantics of all subsequent V-instructions based on the current VLEN configuration. For a JIT compiler in an Emulator and for an Emulator in general, this means having to continuously track the vtype state and react to any changes, a fundamental contradiction to the principle of statically analyzable instructions. It feels like the RISC-V Foundation sacrificed the simplicity and elegance of the RISC principle to create a powerful but extremely complex "super-SIMD" that is difficult to efficiently map in a JIT. A more traditional SIMD extension with fixed vector widths and clearly defined instruction semantics would have been much more JIT-friendly. The upcoming P extension does go in that direction, but it is primarily targeted at embedded and low-power applications rather than high-performance computing.

    #riscv #riscv64 #emulation #pasriscv #object_pascal #delphi #free_pascal

  19. @davebauerart @Dreamwieber

    #HyperCard and its programming language #HyperTalk (inspired by #Smalltalk) spread widely into several authoring tools of the early web, like #Macromedia #Director and later #Flash.

    There was also a Windows clone #MetaCard that lives on till today under the name #LiveCode (en.wikipedia.org/wiki/LiveCode). Sadly it didn’t stick to it’s simplicity. It’s now bloatware, not usable for me.

    Some people name the language #Delphi as a successor, but I’ve never tried it.

  20. „I deleted my source code“

    joppe.dev/2026/02/26/i-deleted

    „The classic development workflow we all know and loved, is disappearing fast. We will no longer care about the nitty gritty details of how the code works. We will only care that it does.“

    Experiment in #php that has unit tests, some spec markdown files plus skill files to fill the src folder on every push according to specs/tests.

    Old heads cry in #UML, model driven development and flow based whatever. Can't remember all the hyped methodologies. Thought visual driven development. Typed that into Google and found "visual reverse engineering" that uses legacy UIs to guess what a system does and recreates it in "not #COBOL" or "not #Delphi"!?

    Lots of "The Purpose of a System is What it Does" systems out there nowadays, I guess. What do old cyberneticists make of all of this? #posiwid

  21. „I deleted my source code“

    joppe.dev/2026/02/26/i-deleted

    „The classic development workflow we all know and loved, is disappearing fast. We will no longer care about the nitty gritty details of how the code works. We will only care that it does.“

    Experiment in #php that has unit tests, some spec markdown files plus skill files to fill the src folder on every push according to specs/tests.

    Old heads cry in #UML, model driven development and flow based whatever. Can't remember all the hyped methodologies. Thought visual driven development. Typed that into Google and found "visual reverse engineering" that uses legacy UIs to guess what a system does and recreates it in "not #COBOL" or "not #Delphi"!?

    Lots of "The Purpose of a System is What it Does" systems out there nowadays, I guess. What do old cyberneticists make of all of this? #posiwid

  22. „I deleted my source code“

    joppe.dev/2026/02/26/i-deleted

    „The classic development workflow we all know and loved, is disappearing fast. We will no longer care about the nitty gritty details of how the code works. We will only care that it does.“

    Experiment in #php that has unit tests, some spec markdown files plus skill files to fill the src folder on every push according to specs/tests.

    Old heads cry in #UML, model driven development and flow based whatever. Can't remember all the hyped methodologies. Thought visual driven development. Typed that into Google and found "visual reverse engineering" that uses legacy UIs to guess what a system does and recreates it in "not #COBOL" or "not #Delphi"!?

    Lots of "The Purpose of a System is What it Does" systems out there nowadays, I guess. What do old cyberneticists make of all of this? #posiwid

  23. „I deleted my source code“

    joppe.dev/2026/02/26/i-deleted

    „The classic development workflow we all know and loved, is disappearing fast. We will no longer care about the nitty gritty details of how the code works. We will only care that it does.“

    Experiment in #php that has unit tests, some spec markdown files plus skill files to fill the src folder on every push according to specs/tests.

    Old heads cry in #UML, model driven development and flow based whatever. Can't remember all the hyped methodologies. Thought visual driven development. Typed that into Google and found "visual reverse engineering" that uses legacy UIs to guess what a system does and recreates it in "not #COBOL" or "not #Delphi"!?

    Lots of "The Purpose of a System is What it Does" systems out there nowadays, I guess. What do old cyberneticists make of all of this? #posiwid

  24. „I deleted my source code“

    joppe.dev/2026/02/26/i-deleted

    „The classic development workflow we all know and loved, is disappearing fast. We will no longer care about the nitty gritty details of how the code works. We will only care that it does.“

    Experiment in #php that has unit tests, some spec markdown files plus skill files to fill the src folder on every push according to specs/tests.

    Old heads cry in #UML, model driven development and flow based whatever. Can't remember all the hyped methodologies. Thought visual driven development. Typed that into Google and found "visual reverse engineering" that uses legacy UIs to guess what a system does and recreates it in "not #COBOL" or "not #Delphi"!?

    Lots of "The Purpose of a System is What it Does" systems out there nowadays, I guess. What do old cyberneticists make of all of this? #posiwid

  25. Petite introduction sur les réseaux IP et les sockets tirée du stream Twitch d'hier avant de se lancer dans le codage d'un exemple d'utilisation de socket en UDP.

    videos.apprendre-delphi.fr/w/c
    (aussi dispo sur YouTube)

    Aujourd'hui on tentera de comprendre le fonctionnement de SNMP et de discuter avec mon imprimante réseau. Si tout se passe bien, vendredi et samedi on transforme l'essai en composant pour VCL/FMX afin de surveiller les imprimantes réseau par drag & drop dans n'importe quel projet.
    (et plus tard je coderai la version UDP de la "socket messaging library for Delphi")

    #Delphi #Socket #Network #IP #TCP #UDP #SNMP

  26. 🎤 Never gonna CODE you uuuup! 🎵

    Martedì 10/02 alle 21:30 creiamo un #QRCode Generator in #Delphi per "rickrollare" amici e colleghi! 😜

    Cosa vediamo?
    ✅ Chiamate API #REST in Delphi
    ✅ Sviluppo cross-platform (desktop+mobile) con #FireMonkey
    #UI semplice ed efficace
    ✅ Un aiutino dell'AI per scrivere codice più velocemente

    Partiamo da zero, spiego tutto... anche perché non so nemmeno io come farlo! 😄

    📺 Twitch: twitch.tv/compilaquindiva

    #Coding #Delphi #Programming #QRCode #RickRoll #LearnToCode

  27. 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

  28. Когда gfix бессилен: инструмент восстановления БД Firebird, спасаем данные

    Разбираем бинарный формат Firebird по байтам: структура страниц, транзакции, MVCC. Пишем утилиту на Delphi для восстановления данных, когда gfix и gbak бессильны.

    habr.com/ru/articles/986764/

    #firebird #interbase #delphi #database_recovery #reverse_engineering

  29. Two Words In Japanese sind definitiv auch sehr empfehlenswert. Neue Entdeckung und schöne Bühnenshow.

    #twowordsinjapanese #darkdaysberlin #Berlin #delphi #weissensee

  30. Никлаус Вирт и язык Pascal — легенды 80-х

    В 1970 году молодой швейцарский учёный и программист Никлаус Вирт (Niklaus Wirth) выпустил первую версию Pascal. Прошло более полувека, автор умер в 89 лет, а вот Паскаль остаётся актуальным и популярным языком программирования.

    habr.com/ru/companies/ruvds/ar

    #Никлаус_Вирт #Pascal #Turbo_Pascal #Delphi #Niklaus_Wirth #Free_Pascal #Lazarus_IDE #Algol #Euler #ruvds_статьи

  31. PasLLM is finally publicly released!

    A high-performance LLM inference engine written in pure Object Pascal.

    ✨ No Python dependencies
    🎯 Advanced 4-bit quantization
    🖥️ Cross-platform (Delphi & FreePascal)
    ⚡ Native performance

    Supports Llama 3.x, Qwen, Phi-3, Mixtral, DeepSeek R1 & more!

    Open source (AGPL 3.0): github.com/BeRo1985/pasllm (synced from my private repo on my on server)

    #ObjectPascal #Delphi #FreePascal #LLM #AI