AllyshipContent Radar

News 2943

Chủ đề cộng đồng đang thảo luận

Crawl live-1795144500000 · 10:15 20 thg 11, 2026 · Xuất bản 10:32 20 thg 11, 2026

92 / 2943 chủ đề đạt ngưỡng 55 trong khoảng này.

2

Apple just released Depth Pro 2

56

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

_akhaliq 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Apple just released Depth Pro 2 Sharp and Temporally Consistent Metric Monocular Depth HF: https://huggingface.co/apple/DepthPro2 Media

3

Fly through GPT-6.2 Astra's scenes yourself in the AA-3D Explorer:

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Fly through GPT-6.2 Astra's scenes yourself in the AA-3D Explorer: ➤ Sydney Opera House: https://artificialanalysis.ai/3d/explorer?task=sydney-opera-house&model=gpt-6-2-astra ➤ Mechanical watch: https://artificialanalysis.ai/3d/explorer?task=watch-complications&model=gpt-6-2-astra ➤ Dragon attack: https://artificialanalysis.ai/3d/explorer?task=dragon-over-medieval-town&model=gpt-6-2-astra

4

Or vote in our arenas:

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Or vote in our arenas: ➤ AA-3D Arena: https://artificialanalysis.ai/3d/vote ➤ Video Arena: https://artificialanalysis.ai/video/arena

5

Can language models make better videos than video models?

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Can language models make better videos than video models? LLMs now make motion graphics, edit video as code and drive Blender to build 3D scenes. Can LLMs compete with video generation models? We put GPT-6.2 Astra from @OpenAI, the current #1 on AA-3D, to the test, building the Sydney Opera House, an exploded mechanical watch, and a dragon attacking a medieval town as three.js code. We flew a scripted camera through each scene in a browser: 15 s, 1080p, 24 fps. Dreamina Seedance 2.5 from @ByteDanceSeed_ got the same camera path as a text prompt with reference images of the route, at the same settings. ➤ Top: GPT-6.2 Astra (LLM, AA-3D) ➤ Bottom: Dreamina Seedance 2.5 (video model, AA-Video-T2V) Media

6

Amazon SageMaker Inference: 2026 launches in review, part 2

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Aryaman Kothari 1 bài viết · AWS Machine Learning Blog
Nguyên văn nguồn
Chi tiết nguồn

