hsn915

In Japan, Wantedly is more popular.

Non-native English speaker here.

I would not understand the last two sentences. Sidle? Tromp? I don't think I've seen these words enough times for them to register in my mind.

"Strode", I would probably understand after a few seconds of squeezing my brain. I mean, I sort of know "stride", but not as an action someone would take. Rather as the number of bytes a row of pixels takes in a pixel buffer. I would have to extrapolate what the original "daily English" equivalent must have been.

There are two issues:

- Hosting a website is not so easy for the average person, even the tech savvy person, specially if you try to learn it now using the way large websites are developed.

- Static site blogs lack interactivity: people can't comment on your blog. You have to post a link to Twitter or HN (here!) and interact with people over there.

- Static site blogs also don't usually let people "subscribe" by email or whatnot, so unless people bookmark your website or follow you on Twitter, they are not going to find your content.

P.S. this is a problem area I'm trying to work on, at least on the technical front.

I think it's native as in "native executable".

GPUI is not "native OS widgets".

Nice story but the places I've seen that make use of services, there's never a "1 server -> 1 team". It's more like 20 services distributed among 3 teams, and some services are "shared" by all teams

I think it was around 2015 when everything was basically AWS and Kubernetes

The turning point might have been Heroku? Prior to Heroku, I think people just assumed you deploy to a VPS. Heroku taught people to stop thinking about the production environment so much.

I think people were so inspired by it and wanted to mimic it for other languages. It got more people curios about AWS.

Ironically, while the point of Heroku was to make deployment easy and done with a single command, the modern deployment story on cloud infrastructure is so complicated most teams need to hold a one hour meeting with several developers "hands on deck" and going through a very manual process.

So it might seem counter intuitive to suggest that the trend was started by Heroku, because the result is the exact opposite of the inspiration.

Oh? I had no idea it could mean #2 until I saw this comment.

Sprouts/Gardener: a project to make self-hosting possible (and easy) without linux sysadmin skills

https://judi.systems/sprouts/

Current version focuses on static site hosting, with templates and zero-config localhost preview, one button to publish changes live.

Part of making this project involves creating a GUI framework for Go

https://judi.systems/slay/

Using flexbox-like layout system, it can render UIs for desktop apps in pure go (without using html/js/css).

Can you show me a sample of the code you have AI write for you?

It is time to acknowledge that AI coding does not actually work.

ok, you think it's a promising field and you want to explore it, fine. Go for it.

Just stop pretending that what these models are currently doing is good enough to replace programmers.

I use LLMs a lot, even for explaining documentation.

I used to use them for writing _some_ code, but I have never ever gotten a code sample over 10 lines that was not in need of heavy modifications to make it work correctly.

Some people are pretending to write hundreds of lines of code with LLMs, even entire applications. All I have to say is "lol".

If anything is depressing, it's the amount of people who think these models actually "can code".

Because they can't.

Also, Clean Code is a really bad ideology, you should regret wasting time on it regardless of LLM code generation.

Shouldn't this be "io_uring is faster than mmap"?

I guess that would not get much engagement though!

That said, cool write up and experiment.

Good point.

Backups are definitely part of the vision. Not just for maintenance purposes but because the whole point is to have ownership and control not just of the site itself but the data on it.

The other part is the ability to move to any other host seamlessly.

If someone offers you free stuff for a while, then stops offering it, you should show gratitude for having the privilege of receiving the fruit of their work for free.

You should show gratitude, not hostility.

Open Source does not work for business. It just doesn't.

I intend to make my products source-available but not open source.

I do open source libraries/frameworks that I produce as part of producing the product, but not the product itself.

CA means: this is not just a hobby project, it's a business, and we want to retain the power to make business decisions as we see fit.

I don't like the term "rug-pull". It's misleading.

If you have an open source version of Zed today, you can keep it forever, even if future versions switch to closed source or some source-available only model.

I'm one of the people interested in Zed for the editor tech but disheartened with all the AI by default stuff.

opt-out is not enough, specially in a program where opt-out happens via text-only config files.

I can never know if I've correctly opted out of all the things I don't want.

ُThe Arabic text is the translator's self credit

"Translated by Nancy Qanfar"

The API surface I propose only includes one function. No type needed.

It does not even require the target node to be created with a virtual dom in the first place. Just diff the node with the given tree structure efficiently.

Internally the browser might need to create a few accelerator data structures, but that's an implementation detail.

The linked proposal has many "features" that would be "needed" if you frame the problem in terms of a "template api", centered around "binding" variables, and what not.

https://github.com/WICG/webcomponents/issues/1069

My proposal only adds one native function with nothing else: no new data types, no new apis.

What we need is not templating. What we need is a native implementation of a virtual dom.

More specifically, a native implementation of the "patch" function:

    patch(target_dom_node, virtual_dom)

Where `virtual_dom` is just a plain-data description of the DOM.

Most of the "slowness" of the DOM come from its requirement to be a 90's era Java style object hierarchy.

Don't call it "templating". Just call it "virtual dom". Everyone knows what that means.

Really cool. This might become my goto ambient background solution.

This has been the case since the early 2000s, and much earlier too, probably.

I had thought the industry has matured by now, but nope, still running the same old scripts!

The "It's just JavaScript, so the frontend guys can work on the backend" line has never made any sense to me.

I think it's aimed at HR/recruiting.

Companies tend to think in terms of specific skills when hiring. Something like: We use PostgreSQL, so we will write "3 years PostgreSQL experience" in the job description for a senior backend engineer position.

Unless engineering is explicitly involved in the hiring process, HR will drop your resume automatically if you say "5 years of MySQL and SQLite experience" with no mention of Postgres.

I'd go so far as to say Sonnet 3.5 was better than 3.7

At least I personally liked it better.

Hence, "plateau"

I asked it a few questions and it responded exactly like all the other models do. Some of the questions were difficult / very specific, and it failed in the same way all the other models failed.

Is this something that the models from 4 months ago were not able to do?

I can't be the only one who thinks this version is no better than the previous one, and that LLMs have basically reached a plateau, and all the new releases "feature" are more or less just gimmicks.

Are you talking about full on translation, or just translating individual words?

Yes macOS has builtin OCR, but what about the translation itself? You still need a cloud service for that.

If you want to read Japanese but lookup words/kanji you don't understand, I have a tool for that (full disclosure: it's a paid app) that I developed for exactly this purpose. Yomitai: https://yomitai.app/