What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

1

The death of #XSLT by the hand of #Google (again) is quite saddening.

To be clear, the last time I actively used XSLT was probably around 2010. But I still had an emotional attachment to this technology.

Maybe because one of the first bug reports I contributed to as a coder was this ancient Mozilla bug from 2001 which was about XSLT rendering (and btw it’s still open after 24 years, and since XSLT is now officially dead I don’t think it’ll ever be addressed).

Maybe it’s because one of the first iterations of my personal website relied heavily on XSLT.

My website back in 2007-2008 consisted in a bunch of XML files, which were rendered on the fly either as HTML or RSS feeds depending on the client. And XSLT was there operating this transformation behind the scenes.

I get it, the world doesn’t rely so heavy on XML as it did 15 years ago.

But HTML is a superset of XML. As those unloved RSS/Atom feeds are still XML.

XSLT provided the perfect glue to transform one into another with a (relatively) simple markup language. No boilerplate code required on your application to operate conversion for client presentation purposes. XML in, XML out, XML in between.

Back then, in the early days of jQuery, I used to dream of an XSLT-based solution to generate and reuse DOM components.

Imagine that: an alternative timeline where no React, Vue or 200MB node_modules for transpiling were required, and everything relied on XSLT to transparently transform whatever markup synctatic sugar your frontend framework used into valid HTML.

But I guess that, especially now that XSLT support has been removed for good from Web browsers, we’ve diverged from that timeline quite a bit.

0
0
0
0
0
0
1
1
0
1
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0

RE: mastodon.online/@tarakiyee/115

At the same time, we need to accelerate the adoption of memory-safe technologies, and that requires all hands on deck. That is why our Technologist, @tarakiyee co-wrote a statement calling for "Improving Europe's cybersecurity posture through memory safety.”

Spread the word, together, we can make Europe’s digital infrastructure safer, more resilient, and ready for the future.

@trifectatechTrifecta Tech Foundation

0

ブチ切れ事案が発生して怒りが止まらない

マンションのLPガスが止まってて、ガスメーターの復帰ボタン押して戻るかなと思ったら戻らず、まさか払い忘れてないかなと思ったけどガス代口座振替にしてあるしちゃんと振替されてるのも確認できたし、おかしいなと思ってガス会社に電話したら隣の退去する部屋と間違えて止めてた事が判明、ガス会社のミスでそっちの責任なんだから今すぐ再開しろって言ってもガス漏れとかの緊急事案以外は明日の朝9時まで対応できませんの一点張りで、久々にブチ切れモードが頂点に達してる

1
1
1
0
0
0
1
0
1
0

RE: mastodon.online/@tarakiyee/115

The best way to stop memory-related vulnerabilities from spreading is to make sure they never exist in the first place. We are thankful to be working with extremely brilliant and impactful projects, promoting memory safety in our critical infrastructure and we see huge potential for progress through collaboration.

(1/2)

0
1
1
2
1
0
1

Esto es una vergüenza. Quieren colar mañana que se apruebe una medida de supuesta conciliación que entre líneas supone condiciones incluso peores que las propuestas por última vez por los totalitaristas que empujan .
Todos nuestros esfuerzos año tras año tirados a la basura porque los interesados en convertir Europa en un amasijo fracturado de dictaduras siguen teniendo su asiento, porque nadie agarra a esa gentuza de la oreja y la pone de patitas en la calle.
patrick-breyer.de/en/chat-cont

0
0
0
1
0
0
0

Dice Político que la Comisión Europea planea modificar la normativa de privacidad para facilitar el desarrollo de la IA.

Las empresas tendrían permitido procesar datos como creencias religiosas o salud.

El proyecto, llamado “digital omnibus”, reduce la protección de datos pseudonimizados y ofrece excepciones para el entrenamiento de IA.

Frente a esto, sólo nos queda el activismo.

politico.eu/article/brussels-k

0
0
0
3
0
0
0
0