<p>Once a model is in production, the questions change. Teams want to know which configuration the model should run on now that traffic is real, how to fit more models onto GPUs they already pay for, what to do when the next model is too large for one machine, why requests wait in one Region while GPUs sit idle in another, and why latency rose when nobody changed anything. This post takes those questions in the order teams usually meet them.</p> <p>For HyperPod Inference, it listed additional routing strategies, broader support for model serving frameworks, and expanded multi-Region networking. The Inference Gateway delivers the routing, and managed NVIDIA Dynamo is a new serving framework. For managed endpoints, the roadmap pointed to deeper integration with the rest of the AWS AI landscape. Inference recommendations now run from Amazon SageMaker AI Studio, the SageMaker Python SDK, and the coding agents engineers already use, and endpoints can now route requests across Regions and accounts.</p> <p>To keep each section concrete, we follow one hypothetical team through the blog post. In the spring, they launched a customer support assistant on a 70B-parameter model behind a single SageMaker AI endpoint, using the launches from part 1. By the fall, they need to support more product lines, adopt a larger reasoning model, serve customers in a second Region, and keep their GPU bill flat.</p> <h2 id="the-launches-at-a-glance">The launches at a glance</h2> <div style="width: 810px" class="wp-caption alignnone"> <a href="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/11/19/ML-22497-1.png" target="_blank" rel="noopener"><img src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/11/19/ML-22497-1.png" alt="Five inference stages in this post and the launches grouped under each" width="800"></a> <p class="wp-caption-text">Figure 1: The five stages in this post and the launches in each</p> </div> <h2 id="choose-the-right-configuration-from-wherever-you-work">Choose the right configuration from wherever you work</h2> <p>The team picked its first configuration from a benchmark run in April. Since then, they have added four LoRA (Low-Rank Adaptation) adapters, one for each product line, and the product team has set a target of 500 milliseconds for time to first token (TTFT) at peak load. The April configuration was never tested against either change. The engineers who will re-run the analysis work in notebooks and coding agents, and few of them use the console.</p> <p>Inference recommendations launched in April as an API. Four updates since then make it available in more of the places teams work, and let it answer two harder questions: how many adapters an endpoint can carry, and how much concurrency it can take before it misses a latency target. A new agent skill brings the same expertise into coding agents.</p> <h3 id="inference-recommendations-in-sagemaker-ai-studio-july-2026">Inference recommendations in SageMaker AI Studio (July 2026)</h3> <p><em>Blog:</em> <a href="https://aws.amazon.com/blogs/machine-learning/launching-ui-for-generative-ai-inference-recommendations-in-amazon-sagemaker-ai/" target="_blank" rel="noopener">Launching UI for generative AI inference recommendations in Amazon SageMaker AI</a></p> <p>The April launch automated instance, container, and optimization selection through APIs. Inference recommendations are now also available in SageMaker AI Studio as a guided, low-code workflow. In Studio, choose <strong>Jobs</strong>, then <strong>Inference optimization</strong>. Choose a use-case profile (Interact, Generate, Summarize, or Custom), an optimization goal (minimize latency, maximize throughput, or minimize cost), and a model from SageMaker JumpStart, Amazon Simple Storage Service (Amazon S3), the Model Registry, or an existing SageMaker model.</p> <p>SageMaker AI benchmarks candidate configurations on real GPU infrastructure using NVIDIA AIPerf and applies techniques that match the goal, such as speculative decoding for throughput or kernel tuning for latency. You compare the ranked results by TTFT, inter-token latency, throughput, and cost, and then deploy the chosen configuration to a real-time endpoint from Studio.</p> <h3 id="inference-recommendations-in-the-sagemaker-python-sdk-v3-august-2026">Inference recommendations in the SageMaker Python SDK v3 (August 2026)</h3> <p><em>Blog: <a href="https://aws.amazon.com/blogs/machine-learning/llm-optimization-integration-for-amazon-sagemaker-python-sdk/" target="_blank" rel="noopener">LLM optimization integration for Amazon SageMaker Python SDK</a></em></p> <p>Benchmarking and recommendations previously required SageMaker AI Studio or direct Boto3 calls. They are now part of the SageMaker Python SDK v3 (version 3.17.0 and later), the same interface teams use for training and deployment, so the workflow fits into notebooks, CI pipelines, and MLOps workflows. You can benchmark a live endpoint against your workload traffic, generate ranked recommendations for a latency, throughput, or cost goal, and deploy the top-ranked configuration to a real-time endpoint in a single call.</p> <p>The SDK also supports longer workflows. You can run recommendation jobs in parallel to compare serving frameworks such as LMI and vLLM, and you can resume from a completed job so that deployment happens in a different notebook or pipeline stage without re-running the benchmarks.</p> <h3 id="lora-adapter-support-in-inference-recommendations-september-2026">LoRA adapter support in inference recommendations (September 2026)</h3> <p><em>Developer guide</em>: <a href="https://docs.aws.amazon.com/sagemaker/latest/dg/generative-ai-inference-recommendations-adapters.html" target="_blank" rel="noopener">Get recommendations for models with LoRA adapters</a></p> <p>Many teams use LoRA adapters to specialize one foundation model for several use cases. Each adapter kept in GPU memory reduces the nu

7

Use Kimi Code CLI with models on Amazon Bedrock

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Alex Thewsey 1 bài viết · AWS Machine Learning Blog
Nguyên văn nguồn
Chi tiết nguồn

