Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Veraticus
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
61.
▲
by
Veraticus
3y ago
Not advanced or high-level enough for Kubernetes, eh? Most senior programmers I know love Golang. It is easy to teach, easy to read, easy to understand, and easy to be productive in. And it is difficult to make unclear, complicated, or extr
62.
▲
by
Veraticus
3y ago
Right? So many complaints about "well but it's hard to make N-leaf tries in golang so we need generics!" It's like people believe the success of a programming language is correlated to its ability to express obscure comp
63.
▲
by
Veraticus
3y ago
I would say that a BulkInsert(Any) is a significant premature optimization over just inserting an object as would apply specifically to that object. Because it sounds like you'd have to do weird reflection stuff on the object to determ
64.
▲
by
Veraticus
3y ago
This is a pretty arbitrary benchmark. I would guess, again, that 95% of programmers have never and will never need to create a tree map. Repeat for numerous collections and APIs that are totally irrelevant to most programmers' actual e
65.
▲
by
Veraticus
3y ago
For sure — a lot of language features need to be generic. But most people aren’t coding language features, and giving them the ability to do so can lead to, well, CodeFactoryFactoryMakerGenericMethodHelpersFactory, rather than good, clear,
66.
▲
by
Veraticus
3y ago
I would say 95% of people who are trying to solve a complicated problem with reflection, type erasure, or codegen are solving the problem the wrong way. Obviously I'm glad these tools exist, and some problems can indeed only be solved
67.
▲
by
Veraticus
3y ago
I would say it skews towards languages that are easy to be immediately productive in, which is certainly one of Go's biggest strengths.
68.
▲
by
Veraticus
3y ago
I have written a library actually. I found interfaces perfectly sufficient for allowing applications to consume the contracts of the library without needing generics. Of course I understand that they have a use and are useful, but it's
69.
▲
by
Veraticus
3y ago
But you probably will have to differentiate at some point between what you're inserting. Why not just do that, instead of artificially combine it into one function? Nevertheless I feel like I'm getting lost in the weeds of this ex
70.
▲
by
Veraticus
3y ago
Yeah this was my primary complaint with the inclusion of generics. People will try to be all clever and their code will wind up as an unreadable, unmaintainable disaster. It has definitely led to some cool stuff, but I prefer boring, verbos
71.
▲
by
Veraticus
3y ago
The power of voodoo
72.
▲
by
Veraticus
3y ago
Do you actually have anything of value to add to this discussion? Because this comment is pretty bad.
73.
▲
by
Veraticus
3y ago
Uh, generics are not data structures and generics are neither the only way nor the best way to interact with data structures.
74.
▲
by
Veraticus
3y ago
Dynamic typing via interface{} is also huge Go code smell though, so... Generics are definitely better for you. But I would say the overall pattern you're employing of bulk inserting different kinds of data structures with one function
75.
▲
by
Veraticus
3y ago
Very insightful. Re: the generics point — As a Go programmer I always thought the generics complaint was kind of silly in practice — complicated code should be simplified and made more concrete, not more generic. I’m glad generics were impl
76.
▲
by
Veraticus
3y ago
I’ve been surprised and pleased with Lemmy thus far, but lemmy-ui is kinda barebones at time. Cool that these alternatives exist.
77.
▲
by
Veraticus
3y ago
No I said it. Not really my problem if you can’t read that, since it was honestly pretty obvious. And the other reply to your comment laid out basically the same criticism.
78.
▲
by
Veraticus
3y ago
Not creating weird misogynistic strawmen would be a cool start
79.
▲
by
Veraticus
3y ago
Yikes, it sounds like you have something you need to work on.
80.
▲
by
Veraticus
3y ago
Culture is changing constantly; the idea that there's a fixed point there is absurd, because again, there is nothing inherent to a nation other than lines drawn on an arbitrary map. White people already do include all sorts of people -
81.
▲
by
Veraticus
3y ago
There are 8 billion people on the planet and the population is still growing. Concern trolling about the future of humanity itself is pretty dumb given that, don't you think? Though maybe not quite as silly as claiming that the individ
82.
▲
by
Veraticus
3y ago
If you don’t have the intellectual capacity to continue that’s okay. I understand ethnostatists get easily confused by ambiguity and historical fact.
83.
▲
by
Veraticus
3y ago
No. Nations are lines drawn on a map. The people inside need have nothing in common other than geographic proximity. Japan will exist as long as people live there and call it Japan. It has nothing to do with ethnicity, land, culture, or his
84.
▲
by
Veraticus
3y ago
Cultures are and always have been constantly shifting and changing; conquest is one method of that happening, as you point out, but is far from the only one. Immigration, emigration, catastrophe, technological progress, climate change... al
85.
▲
by
Veraticus
3y ago
I thought nations and the species were composed of women, so what is worse for women is probably worse for them too. Or are women outside of nations and the species?
86.
▲
by
Veraticus
3y ago
Why would there be anything wrong with it? This is the way cultures and people have changed since time immemorial.
87.
▲
by
Veraticus
3y ago
Women wanted to enter the workforce. No one (capitalism, capitalists, men) forced them to do so. That is why your framing is bad.
88.
▲
by
Veraticus
3y ago
> You can increase Google's stock price by $x by serving better ads or implementing the next killer YouTube feature, but those things will eventually cease to exist, and your name will most likely not be tied to that any longer tha
89.
▲
by
Veraticus
3y ago
If economic growth is a byproduct of population growth, then we need to find new patterns for economic growth. There was never a future in which human populations would (or could) increase forever. Blaming wealthy capitalists for ruining mo
90.
▲
by
Veraticus
3y ago
> the point I make is how this only really happened because the forces of capitalism demanded/allowed them to, in order to drive down everyones' wages with the increased competition. Right, this is the part with the weird frami
More ›