#plugindevelopment — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #plugindevelopment, aggregated by home.social.
-
🎉 Behold, the grand unveiling of the Obsidian Plugin Future—a revolutionary concept where developers can finally wallow in an endless abyss of plugin chaos and dashboard mania. 🚀 Because who needs simplicity when you can have a buffet of broken features and language options, right? 🙃
https://obsidian.md/blog/future-of-plugins/ #ObsidianPlugin #Future #DashboardChaos #PluginDevelopment #SoftwareInnovation #HackerNews #ngated -
🎉 Behold, the grand unveiling of the Obsidian Plugin Future—a revolutionary concept where developers can finally wallow in an endless abyss of plugin chaos and dashboard mania. 🚀 Because who needs simplicity when you can have a buffet of broken features and language options, right? 🙃
https://obsidian.md/blog/future-of-plugins/ #ObsidianPlugin #Future #DashboardChaos #PluginDevelopment #SoftwareInnovation #HackerNews #ngated -
🎉 Behold, the grand unveiling of the Obsidian Plugin Future—a revolutionary concept where developers can finally wallow in an endless abyss of plugin chaos and dashboard mania. 🚀 Because who needs simplicity when you can have a buffet of broken features and language options, right? 🙃
https://obsidian.md/blog/future-of-plugins/ #ObsidianPlugin #Future #DashboardChaos #PluginDevelopment #SoftwareInnovation #HackerNews #ngated -
🎉 Behold, the grand unveiling of the Obsidian Plugin Future—a revolutionary concept where developers can finally wallow in an endless abyss of plugin chaos and dashboard mania. 🚀 Because who needs simplicity when you can have a buffet of broken features and language options, right? 🙃
https://obsidian.md/blog/future-of-plugins/ #ObsidianPlugin #Future #DashboardChaos #PluginDevelopment #SoftwareInnovation #HackerNews #ngated -
🎉 Behold, the grand unveiling of the Obsidian Plugin Future—a revolutionary concept where developers can finally wallow in an endless abyss of plugin chaos and dashboard mania. 🚀 Because who needs simplicity when you can have a buffet of broken features and language options, right? 🙃
https://obsidian.md/blog/future-of-plugins/ #ObsidianPlugin #Future #DashboardChaos #PluginDevelopment #SoftwareInnovation #HackerNews #ngated -
WordPressプラグイン開発記 vol.3！
今回は記事のスラッグを入力した際に既に使われていないかチェックする機能を導入してみました😆
#WordPress #PluginDevelopment #Gutenberg #JavaScript #Web開発 #フロントエンド #CMS
-
Ihre QGIS-Plugins fit für Qt6 machen – so geht's! 🚀
⚡️ Mit QGIS 4 wechselt das Framework auf Qt6 – viele Plugins laufen nicht mehr "out of the box".
Johannes Kröger zeigt gleich auf der #FOSSGIS2026 wie der Umstieg gelingt:
• Portierungs-Guide für Qt6
• Hilfreiche Migrations-Tools
• Typische Stolpersteine vermeiden📅 Do, 26. März | 09:10 Uhr
📍 Raum HS4 (ZHG 008) -
Ihre QGIS-Plugins fit für Qt6 machen – so geht's! 🚀
⚡️ Mit QGIS 4 wechselt das Framework auf Qt6 – viele Plugins laufen nicht mehr "out of the box".
Johannes Kröger zeigt gleich auf der #FOSSGIS2026 wie der Umstieg gelingt:
• Portierungs-Guide für Qt6
• Hilfreiche Migrations-Tools
• Typische Stolpersteine vermeiden📅 Do, 26. März | 09:10 Uhr
📍 Raum HS4 (ZHG 008) -
Ihre QGIS-Plugins fit für Qt6 machen – so geht's! 🚀
⚡️ Mit QGIS 4 wechselt das Framework auf Qt6 – viele Plugins laufen nicht mehr "out of the box".
Johannes Kröger zeigt gleich auf der #FOSSGIS2026 wie der Umstieg gelingt:
• Portierungs-Guide für Qt6
• Hilfreiche Migrations-Tools
• Typische Stolpersteine vermeiden📅 Do, 26. März | 09:10 Uhr
📍 Raum HS4 (ZHG 008) -
Ihre QGIS-Plugins fit für Qt6 machen – so geht's! 🚀
⚡️ Mit QGIS 4 wechselt das Framework auf Qt6 – viele Plugins laufen nicht mehr "out of the box".
Johannes Kröger zeigt gleich auf der #FOSSGIS2026 wie der Umstieg gelingt:
• Portierungs-Guide für Qt6
• Hilfreiche Migrations-Tools
• Typische Stolpersteine vermeiden📅 Do, 26. März | 09:10 Uhr
📍 Raum HS4 (ZHG 008) -
Ihre QGIS-Plugins fit für Qt6 machen – so geht's! 🚀
⚡️ Mit QGIS 4 wechselt das Framework auf Qt6 – viele Plugins laufen nicht mehr "out of the box".
Johannes Kröger zeigt gleich auf der #FOSSGIS2026 wie der Umstieg gelingt:
• Portierungs-Guide für Qt6
• Hilfreiche Migrations-Tools
• Typische Stolpersteine vermeiden📅 Do, 26. März | 09:10 Uhr
📍 Raum HS4 (ZHG 008) -
JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.
Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.
I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.
My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.
Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.
Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.
The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.
JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.
Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.
Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.
#JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies
-
JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.
Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.
I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.
My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.
Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.
Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.
The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.
JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.
Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.
Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.
#JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies
-
JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.
Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.
I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.
My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.
Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.
Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.
The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.
JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.
Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.
Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.
#JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies
-
JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.
Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.
I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.
My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.
Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.
Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.
The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.
JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.
Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.
Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.
#JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies
-
JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.
Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.
I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.
My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.
Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.
Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.
The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.
JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.
Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.
Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.
#JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies
-
ICYMI: WordPress translation loading error hits thousands of sites overnight: 6.7 internationalization improvements trigger widespread notices as plugin developers scramble to update code. https://ppc.land/wordpress-translation-loading-error-hits-thousands-of-sites-overnight/ #WordPress #TranslationError #WebDevelopment #Internationalization #PluginDevelopment
-
ICYMI: WordPress translation loading error hits thousands of sites overnight: 6.7 internationalization improvements trigger widespread notices as plugin developers scramble to update code. https://ppc.land/wordpress-translation-loading-error-hits-thousands-of-sites-overnight/ #WordPress #TranslationError #WebDevelopment #Internationalization #PluginDevelopment
-
ICYMI: WordPress translation loading error hits thousands of sites overnight: 6.7 internationalization improvements trigger widespread notices as plugin developers scramble to update code. https://ppc.land/wordpress-translation-loading-error-hits-thousands-of-sites-overnight/ #WordPress #TranslationError #WebDevelopment #Internationalization #PluginDevelopment
-
Need a WordPress plugin that actually fits your site? 🧩
We build high-performance, secure, and scalable plugins for WordPress, BuddyPress, LearnDash, and WooCommerce.
Custom-built, fully supported. Let’s build something made for you. 💻✨Let’s build it together → https://wbcomdesigns.com/custom-wordpress-plugin-development
#WordPress #PluginDevelopment #WordPressPlugins #CustomPlugins #BuddyPress #LearnDash #WooCommerce #WbcomDesigns #WPDev #WebsiteSolutions
-
Achieve Clean Code: JetBrains Qodana Supports C and C++ for In-Depth Code Analysis
#Clang #Clion #Crosspromotion #Plugindevelopment #Eap #Info #Jetbrains #Releases #Webdevelopment #Net #Codequality #Codereviews #Dotnet #News #Qodana #Releasehttps://blog.jetbrains.com/qodana/2024/05/clean-code-c-and-c-linter-provides-in-depth-code-analysis/
-
EAP: JetBrains Qodana Now Supports C and C++ for In-Depth Code Analysis
#Clang #Clion #Crosspromotion #Plugindevelopment #Eap #Info #Jetbrains #Releases #Webdevelopment #Net #Codequality #Codereviews #Dotnet #News #Qodana #Release -
Just as a quick reminder: auroraSuite could potentially be going offline from the Roblox Creator Store today.
I honestly thought about making it free with the suggestion @[email protected] gave me but I think it's honestly unfair that Robux payment methods at a marked up price (since you pay like 40x more tax when going through Roblox lol (75.5% tax Roblox takes, I think it's roughly 2% for Stripe) can't still be offered. Developers from countries such as Brazil and Russia (which are apparently big) are unable to use Stripe (although granted it's understandable for Russia) and developers aged under 18 (such as myself) cannot use it either.
Thanks for your support #Roblox #RobloxDev #RobloxPlugin #GameDev #GameDevelopment #PluginDev #PluginDevelopment
RE: https://lethallava.land/notes/9qjsptrezy -
⚙️ Update to my GitHub Workflow Plugin! 🛠️ After months of dedicated work, I am navigating the 5th refactoring phase within one year. While the JetBrains Plugin SDK presents challenges in performance, maintainability, and testing, I am committed to overcoming these hurdles to bring you a top-notch tool. 🧩 https://plugins.jetbrains.com/plugin/21396-github-workflow #IntelliJ #JetBrains #PluginDevelopment #OpenSource #GitHubPlugin #GitHub #DevOps #jetbrains #JBPlatform #GitHubActions
-
I'm developing my first plugin for the Elgato Stream Deck. My code wasn't triggered by the Stream Deck and I needed several hours of debugging to find the problem: The Plugin ID has to be written completely in lower cases. What a bad API Design! Hopefully the rest of the framework is working better.
-
I'm developing my first plugin for the Elgato Stream Deck. My code wasn't triggered by the Stream Deck and I needed several hours of debugging to find the problem: The Plugin ID has to be written completely in lower cases. What a bad API Design! Hopefully the rest of the framework is working better.