I find grep and common cli command spam to be the primary issue. I enjoy Rust Token Killer https://github.com/rtk-ai/rtk, and agents know how to get around it when it truncates too hard.
You would be wrong. The IRA is projected to remove a California-sized block of US emissions by 2030. The IRA is the single strongest climate action tried by any country since the Paris Accords.
In an effort to lower the deficit effects of the Trump tax cuts (i.e. increase revenue so they could cut further in other areas), they reclassified software developers salary so that their salaries have to be amortized over multiple years, instead of just a business expense in that year. This is usually done for assets as those things have an intrinsic value that could be sold.
In this case, business have to pay taxes on "profit" that they don't have as it immediately went to salaries. There were a lot of small business that were hit extremely hard.
I don't know if I'd go that far. It's pretty easy to go from ARM to Bicep. And Bicep is genuinely better at everything ARM does and has a wider breadth of features as a DSL- and that is genuinely valuable. It was always going to have to be back compatible/compile to ARM: moving off it has to start somewhere.
Bicep is fantastic. But it compiles to ARM, so it's still limited by ARM's weaknesses and gaps, in addition to the underlying general instability of Azure and the inconsistencies from the Resource Providers. As well, Bicep is declarative- which is elegant in theory, but the stateful design of Terraform can cover up some of those underlying ARM/Azure gaps in practice. The deployment stacks approach on Azure should help further, but there's still a long way to go.
I've always liked the idea of this monetization model. But have you thought about how to disincentivize content stealing? Feels like these models end up needing a very thorough verification system.
That's not all of it, either. Older buyers have gotten the lionshare of their wealth from housing appreciation by preventing new housing and pay a lower tax burden than new buyers due to Prop 13. There's a reason that when it made it to the supreme court Justice Stevens called it medeival and referred to entrenched owners as Squires.
"During the two past decades, California property owners have enjoyed extraordinary prosperity. As the State's population has mushroomed, so has the value of its real estate. Between 1976 and 1986 alone, the total assessed value of California property subject to property taxation increased tenfold. Simply put, those who invested in California real estate in the 1970s are among the most fortunate capitalists in the world.Proposition 13 has provided these successful investors with a tremendous windfall and, in doing so, has created severe inequities in California's property tax scheme. These property owners (hereinafter "the Squires) are
guaranteed that, so long as they retain their property and do not improve it, their taxes will not increase more than 2% in any given year. As a direct result of this windfall for the Squires, later purchasers must pay far more than their fair share of property taxes." https://www.law.cornell.edu/supct/html/90-1912.ZD.html
there were no deployments near 11/10, according to that graph - they also say in the blog that scala2 could go for two weeks without restart, so theyre presumably aware of some sort of memory management issues they're just okay with it.
Probably not? The crux of the opinion seems to grant fair use because it enabled a "new and transformative use," which is a box that a different line of encyclopedias doesn't seem to check.
It's an ISO 8601 vs Gregorian calendar peculiarity, not inaccuracy. See the date section here https://en.wikipedia.org/wiki/ISO_8601, another example of a week 53.
I believe one of the main security benefits of these requirements are ensuring a binary hasn't been altered maliciously, or otherwise I guess. Not preventing outright malicious applications.
Also so the os doesn't have to repeatedly rescan apps, etc.
I also use Azure DevOps for work and am a recently-former MSFT person. From what I've heard from those still there, most of the new development is going towards Github Actions, which is also reflected in their staffing movements. However with GHA running on top of ADO pipeline infrastructure (public info), Microsoft's success with the strategic slow burn as OP called it, and their super-long-term-support reputation, it's probably not in their interest to rush the move. I'd be willing to bet that in a year+ or so the writing on the public wall becomes much clearer. To that extent, we've started planning a migration at my company.
I think you're giving the author too much credit. They recently chimed in on Twitter in a similar context- which I'm guessing is where the motivation for this blog post originates. And despite having a WebKit engineer publicly discuss design decisions and reasoning, they ignore them during that discussion and go on to write this article while making note of literally none of the context that was provided? https://twitter.com/johnwilander/status/1191185213012865025.
It's bad faith commentary, to say the least. Look at the level of accusation they're making "Apple Is Trying to Kill Web Technology" ... "It wants its Mac App Store to be filled with apps that you can’t find anywhere else." Leaving aside the fact that there's no way Apple makes enough from some imaginary exclusivity to justify trying to "kill web technology," none of their moves can even rise to that level. So they were slow to implement WebRTC? Service Workers? Both have massive privacy issues- and partitioning service workers out of process is the crux of how WebKit enforce's privacy- which they're pushing even harder these days. And according to said engineer they even added a compile flag so Google didn't have to use partitioning (I wonder why they wanted that...)- how very anti competitive of Apple. And suddenly mandatory WebKit on iOS is a "monopoly?" It's their platform- they define the security and privacy baselines. Apple has had a walled garden since before the "Web Technology" the author is referring to existed and this is a piece of that. It's another valid consumer selling point- their stores aren't cluttered with trash and I know what those apps can access. But, according to this person, every single point here is fake marketing speak because... checks notes... they want to force people to develop apps only for the Mac Store? Really?
We can be critical of Apple for a lot of web stuff, but it takes a delusional level of self-absorbance to think that Apple is bringing about the end of cross platform web tech because they put up a completely fair and valid barrier, that will probably be resolved shortly, as you said, on one's tech stack of choice.
I started ML work in python coming from a .NET background. To echo one of the other comments here- I believe one main reason is due to the iterative nature of data science. You have to sort of re-build completely every time you make a change in .NET. There isn't much of a notebook concept in .NET- a running engine you can query with additional commands/cells/etc, which is beneficial. As well, real-world data feels easier to work with in a more forgiving environment (non-static typing, etc) like Python. However ML.NET is a cool endeavor and as the .NET data prep libraries get more mature we may find some more production benefits from the very typing/compiling system that, while making it difficult to iterate in, provide more stability in the wild.
You can absolutely train your own models. Your comment is patently false and a fraction of the time it took to write it should have been spent reading that API you have so inaptly described. I encourage you to delete it.