itsnowandnever

Dodd-Frank does not clearly state there cannot be those contracts. Dodd-Frank grants the CFTC jurisdiction to govern those contracts. what you are saying was struck down in court in September 2024 where the judge ruled those contracts are legal but the content, fairness, and quality of such contracts are CFTC jurisdiction.

in what way do they violate Dodd-Frank?

spoken like a true go developer ha

foundation has an incredible cast but even among such talent he's a clear outlier

theyve been marketed as a serious competitor to vmware for 15 years. their sales reps mightve just not found you until recently. but we did a poc with them 10 years ago and i dont believe much has changed since

everything will eventually go to zero. we look at some of these things and laugh because we're pretty sure they're going to go to zero within weeks or months vs years. but by the end of all of our lifetimes, most the companies on the stock market will be replaced. the few that won't are probably investment banks like goldman sachs

these deals are made as part of a market so it's more like musical chairs where every time you change a chair you get a ton of money but you don't want to be the one that's stuck without a chair at the end

I think people don't understand what this means either. the nation-state "agencies" that can and will get into your network/devices can do so because they would employ tactics like kidnapping and blackmailing a local telco field technician. or if it's your own government, they can show up with some police and tell them to do whatever and most will comply without even receiving a proper court order.

so unless you're worth all that trouble, you're really just trying to avoid being "low hanging fruit" compromised by some batch script probing known (and usually very old) vulnerabilities

he essentially invented the modern concept of conscription. there were press gangs and conscription-like things all through history but for the most part soldiers were professionals

who has discouraged "sucking it up"? what systemic policies have changed to accommodate this? as far as I can tell, someone can explain how they're the victim to anyone and everyone they come across and no one will care. I can't see how anyone emotionally or materially benefits from saying they're a victim. they may want sympathy but they will not get it.

that said, I don't live in a coastal city where there might be more accommodations for such things. where I live, people are generally on their own to find the means to survive. but, in line with the theme of the post, I'm fairly certain people here have a lower life expectancy and generally lower health than people in places where there is a more robust support network. in which case, the body must, in fact, keep the score.

everyone is the Magnus Carlsen of their own life, though. and humans are irreplaceable. sure, budget decisions are made that cause people to have to go find another employer. but there is no civilization without people in it.

100% - given the resources we have, America is far underperforming at the moment

why do they always say "not only" or "it isn't just x but also y and z"? I hated that disingenuous verbosity BEFORE these LLMs out and now it'll all over the place. I saw a post on linked in that was literally just like 10+ statements of "X isn't just Y, it's etc..." and thought I was having a stroke

i cant imagine it's related. if it is related, hello Bloomberg News or whoever will be reading this thread because that would be a catastrophic breach of customer trust that would likely never fully return

I think the author didn't account for different types of engineering orgs at different points in their lifecycle. "just fix it" at an enterprise massive company as a junior is fine but a senior would know "if you fix it, you own it" and it could cause downstream issues with what your team does or owns at the company. whereas at a startup, if you're relying on junior devs to "just fix it"... good luck with that

commentary from first time staff engineers should be taken with a grain of salt because they can be silly trying to prove themselves. same as first time people managers with an engineering background. if they're not a few iterations through the engineering manager pendulum, they're still getting their bearings.

if you're at a company where leadership doesn't understand this, do your mental health a favor and leave.

I think there's a theory out there that if something can't die, it's more of a "library" than "immortal"... because being born and dying (and the fact that you sharing resources with another living thing is possibly you sharing/shortening your one finite life with another) is so essential for any social bonding. so a machine that has obtained all the knowledge of the universe and enabled to act upon that knowledge is still just a library with controllers attached (no more sophisticated of a concept than a thermostat)

in the end, if synthetic super intelligence results in the end of mankind, it'll be because a human programmed it to do so. more of a computer virus than a malevolent synthetic alien entity. a digital nuclear bomb.