<p><a href="https://github.com/moonshotai/kimi-code" target="_blank" rel="noopener">Kimi Code CLI</a> is an open source coding agent from Moonshot AI, the creator of the Kimi series of open-weight foundation models. Previously, using Kimi Code with models on <a href="https://aws.amazon.com/bedrock/" target="_blank" rel="noopener">Amazon Bedrock</a> meant configuring a generic connection “provider” with an Amazon Bedrock API key. For many AWS customers, this meant introducing an extra credential to obtain and protect.</p> <p>With v2.7.0, Moonshot AI adds a native bedrock provider to the CLI. You can now configure the agent to use your standard AWS credential chain, including named profiles and single sign-on (SSO), instead of creating and managing a separate API key.</p> <p>In this post, we show you how to connect Kimi Code CLI to models on Amazon Bedrock using your existing AWS credentials. We use <a href="https://aws.amazon.com/blogs/machine-learning/introducing-kimi-k3-1-pro-on-amazon-bedrock/" target="_blank" rel="noopener">Kimi K3.1 Pro Highspeed</a> as an example, which supports streaming, configurable reasoning, image input, and client-side tool calling.</p> <h2 id="whats-new">What’s new</h2> <p>Amazon Bedrock provides pay-per-token inference for a range of open and proprietary models from leading providers, available through <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/apis.html" target="_blank" rel="noopener">standard APIs</a>. Processing stays within the AWS data boundary, as detailed in the <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/data-protection.html" target="_blank" rel="noopener">Data protection</a> section of the User Guide. The <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/model-cards.html" target="_blank" rel="noopener">model cards</a> detail which APIs and features are supported for each model.</p> <p>In older versions of the Kimi Code CLI, you could connect to Amazon Bedrock through a provider with <code>type = "openai"</code> or <code>type = "openai_responses"</code>. These use the OpenAI-compatible <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/inference-chat-completions.html" target="_blank" rel="noopener">Chat Completions</a> or <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/inference-responses-api.html" target="_blank" rel="noopener">Responses</a> APIs, respectively. This approach required you to set the regional <code>base_url</code> and provide an <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/api-keys.html" target="_blank" rel="noopener">Amazon Bedrock API key</a>. The key could be short-term or long-term, but it was a separate credential for you to obtain and manage.</p> <p>The native provider changes that setup:</p> <ul> <li><strong>Use your existing AWS authentication workflow.</strong> The <code>bedrock</code> provider can resolve temporary credentials through the standard <a href="https://aws.amazon.com/cli/" target="_blank" rel="noopener">AWS Command Line Interface (AWS CLI)</a> credential chain. You can use the default chain or select a named profile, including a profile backed by SSO.</li> <li><strong>Override the protocol for each model, if needed.</strong> The provider infers an API format and regional endpoint from the model ID, but you can change them as detailed in the “Override endpoint URL and protocol” section of this post.</li> </ul> <p>AWS recommends short-term credentials over long-term credentials. This new path reduces reliance on manually managed API keys, but it doesn’t change your responsibility to protect AWS credentials and scope permissions appropriately.</p> <h2 id="how-it-works">How it works</h2> <p>The native provider handles authentication and request routing in four steps:</p> <ol type="1"> <li><strong>Resolve AWS credentials.</strong> Unless you configure an Amazon Bedrock API key, the bedrock provider uses the standard AWS credential chain in your environment. You can set <code>AWS_PROFILE</code> to select a specific <a href="https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html#cli-configure-files-using-profiles" target="_blank" rel="noopener">named profile</a>.</li> <li><strong>Generate a short-lived bearer token.</strong> The provider uses <a href="https://www.npmjs.com/package/@aws/bedrock-token-generator" target="_blank" rel="noopener"><span class="citation" data-cites="aws/bedrock-token-generator">@aws/bedrock-token-generator</span></a> to create a short-term Amazon Bedrock API key, and renews it when necessary. You don’t need to place any AWS access key or manually generated Amazon Bedrock key in the Kimi Code <code>config.toml</code>. However, an explicit key given through <code>api_key</code> or <code>api_key_env</code> takes precedence if you provide it.</li> <li><strong>Build the regional endpoint.</strong> The provider resolves <code>AWS_REGION</code> or <code>AWS_DEFAULT_REGION</code> and constructs the appropriate <code>bedrock-runtime</code> endpoint for the model’s inferred API. For Kimi models, this resolves to the recommended OpenAI-compatible Chat Completions path.</li> <li><strong>Call the selected inference profile.</strong> The model alias maps to an Amazon Bedrock model or <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/inference-profiles.html" target="_blank" rel="noopener">inference profile</a> ID. This example uses the global inference profile <code>global.moonshotai.kimi-k3.1</code>. The <code>global.</code> prefix selects the profile, while <code>AWS_REGION</code> determines the regional endpoint that receives your request.</li> </ol> <p>The CLI then streams the model response and can use the model’s client-side tool-calling support during coding tasks. Authentication, authorization, model access, and network connectivity must all succeed for a request to complete. The ephemeral API keys generated by the provider are valid for up to 12 hours or your AWS session length, w

