1,037 karma · joined July 28, 2019
But i use Flakes through my entire setup, so i imagine that's why.
I am uninformed in this game, so this is not a statement by me: However i've been told that one issue is squatters, land being used purely as investment and with low costs you can easily afford to buy land and squat it till a time when you later sell it in the market.
As someone looking to buy land to build a home on, i've noticed quite a lot of property seemingly being used purely for investment. Flipped through the years for profit with no real added value, in an area of the country (PNW) that is very, very expensive due to limited supply. It is very cheap to keep land, tens of dollars a year for 10 acres (the lot size i'm familiar with) iirc.
Inhibiting this behavior seems beneficial.
Though i imagine more interesting (than simply "high") taxes could help more. Ie something like a higher tax on unimproved and uninhabited land. Encourage usage, not squatting.
But.. i don't know anything here. I just have experience looking to buy land, and watching what goes up for sale.
Until automation "saves humanity"[1] we have to work. We can and should push for healthy balances, respectful treatment of workers, sane retirement ages, etc. But still, work needs to be done, and i find it incredibly frustrating that some people think we can all just stop working.
[1]: Though i'm quite pessimistic that automation will save humanity. I suspect that while it could, it will also cause such turmoil in the beginning that we fail as a species. A nuclear winter of the working class.
For those unfamiliar, here is the interesting bit:
> rkyv implements total zero-copy deserialization, which guarantees that no data is copied during deserialization and no work is done to deserialize data. It achieves this by structuring its encoded representation so that it is the same as the in-memory representation of the source type.
A second or two of a song is shockingly good at triggering your memory of songs you know well.
and with that said, i often wanted to add Reed Solomon simply because i found it fascinating. Truly an ingenious "trick". Though i never got past the idea phase, as it felt i was just double encoding everything and if bits were to flip then my storage mechanisms (HDD/S3/etc) would be the one seeing the flip and fixing it. I figured my software was never going to see bitflips to make this type of feature useful.
I'd be curious if any blockchains/immutable storage/etc actually use this type of error recovery. Ie if the layer _above_ network and storage actually benefit from error recovery. Since i often expect both network and storage themselves to bake error recovery in.. /shrug
Looking at the release notes, %w was introduced in 2019. So yea, my professional experience with Go predated that. It was all strings back then, and miserable. My team usually used libraries to deal with the shortcomings.
I ended up leaving Go frustrated mostly because of how simple patterns, like Iterators (in Rust) were so horribly expressed in Go. Stretched out into many, many lines of code. All the simplicity of the language left me with no help to manage my actual app complexity.
However i am aware that slowly Go is adding complexity to help you manage real problems. Generics, and apparently sane error handling. I'd love to see them add Enums, as Go's version always felt ... well, just a bunch of consts in userland pretending to be Enums heh.
Maybe one day Go will be feature complete enough for me to look back. Though i'm a big fan of Rust, so maybe not. The only area i feel Go is better than Rust is the way in implements Async, but that's likely more to do with the GC - so, tradeoffs as with everything.
I think you misunderstand me. I'm not complaining that there is no context. I'm complaining about destroying all structured content. If you want information out of that, you have to string parse your errors! No type checking or anything useful on error types either.
Yes, it's possible, but that usually comes with 3rd party libraries that manage errors with structure. Such as a large array of arrays producing a structured "stack". But if a single person uses string formatting with your nice structured error? Goodbye structure, hello string parsing.
It's a very, very low bar.
What i learned in school was how awful people can be. The extremes where we humiliate and torment others. The mindless churn to be in a clique and simply fly under the radar.
Slight tangent, but: In my view a parents jobs is to let children fail with a safety net. To be there and help them recover after failures are experienced together, to grow from them.
Public School, in my view, does none of this. It attempts to educate, sure, but not in socialization. Likewise parents, even the well executing ones (by my definition) cannot share the experiences. Parents can only see the aftermath and try to mend some wounds.. but the growth is up to the child, in isolation.
I don't know the better solution. I don't have the answer. All i know is that in the context of how i judge parenting, school fails entirely on. School is lord of the flies. Many prosper. Many drown. Many could grow, if only a guiding hand existed.
Clearly i'm a pessimist here. I'm also not having children, which may not surprise you. Hah.
You're probably not wrong in general, but as is often the case, i imagine reality is a bit more complex.
You'd have a difficult time learning Rust with Go, hah.
I love/use Rust. I don't think any of this is complicated. BUT, i'm a big fan of just "clone your problems away" for beginner Rust users. Going knee deep into techniques which merely reduce memory usage when people likely don't actually care - at all - about it just feels wrong to me.
So yea, maybe a cursed library where SimpleString is just some niceties around some Cow + Arc thing which is also Copy. Hell, you could probably just apply it Vec and who knows what else.
Anyway, clearly not something i'm advocating anyone _really_ use. But it seems a nice way to make stuff "Just Work" in the beginning.
I will say someone here was right though. :)
Hah. Related, i became disgruntled with my previous favorite language for this reason. It promoted this style of development. Surface level simplicity built into the language, with minimal tools to actually manage the complexity that is inherent to the problem space you're working in.
Not sure what typing system you're referring to, but it sounds very half-baked at best. I'm using Rust fwiw.
I cannot access any field or method that does not exist. Even dynamic traits are compile time enforced, but i think we can largely have this discussion around static dispatch.
You need the same tests from a typed system in a non-typed. You _don't_ need all the tests from a non-typed system in a typed system.
Writing tests to enforce types just hand-rolls a type system, in my experience.
Not sure if it makes sense as an LSP, but if it was i could hook it into my editor of choice (Helix, at the time of writing) easily
I'm never sure what will break if i don't give it internet access :/