isn't "we made a machine to do something that people used to do" basically the entire history of of technology?

kinda, I guess. but what has everyone on edge these days is humans always used technology to build things. to build civilization and infrastructure so that life was progressing in some way. at least in the US, people stopped building and advancing civilization decades ago. most sewage and transportation infrastructure is from 70+ years ago. decades ago, telecom infrastructure boomed for a bit then abruptly halted. so the "joke" is that technology these days is in no way "for the benefit of all" like it typically was for all human history (with obvious exceptions)

that's not my point - my point is it would not have gotten the adoption it has without etcd and the fact that it was resilient and scalable out of the box

not exactly a fair assessment since neither of those were out and/or available to the kubernetes team at the time. sure, some things at many times from now into eternity may be or become better suited for the kubernetes data plane but at the time if etcd wasn't used there would be no kubernetes today

that touches on what I consider the dichotomy of k8s: it's a really scalable system that makes it easy to spin up a cluster locally on your laptop and interact with the full API locally just like in prod. so it's a super scalable system with a dense array of features. but paradoxically most shops won't need the vast majority of k8s features ever and by the time they scale to where they do need a ton of distributed init features they're extremely close to the point where they'd be better served by a bespoke system conceived from scratch in house that solves problems very specific to the business in question. if you have many thousands of k8s nodes, you're probably in the gray area of if using k8s is worth it because the loop of k8s will never be as fast as a centralized push control plane vs the k8s pull/watch control plane. and naturally at scale that problem will only compound

that's fair but that 99% of all apiserver deployments in the world have the same standard boilerplate footprint is a large part of why it became so ubiquitous. that people running it locally don't have to make any decisions about how to deploy which database or why to use this one over that one... and that's also the same situation in production so people doing stuff in dev aren't punched in the face by an exponentially more complex system in production is huge.

etcd is also the entire point of k8s. that it's a single self-contained framework and doesn't require an external backer service. there is no kubernetes without etcd. much of the "secret sauce" of kubernetes is the "watch etcd" logic that "watches" desired state and does the cybernetic loop to bring the observed state adhere to the desired state.

right, that's exactly what he did. "politics for me but not for thee"

he's definitely disingenuous, though. I think the "cancel" situation was cringe but the guy posts nativist musings about London and then acts apolitical. look, I get it. the first large generation of professional developers that came up in the web 2.0 era are getting older now so naturally many are becoming more conservative. but a lot of this comes across as some kind of backlash because these guys aren't "cool" anymore. there'd be a lot less drama in this situation in particular if DHH didn't act like he needs the approval of 26 year olds. they're never going to see eye to eye with him because he's an old man at this point so he should have some tact and be the bigger person if he cares about the dev community he was a part of. very similar situation to Musk who used to be adored around the world and now he's seen as a basket case.

this is good and I hope this puts a lot of the drama in the rearview mirror. younger developers coming across Ruby must be like "wtf" about this situation. very peculiar to have these projects so politicised and I say that to the people that "try and keep politics out" (DHH) more than anyone. making your politics known and then being like "but you're not allowed to have an opinion on it" is't cute or clever. it's childish and everyone everywhere deserves to be treated with more respect than that.

haha no worries, it's a great site, though! congrats!

I always thought it was funny that for my entire lifetime people have talked about Arizona being perfect for fabs because it's dry there and not subject to tremors meanwhile Taiwan where 60% of all chips are produced (and 90% of the most sensitive ones) is tropical and has earthquakes fairly frequently.

alright, everyone - let's send 10Tbps to SQLify to test the performance of emixam's new framework

I made the switch from FastAPI + Jinja + HTMX to Go and embedding the HTML into the Go binary directly... it's very nice being able to run the apps without an interpreter. I'm able to make ~5MB sized containers to run the full stack

there's a performance increase too, but these apps I'm talking about are so simple it's not enough to really notice. objectively FastAPI is really good and makes running a simple site so easy, I'd still recommend to most people using that.