ads
Thursday, February 29, 2024
Show HN: Marimo – open-source reactive Python notebook – running in WASM https://ift.tt/uWHsqOg
Show HN: Marimo – open-source reactive Python notebook – running in WASM Hi HN! Last month, we shared marimo [1][2], an open-source reactive notebook for Python. For those who missed it, marimo notebooks are reproducible, stored as Python files, executable as Python scripts, and deployable as web apps. It’s now possible to run marimo notebooks entirely in the browser via WebAssembly (WASM). - A marimo tutorial as a WASM notebook: https://ift.tt/lqfC8iR - Training a neural network with Karpathy’s micrograd: https://ift.tt/xFDJ4d0 - Visualizing attractors, as a read-only app: https://ift.tt/5XSCyk6 - A blank notebook: https://marimo.new - Docs: https://ift.tt/3bT2LDY WASM notebooks let you experiment with code without having to install Python on your machine. These notebooks can be easily shared — marimo includes a button that generates a marimo.app URL (code encoded as a query parameter), and marimo.app has a built-in permalink generator. We also support embedding via iframes: you can use this to (say) author interactive documentation or standalone interactive blog posts. We now in fact use embedded WASM notebooks throughout our API docs. Our WASM notebook is powered by Pyodide [3], a WASM-based Python distribution. Pyodide can run any Python package that has a pure Python wheel, as well as many popular libraries for scientific computing and machine learning, including Pandas, NumPy, SciPy, and scikit-learn. Over time, we expect more and more libraries to be packaged for Pyodide. We’re very excited by the potential of WASM notebooks to make computing more accessible, and we’re in awe of all that the WASM and Pyodide contributors have accomplished. We have lots more planned (one example: we plan to make it easy to work with local files), and hope to share new developments with you in the future. In the meantime, please try https://marimo.app out. We’d appreciate feedback! P.S. Our support for WASM is very new; you may encounter sharp edges. Still, since WASM-compatibility was one of the most requested features from our previous HN, we felt it was worth sharing. [1] https://ift.tt/Bru6fcm [2] https://ift.tt/NcMFAnT [3] https://ift.tt/K7xT8CP https://ift.tt/lqfC8iR March 1, 2024 at 01:12AM
Show HN: PyAirbyte – We built a lightweight Python library for ELT https://ift.tt/J1Vxu4E
Show HN: PyAirbyte – We built a lightweight Python library for ELT https://ift.tt/EQLSUWj March 1, 2024 at 12:51AM
Show HN: We Built the Fastest Spreadsheet https://ift.tt/fKsVpcN
Show HN: We Built the Fastest Spreadsheet https://rowzero.io February 29, 2024 at 10:57PM
Wednesday, February 28, 2024
Show HN: Unicode Separated Values (USV) Rust Crate https://ift.tt/7X4jrMC
Show HN: Unicode Separated Values (USV) Rust Crate https://ift.tt/Cz65iGc February 29, 2024 at 12:43AM
Show HN: Fractional GPUs for AI https://ift.tt/PTlpwsQ
Show HN: Fractional GPUs for AI https://ift.tt/CkR0Byu February 29, 2024 at 12:20AM
Show HN: Noop Workshop, Develop with Local/Cloud Parity https://ift.tt/cDHaVQM
Show HN: Noop Workshop, Develop with Local/Cloud Parity Hello HN, Milin @Noop.dev[1] here! We're very excited to share Noop Workshop with you! For the past several months we have been preparing to launch the Noop Developer Platform. The platform handles all aspects of running and operating your software. Until a few months ago, our focus was on hosting and running software in the Cloud. But we realized there's a growing need for local development tools that can help make the transition from local development to cloud hosting easier. And so, Workshop was born. We felt existing tools were either too specialized or too disconnected from the specific constraints and complexities of cloud hosting. Noop Workshop aims to solve this problem by defining an Application in one unified format that works in both local and cloud environments. It’s possible to use Noop Workshop even if Noop Cloud is not your target deployment. The Noop Application config, called a Blueprint, will be familiar to developers that have experience using popular container orchestration tools. However, Blueprints are a higher-level abstraction, and more Application concepts can be defined with less code. Once you're up and running, Noop provides a suite of tools for analyzing logs, interacting with running containers, routing traffic (all HTTPS) and automatically detecting code changes. In addition to technical advantages, our license has no commercial use restrictions — we intend to keep it that way. We want to eliminate the operational overhead of software. Workshop along with Cloud is the foundation on which we plan to achieve that goal. Our Cloud platform is available by invitation. If you’d like to join the waitlist, download our Desktop app [2] and select the Cloud button on the app home screen to register. 1. https://noop.dev 2. https://ift.tt/ecTsBb7 https://ift.tt/JyQW0P1 February 28, 2024 at 10:50PM
Tuesday, February 27, 2024
Show HN: Velvet – Data platform with an AI SQL editor https://ift.tt/GrsaDph
Show HN: Velvet – Data platform with an AI SQL editor Hi HN — Chris here, Velvet co-founder. I’m excited to share what we’ve been working on, a platform to unify disparate data sources into a single queryable interface. We built Velvet to solve our own problem. We’re a small team and wanted to combine the data from various services (Stripe, Supabase, etc.) into a layer that would help us make product decisions and ship new features faster. On the surface, it may look like a simple text-to-SQL data notebook. But under the hood, it’s an accessible and interoperable backend-as-a-service that your entire product team can utilize. Connect to your databases, sync third-party APIs, capture webhook events — then write data directly, spinning up queues and analytics databases on the fly. The magic of our tool is in unifying data sources into a native SQL layer. We leverage ClickHouse to enable you to write joins across datasets you’ve never been able to pair together before (without significant effort). We layer on an iterative SQL query interface to help you write and refine queries with the assistance of AI. Our product works great for individual contributors and solo devs, but we’ve also built in collaboration features so data access doesn’t get siloed. Your saved queries can be turned into API endpoints and used directly in feature development. This makes the workflow of shipping new features really fast! Ping me if you want to early access to this feature. Watch our video demo ( https://youtu.be/CW5TXMCyfC0 ) and try the live demo in our app. Feel free to email me directly (chris@usevelvet.com) with questions and feedback. Thanks for checking out Velvet! https://ift.tt/vaLXiVN February 28, 2024 at 01:11AM
Show HN: Leaping – Open-source debugging with LLMs https://ift.tt/W8hVQvN
Show HN: Leaping – Open-source debugging with LLMs Show HN: Leaping - Open-source debugging with LLMs Hi HN! We’re Adrien and Kanav. We met at our previous job, where we spent about a third of our life combating a constant firehose of bugs. In the hope of reducing this pain for others in the future, we’re working on automating debugging. We started by capturing information from running applications to then ‘replay’ relevant sessions later. Our approach for Python involved extensive monkey patching: we’d use OpenTelemetry-style instrumentation to hook into the request/response lifecycle, and capture anything non-deterministic (random, time, database/third-party API calls, etc.). We would then run your code again, mocking out the non-determinism with the captured values from production, which would let you fix production bugs with the local debugger experience. You might recognize this as a variant of omniscient debugging. We think it was a nifty idea, but we couldn’t get past the performance overhead/security concerns. Approaching the problem differently, we thought - could we not just grab a stack trace and sort of “figure it out” from there? Whether that’s possible in the general case is up for debate – but we think that eventually, yes. The argument goes as follows: developers can solve bugs not because they are particularly clever or experienced (though it helps), but rather because they are willing to spend enough time coming up with increasingly informed hypotheses (“was the variable set incorrectly inside of this function?”) that they can test out in tight feedback loops (“let me print out the variable before and after the function call”). We wondered: with the proper context and guidance, why couldn’t an LLM do the same? Over the last few weeks, we’ve been working on an approach that emulates the failing test approach to debugging, where you first reproduce the error in a failing test, then fix the source code, and finally run the test again to make sure it passes. Concretely, we take a stack trace, and start by simply re-running the function that failed. We then report the result back to the LLM, add relevant source code to the context window (with Tree-sitter and LSP), and prompt the AI for a code change that will get us closer to reproducing the bug. We apply those changes, re-run the script, and keep looping until we get the same bug as the original stack trace. Then the LLM formulates a root cause, generates a fix, we run the code again - and if the bug goes away, we call it a day. We’re also looking into letting the LLM interact with a pdb shell, as well as implementing RAG for better context fetching. One thing that excites us about generating a functioning test case with a step-by-step explanation for the fix is that results are somewhat grounded in reality, making hallucinations/confabulations less likely. Here’s a 50 second demo of how this approach fares on a (perhaps contrived) error: https://ift.tt/YTPMnJf We’re working on releasing a self-hosted Python version in the next few weeks on our GitHub repo: https://ift.tt/3fVYQPp (right now it’s just the demo source code). This is just the first step towards a larger goal, so we’d love to hear any and all feedback/questions, or feel free to shoot me an email at adrien@leaping.io! February 28, 2024 at 01:59AM
Show HN: Scribbler - An open source notebook tool for JavaScript https://ift.tt/3XRaLfG
Show HN: Scribbler - An open source notebook tool for JavaScript Scribbler is a tool to do experimentation in JavaScript using a notebook kind of environment. It runs in the browser without the need for a backend. It is deal for learning and experimentation in JavaScript. USP of Scribbler are: no login, no node/npm, can load ES 6 modules. Check the website at: https://scribbler.live . The web-app is available at: https://ift.tt/D2AIg9r . Scribbler has been built to satisfy a need for doing experimentation. Jupyter Notebook is very popular amongst python developers and data scientists for experimentation. It gives a simple interface for experimenting in python for testing code or for experimental analysis. Jupyter Notebook provides this application by running what is known as a “kernel” in the backend and giving back the results to the ui for display. It is an open source and free to use tool. Thus it has become extremely popular. As it is in Python, it requires installation of python environment and the libraries to use the tool. There are fully hosted alternatives like Google Colabs, where one can experiment in Python without installing anything. There is no similar open source tools for Javascript. There are online tools like jsfiddle/codepen etc but none that can be downloaded and used as a free tool or embedded on other solutions. Pure Javascript and JS libraries can ideally run without the need for a backend code like node.js or Python. Javascript is built to run by default in the browser. Optimization of the browser tech by Chromium (i.e. V8) and Firefox has ensured Javascript in the browser is fast and efficient. Thus we can build a good notebook tool using just front end technologies. I’ve been looking for such a solution for quite sometime mainly to test out some of the open source JS libraries and also for building some new open source projects. As I couldn’t find any solution I have built a simple tool to run javascript in notebooks. I call it Scribbler (so much for creativity). It is available as an open source solutions — free to use and modify. The source code is available at: https://ift.tt/dKXxjph It does not require any backend technology. Users can download and use it in the file system or host it in webserver to use it on the internet. I have used Github Pages to host it. As it does not require backend, I need not buy/host a server to do that (ain’t it beautiful?). JavaScript can be used for a variety of experimentation. I’ve learnt a lot about Dynamic systems while using Scribbler to do simulations. It has also helped me in understanding some concepts of decentralized finance. I’ve also used Scribbler to solve some equations using numeric methods. Given the dynamic nature of JavaScript and its close integration with the UI, one can use it for building charting/dahsboarding tools. Scribbler can infact be even used for data science and machine learning. JavaScript has a vibrant community with a wide range of libraries available. Thus the usecases of Scribbler are limitless. I hope as more people start using Scribbler, there will be more and more applications including interactuve data science, Generative AI, scientific simulations, financial/economic applications, decentralized computing etc. Happy experimenting!! https://ift.tt/D2AIg9r February 27, 2024 at 11:47PM
Show HN: Nuke – A memory arena implementation for Go https://ift.tt/zfd3eGx
Show HN: Nuke – A memory arena implementation for Go https://ift.tt/6ikLszW February 28, 2024 at 12:31AM
Monday, February 26, 2024
Show HN: Teraace: Product Analytics Beyond Numbers https://ift.tt/7vFR9Ux
Show HN: Teraace: Product Analytics Beyond Numbers Profitable growth relies on understanding user behavior. Discover the why, not just the what. Traditional analytics skim the surface, falling short of capturing the narrative 'why'. Event tracking quickly becomes cumbersome and hard to keep up with. Whether your growth is sales or product-led (PLG), use Teraace to accelerate activations, optimize onboarding, or target training. Teraace harnesses machine learning to transform user behavior into a clear visualization of the actual buyer's journey. Crucial insights even at low user volumes. Private and secure data ingestion methods include an easy one-line script for automatic interaction capture, integration with Segment for streamlined data flow, or send your own direct batches from Mobile, App, or Web through our secure API. Uncover hidden patterns in user behavior. By joining our free beta, you gain early access to tools that will evolve to predict and influence user journeys, with a commitment to maintaining fair and predictable usage-based pricing. https://www.teraace.com February 27, 2024 at 01:16AM
Show HN: Sqlbind a Python library to compose raw SQL https://ift.tt/QAm1DW7
Show HN: Sqlbind a Python library to compose raw SQL https://ift.tt/5hQvyjF February 27, 2024 at 12:22AM
Sunday, February 25, 2024
Show HN: Continuous-eval – Granular evaluation of GenAI pipelines https://ift.tt/HSduPVA
Show HN: Continuous-eval – Granular evaluation of GenAI pipelines Hi HN - we are the creators of “continuous-eval”, an open-source tool to test and evaluate generative AI apps. "Continuous-eval" came from our efforts to measure, validate and improve the reliability of a finance AI copilot we were developing for banks. End-to-end evaluation was not enough for us. We wanted to have granular evaluations that help pinpoint the bottlenecks and identify what / how to improve. We’ve since developed more metrics and made the framework more flexible so it can evaluate components like agent tool use, code change, retrieval steps, etc. Let us know what you think of our approach to GenAI App evaluation. https://ift.tt/mnDjhep February 26, 2024 at 01:41AM
Subscribe to:
Posts (Atom)