vetrom

10 ms·

91.
by vetrom 2y ago
There are a great many reasons the game is referred to as "Spreadsheets in Space", and decisions from the developers related to the ingame inflationary and deflationary mechanisms have had sea-change effects on its day-to-day game
92.
by vetrom 2y ago
Nifty project, this also reminds me of m68k.news which I think was on here a few years back. (source: https://github.com/ActionRetro/68k-news )
93.
by vetrom 2y ago
It's certainly an annoying future. I fully expect some sort of ASN-reputation map and service to become de rigeur in the next decade. Pretty sure heavier-duty SIEM/IPS systems already do that.
94.
by vetrom 2y ago
Email platforms are actually two platforms, composition, and delivery. In the before times, I helped build and was a lead engineer on a team building a delivery platform from scratch, with very minor composition bolted on. (For a time refer
95.
by vetrom 2y ago
> Sentry has never been GPL. That was my mistake, my brain remembering wrong. https://github.com/getsentry/sentry/blob/9.1.2/LICENSE was its last open source license, MITish, right? As for calling it
96.
by vetrom 2y ago
Not one bit, I misspoke from memory there, sorry. FWIW I spent multiple years running Sentry for some fairly large orgs in the eras prior to Sentry's first relicensing. A large part of what got our teams interested in the product wer
97.
by vetrom 2y ago
I see your point about commit ratio, and that I admit is a correct view of the tangible contributions, but I also dont think those are what got Sentry its traction. I will then ask, do you think Sentry would have been able to get enough of
98.
by vetrom 2y ago
Per previous discussions: - https://news.ycombinator.com/item?id=38877059 (sentry FSL relicense) - in particular: https://news.ycombinator.com/item?id=38312686 (rugpull licensing still possible on future
99.
by vetrom 2y ago
This, in part, is why distributions like Debian go to the trouble they do to build everything from more-or-less isolated sourcecode artifacts. Sure, its not always perfect, and getting say, blobless, is a challenge of its own, but no distro
100.
by vetrom 2y ago
Way back in my matriculation, I saw the same behavior but written in terms of CVS, even. As some other posters have written, CS, as it is purely taught, doesn't often touch on the realities of software engineering and delivery. IMO, i
101.
by vetrom 2y ago
What have search engines got to do with vehicle data reporting privacy? I suppose there must be some connection, but how is it relevant to this concern and article? That said, developing, and operating a search engine is no small lift. Br
102.
by vetrom 2y ago
They prefer it for a number of reasons, for better or worse. The big reasons I usually call out are: - packages should be buildable without calling out to any network resources. (this is the primary reason Debian dh-make-golang disables 1.1
103.
by vetrom 2y ago
Lots of browsers avoid it for reasons, but isn't this the whole point of the OCSP( https://en.m.wikipedia.org/wiki/Online_Certificate_Status_Pr... ) and OCSP stapling?
104.
by vetrom 2y ago
> Hell, they allow scripts for one-click product activation bypass to be hosted on GitHub. On one hand, it's a potential revenue center -- I would not be one bit surprised if data collected from these repos gets fed to processes lik
105.
by vetrom 2y ago
You don't need government backdoors when os trust isnt user-trustable and you could chain whatever into a sesame backdoor: https://eprint.iacr.org/2021/626.pdf (for the tldr crowd; this explains a fairly glaring f
106.
by vetrom 2y ago
I am generally wary of anything that proposes to monetize the process of doing my core work. I recognize that that attitude makes marketing and selling a product to developers difficult, though. If they changed from a CLA to a DCO I'd
107.
by vetrom 3y ago
You may have induced latency driven by window sizing/scaling/acknowledgement RTT as well.
108.
by vetrom 3y ago
If nothing else, technician-free battery replacement simplifies maintaining a personal chain of custody, and thus, longevity of the trustable life of a product. Not a directly trust related issue, but an often conflated factor. (assuming yo
109.
by vetrom 3y ago
Not to keep running with thr joke, but: - while a total lockdown on exposure control of your personal data is basically impossible, proactive choices do limit it shouldn't be dismissed out of hand - a working knowledge and practice of
110.
by vetrom 3y ago
IMO Gitea is fairly protected against a 'random' relicensing, as the project does not use a contributor licensing agreement. While license and quality shenanigans can still happen, say if their technical oversight committee went b
111.
by vetrom 3y ago
nVim has interesting ideas, but it doesn't yet have the level of stability that I require in my daily driver text editor. I have colleagues that heavily use nVim and note that it crashes occasionally. While you can make pretty much a
112.
by vetrom 3y ago
It is no longer a requirement, but there is a significant amount of amateur spectrum where CW (morse) is the preferred or only permitted modulation.
113.
by vetrom 3y ago
The expression is a bit different but this is literally a (minor) piece of worldbuilding in Daniel Suarez's 'Daemon' (2006).
114.
by vetrom 3y ago
Having an automated per-user publishing pipeline for packages is a non trivial endeavour. These days you can get close with github-actions style pieplines and releases, but the PPA system has always been a more complete platform in terms of
115.
by vetrom 3y ago
They also benefited from a large ecosystem of third party contributors, whom were not (at least, visibly?) considered as stakeholders when Hashicorp implemented this license change. I'm pretty sure no-one contributing to a product&#x27
116.
by vetrom 3y ago
Theres VLIW/'preprediction'/some other technical name I forget for infrastructures which instead ask you to explicitly schedule instruction/data/branch prediction. If I remember, the two biggest examples I can
117.
by vetrom 3y ago
Even before then, the sufficiently paranoid (but still bound to AWS for whatever reason) would track usage/steal/IO reporting along with best guesses for Amazon hardware expidenture and use that information to size instances to at
118.
by vetrom 3y ago
A VM nest in "big iron" isn't a special case. It's a context push with comparatively exhaustively defined costs, side effects, and implications.
119.
by vetrom 3y ago
JVM runtimes have a relatively high startup cost, are not often good 'citizens' in an instance running multiple types of software, and the build processes for a lot of JVM deliverables is an ungodly mess. Many of those bells and w
120.
by vetrom 4y ago
`rm -r` is a great starter. Real conniseurs go for `wipe -fcrsQ1 /dev`.

More ›