8

See the diarization results on our speech to text leaderboard: https://artificialanalysis.ai/speech-to-text/non-streaming#diarization

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

See the diarization results on our speech to text leaderboard: https://artificialanalysis.ai/speech-to-text/non-streaming#diarization Methodology: https://artificialanalysis.ai/methodology/speech-to-text#diarization-evaluation

10

v0.40.17

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

github-actions[bot] 1 bài viết · ollama/ollama releases
Nguyên văn nguồn
Chi tiết nguồn

<h2>What's Changed</h2> <ul> <li>Improve ChatGPT CLI restore and graceful restart by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/hoyyeva/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/hoyyeva">@hoyyeva</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6251854019" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/19583" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/19583/hovercard" href="https://github.com/ollama/ollama/pull/19583">#19583</a></li> <li>cmd/launch: use thinking metadata for OpenCode settings by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/hoyyeva/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/hoyyeva">@hoyyeva</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6122368894" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/19409" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/19409/hovercard" href="https://github.com/ollama/ollama/pull/19409">#19409</a></li> <li>llm: use mmap for Vulkan integrated GPUs by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/dhiltgen/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/dhiltgen">@dhiltgen</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6309814784" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/19640" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/19640/hovercard" href="https://github.com/ollama/ollama/pull/19640">#19640</a></li> <li>rpreslar4765/Ollama by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/rpreslar4765/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/rpreslar4765">@rpreslar4765</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4877598143" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/17163" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/17163/hovercard" href="https://github.com/ollama/ollama/pull/17163">#17163</a></li> <li>mlx: support concurrent generation by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/dhiltgen/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/dhiltgen">@dhiltgen</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5970886020" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/19197" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/19197/hovercard" href="https://github.com/ollama/ollama/pull/19197">#19197</a></li> <li>llama.cpp: version bump b12257 by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/dhiltgen/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/dhiltgen">@dhiltgen</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6315369343" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/19646" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/19646/hovercard" href="https://github.com/ollama/ollama/pull/19646">#19646</a></li> <li>MLX, MLX-C: version bump by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/dhiltgen/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/dhiltgen">@dhiltgen</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6316056226" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/19647" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/19647/hovercard" href="https://github.com/ollama/ollama/pull/19647">#19647</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/rpreslar4765/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/rpreslar4765">@rpreslar4765</a> made their first contribution in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4877598143" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/17163" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/17163/hovercard" href="https://github.com/ollama/ollama/pull/17163">#17163</a></li> </ul> <p><strong>Full Changelog</strong>: <a class="commit-link" href="https://github.com/ollama/ollama/compare/v0.40.16...v0.40.17-rc0"><tt>v0.40.16...v0.40.17-rc0</tt></a></p>

  • v0.40.17 ollama/ollama releases · 20 thg 11, 2026
12

we're celebrating this fundraise with a ton of product launches next week, and then a webinar on friday to wrap it all up

64

2 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

hwchase17, langchain 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

we're celebrating this fundraise with a ton of product launches next week, and then a webinar on friday to wrap it all up come join us! https://events.langchain.com/webinar/future-of-agents/#Registration

13

Scaling Linear’s GTM to $100M ARR — Cristina Cordova, COO

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Basil Chatha 1 bài viết · Latent Space
Nguyên văn nguồn
Chi tiết nguồn

