setheron

Docker did us wonders but also set us back in many ways (same view point about the proliferation of development on MacOS).

I've lately been thinking why isn't there a public vendored third_party set to use.

If we can agree living at HEAD is preferred having a communal vendored third_party seems like a clear win.

Single version policy doesn't solve version conflicts but it does put it right in your face which is as good as we can do.

Without single versions, new packages to the SAT solver can introduce new duplicate shared objects secretly breaking your hermetic seal.

It doesn't hide the complexity like package managers do by picking a language package by SemVer and crossing our fingers that the shared objects included will work too.

You'd have the same problem with CGO or JNI for Java. C/C++ shared libraries are never part of the package versioning in language package managers (that's the part we stick our heads in the sand about)

my thinking:

40ms might matter if you consider the number of times a process might restart, the number of instances you run and on how many hosts. That could be considerable wasted cycles in aggregate. (i.e. cloud provider)

Also it's not only a function of how many shared libraries but how many symbols they each individually have as well -- also their symbol length as well.

Cool! Reach out to me.

I'd love to experiment with this + additional ideas that further OS when more control is known such as in NixOS.

I have another idea that's quite crazy but I have done some rough benchmarking to prove its efficacy.

Wow! That was a nice reply to see. Made my week.

The knowledge of that scraper went into a Chrome extension that sees some good downloads to this day (I guess people this use hypemachine... I have kids now so my music listening time is on a pause)

Hope you are well as well.

(author) Of course with utmost care a lot of things are possible.... ;)

unfortunately on a traditional system nothing is stopping anything (user?) from mucking with the system outside the knowledge of the package manager.

You clarified correctly (author)

Isnt this what header guards are for or the #pragma include

I'm looking for contributors always to hack together.

I have a project now in Python. Feel free to reach out.

It also treats SWEs as identical; I wish they were a commodity like hardware....

Unfortunately 1 Jeff Dean SWE != SWE

Titles mean nothing. Scope and pay are what matters.

Work backwards from that and call yourself whatever you want :)

The market is really testing being irrational longer than I can withstand.

(Self promotion) Check out my tool which let's you explore ELF using SQL

https://github.com/fzakaria/sqlelf

CosmopolitanC has this cool feature that launches gdb immediately and execs it.

Apache Calcite has this as an integration as does SQLite though virtual tables.

Nonetheless nice work

I couldn't get web archive link to work either.

Is the dump order preserving ? It technically doesn't have to be....

I like the side by side docco thing. I remember underscore or lodash doing that. A nice way to view source. Almost like it's annotated.

Kagi uses CrystalLang. Wow. Didn't know it was used anywhere in production

Oops. I must have missed the mentions.

Surprised he didn't refer to stack PR based systems like Gerrit for reference.

I have never tried those apps that build a top GitHub. I remember Facebook's sapling has a web client as well that does stack reviews.

Typically companies just pay the menial fine. It's run by a self-regularing body and doesn't impact your citizenship -- it's not the government who enforces it.

I graduated from UW in 2011 in software engineering. Never did my P.Eng. I drank the juice that software practitioner will need liability in the future....but it never panned out.

I remember the idea being that he wasn't a real person or a group of people. Fun times. Hope you're doing well TJ.

this is more about doing it on the fly.

author here: it's a bit over the top I admit but the point to get across is that having a DB, and specifically SQL, over which to do your analysis is game changing.

That in of itself is not new, that's why databases were invented :) The idea here is bringing this to the linux low-level toolkit which hasn't seen (historically) much change.

You could imagine software that interacts with ELF as well.

I actually support both by having default.nix

At this point I recommend we take this through another medium like email or feel free to open up a discourse to help fill in the knowledge gap. Feel free to tag me on it.

# non-flake $ nix run -f https://github.com/fzakaria/mvn2nix/archive/master.tar.gz --command mvn2nix

# flake $ nix run github:fzakaria/mvn2nix#mvn2nix

You can still `nix run` packages using niv -- no clue what you talking about.

You can also just look at the niv sources.json file pretty easily if you knew the URL. Rather trivial command to run.

I don't find the above compelling (or correct?)

I tend to just override nixpkgs downstream. I think the situation you are describing is more power-user.

Flakes to me introduced a lot of overhead beyond what niv can provide.

I get 99% value just pinning my top level dependencies since most of the time I'm referring nixpkgs + 1-2 other packages.