2,660 karma · joined May 6, 2012
At a cap of $5,000, the dependent care FSA does not even cover 2 months of daycare for my daughter, and the tax savings amount to less than two weeks of care.
GDScript is, in my opinion, unsuitable for anything more than a couple hundred lines at most.
I take some issue with this characterization. Let's look at Grafana in particular. Grafana was not always AGPL, and much of its popularity came before the license change. I've been in multiple organizations who only purchased a license for Grafana to avoid the AGPL terms because it had gained traction already in the organization and switching away would have been more costly, and AGPL software is still outright banned.
That Grafana is still popular does not show that the AGPL doesn't impact usage or popularity, only that Grafana is still popular.
Alternatively, from the article: > For early-stage AI startups, Hu says one of the most common issues she hears is that startups are compute-restrained. Large enterprises are able to strike multi-year, massive deals with cloud providers for GPU access, but small startups are often left out to dry.
They're being paid, so of course they would do it. It's not much different than the reservations that GCP allows you to purchase today.
We put absolutely no critical thought into whether this was a likely thing, and we completely ignored the many government and media reports that are credibly sourced which state that there are known phishing scams and other threat actors trying to capitalize on this incident.”
I highly doubt this is something that Crowdstrike actually did.
Edit: Amazingly they did, the article has been updated with a statement. Amazingly stupid all around.
That's not to say that there haven't been other Crowdstrike fails on Linux, especially pre-eBPF module, but that's not one, and that class of failures has been eliminated in the move to the eBPF based module.
Strings are immutable, so no efficient truncation, concatenation, or modifications of any time, you're always reallocating.
There's no native support for a view of string, so operations like iteration over windows or ranges have to allocate or throw away all the string abstractions.
By nature of how the interpreter stores objects, Strings are always going to have an extra level of indirection compared to what you can do with a language like C.
Python strings have multiple potential underlying representations, and thus have some overhead for managing and dealing with those multiple representations without exposing those details to user code
Generally, no, that volume of money is not even worth the effort of maintaining the polluted cap table.
On Portugul, it's worth asking why it's failing after many years of being such a success that the model was copied around the world. https://www.washingtonpost.com/world/2023/07/07/portugal-dru...
> After years of economic crisis, Portugal decentralized its drug oversight operation in 2012. A funding drop from 76 million euros ($82.7 million) to 16 million euros ($17.4 million) forced Portugal’s main institution to outsource work previously done by the state to nonprofit groups, including the street teams that engage with people who use drugs. The country is now moving to create a new institute aimed at reinvigorating its drug prevention programs.
> Twenty years ago, “we were quite successful in dealing with the big problem, the epidemic of heroin use and all the related effects,” Goulão said in an interview with The Washington Post. “But we have had a kind of disinvestment, a freezing in our response … and we lost some efficacy.”
I just wanted to respond to this a bit more. My moving away from a project is my choice. Just because it has active devs and regular commits doesn’t mean that I’m in any way obligated to continue to use it, or contribute to it. It doesn’t fit my workflow, and the issues are longstanding and glaring. Might they be fixed in the future? Sure. Am I interested in sending patches in or tracking that effort? Actually it really doesn’t even matter, a broken workflow is a broken workflow, even when the tool is free. It doesn’t work for me as is and I will find something else if I want.
This seems to be some sort of defensive response as if I was attacking the project. On the contrary, and like I said before, I generally like it, but the issues I have, which are to be both glaring and longstanding, means that it doesn’t fit my workflow and I’m considering moving. Not all tools need to suit everyone’s workflows, and “patches are welcome” is very beside the point.