0xthierry

How I got Computer Use and Browser Use running with Codex in E2B

I wanted my background coding agent to use the app it was building. Open Chromium, inspect the page, click through a flow, and see whether it actually works.

I got it running with codex app-server, OpenAI’s first-party computer/browser runtimes, and a Linux desktop inside E2B.

Here’s how I put it together, including the auth issues that took me a while to figure out.

🖥️ Give Codex a desktop

EduardoRFS

Bend vs Reality

TLDR: I understand the proposal of Bend, but when the efficiency reduction is so big that a RTX 4090 is only 7x faster on a near-optimal scenario than 2 cores of a M3 Max in a language like JavaScript, you should probably not take it.

On the otherhand, easy to use, but opt-in, parallel languages such as OCaml exists and they can compete, so you should likely take those. If you need even more performance, Rust could likely beat the RTX 4090 results on a mobile CPU.

Of course future optimizations should improve Bend results, but my goal here is to show that the current results are not as impressive as they may look, likely a JIT would make the RTX 4090 results 10x faster, but an RTX 4090 still uses at least 100 times more power than a single M3 core at any instant, additionally in principle GPUs are better for purely parallel tasks.

Also this example is a very parallelism friendly, this is both against Bend and in favour of it, most real code is not pure and not a purely binary alg

cpursley

PostgreSQL is Enough

See the new site: https://postgresisenough.dev

---

• Simplify: move code into database functions
• Just Use Postgres for Everything
• Just use Postgres
• PostgreSQL is the worlds’ best database

EduardoRFS

Como Pensar

Ler e entender um pouco desse artigo. https://wiki.c2.com/?FeynmanAlgorithm

• Reconhecer como você pensa
• Descrever métodos que você usa para pensar
• Entender métodos diferentes de pensar
• Fazer perguntas sobre tudo(incluindo sobre perguntas)

Perguntas

EduardoRFS

Examples

[@import stdlib.http.v1];

(x => y => (x_plus_y: x + y) => );

((A, x))
(f: () -> (A: *, x: A)) =>
  (A, x) = (f ());

coproduto

defmodule Quine do
  @header "defmodule Quine do\n  @header \""

  @indent """
    def indent(str) do
      str
      |> String.split(\"\\n\")
      |> Enum.map(&(\"  \" <> &1))
      |> Enum.join(\"\\n\")
    end

kimjoaoun

Em Linux todos os arquivos carregam um conjunto de permissões, elas que dizem para o sistema operacional que tipo de operação pode ser executada sobre um arquivo e quem pode executar essas operações. Todo arquivo tem instruções acerca de 3 grupos:

• owner - Permissões que o dono do arquivo possui

• group - Permissões que os usuários que fazem parte de determinado grupo possuem.

• all users - Permissões que todos os usuários cadastrados naquele computador possuem.

owner é aquele que é dono do arquivo. Geralmente - porém não sempre, lembre-se que em Linux aplicações podem operar como um usuário -, este é o indivíduo que criou o arquivo.

dkarter

name: Elixir CI

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

env:
  MIX_ENV: test

fnky

ilyazub

const { promisify } = require('util')
const puppeteer = require('puppeteer')

const got = require('got')
const { CookieJar } = require('tough-cookie')

const cookieJar = new CookieJar()
const setCookie = promisify(cookieJar.setCookie.bind(cookieJar))

;(async () => {