Open video on YouTube ↗ Linear was founded to build a better issue tracker. Seven years and $134 million in funding later, its CEO Karri Saarinen published a post titled "Issue tracking is dead." In this episode, we chat with Cristina Cordova , COO of Linear , about how the company navigated that and how its go-to-market changed along the way. Cristina spent seven and a half years at Stripe, led platform and partnerships at Notion, and was a partner at First Round before joining Linear in 2023. Linear's founders built it after living with legacy issue trackers at Coinbase, Airbnb and Uber, and it spread self-serve through startups like Vercel and Ramp. When she joined, Linear had about 40 people and one salesperson. Since then it has shipped an MCP server, a platform for building agents into Linear, integrations with Codex, Cursor and GitHub Copilot, and its own Linear Agent. Agents created 3% of Linear's work a year ago. Now it's more than half. Linear passed $100 million in ARR this year with more than 40,000 paying customers and 177% net revenue retention, and in August employees sold $99 million in stock at a $2.5 billion valuation . We talk about why she stopped chasing enterprise deals three weeks after joining, why Linear has never hired a single SDR, why it won't let an LLM answer support tickets on its own, and what the AI budgets behind $100M-in-months ARR mean for everyone else. Half the work on Linear is now created by agents Linear shipped its MCP server in May 2025, and Cristina says it was basically the first in its category. A year and a half later, more than half the issues created in Linear come from agents. That doesn't mean Linear wants to be a database with an MCP server on top. Cristina thinks SaaS companies settling for that are making a big mistake. If the agent workflows inside your product aren't better than the ones outside it, nobody has a reason to open your app. So she watches two lines: agent usage and app usage. If agent usage climbs and app usage doesn't, you're becoming a commodity. At Linear, both are up and to the right, because people still come back to the app to see and coordinate the work. Jump to the MCP discussion → "Issue tracking is dead" When Karri published "Issue tracking is dead" in March, most of Linear's customers agreed with him. Then they asked the obvious question: so what am I buying? Linear's answer is a product development system built around agent orchestration, where humans stop doing the manual work of filing, labeling, assigning and closing issues. Customers had been pushing it there. Most of the frontier AI labs run on Linear and wanted it to move faster. Pre-AI companies like Ramp and Coinbase were building their own internal agents and needed an API to plug them into Linear. Cristina says Linear is lucky it's small enough to cannibalize itself. Google has a much harder problem: put an AI answer above every search result, and fewer people look at the ads. Jump to the "issue tracking is dead" discussion → The AI budget behind $100M in months The thing speeding up purchases right now, Cristina says, is AI budget. Companies carved out money for AI tools that didn't exist before, and any product that fits inside it skips the usual fight for spend. At some companies that budget is very high. It's already starting to change. Buyers are signing one-year deals and paid pilots, not three-year contracts, because nobody knows what they'll want in two years. And some overnight-$100M stories are a handful of $30 to $40 million contracts with defense companies or giant law firms. That's a very different business from Linear's 40,000 paying customers on what was, until June, entirely seat-based pricing. When those one-year deals come up for renewal, we'll find out whose ARR was real. Jump to the AI budget discussion → Linear threw out its 2025 enterprise roadmap Three weeks after joining in 2023, Cristina crossed "move upmarket to enterprise" off Linear's company goals. It had one salesperson. She went after growth-stage companies that would have to rip out an existing tool instead, the same way Stripe won new businesses long before it won switchers. Linear finally declared an enterprise push in 2025, with a roadmap full of features for large organizations. Then agents happened. Linear built an MCP server, an agents platform with a whole new set of APIs, and integrations with Codex, Cursor and GitHub Copilot. None of it was planned, and a lot of the enterprise work never got done. Cristina chose to race ahead anyway. Competitors waited, and enterprises started putting Linear on their shortlists. Jump to the enterprise roadmap discussion → No SDRs, no forward deployed engineers Linear has never hired a single SDR. Cristina thinks the qualification call wastes the customer's time: they want a demo, not questions about their budget. AEs do their own outbound, with tooling to keep it personal. It doesn't do forward deployed engineering either. Linear should be easy enough to adopt that nobody needs access to your systems. Solutions engineers sell alongside enterprise AEs instead, sometimes building a working ServiceNow integration overnight to show a prospect it can be done. Cristina adds that an opinionated tool gives agents cleaner data than one where every team defines "bug" differently. Support stays in-house, and Linear won't let an LLM answer tickets on its own. AI drafts replies and a human decides what goes out. Customers sometimes assume the replies are AI because they arrive so fast. In three and a half years, Cristina has never had an escalation over a bad support experience. Jump to the sales team discussion → Everyone wants outcome-based pricing Cristina would love a model like Intercom's Fin, which charges for each support conversation its AI resolves. It's harder for Linear. What is auto-triaging a bug to the right team worth when one company thinks that's the PM's job and another doesn't? Until someone cracks that, Linear charges

