I am connected to an #openSUSE 11.0 machine (don't ask why). I can run #emacs with ediff to check the code's diff from git! That's the benefit of using stable tooling :-)

(Yeah for #Linux and #BoringTechnology)

Edit for clarity: openSUSE 11.0 was released in 2008, hence my happiness to have good tools that I use regularly đŸ€“

#boringtechnology ?

"[..] Static site generators performant websites and have become boring technology over the past 10 years. However, some developers did not get that memo. They have bet on JS frameworks and are too stubborn to admit they made the wrong choice. They try to force-fit their ‘sexy’ stack to ‘boring’ problems, like building a website.

My two cents
"
I mostly agree with Joost post... ( #hugo #dev here )

Dear colleagues, opinions/other reactions ?
#blog

https://www.usecue.com/blog/why-devs-dont-care-about-performance/

Why devs don't care about performance

I read this on Reddit [redacted]: “Why do most programmers that I talk to, who have more experience than me, seem to not care about performance as much? Why does a web page takes 3s to load? Why can’t you learn develop a fully functioning web app without a ton of libraries? And don’t get me started on frameworks. Does anyone relate?” Here is my reply: If you are talking about web applications: A simple LAMP stack performs crazy good, but is not not ‘sexy’. Newer stacks are much ‘sexier’, but in general they perform terrible. High paying companies often use ‘sexy’ stacks to attract programmers. Devs with more experience get that and will choose ‘boring technology’ if it needs to work and ‘sexy’ stacks if they want to make money. They will be vocal about the latter. This is probably what you are experiencing. No bank runs ‘serverless’ or uses AWS.

Usecue web development
What these greenhorns fail to appreciate is the us old-timers have seen the wheel turn, through several cycles. We've seen this *exact shit* before, only usually the new thing is not actually innovative, it is a rehash of an old idea, less well thought through, less well executed, untried and full of bugs.
The old thing may be odd, unfamiliar and #BoringTechnology but it is also fast, reliable, and does the job.
I see soooo much attention going to waste reinventing the wheel.

While there are some nice points about individual #software systems & services here đŸ‘†đŸœ, the big question is *why* does #Cresta (https://cresta.com/) require such a complicated stack? 😰

#WTF #Complexity #BoringTechnology

Cresta AI | Generative AI for the Contact Center

Self-service, live coaching, and post call insights. AI-driven contact center intelligence allows teams to make every customer conversation count.

Cresta
Cold-blooded software

English version:

"I absolutely agree that the future belongs to fusion power. I am in favor of using everything in our power to roll it out without delay, decentralized, anywhere we can. The technology is available and incredibly mature at this point, after all!"

I love, love, LOVE the confused stares I get. Every. Single. Time. #solar #boringtechnology

"Ich stimme dir total zu, der Fusionsenergie gehört die Zukunft. Ich bin dafĂŒr, dass wir das mit aller Macht, unverzĂŒglich, dezentral und flĂ€chendeckend ausrollen. Die Technologie ist schließlich lĂ€ngst da!"

Dieser verwirrte Blick jedes Mal... herrlich. #solar #boringtechnology

#WochenrĂŒckblick, Ausgabe 13 (2023-44) – nach einer Woche Pause, da unterwegs und keine Lust auf Computer.

Diesmal mit einem dummen Fehler, den ich bei einer Online-Bestellung gemacht habe, Livegang der „großen” PV-Anlage, #Photovoltaik-Wettervorhersage, #Laravel #Mix und dem automatischen Entfernen von `console.*`-Calls, #EURkey – dem besten Keyboard-Layout aller Zeiten, „Confusing #Git Terminology“ und #WebComponents sowie #BoringTechnology.

https://www.marcusjaschen.de/blog/2023/2023-44/

RĂŒckblick Kalenderwoche 2023-44

Eine kleine Zusammenfassung der Dinge, die mir in der Kalenderwoche 44 widerfahren sind.

Marcus Jaschen

@yvg I use Jekyll + Minima theme + Netlify CMS + Netlify for hosting (although I think you can substitute GitHub pages for the last). This might fulfill most of your criteria, except Netlify CMS has an "OK writing experience" at most.

I liked this setup because it uses boring technology and does not have any vendor lock-in (everything is open source and possible to self host).

Looking forward to reading your blog posts :)

#BoringTechnology