masklinn

32 ms·

781.
by masklinn 1y ago
> having a mechanism like npm or pip or whatever to automatically handle that is probably easier Re-running `cargo install <crate>` will do that. Or install `cargo-update`, then you can bulk update everything. And it works hella be
782.
by masklinn 1y ago
Technically you could already do that on DisplayPort (since DP2, the standard of which was released 6 years ago), manufacturers don't want to do anything other than high refresh rates. I just want a damn widescreen hidpi display (I d
783.
by masklinn 1y ago
Fortescue has been testing a mine truck capable of that for a year or two (it was built with liebherr).
784.
by masklinn 1y ago
Yes there are multiple systems in testing or production which do battery KERS e.g. Fortescue‘s roadrunner mine truck. There are also trains which do energy recovery but shove it onto the network e.g. Sweden’s Malmbanan. As you note direct g
785.
by masklinn 1y ago
Because rust is a lot harder to experiment with and really does not work for interactive or notebook stuff. Python also has a massive ecosystem of existing libraries. And thus rust is used to either make tools, or build libraries (de novo o
786.
by masklinn 1y ago
A uuid has 122 bits of payload. Depends what you consider “a remote possibility” to be (the birthday attack wiki page has a table for various p and powers of 2)
787.
by masklinn 1y ago
> Can't you improve a compression algorithm and still produce a still valid decompression input? PNG is based on zip, there's certainly ways to improve zip without breaking backwards compatibility. That's just changing an
788.
by masklinn 1y ago
That’s because hydro does not deserve credit: if you can do hydro you already do because it’s cheap and reliable, and if you can’t do hydro that’s it. It is thus of next to no interest. Same with geothermal heating.
789.
by masklinn 1y ago
Costs. Lidar is extra sensors (and also extra signal integration but not having a lidar requires a lot of extra video processing to get information the lidar would straight up give you).
790.
by masklinn 1y ago
Because they did more than just support 3.13: > I'm sure some of the changes are going too far. We are open to revert them if there's an interest from maintainers to merge this PR :) Notably they bumped the bindings (“O3”) fo
791.
by masklinn 1y ago
According to the very link you provide, the sticking point was a dependency which does not use rust, and the maintainer probably being busy. I updated a rust-implemented wheel to 3.13 compat myself and literally all that required was bumpin
792.
by masklinn 1y ago
> Regarding change ids: I wish git itself had those, as then also the tooling would understand them. Identifying commits by their commit messages is fragile, in particular when you may update those for an MR. While commit id truly identi
793.
by masklinn 1y ago
> The reason its like that is that Go philosophically is very much against the idea of annotations and macros, and very strongly about the idea of a clear upfront control flow Annotations have no control flow, they just attach metadata t
794.
by masklinn 1y ago
> This contrasts to Go's approach, much like python, of using casing convention to determine private vs public fields. ( Please correct me if I'm wrong on this? ) Go actually ties visibility to casing, instead of using separate
795.
by masklinn 1y ago
> If you're building a JSON object, you can just not write the code to format some fields out. Did you fail to read the article somehow? Few if any modern language requires you to write the code to format individual fields out. Even
796.
by masklinn 1y ago
> In my dayjob I see this tendency constantly to have a lot of different very narrow structs that somehow integrate into some library, and then a TON of supporting code to copy between those structs. Maybe that's the problem to solv
797.
by masklinn 1y ago
> struct tags greatly reduce the boilerplate code required to map fields to fields. Are you somehow under the impression that Go is unique in having a terse way to map fields to fields? > It’s really quite novel once you understand it
798.
by masklinn 1y ago
Not only are those not technically private, they were never intended for information hiding in the first place. Name mangling was introduced to avoid namespace conflicts in inheritance scenarios.
799.
by masklinn 1y ago
> People will pay untold thousands for a Mac, but God forbid when a PC manufacturer charges more than $599 for a laptop. The article compares the FL12 to laptops of the same price range, including other framework laptops to note that i
800.
by masklinn 1y ago
That is a bit of a truism, as conservators don't have access to time magic and can only conserve what's left. The question is how far conservation extends. To my layman's understanding, the current logic of conservation is: 1
801.
by masklinn 1y ago
It didn’t necessarily need to be highly productive, just more productive than cultivating local stuff, and even if the corn was not necessarily at its most productive it might have been worth it (and with no real replacement) as part of the
802.
by masklinn 1y ago
> AFAIK one factor that accounts for the amazing longevity of old paintings was the compatibility between their many layers. The canvas, the primer, the paint and the medium were all derived from the same plant: flax. AFAIK that's l
803.
by masklinn 1y ago
As far as I understand this only replaces the retouching phase. A human needs to do that in place in order to color and pattern match (and it's already hard enough that way). And I do not know but would assume the retouching paints can
804.
by masklinn 1y ago
That’s not exactly a gotcha. Art conservators have been grappling with variants of that question for hundreds of years.
805.
by masklinn 1y ago
I would assume the mask only covers the damaged areas. This means it replaces manual retouching, so you still need to clean the original painting and remove the varnish in order to get at the original colors, and as part of the usual cleanu
806.
by masklinn 1y ago
In Python this is going to be slow, as you’ll have a ton of Python code in your hot loop. It’s also going to be even more broken than TFA if any non-ascii character is present in the string.
807.
by masklinn 1y ago
glibc will return memory to the OS just fine, the problem is that its arena design is extremely prone to fragmentation, so you end up with a bunch of arenas which are almost but not quite empty and can't be released, but can’t really
808.
by masklinn 1y ago
> jemalloc was probably booted from Rust binaries sooner than the natural course of development might have otherwise dictated. FWIW while it was a factor it was just one of a number: https://github.com/rust-lang/ru
809.
by masklinn 1y ago
Everything is in P4: you checkout the project to work on it, you have everything. You update, you have everything up to date. All the tools are there, so any part of the pipeline can rely on anything that's checked in. You need an olde
810.
by masklinn 1y ago
You can curate a music library without ripping CDs tho.

More ›