4,679 karma · joined February 25, 2007
If they've performed an Unauthorized Access to a Computer System then they may want to drop any copyright claim.
uv is not written in python so it doesn't suffer from the bootstrap problem of having a python version installed to begin using it. Users (new and even experienced) get confused and annoyed when they try to use python tooling in the same venv as their application instead of using pipx.
People also get confused and annoyed if they use mac and run `brew upgrade` and find themselves with python 3.13 or just any version that is new (yes we can pin to python@3.11 or whatever) so pyenv is a good option.
So now you have pdm, pipx, and pyenv to manage all this stuff. With uv all this hassle goes away.
This is one feature I wouldn't mind making it into other languages. It makes so much sense for doing UI stuff.
It's faster than a Lamboghini Spire.
This is mirrored in Europe where countries using subs (Norway, Sweden, Netherlands, etc) have better English language skills than dub countries (France, Germany, Spain).
> We just need to encourage async runtimes to implement this fix.
This likely needs async drop if you need to perform a follow up call to cancel the outstanding tasks or closing the open sockets. Async Drop is currently experimental:
If you haven't seen the remix, here you go: https://www.youtube.com/watch?v=1gI_HGDgG7c
> Ballmer wins... 2010: Microsoft creates Azure
The Azure project was run by Nadella before he became CEO. And it succeeded despite Ballmer. Azure was seen as the Microsoft cloud, where people ran Windows Servers. But Microsoft had long lost the battle for the server space to Linux.
When Ballmer stepped aside, only then could Nadella drop the limiters and push the Microsoft <3 Linux perspective to get the message out that Azure is a home for Linux workloads too.
I guess this is part of the clarifications one normally asks when in an interview setting, but he has specified numbers and not integers. One could choose (pi*2)/2 and you will owe a lot of money.
slog is shorthand for structured logs[1][2][3][4]. So refactoring the logs [without a tool] is manually converting them to a slog. You have a great pun on your hands.
> Speaking from experience?
I have a notebook laying around with a loose plan on how to get the most compression possible out of a log file. It would use ML to figure out what the log strings would be - but I think your idea of scanning the executable is even more clever. Anyway, once it knows the log strings you can probably stuff it into off the shelf column storage for great compression rates. And if the compression rates are good enough then searches should be much much faster as well.
Who do you reckon are the more important existing competitors? Grafana labs or Sonarqube?
[1] https://github.com/slog-rs/slog
[2] https://github.com/gookit/slog
Nice.
If you find the time and urge I'd be interested to know the results.
Before Go had iterators, you either had callbacks or channels to decompose work.
If you have a lot of files on a local ssd, and you're doing nothing interesting with the tree entries, it's a lot of work for no payoff. You're better off just passing a callback function.
If you're walking an NFS directory hierarchy and the computation on each entry is substantial then there's value in it because you can run computations while waiting on the potentially slow network to return results.
In the case of the callback, it is a janky interface because you would need to partially apply the function you want to do the work or pass a method on a custom struct that holds state you're trying to accumulate.
Now that iterators are becoming a part of the language ecosystem, one can use an iterator to decompose the walking and the computation without the jank of a partially applied callback and without the overhead of a channel.
Using the "Code" column to ignore comments and blanks.
This is based on the mozilla-central-78a5d30a370f bundle.
(Also, holy crap it took tokei 10m to run this analysis).
Wtaf.