Rust<\/a> has leaped to its highest position ever in the monthly Tiobe index of language popularity<\/a>, scaling to the 13th<\/sup> spot this month, with placement in the top 10 anticipated in an upcoming edition.<\/p> Previously, Rust has never gone higher than 17th<\/sup> place in the Tiobe Programming Index. Tiobe CEO Paul Jansen attributed Rust\u2019s ascent in the\u00a0just-released July index to a February 2024 US White House report recommending Rust over C\/C+, for safety reasons<\/a>. He also credited the growing community and ecosystem support for the language. \u201cRust is finally moving up. After the tailwind of the US government, which recently announced to recommend moving from C\/C++ to Rust for security reasons, things are going fast for Rust,\u201d Jansen said. \u201cThe community is growing, including the number of third-party libraries and tools. In short, Rust is preparing itself for a top 10 position in the Tiobe index.\u201d<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> In a highly-anticipated federal ruling on July 3, US District Court Judge Ada Brown determined that the US Federal Trade Commission (FTC) did not have the authority to issue a nationwide ban of non-compete agreements. Although the judge\u2019s decision was preliminary, employment lawyers watching the case agree that the FTC non-compete move is effectively dead.<\/p> Brown, of the US District Court for the Northern District of Texas, said that she would issue a final ruling on Aug. 30, the day before the FTC ban was slated to take effect. But based on the strong wording of her preliminary decision, there seemed little doubt that she would ultimately block the ban.\u00a0<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> As agents using artificial intelligence have wormed their way into the mainstream for everything from customer service to fixing software code, it\u2019s increasingly important to determine which are the best for a given application, and the criteria to consider when selecting an agent besides its functionality. And that\u2019s where benchmarking comes in.<\/p> However, a new research paper, AI Agents That Matter<\/a>, points out that current agent evaluation and benchmarking processes contain a number of shortcomings that hinder their usefulness in real-world applications. The authors, five Princeton University researchers, note that those shortcomings encourage development of agents that do well in benchmarks, but not in practice, and propose ways to address them.<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> Well, that didn\u2019t take long. After all the \u201cthis time it\u2019s different\u201d comments about artificial intelligence (We see you, John Chambers<\/a>!), enterprises are coming to grips with reality. AI isn\u2019t going to take your job. It\u2019s not going to write your code. It\u2019s not going to write all your marketing copy (not unless you\u2019re prepared to hire back the humans<\/a> to fix it). And, no, it\u2019s nowhere near\u00a0artificial general intelligence<\/a>\u00a0(AGI) and won\u2019t be anytime soon. Possibly never.<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> In 2007, some of the programmers at Google looked at their options for writing software and didn\u2019t like what they saw. They needed to manage millions of lines of code that would be constantly storing and shipping data for the world wide web. The code would juggle thousands or maybe millions of connections on networks throughout the globe. The data paths were full of challenges from race cases and concurrency.<\/p> The existing programming languages weren\u2019t much help. They were built for games or managing desktops, or many of the other common tasks from\u00a0a world before the web browser. Their rough edges and failure modes drove coders at Google crazy enough to start asking if there might be a better way. Was there something that could handle the I\/O chores in just a few lines with all of the safety and security that Google needed?<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li><\/ul>[\/et_pb_code][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":" Rust<\/a> has leaped to its highest position ever in the monthly Tiobe index of language popularity<\/a>, scaling to the 13th<\/sup> spot this month, with placement in the top 10 anticipated in an upcoming edition.<\/p> Previously, Rust has never gone higher than 17th<\/sup> place in the Tiobe Programming Index. Tiobe CEO Paul Jansen attributed Rust\u2019s ascent in the\u00a0just-released July index to a February 2024 US White House report recommending Rust over C\/C+, for safety reasons<\/a>. He also credited the growing community and ecosystem support for the language. \u201cRust is finally moving up. After the tailwind of the US government, which recently announced to recommend moving from C\/C++ to Rust for security reasons, things are going fast for Rust,\u201d Jansen said. \u201cThe community is growing, including the number of third-party libraries and tools. In short, Rust is preparing itself for a top 10 position in the Tiobe index.\u201d<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> In a highly-anticipated federal ruling on July 3, US District Court Judge Ada Brown determined that the US Federal Trade Commission (FTC) did not have the authority to issue a nationwide ban of non-compete agreements. Although the judge\u2019s decision was preliminary, employment lawyers watching the case agree that the FTC non-compete move is effectively dead.<\/p> Brown, of the US District Court for the Northern District of Texas, said that she would issue a final ruling on Aug. 30, the day before the FTC ban was slated to take effect. But based on the strong wording of her preliminary decision, there seemed little doubt that she would ultimately block the ban.\u00a0<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> As agents using artificial intelligence have wormed their way into the mainstream for everything from customer service to fixing software code, it\u2019s increasingly important to determine which are the best for a given application, and the criteria to consider when selecting an agent besides its functionality. And that\u2019s where benchmarking comes in.<\/p> However, a new research paper, AI Agents That Matter<\/a>, points out that current agent evaluation and benchmarking processes contain a number of shortcomings that hinder their usefulness in real-world applications. The authors, five Princeton University researchers, note that those shortcomings encourage development of agents that do well in benchmarks, but not in practice, and propose ways to address them.<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> Well, that didn\u2019t take long. After all the \u201cthis time it\u2019s different\u201d comments about artificial intelligence (We see you, John Chambers<\/a>!), enterprises are coming to grips with reality. AI isn\u2019t going to take your job. It\u2019s not going to write your code. It\u2019s not going to write all your marketing copy (not unless you\u2019re prepared to hire back the humans<\/a> to fix it). And, no, it\u2019s nowhere near\u00a0artificial general intelligence<\/a>\u00a0(AGI) and won\u2019t be anytime soon. Possibly never.<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> In 2007, some of the programmers at Google looked at their options for writing software and didn\u2019t like what they saw. They needed to manage millions of lines of code that would be constantly storing and shipping data for the world wide web. The code would juggle thousands or maybe millions of connections on networks throughout the globe. The data paths were full of challenges from race cases and concurrency.<\/p> The existing programming languages weren\u2019t much help. They were built for games or managing desktops, or many of the other common tasks from\u00a0a world before the web browser. Their rough edges and failure modes drove coders at Google crazy enough to start asking if there might be a better way. Was there something that could handle the I\/O chores in just a few lines with all of the safety and security that Google needed?<\/p>Benchmarks don\u2019t reflect real-world applications<\/h2>\n
Benchmarks don\u2019t reflect real-world applications<\/h2>\n