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.
160 karma · joined February 26, 2018
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.
i'm building a framework with minimal dependencies at https://www.plainweb.dev so i'm super excited about everything that node builds in (sqlite, typescript).
but there is a difference between supporting the bare minimum and actually making it nice to use day to day.
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 avoid typescript because of similar soundness issues. but in the context of web dev this weird type system that evolved from adding types to javascript turned out to be so nice to use. it's bonkers because on paper it shouldn't be this nice haha.
it blows my mind weekly how ergonomic and flexible typescript’s type system is. it allows me to write great apis for my team mates.
is it possible for the type checker to end up in an infinite loop or for a junior developer to abuse “as”? absolutely, but it doesn’t really matter in practice.
i wouldn’t want to run typescript in rockets or submarines tho!
i wrote a similar tool the other day: https://github.com/joseferben/makeitpass
it can make all kinds of commands pass by checking stdout/stderr and it’s language agnostic (you need npx to run makeitpass)
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 giving bun a shot again to replace node + tsx (esbuild).
nowadays i default to htmx, alpine, sqlite and typescript, recently i’ve been working on a framework/starter using these tools: https://www.plainweb.dev/
plainweb avoids build processes that bundle js that runs in the browser.
i'm building https://www.plainweb.dev/, which uses htmx + react style components for templating.
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 htmx is not enough, just need to make sure the alpine directives are type-safe.
i think it's exciting what astro, hono or fresh are doing with islands of interactivity but plainweb tries to be even more minimalistic.
I blog mainly about web development.
Location: Switzerland
Remote: Yes (hybrid or on-site for a good fit)
Willing to relocate: For a good fit
Technologies: React, TypeScript, Remix, Next, Node, Django, Python, Tailwind,
SQLite, OCaml, Nix
Résumé/CV: https://www.linkedin.com/in/josef-erben-90a002b1/
Email: josef@erben.systems
Blog: https://www.joseferben.com/
Github: https://github.com/joseferben
I am currently bootstrapping a product (https://www.performance90.com) but I am open for employment if it's a great fit. I have 8 years of experience as an engineer and 3 years as an entrepreneur. As an engineer I feel at home in the TypeScript and Django ecosystems.I have my own LLC and I am also open to contract work.
> I asked Django Fellow Carlton Gibson what it would take to update that advice for 2022.
Glad to see that SQLite is being presented as a valid option in the current version of the docs.
> Even without WAL mode, bumping the SQLite “timeout” option up to 20s solved most of the errors.
Can you say anything about the tradeoffs when increasing the timeout, maybe in the context of Django?