I just poked around in your reference and every county I looked at in california is near all-time highs (higher than or equal to 2022) except for the northern nowheresville counties.
"compiles to a binary" is not a useful criterion. The criterion Go is winning on is "compiles to a single, completely self-contained binary," meaning it does not depend on libc or any external runtime. You can't say that about .NET. You can't say that about damn near any other programming language. It's extremely rare. The fact that .NET uses a binary packaging format is, like... well ok, so what?
Lol well I don't know what the trigger is for pulling in libc there, because I've built massive scale services that did a lot of nontrivial stuff and then the deployment was a single-binary docker container that did not have libc. The only thing needed to be put in the container was a directory full of root certs so it could do TLS.
(full disclosure, I don't think I ever had my service look up the address of localhost)
edit: seems like you probably have CGO_ENABLED=1, which is now the default and will cause simple networking things to use libc. Set CGO_ENABLED=0 and you won't have libc.
Oh that's good to know. I happen to think Microsoft is chasing a bad philosophy with that declaration, and there is no more danger in statically linking ssl if you're continuously rebuilding and deploying your statically linked scratch image, but then again, the Microsoft approach to a lot of things isn't what I want in my datacenter. To each their own, I guess. I happen to love how self-contained Go programs can be and do not consider that a liability but a strength.
I agree that this is the best approach if your organization is technically mature enough to be on top of it. I do have some sympathy for Microsoft here because they have to ship one set of safe defaults for all the different distribution and deployment setups that are out there, and statically linking your TLS library has the more dangerous failure mode (shipping a known-vulnerable version) if you don't have a rock-solid continuous-delivery setup, which Microsoft has no way of knowing whether is the case or not. I do think they could formally document this with a "don't enable this unless you've got monitoring set up for vulnerable native dependencies and can quickly ship a new build" security warning, though.
Yes, totally agreed that for a LOT of organizations, relying on a system dependency that will likely get upgraded independent of your service is probably the simpler way to go and the way to make sure your TLS implementation stays current. But when you're building tier zero services that must control their dependencies like their lives depend on it, the opposite approach can be quite beneficial, and I don't need Microsoft telling me I'm doing it wrong because I'm not in the 99% use case.
I suppose you are missing the point. Go had support for self contained binaries since its introduction in ~2009. This was not the case with dotnet, if i am not wrong.
But nevertheless , if any language provides something like that, win-win for entire ecosystem.
Agreed. The fact that .NET has a way to do true static linking is great and I didn't know it existed. The fact that they apparently think it's a weird and undesirable thing is less great and would make me worried that they're going to undermine the ability at some point. Golang has had this ability since way back and they think it's a strength.
The consequence of saying they cannot choice to not have them. Is saying your requiring them to have them whether or not the people their want them. Its also a temporary moratorium. Maybe the industry should have been more responsible and not pasted so many externalities on to the public sector if they didnt want to face regulations.
I think the highest parent comment basically hasn't engaged in any of the cost benefit analysis just strawman the subject to banning all industry. They are not doing that and allow other manufacturing to exist maybe the data center business should learn from those industries how to conduct themselves
So if companies are actively trying to build them in the state. And your claim is the state has to allow them to be built? Isn't this just a delay requirement to force them to have data center? Sure they aren't build today but if the government cannot stop them at the permit, or at any point after its a requirement to have them. If you want to deny a state that right to decide via democratic processes you are effectively requiring them to build in their state.
How else could states that deny those data centers if they cannot pass legislation to prevent them or require XYZ parameters before they are allowed to be built? Your argument is nonsensical in my opinion especially in context. I get that if you do a string compare they are different sentences but the semantic effects of the two statements are equavalanet in the framing that comapnies are actively trying to permit and build them.
As someone who's really into music theory, I am always annoyed by what I perceive as a patronizing faux exaltation of it supposedly being mathematically based. It's not math; it's cyclical patterns. Yes, it can all be represented mathematically, and it is surprising to some people how something with feeling can map to these interesting cycles of discrete values in unexpectedly regular ways, and there are very interesting mathematical ratios involved, but that doesn't make it math. I don't think we need to pat John Coltrane on the head and talk about how he's actually kind of smart because he's doing math.
Actually I think that maths and jazz have something in common in the general public peception that you have to be smart to "get it".
Nobody will try to perform a deep intellectual analysis of Lady Gaga's or Ed Sheeran's work the way they analyse Coltrane or Miles Davis (or Mozart, or Stravinsky). Those musicians are intellectuals of the sort Einstein is, unlike Lady Gaga or Ed Sheeran (in the collective perception). Jazz is intellectual music.
And when they analyse something, "smart" people use maths.
I am putting scare quotes around "smart" here to insist that this is largely a social perception and expected behaviour. However, maths can sensibly be used to analyse art, just like it's used elsewhere. This is not patronising, it is more that maths provides a useful language to talk about patterns.
Because I have personally never seen "jazzes" pluralised and I didn't think of it.
Maths and math are both used, and the reason I used the plural form is not because I insist on anything but because it is the most commonly used of the two. I personally don't mind either forms.
With that said, linguistically using the plural for either is a bit odd, since that would imply you can pick "a" mathematic out of many, or "a" jazz out of many. But linguistic is not math (nor are lingustics maths), logic doesn't always apply.
Number theory is all about cyclical patterns, and its theorems fetishize finding cycles of discrete values with suspiciously regular behavior. Last I heard, number theory, group theory, and Fourier analysis are all math.
And yes, I will die on this singular hill: it's all one math, not a bunch of "maths". Math is one interconnected cathedral with music flowing through it, not a drawer full of unrelated trinkets. The British habit of calling it "maths" is oddly reductionist -- it makes it sound like you've got separate jars labeled "algebra", "geometry", and "spicy numbers".
>In linguistics, a mass noun, uncountable noun, non-count noun, uncount noun, or just uncountable, is a noun with the syntactic property that any part and quantity of it is treated as an undifferentiated unit, rather than as something with discrete elements. Uncountable nouns are distinguished from count nouns.
So "math" is the proper shortening of the mass noun "mathematics". What other mass nouns do you shorten by abbreviate by keeping the "s" ending?
We do not say "phys" for physics or "econs" for economics, so keeping the "s" in "maths" breaks the rule.
That's an excellent comparison and it raises an interesting question. When cooking a basic understanding of chemistry techniques will generally prove quite useful but when it comes to music I'm not so sure about math. Maybe some electronic artists who write their own tools?
There are features described with math, but if you try to approach music purely as math it evaporates.
DSP uses a lot of actual math for processing and synthesis. But trad music's chords, rhythms, melodies, and forms are linguistic grammars that can be annotated mathematically after they're defined.
The creation process isn't mathematical. Composers are always making choices from possibilities, and the choices rely on subjective taste.
With Coltrane there a lot of similar structures he could have used, and likely experimented with.
But he picked this particular one for subjective creative reasons.
I'm certainly no chef, and am only somewhat familiar with one particular side of chemistry (physical chemistry) but I don't see how it would be useful in cooking. Unless you count boiling water as chemistry.
The logic behind organic extractions, the temperatures at which different things oxidize or otherwise degrade, the temperature dependence of reaction kinetics (it's nonlinear which is incredibly important when you want one thing but not another), the thermal transfer characteristics of different materials and configurations, all sorts of stuff. The actual "doing" in cooking and baking is figuratively 95% chemistry (and 5% biology) even if the goal is different.
You don't see as much of that mindset in the mainstream of the layman but it's how all industrial processing is done. As an arbitrary example, given a process involving yeast you can construct time vs temp vs moisture vs salt curves to model its behavior.
I would love to see the effect of the mirror's effect on the motion of the camera in a weightless environment. I bet it's enough to measurably affect the picture, especially on a long exposure. Net torque of it opening and then closing should be near (but probably not exactly) zero, but while it's open the camera should spin a tiny amount.
Oracle Cloud isn't actually "terrible cloud", but it definitely isn't geared toward smaller users like startups and individuals. It's downright hostile to casual use. But for fortune 500 companies who don't mind being in bed with Oracle, the price can be right.
The focus not being the DB for 20 years is mostly true, with the exception that all of their applications are well-served by having a very scalable and very bulletproof database in-house.
reply