jatone

8 ms·

31.
by jatone 5y ago
thats the problem with all these syntax sugar features in languages. you literally can't change them without blowing up your entire ecosystem.
32.
by jatone 5y ago
I get intellectual satisfaction from solving the problems not from the language I use to do it. go hits a fantastic blend in that regard.
33.
by jatone 5y ago
NE cities are more similar to european cities than most of the USA. I have no doubt cars can handle european cities if they can handle NE cities.
34.
by jatone 5y ago
businesses can afford it though. 65K to replace a very large, yearly, expense of a driver? you bet your ass they are going to switch and fast. That is what is going to cause most of the fallout. the ROI is basically 1 year, 2 tops.
35.
by jatone 5y ago
nope. it was an intentional trade off with respect to compilation speed. once generics have baked for a bit with real world usage said decision will almost certainly be revisited. edit: for example one could envision the compiler generates
36.
by jatone 5y ago
I agree. I find this snippet interestingly incorrect. > with very few regressions, up until now. the idea that this is a regression is silly. you can't have a regression unless old code is slower as a result. which is clearly not th
37.
by jatone 5y ago
what I expect to happen now that golang has generics and reports like these will show up is golang will explore monomorphizing generics and get hard numbers. they may also choose to use some of the compilation speeds they've gained fro
38.
by jatone 5y ago
your attempting to dismiss the reality of empirically proven occurrences with hand waving. I have no interest in engaging in such a pointless discussion. NASA, the manhattan project, and other endeavors ALL generated giant economic returns
39.
by jatone 5y ago
these are not mutually exclusive choices. we can easily afford to do both. case and point: we currently are doing both.
40.
by jatone 5y ago
but i do both simultaneously.... the tv is background noise.
41.
by jatone 5y ago
I have no respect for people that ignore them. its been shown empirically again and again to occur. without the original research, the spinoffs may never occur because the initial capital outlay isn't warranted for the various individu
42.
by jatone 5y ago
maintenance for a mature project is pretty low if you just don't deal with the masses constantly bombarding you with feature requests/unrelated fixes. outside of a few specific areas; like compilers but that's mainly because
43.
by jatone 5y ago
> I'm so risk adverse that even risks that are defined as periods longer than my life span are too risky! ok then nothing useful will be gleaned from this article. lol
44.
by jatone 5y ago
the idea that ignores the fact that tackling hard technological problems actually generates a ton of economic activity and generates solutions to other domains. magnetic confinement, lasers, material sciences have all advanced because of th
45.
by jatone 5y ago
for the love of god upbeat scifi please. I can't take the dystopian themes anymore. I need escapism damnit.
46.
by jatone 5y ago
having used rust that isn't a sane trade off. rust is a wonderful language but its orders of magnitude slower than go for development.
47.
by jatone 5y ago
> Error handling is a big one for me. This could be generalized to lack of expressivity; this has been shown over and over to be incorrect. go programs are within the ballpark of other languages in terms of LOC. usually the examples give
48.
by jatone 5y ago
glad other people see that as a problem as well. it irritates me to no end esp considering possible solutions are fairly straight forward but people can't get buyin from the golang team. for the record it stopped working in go 1.15. 1.
49.
by jatone 5y ago
never once was it said by the go devs that generics are bad. it was asserted that generics are complicated to get right and they wanted to take their time.
50.
by jatone 5y ago
var temp func(x) T = g if cond(x) { temp = f } err := h(temp(x))
51.
by jatone 5y ago
and its an optimization the ruby version doesn't necessarily have. you could have just as easily written: var names []string for i, user := range users { if user.isAdmin { names = append(names, user.Name)
52.
by jatone 5y ago
which helps customers. hence why competition is good.
53.
by jatone 5y ago
garbage collector isn't a limiting factor for wasm. my main issue with wasm is no standard interopt for primitive types. thankfully some sort of FFI is in the works from my understanding.
54.
by jatone 5y ago
you just don't know the right girls.
55.
by jatone 5y ago
yeah fog of war makes understanding the situation as a 3rd party cumbersome. I've essentially given up and just going to wait and see what falls out.
56.
by jatone 5y ago
P(x|y) is a fairly common notation in statistics representing a function that computes a probability. its the classic jargon speak problem most specialized fields have.
57.
by jatone 5y ago
they wouldn't point is use both then you are reliant on neither.
58.
by jatone 5y ago
I very much doubt this will occur. cities have many lifestyle benefits. whats going to happen is a whole class of employment is going to die out sure. but it'll be replaced with more interesting things like entertainment focused market
59.
by jatone 5y ago
mac problems.... =) rolling distro's for the win.
60.
by jatone 5y ago
the real question is why they didn't end it entirely. but we all know the reason.

More ›