joseferben

7 ms·

31.
by joseferben 2y ago
impressive, imagine this but photo realistic with vr goggles.
32.
by joseferben 2y ago
https://www.plainweb.dev is my shot at making web development simpler. my bet is that most companies and solo devs only need a single process and sqlite to drive revenue. i’m considering switching from tsx to bun, but i’m hesita
33.
by joseferben 2y ago
for typescript there is pg-boss, works great for us
34.
by joseferben 2y ago
excellent article! my approach is to to break down larger bits into smaller monorepo packages with turbo repo where each package builds itself and the task graph is managed by turbo. the drawback is that watching across local packages does
35.
by joseferben 2y ago
the issue i ran into recently was around react/jsx where i wanted .tsx files server side. might have to look into it again but there was an issue where some react/jsx/fragment bit had to be ported to esm first.
36.
by joseferben 2y ago
for instance exiting the runner on the first error. and the diffs with node:assert are not as nice either compared to vitest. i'm building a framework with minimal dependencies at https://www.plainweb.dev so i'm super
37.
by joseferben 2y ago
for my use case (web dev) ts is fast enough. but i do miss the ocaml compile times! it's mainly the lack of ad-hoc polymorphism that makes ocaml feel a bit clunky to me at times. but structural typing sure would be nice. i used to avoi
38.
by joseferben 2y ago
having written ocaml in production for a few years, i think soundness comes at a cost of dev ergonomics. at least with the type systems of today’s industry languages. it blows my mind weekly how ergonomic and flexible typescript’s type syst
39.
by joseferben 2y ago
i wish it was that easy. i keep trying to default to esm on node projects but the ecosystem is not there yet, at least in the context of server side nodejs stuff.
40.
by joseferben 2y ago
i tried that but had to revert to vitest, the native test runner feels incomplete atm.
41.
by joseferben 2y ago
looks like a great way for someone with 2d pixelart skills to get started with 3d!
42.
by joseferben 2y ago
this looks interesting. any first hands experience applying this for tech incidents?
43.
by joseferben 2y ago
i found that the feedback loop between llm and test suite works really well, especially with sonnet 3.5 i wrote a similar tool the other day: https://github.com/joseferben/makeitpass it can make all kinds of commands p
44.
by joseferben 2y ago
atm it only supports claude models, but will look into supporting openai and ollama
45.
Show HN: A CLI that uses Claude to fix your code until the tests/builds pass(github.com)
12 points by joseferben 2y ago|4 comments
46.
by joseferben 2y ago
author of plainweb here, thanks for posting! i posted a Show HN a couple of days ago to get some feedback: https://news.ycombinator.com/item?id=40726710 not much changed so far, mainly working on the docs still. considering
47.
by joseferben 2y ago
would you say running bun or deno would be simpler since compilation doesn’t happen in “user land”?
48.
by joseferben 2y ago
impressive to decide against something as shiny as langchain as intern
49.
by joseferben 2y ago
i mostly agree with the rant, except for styling, i think tailwind is great. nowadays i default to htmx, alpine, sqlite and typescript, recently i’ve been working on a framework/starter using these tools: https://www.plainwe
50.
by joseferben 2y ago
strictly speaking there is a simple build process on the server since plainweb uses node + tsx (the esbuild wrapper, not the markup) instead of something like bun or deno that supports typescript natively. plainweb avoids build processes th
51.
by joseferben 2y ago
i mostly agree with your take, except that if you primarily want to produce html going with a server-side rendered approach might be simpler. i'm building https://www.plainweb.dev/ , which uses htmx + react style compon
52.
by joseferben 2y ago
awesome, let me know how it goes!
53.
by joseferben 2y ago
JSX components (.tsx) are rendered server-side, it's all just GET/POST with optional HTMX
54.
by joseferben 2y ago
thank you! yes, it's server-side with htmx at the moment. anything client-side that has a build process is entirely out of scope as i think that's a major source of complexity. i'm considering embracing alpine.js for when htm
55.
Show HN: Simpler web dev with Htmx, SQLite and TypeScript(plainweb.dev)
15 points by joseferben 2y ago|14 comments
56.
Show HN: Arewedownyet.com(arewedownyet.com)
5 points by joseferben 2y ago|4 comments
57.
A TypeScript monorepo that sucks less(beeps.co)
5 points by joseferben 2y ago|0 comments
58.
by joseferben 2y ago
i didn't know the simple.wikipedia.org subdomain, pretty neat!
59.
by joseferben 2y ago
recent google algo changes seem to penalize domains with a low domain rank even more. if you want to be found through search it makes sense to use an established platform.
60.
by joseferben 2y ago
imo remix ( https://remix.run/ ) does a great job at that

More ›