Yes, and...
https://four.htmx.org/essays/yes-and
3 months ago
Public list by tgogos
sources with content of how things have evolved in tech
https://four.htmx.org/essays/yes-and
3 months ago
https://macwright.com/2020/05/10/spa-fatigue.html
about 1 year ago
https://www.jonoalderson.com/conjecture/its-time-for-modern-css-to-kill-the-spa/
about 1 year ago
https://htmx.org/essays/codin-dirty/
almost 2 years ago
https://www.gitpod.io/blog/we-are-leaving-kubernetes
almost 2 years ago
https://www.matuzo.at/blog/2023/single-page-applications-criticism
about 2 years ago
https://stackoverflow.blog/2024/06/10/generative-ai-is-not-going-to-build-your-engineering-team-for-you/
about 2 years ago
https://intercoolerjs.org/2016/01/18/rescuing-rest
HATEOAS The acronym stands for Hypermedia as the Engine of Application State and, in plain terms, it means that a REST-ful system should send both data and the network operations on that data in responses to clients, so clients don’t need to know anything in advance about the structure of the server. This actually makes loads of sense and, upon reflection, you will realize that this is exactly how the web and normal HTML works: you get a page of HTML (data) and, embedded in that HTML, you have links and forms that tell you what you can do with that data. So far, so good. But, as we know, REST was being pushed for and adopted by JSON APIs. JSON doesn’t have a native notion of links or forms, so it wasn’t obvious what to do. Some people started including representations of links encoded in the JSON itself, other people thought that using HTTP headers was the right approach. Lots of arguments were had and no one obvious and widely used solution emerged. Again, holy wars were waged, friendships were won and lost, and so on, ad internetum. Most normal developers dropped (or never really understood) HATEOAS in the JSON context anyway, so it didn’t end up mattering too much. Except that, unfortunately, it was the most important and innovative aspect of REST! As the wikipedia page says: HATEOAS is a constraint of the REST application architecture that distinguishes it from most other network application architectures. Without HATEOAS, REST is just a collection of (very) good ideas on client-server layout, but not a revolutionary architecture shift.
about 2 years ago
https://intercoolerjs.org/2016/02/17/api-churn-vs-security.html
about 2 years ago
https://hypermedia.systems
almost 3 years ago
https://www.youtube.com/watch?v=2hMrk7A8Wf0
almost 3 years ago
https://www.youtube.com/watch?v=NA5Fcgs_viU
almost 3 years ago
https://isovalent.com/blog/post/ebpf-documentary-creation-story/
almost 3 years ago
https://samnewman.io/blog/2023/02/08/dont-call-it-a-platform/
over 3 years ago
https://www.allthingsdistributed.com/2022/11/amazon-1998-distributed-computing-manifesto.html
almost 4 years ago
https://tailscale.com/blog/modules-monoliths-and-microservices/
almost 4 years ago
https://www.coss.community/cossc/elastic-license-2-0-and-the-evolution-of-open-source-licensing-3jb3
over 4 years ago
https://www.lastweekinaws.com/blog/nobody-cares-about-the-operating-system-anymore/
over 5 years ago
https://twitter.com/networkop1/status/1298914612851757057
about 6 years ago
https://www.infoq.com/articles/cloud-native-architecture-adoption-part2/
about 6 years ago
https://twitter.com/BrandonPhilips/status/1253375516180017153
Starting 7 years ago the CoreOS team built a number of influential technologies. The pursuit was always better automation, security, and efficiency. So, I went through the CoreOS blog from the beginning and highlighted a number of the technologies that we built together. 1/x
over 6 years ago
https://www.honeycomb.io/blog/the-future-of-software-is-a-sociotechnical-problem/
"We are in the Middle Ages of software delivery" "Observability is about the unknown-unknowns"
over 6 years ago
https://blog.cloudflare.com/the-history-of-the-url/
over 6 years ago
https://speakerdeck.com/mcfunley/choose-boring-technology
slides with comments here: http://boringtechnology.club/ "If you’re giving individual teams (or gods help you, individuals) free reign to make local decisions about infrastructure, you’re hurting yourself globally." "Technology has global effects on your company, it isn’t something that should be left to individual engineers. You have to figure out a way to make adding technology a conversation." "You should have a process for adding technology to your stack that involves talking to other humans." "Prefer technology that’s well understood, with failure modes that are known. Prefer things that let you focus your attention on what really matters." "It’s important to master the tools that you do pick."
over 6 years ago
https://blog.jessfraz.com/post/the-life-of-a-data-byte/
over 6 years ago