14

Full results:

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Full results: https://artificialanalysis.ai/speech-to-text/streaming Methodology: https://artificialanalysis.ai/methodology/speech-to-text

15

Show HN: erXos – a microkernel OS in Erlang based on Genera/Plan 9/QNX ideas

61

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 7 tương tác đã đo · Nguồn crawl

stass 1 bài viết · HN: GPT
Nguyên văn nguồn
Chi tiết nguồn

What if every Erlang process were an operating-system process? With as much system code and drivers written in Erlang itself. This is something I was pondering for a while, and finally was able to prototype thanks to AI coding agents. erXos is a capability-based microkernel OS in Erlang: drivers, filesystems, and the network stack are all supervised Erlang processes, same as any app. The kernel itself is Fiasco, in C++, slightly modified for erXos needs. This is an OS I wanted for a long time: an Erlang machine where every BEAM process is a process visible to the OS and scheduler, not something bolted on top. You can try it right now with nothing to install: there is an emulator on the website that boots the whole OS in the browser ARM64 emulator. At the rc prompt, try `ps`, `top`, `ping` or `erl` and write any kind of erlang code. There's a Pi 4 SD image and a QEMU image too. The goal is to build an ultra-reliable microkernel OS with hot code loading and both system and BEAM-based isolation. The latter is one thing that would allow you to run millions of processes on the system, something that would be prohibitive on a microkernel alone due to the context switch overhead. Capabilities keep every component least-privileged, supervision keeps the machine running when drivers or subsystems crash, and hot code loading would let you fix a broken driver without reboot. The secondary goal is to keep as much of a UNIX face as possible. Too many novel OSes change things for no particular reason that makes them hard to use. erXos tries to preserve as many existing UNIX/FreeBSD concepts as much as possible to remove the learning curve. What works today: - Boots in the browser/v64, in QEMU, and on a Raspberry Pi 4 from an SD card - A real shell (plan9 rc) with job control, pipes, `ps`, `grep`. It feels like UNIX on the surface - Erlang versions of basic UNIX apps. - Drivers written in Erlang: UART, virtio, SD card, Ethernet (GENET), display - A pure Erlang EROFS filesystem for root images - A TCP/IP stack in Erlang based on FreeBSD network stack and verified for correctness against it - Domains: every app runs as its own address space or Erlang node, isolated from others - Plan 9 namespaces and 9P everywhere; windows are files like RIO and 9P is a file protocol between OS servers - Supervision end to end: if a driver fails, its supervisor resets the device and restarts it I also have 2 demo apps built on app sdk: a full-screen kiosk app with live crypto quotes and clock and, of course Doom, which ships on the Pi 4 card image (type `doom`). What's coming: - Raspberry Pi 5 support - Full display on the Pi - WIFI - Bluetooth - POSIX-lite for C programs, so existing code can run as a domain - Performance, debugging and tracing features. The code is all available under the BSD license. Would love to hear all and any feedback!

19

We’re also working on a new mobile experience for ChatGPT!

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

thsottiaux 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

We’re also working on a new mobile experience for ChatGPT! It’s easier to get to your favorite features and discover what you can do in ChatGPT. We’re starting with Pro users who have a dot or are eligible to create one. Your dot gets its own tab, and you can pin Codex, Projects, Images, and more to the tab bar. Some of you will see the new experience by default. You can turn it on or off anytime in Settings > New ChatGPT Design. Super excited to hear your feedback before we roll it out more widely! Media

20

b12556

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

github-actions[bot] 1 bài viết · ggml-org/llama.cpp releases
Nguyên văn nguồn
Chi tiết nguồn

