Great project which you can also use as your package manager on your system. This works nice if your developers have a MacBook with an Arm processor and want to have the build process close to what you do in your ci server which might be a Linux amd64

This post rings a bell for me. I fell in the same trap and saw teams falling in the trap that one might take Docker as a tool to do dependency management since it is very easy to use a FROM statement.

So the trap for me is: mixing up dependency management with Docker, which is just a wrapper for your runtime in 2023™ .

There are already tried and proven tools out there (Deb, rpm) which solve the dependency management problem. Better publish your artifacts as a package backed by a dependency manager and then use the managers tools to make an OCI image as a target.

Using docker images for dependency management does not work. Your FROM will explode with all the combinations you will have to keep in the registry (I.e. „I need nodejs with a C++ image library“)

Docker multistage builds on top seem to confuse people, and they mistake Docker as a CI system to copy artifacts between their multistage builds and maybe start implementing their own caching behavior.

Therefore I suggest to clearly separate the reaonbilities of Docker from a CI runner and from a dependency manager. Otherwise patch management or dependency resolution does not scale for multiple teams.

I think Excel + Visual Basic is some kind of fixed point.

If you iterate long enough on your self developed backend/Frontend system to enable your BI department to work in their own with their data, it will eventually converge into something like a spreadsheet application with a custom DSL.

Or the database + SQL will be your converged application

I think Excel + Visual Basic is some kind of fixed point.

If you iterate long enough on your self developed backend/Frontend system to enable your BI department to work in their own with their data, it will eventually converge into something like a spreadsheet application with a custom DSL

Like Access?

This looks interesting. I am trying to generate comics for my daughter to explain graphically some upcoming events so she hopefully can understand them better or is prepared.

Hope it helps!

Partially related question:

There was an article about the implementation of supervisors and you can’t use the “let is crash philosophy” in the whole erlang/beam stack but there is a small (loc) implementation in C which has to be proven safely in order for the “let it crash philosophy” to work.

I don’t know if this was the definition and implementation of a supervisor itself or a process itself.

Does anybody know what I mean and which article I am referring to? If so, I would be glad if you could post a link to the article

Mandate everybody to delete their calendars each quarter. Only allow to schedule meeting s on specific workdays. Cancel the meeting if the agenda is not set or people are not prepared

Not on this topic, but I wonder why on your cell phone you have to opt-in to safe battery/energy.

Like what amount of energy could you save with the leverage of iOS/Android if people were to opt-out of energy-saving mode

Breath by James Nestor

https://en.m.wikipedia.org/wiki/Breath:_The_New_Science_of_a...

I literally learned to breath properly after reading this book. Took me months to train out of the bad habits I had acquired over the years.

Same here. I now breathe through my nose all night, have trained myself out of a mouthguard and am not bruxating (confirmed by dentist: no more wear from grinding), and I wake up refreshed (even moreso now after quitting caffeine, but that only months compared to years since reading Breath).

So hopefully in the future I can just inject an Apm agent once in my code and it will get the underlying traces?

Yes, Application Observability is a lot of the purpose of this.

Instrumentation will be richer, more accurate, low cost, and able to be of value throughout the application for the purposes of tracing and profiling.

What it will mean is that thing like https://github.com/open-telemetry/opentelemetry-go will be able to use this to better instrument Go applications, and when OTel includes profiling (as well as traces) then you'll be able to use Pyroscope, Polar Signals, etc for that in addition to Tempo (or whatever you use for tracing), as well as using something like Grafana and Datadog to view all of the above.

(I work for Grafana, but the above is relatively vendor neutral as yes we recently acquired Pyroscope and launched Grafana Cloud Profiles, and yes some of the people cited work for Grafana, but others are doing great work here too and it all benefits people who write and run applications using Go).

I am not sure what an Apm agent is, but you don't need to inject anything in your code to use the Go execution tracer today. In general, it's exposed through HTTP (though it needs to be explicitely enabled by the programmer).

This design document is about improving the implementation of the Go execution tracer, but IIUC the user-level tooling and behavior will remain the same (except that the wire format will be documented).

I think you and OP are talking about different things (pprof vs OTEL spans). OTEL spans need to be initialized in every function you want traced, it sucks.

Yep! This is what dotnet and java does and it’s awesome.