As a Chinese, I feel tiered, it's like the cold war, what is takes to keep competitive with every aspect, it's just another win for the country and the corp
HN user
wener
A Programmer live at https://github.com/wenerme .
The only thing I prefe peggyjs over ohm is runtime deps, I thinkg this might let ohm aot the grammar to avoid the deps.
Why not use mcp-cli mode, I even made a replica for that https://github.com/wenerme/wode/tree/develop/packages/wener-...
I use https://github.com/ariga/atlas for this, migration based and schema base both has there good and bad side, I prefer both even in one project, schema based can make dev faster, eaiser, migration based make feel reliable.
https://wener.me my notes https://abc.wener.cc my things
Really hope there is a layout mode or ocr with bbox mode, I want to see the model restore the whole page.
Nats is the way
So, the final choice is dexie + custom backend? I've researched these open source solution before, I think dexie is the choice that you will never regret.
I just track my bookmark as Awesome https://wener.me/notes/tags/awesome
The source is at https://github.com/wenerme/wener
I found it's very useful, especially the license and basic tech stack & description. One day I will grab the meta and display along with the link.
I still try think /v1 /v2 is a break, I don't trust you will keep v1 forever, otherwise you'll never introduce this execuse.
I'd like to introduce more fields or flags to control the behavior as params, not asking user to change the whole base url for single new API.
I used to use sqlite3 with stdio to read VoIP SQLite data. It's difficult or impossible to get a compatible SQLite version, and it's also hard to use cgo. I want to read the SQLite data on the server, and stdio is the only choice.
Bootstrap is a good practice in old time, tailwind is modern css, daisy ui is a battery included components in pure css based on tw. I use daisy ui in every project I work on, by using daisy ui, I don't need shadcn, I prefer <button> instead of wrap my own <Button>, and menu, dialog etc. With baseui components I have a very powerful toolset that let me build thing's fast and good enough.
I add nano to every alpine base container, micro seems good, but
apk add nano # Installed size 308 kB
apk add micro # Installed size 12.17 MBSystemd is a complete solution to a variety of problems may not exists. :P
Not by s6, but s6 author may introduce a new init for alpine
Tinc can work on L2, which means works like switch, means it can works like an cable between any nodes.It doesn't need an ip, you can make a bridge. There is no known good replacement for this.
The down side is
- single thread (perf has limits in 10gbe)
- userspace (wg can works in kernel)
- 1.1 is stable enough, but still may crash, be careful
You may also interested in n2n
Any plan to support musl ?
Deno looks good, but don't support musl, I'm not the target audience.
Recently build a simple SQL Parser for sequelize
A better link https://github.com/bloomberg/comdb2
But, vite is working on to become the next nextjs, like ssr, isg etc. Nextjs only support react, so it's easier to leverage the react's ability to do these.
When there is ssr, there is runtime, more than just a dev/build tool.
React Context HMR still has problem. Due to this problem, I think nextjs still the better choice for react dev. Maybe vite supports too many frameworks, do not have enough time to handle the react problems.
WAL-G like the litestream for PostgreSQL, MySQL/MariaDB, Mongo, Redis, FoundationDB WIP, Greenplum WIP.
Checkout ZeroVer: 0-based Versioning https://0ver.org/
Electron is irreplaceable if
- you want to cut the dev cost on support all platform - maybe MOST important
- you want Browser like feature - embed webview not iframe
- you want to make sure the feature is there, if you can not polyfill
Memory is cheap, download size is cheap.
Sciter is like React Native with extra Web like feature and a more flex "jsx".
Nowadays, it's called react-native, you get HTML like compiler to a windows/macos exe.
Asked for the same thing, but it's impossible or too hard to do it.
It's just take time and browser feature complete, like photoshop is one web now.
CSS should be portable across any browser/web view. And given that browsers nowadays occupy tons of memory (even though they are written in highly performant languages) I am still impressed by sciters small shipping size.
Chrome is new IE since June 15 2022, and happy about it. Interop 2022 is about make safari and chrome get on the same page about new css feature.
Memory, portable CSS and browser compat is about cost, if I can make whole company install chrome, that can save a ton of money investing on support unexpected browser, one time install is way cheaper than continue support. If the company is big enough, there will be no problem, like google can rewrite whole Google Doc to canvas to support cross browser. If building a sciter based app biz, that's all your investing goes, that make sense.
[Interop 2022]: Blog https://web.dev/interop-2022 Current status https://wpt.fyi/interop-2022