slowtec | 1 year ago | on: Show HN: A no-build fullstack SSR TypeScript web framework
slowtec's comments
slowtec | 1 year ago | on: Show HN: One – A new React framework unifying web, native and local-first
slowtec | 2 years ago | on: Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
slowtec | 2 years ago | on: Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
2) Yes and no, it really depends on your requirements. We have already created two customer projects with it and are very satisfied (although I personally still prefer the Elm approach to the reactive approach).
slowtec | 2 years ago | on: Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
slowtec | 2 years ago | on: Zed, a collaborative code editor, is now open source
slowtec | 2 years ago | on: Zed, a collaborative code editor, is now open source
slowtec | 4 years ago | on: Lapce – Fast and Powerful Code Editor written in Rust
slowtec | 6 years ago | on: Climatescape.org – Mapping the global landscape of climate-saving organizations
For years, a new framework has appeared every week (it feels like every day) that promises to solve all problems with the latest buzzwords. The mere fact that this happens shows that today's web development suffers from a plethora of unsolved fundamental problems.
Instead of fighting a problem with workarounds (and thus new problems), it would be nice if the community would sit down and ask itself how we can create a future that makes frameworks obsolete.
Sometimes I get the impression that we have more of a social problem than a technical one. If browser vendors, developers, managers, corporations, startups, freelancers and everyone else involved sat down at a table and talked constructively with each other, things would certainly be possible that would save everyone a lot of work, or am I wrong?