HackerTrans
TopNewTrendsCommentsPastAskShowJobs

tyri_kai_psomi

no profile record

comments

tyri_kai_psomi
·7 yıl önce·discuss
You mistakenly assume I mean strictly from a moral perspective. Assume a cost:benefit analysis, where the factors are, depending on the person, some combination of morality, desire to not face consequences (legal system, job, family), and perceived risk:reward ratio.
tyri_kai_psomi
·7 yıl önce·discuss
Most people don't like to intentionally break the law.
tyri_kai_psomi
·7 yıl önce·discuss
The false equivalence is strong with this one. In no way shape or form is it even remotely similar.
tyri_kai_psomi
·7 yıl önce·discuss
I view the draw away from OO as a feature and not a bug. Classical OO patterns should have never been introduced into JavaScript, and it had a just fine object model, that no one ever took the time to understand properly, for those small use cases it was called for. Emphasizing the functional aspects of JavaScript, it's clear strength, is the right call.

It just seemed like it was thrown in there because Java and C# developers who were increasingly being forced to use JavaScript begrudgingly just couldn't live without their "class" keywords, so they took to the forums to make JavaScript more like a "real" language.
tyri_kai_psomi
·7 yıl önce·discuss
Well you mentioned it in your comment, tags are not specific commits. Go Modules standardize around SemVer, and fallback to hashes only when it needs to. The reality is anyone can git push -f and change what a tag points to currently.

So the scenario goes like this: 1. Someone requests a module from GoCenter that is currently not in it's caches. 2. Gocenter downloads the requested version v1.2.3, and stores that. 3. Bad/Careless/Ignorant/Evil (depending on circumstances, I guess) git push -f's 4. Module is requested in Google's module proxy, which now loads a "v1.2.3" into it's local caches, but it contains different code now than "v1.2.3" of GoCenter

Outside of git push -f, there are other hacky techniques you can use to "update" the code a tag points to.
tyri_kai_psomi
·7 yıl önce·discuss
Also I would like to bring up since JFrog's module proxy, GoCenter was publicly hosted first, they will have more than likely been first to host a module version. That means you are now open to the situation where someone uploaded v1.0 of a module to Go Center, and v1.0 of a module to Google's Mirror, and they contain different code.

I am not sure how the Go team plans to handle this, but the only obvious solution would be for Google's proxy to reach out to GoCenter first to see if they have a copy of a specific version, download and cache, and serve that. Does anyone know if that happens?
tyri_kai_psomi
·7 yıl önce·discuss
> The easiest way to identify a monopoly is to look at how badly a company can treat its customers and still get away with it. My company has a half dozen stories like this about Google in the last year alone.

Unfortunately, this doesn't seem to apply to my local general contractors, painters, landscapers, electricians, etc.