jatone

also did this, hasnt resolved yet.

indeed, I was just on their support prior to that getting posted. lol

no, its not used correctly. If i've misunderstood the point being communicated its because the original comment isn't using words correctly. ;)

How you 'live your life' is orthogonal to that mission

orthogonal does not mean what you think it means given your usage. orthogonal means its entirely unrelated. but the fact is disease control and being able to make personal choices w/ respect to living your life can be in direct conflict means its not orthogonal.

apologies for this correction orthogonal is just one of my favorite words. =)

i know what the water is for i'm saying there is no need to release the steam and have to pump additional water for cooling; you can also use radiators to cool water down etc. as i said the additional water and steam stacks are a quick and easy method for cooling when a water source is nearby. there are other options that can be used when water isn't available.

The nuclear plants need to be built near water, which means they're likely to end up near habitation.

personally I feel this is untrue. its done out of convenience; but from an engineering/infrastructure standpoint there isn't a reason we can't condense the steam that gets pumped out of the towers.

Is Golang "ruthlessly productive" for interfacing with complex relational databases?

neither is ruby lol.

Once you actually start heap allocating you hit massive pauses.

citation needed. go afaik has millisecond pauses at most. maybe you're thinking of throughput losses due to forcing more CPU to be spent on collecting?

the strategy you're mentioning is also known as slab allocation. all GC implementations allow this strategy naturally.

words have meaning; using them correctly in context matters. the fact of the matter is the term you used has nothing to do with stimulus'. you were attempting to imply that forgiveness somehow harms the lower classes when it categorically doesnt.

the only person being 'uncharitable' here is you; attempting to label someone calling out your BS position as 'extreme' and then attempting to categorically label an entire political spectrum with the same brush.

I didn't say unchecked exception don't work. I was pushing against the assertion that 'Java is more explicit'; its not since java developers actively work to avoid using the damn feature being mentioned.

which still isn't correct. it doesn't hurt the poor that the upper middle class will also receive this benefit. regressive taxes do. in fact this policy still helps the lower income class because many of them will also benefit from it and far more than the upper middle class.

this means testing bullshit has got to stop.

bankruptcy has regulation already. you have to actually show an inability to pay, etc.

i'm not suggesting terminating the federal loan program either. just make it possible to default to get out of these situations to ensure they are not predatory.

I'm perfectly capable of complaining about both. biden hasn't done jack shit beyond not being a raging asshole.

working american's are still getting shit on; american's are still being disenfranchised of their votes.

and none of his action are helping the very real situation of income inequality.

and I'm still waiting for him to actually deliver on campaign promises.

every java team i've worked with handles their exceptions by making them runtime exceptions to bypassing the very thing you're pro-porting.

this isn't targetted relief. this is shit that was already suppose to be done.

also regressive stimulus are not even a thing. maybe you're thinking of regressive taxes? which still wouldn't be right.

I'm aware. and but these things are being trotted out by people as 'look hes (biden) done so much!!'

when in reality: hes done jack shit except what already is suppose to happen!

I promise you biden's PR group is the force behind these articles.

or you know we could just make student loan eligible for bankruptcy.... then just let the courts deal with it as usual.

its 100% intentional on the administrations part. this is their 'creative' way of trying to not meet their campaign promise. highly annoying.

gasp new code can introduce bugs... whatever will one do?!

didn't say it invalidated your point just that it was a bad example. just because something has inertia doesn't mean its good or even okay. it just means it timed the market correctly.

you could have used UDP for example which being as old as TCP has spawned many new protocols on top of it (including quic) and in its own right has been the backbone of many applications.

TCP is a bad example; since its actively being supplanted by quic simply because TCP is such a inefficient protocol.

that's a user problem. they granted the extension permission to access the data. that's on them. You will never be able to solve that problem. after all a user can just hand out their credentials if they want to.

Facebook's issues stems from the fact they allowed apps in their market to access data they didn't need to function / hide exactly how much access these applications are granted.

the reality here is auth is the solution; for browser extensions we need better UX. if a extension is asking for access to your navigation / page data that needs to be flagged and warned about during the setup flow.

many of these auth systems make the risky API access grants appear extremely benign.

except that isn't the answer gnome is notorious for being a pain to work with if it doesn't align with their vision.

all the issues you mention for go literally plague every other language out there except for a very small minority. of which rust is one. its a fair criticism but you're completely disregarding the downside around development speed.

I've used both languages extensively. I like both languages. I still reach for golang first because its faster to develop with simply due to the compile times.

not really. if you're in a steady state (like discord was) you wouldn't see any spikes. you'd have a consistent utilization. if you start allocating heavily then you would potentially see an increase. which makes sense, you're increasing your workload, utilization needs to increase. but still not necessarily a 'spike'

sure - https://github.com/golang/go/issues/44167. you'll see the new design the CPU util only increases in GC CPU utilizations when you're actually allocating heavily. which makes sense you're doing more work. this should completely resolve the problem discord had; since their system was in a steady state.

or you know; just pace the GC mark and sweep algorithm. which is what go is doing now.

goat -> greatest of all time. doesn't seem counterintuitive. its jargon most often seen in sport literature.

actually that is the problem. no they can't 'easily' add a new flag (or they would have). it doesn't fix the problem of being broken by default and any fundamental change in behavior will lead to problems as well.

the point is the language is broken fundamentally and because its syntax sugar there isn't anything you can do realistically. a function call can be replaced, deprecated, and then removed and all of that can be automated and be non-disruptive over a few releases.