pylua

I could see this as a recursive lawsuit. One set of lawyers negiotates the pay down to the payment down to 3 billion. The next set of lawyers argues two billion is too high and negiotates it down to 1 billion, all the way to zero. It's lawers all the way down!

> did not win or lose anything

Is this true? Would there not be dilution?

The board, run by the shareholders, wanted that deal and put it in place. They must have thought that the value add was worth it. Granted, it seems many do not think they acted correctly, hence the ruling and the lawsuits.

The point is that time will tell if this really saves money over the long run. I do not know the law and I am not questioning the board here.

Or, in this case, what you potentially can sue for? Nothing here was negiotated as far as I can tell.

I am confused. These are the lawyers that sued Tesla and won, not Elon/Telsa's lawyers, and they want that sort of payout due to the cost savings to Tesla? If so, I wonder who funded the original lawsuit -- was that not enough -- or was this the idea all along?

I like that istio does mtls. It also helps with monitoring the requests.

I think this is on point. Humans will take a back seat to ai and will primarily test the outputs as if the ai is a black box instead of having deep insights.

There will be no need for human ingenuity. Perhaps if llm had existed at the time of assembly language being predominate there would be no higher level language for humans to use.

The rates in that article are absolutely eye popping. I don’t understand their methods but I can say the charts align with what I witness.

I have never seen that before. When it generates images that have people in the background they look HORRIBLY disfigured.

This seems to be the problem with generative ai. It’s unable to tackle the hard problems due to a lack of massive data sets and existing solutions?

All it is good at is solving things humans have already solved. When I see this I definitely wonder why we aren’t researching bigger issues that really affect people.

Producing a plan is easy, executing is hard. We’ll see how sincere they are.

Companies that handle or touch U.S. customer data must have code written exclusively by citizens or people with visas with the appropriate clearances inside the U.S.

More software , such as banking software, iot, control systems all needs to be done vertically in the U.S. just as cyber security should be done by people with clearances.

It really is a security concern.

This is definitely trending. It’s not just software — it seems like most jobs that don’t require in person or a U.S. license/certification are moving to other countries.

Profits are becoming hard to come by at many places and a large driver of cost is salary.

The U.S. dollar has also grown in strength over the past ten years. I think it has more than doubled compared to inr?

From what I have seen unwanted attrition is higher in India.

This is especially true with the lower cost workers, which is one of the main points of outsourcing.

I found test containers to be slow to startup last year. It wasn’t worth the effort considering how long it took to run compared to traditional spring IT h2 hibernate.

Maybe they will just acquire a firm?

I agree completely. The problem here is that ai can’t run the code 1000s of times to deduce the context to create more meaningful comments.

Maybe this is what will save humans against the robots — the ability to verify and study topics in their context efficiently.

It looks like a lot of boiler plate that adds noise. Usually the most useful comments explain the function in its context, not the code itself. Or, if the code does something atypical then a comment is very useful.

This is interesting, but a waste .

> It was only slightly slower. (Netty vs virtual threads) that could easily just come down to implementation differences.

I think this might be it. After my post I thought about it and guessed that maybe the workload was potentially not an optimal netty workload, or there are aspects to the workloak that are not well suited for netty. I am unsure, however.

> That said, it's definitely possible for the reactive libraries to simply use virtual threads whenever they do anything in parallel. That'd allow the model to avoid potential issues when calling into blocking code.

Definitely would be a great enhancement for the elastic thread pool.

> The benefit of virtual threads is making things even simpler so you don't need to understand those complicated constructs. You just spawn new threads whenever you need to run things in parallel.

Once you get used to it, in my opinion, those constructs are simpler and easier to use than the standard multithreading options in java, specifically flux and timed operations. However, some items like request scope or session scope is a problem and harder (impossible?) to do right.

Apparently that is not what the regulations say? I don't think us employees / employers are able to go against the regulations without legal consequences.

Some rules are put in place to prevent situations that are extremely unlikely to occur in the first place, but are more catastrophic when they happen. Trying to compare incident rates would not account for how well rounded a system of rules really is. I would suggest that the best course of action would be to follow the advice of our fellow countrymen who drafted these rules, then ask other countries to follow it if they want to sale products in our country.

Here is one the articles I was referencing.

https://www.theguardian.com/business/2023/aug/28/phoenix-mic...

When I read through it again it I realized many problems seem similar to common issues in software projects.

That's the key thing -- not expecting other countries to follow the standard we set. At times it is also even the same values. It's absurd that we don't do this.

It's not so simple. There were previous articles posted on here months ago basically saying that the building standards are much higher in the United States in terms of permits and certifications and that is what is slowing things down. Sectors are heavily regulated in the United States which comes with a very high price tag, however, they are often done for the right reasons.

If American workers are expected to follow the rules but other countries have less strict rules with different tradeoffs, maybe the regulations need to be examined.

Over the past 10 years the us dollar has gained in strength a lot compared to other countries. Perhaps if we want to bring this stuff back into the country the currency needs to be devalued. I assume it will be naturally devalued over time, even compared to other countries, considering the national debt.

That’s really interesting —- looks like there is a clear winner. I am curious as to why non blocking is slower.

I also wonder if the reactive libraries could be refactored to use the virtual threading model. It would help with a lot of the debugging issues. I would be sad to see those libraries go by the wayside as they do make a lot of complicated tasks simpler once you understand it.

Have there been any benchmarks compared to netty for real world use? Or any comparisons ? That would be useful for those of us considering a switch.

Sometimes hallucination is sort of a feature instead of a bug. For instance, if I ask it how to do something and it hallucinates , usually it is perfectly logical for it to work the way it suggests, even though it is wrong.

In other words, it can be a good feature request or idea.

Worse is that no one wants to pay to keep the domain knowledge alive. The project finishes, the team disbands which makes maintenance cost more.

If interest rates go down, it may prolong it for a lot longer? People have to put their money somewhere.