<details open=""> <p>model : hrm : do not compute slot count as uint32_t (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6488146246" data-permission-text="Title is private" data-url="https://github.com/ggml-org/llama.cpp/issues/32601" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/32601/hovercard" href="https://github.com/ggml-org/llama.cpp/pull/32601">#32601</a>)</p> <p>load_arch_hparams multiplies n_hrm_layers_per_stack, n_hrm_h_cycles and<br> (n_hrm_l_cycles + 1) into a uint32_t, then asserts the product equals<br> block_count.</p> <p>Any factors whose true product is block_count + k*2^32 still pass the<br> assert; 1073741825 * 2 * 2 = 2^32 + 4 compares equal to block_count = 4.</p> <p>load_arch_tensors iterates the same three values in int and writes past<br> the end of the block_count-sized layers vector.</p> </details> <p><strong>Website:</strong></p> <ul> <li><a href="https://llama.app" rel="nofollow">https://llama.app</a></li> </ul> <p><strong>Attestations:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/attestations/69899989">https://github.com/ggml-org/llama.cpp/attestations/69899989</a></li> </ul> <p><strong>macOS/iOS:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-macos-arm64.tar.gz">macOS Apple Silicon (arm64)</a></li> <li>macOS Apple Silicon (arm64, KleidiAI enabled) <a href="https://github.com/ggml-org/llama.cpp/pull/23780" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/23780/hovercard">DISABLED</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-macos-x64.tar.gz">macOS Intel (x64)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-xcframework.zip">iOS XCFramework</a></li> </ul> <p><strong>Linux:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-x64.tar.gz">Ubuntu x64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-arm64.tar.gz">Ubuntu arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-s390x.tar.gz">Ubuntu 24.04 s390x (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-26.04-s390x.tar.gz">Ubuntu 26.04 s390x (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-zdnn-s390x.tar.gz">Ubuntu 26.04 s390x (zDNN)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-vulkan-x64.tar.gz">Ubuntu x64 (Vulkan)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-vulkan-arm64.tar.gz">Ubuntu arm64 (Vulkan)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-cuda-12.8-x64.tar.gz">Ubuntu x64 (CUDA 12)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/cudart-llama-b12556-bin-ubuntu-cuda-12.8-x64.tar.gz">CUDA 12.8 libraries</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-cuda-13.5-x64.tar.gz">Ubuntu x64 (CUDA 13)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/cudart-llama-b12556-bin-ubuntu-cuda-13.5-x64.tar.gz">CUDA 13.5 libraries</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-cuda-13.5-arm64.tar.gz">Ubuntu arm64 (CUDA 13)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/cudart-llama-b12556-bin-ubuntu-cuda-13.5-arm64.tar.gz">CUDA 13.5 libraries</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-rocm-10.0-x64.tar.gz">Ubuntu x64 (ROCm 10.0)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-openvino-2026.4.1-x64.tar.gz">Ubuntu x64 (OpenVINO)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-sycl-fp32-x64.tar.gz">Ubuntu x64 (SYCL FP32)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-ubuntu-sycl-fp16-x64.tar.gz">Ubuntu x64 (SYCL FP16)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-linux-arm64-snapdragon.tar.gz">Linux arm64 (Snapdragon: CPU, Adreno GPU, Hexagon NPU)</a> - <a href="https://github.com/ggml-org/llama.cpp/blob/master/docs/backend/snapdragon/linux.md">setup guide</a></li> </ul> <p><strong>Android:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-android-arm64.tar.gz">Android arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-android-arm64-snapdragon.tar.gz">Android arm64 (Snapdragon: CPU, Adreno GPU, Hexagon NPU)</a> - <a href="https://github.com/ggml-org/llama.cpp/blob/master/docs/backend/snapdragon/README.md">setup guide</a></li> </ul> <p><strong>Windows:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-win-cpu-x64.zip">Windows x64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-win-cpu-arm64.zip">Windows arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-win-opencl-adreno-arm64.zip">Windows arm64 (OpenCL Adreno)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12556/llama-b12556-bin-win-cuda-12.4-x64.zip">Windows x64 (CUDA 12)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b

  • b12556 ggml-org/llama.cpp releases · 20 thg 11, 2026
1–20 / 92
Trang 1 / 5