Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
flohofwoe
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
3 ms
·
1.
▲
by
flohofwoe
5d ago
Correct me if I'm wrong, but an MCP server still make a lot of sense for remote-controlling a UI application (like a game engine editor) which otherwise doesn't have any 'access points' for remote-control right? An Amiga
2.
▲
by
flohofwoe
5d ago
The internal string encoding of a programming language doesn't matter as long as it supports UTF-8 at the boundaries. E.g. the text encoding standard on the web is clearly UTF-8, even though JS strings may be internally stored as UTF-1
3.
▲
by
flohofwoe
5d ago
Yes, UTF-16 is the worst of all alternatives and should be abolished rather sooner than later. UTF-32 is fixed-width for UNICODE code points, but a single visual character (e.g. a "grapheme cluster") can be built from multiple cod
4.
▲
by
flohofwoe
5d ago
IMHO a 30 percent size increase for sharing text data is really not a problem when most data sharing (by volume) happens via audio, video and image data which is infinitely larger. We obviously have both the bandwidth and storage volume to
5.
▲
by
flohofwoe
5d ago
So educate me then what I'm missing in the 'agentic loop' workflow, oh wise one ;) I'm using this sort of spec-driven + feedback-loop workflow at work to pretty to good effect, and would say I'm quite familiar with
6.
▲
by
flohofwoe
6d ago
That combination is how it already works. You can build combined "characters" (grapheme clusters) from multiple code points, e.g. you could have a "base emoji" followed by a "modifier" emoji, and AFAIK that
7.
▲
by
flohofwoe
6d ago
> How should a reader infer the bye order for a UCS-2 or UTF-16 file without a BOM? Simple: switch to UTF-8 as the only encoding standard for sharing text data, keep UTF-32 as 'internal' runtime format for random access to code
8.
▲
by
flohofwoe
6d ago
> "UTF-8" support was often just single byte, so it was little more than ASCII "Single byte UTF-8" is ASCII. That's one of its most important properties. > Even now it's common for programs to choke on
9.
▲
by
flohofwoe
6d ago
OTH UTF-8 is just one variable-length stream encoding among many others (RLE, LBE128, etc...).
10.
▲
by
flohofwoe
6d ago
But the nice thing about UTF-8 is that this proposal isn't really a "complication", but a minimal and natural extension of the original idea to allow more than one lead byte.
11.
▲
by
flohofwoe
6d ago
> ...24-bit numbers? Technically current UTF-8 only goes up to 21 bits (that's the current UNICODE range), for the encoding itself that is an arbitrary limit though, with the 'single lead byte' method of traditional UTF-8
12.
▲
by
flohofwoe
6d ago
It's still a joy to see how frigging elegant and extensible the UTF-8 specification is. And even without the esoteric 0xFF lead byte, the regular UTF-8 encoding with a 0xFE lead byte (11111110) would still have plenty of headroom (36 b
13.
▲
by
flohofwoe
6d ago
Phew, and I was worried that we'd be running out of UNICODE space for new emojis ;)
14.
▲
by
flohofwoe
6d ago
At least when plugging a computer together I know who built the components. When building with LLMs I have no idea who actually wrote the code snippets that are thrown into the mixer ;)
15.
▲
by
flohofwoe
6d ago
INHO the only unsatisfactory part for this "explorative" work is that you never really get into the flow since the LLM just takes too long between interactions (sometimes minutes). That's long enough to prevent from getting i
16.
▲
by
flohofwoe
6d ago
Don't know, but AFAIK this wasn't a popular programming language on home computers in the 1980s (from what I've seen, the popular non-asm languages were usually BASIC, Forth and Pascal, even C was kinda rare).
17.
▲
by
flohofwoe
6d ago
The difference is that you'll get a different "ZX Spectrum GUI" each time with an LLM, but the same result with a compiler. The actual work in both cases is not to write the source code, but to figure out and describe exact
18.
▲
by
flohofwoe
6d ago
When your manager gives you the task of building a complex product with a more or less vague "do what I mean" specification, and once a week shows up for 2 minutes to nudge you into a different direction, would you agree when the
19.
▲
by
flohofwoe
7d ago
Maybe Claude one-shotted the project ;)
20.
▲
by
flohofwoe
7d ago
There is practically no other choice on a Z80. C compilers really don't like the Z80 ISA and create both slow and bloated output, at least compared to manually written asm. And on top, you can do many optimization tricks in assembly th
21.
▲
by
flohofwoe
7d ago
For me the red line is obviously AI generated readmes. If the author can't even be arsed to write obviously human facing text by himself I immediately lose all interest too.
22.
▲
by
flohofwoe
7d ago
Not the parent, but it reads a lot like written by AI. It has that typical breathless style that's exhausting just from reading. Also, looking at the code, the whole project looks vibe coded, no human would write such comments. Everyth
23.
▲
by
flohofwoe
7d ago
I don't quite agree with the Assembly => Compilers => LLMs as some sort of "stages of evolution" argument tbh. LLMs are an additional way to generate code, but it's not like code generation or "low-code"
24.
▲
by
flohofwoe
7d ago
In short: Benchmark numbers were always more important than consistency (traditionally, GPU vendors competed on frames-per-second, not on image quality). E.g. floating point behaviour is only the tip of the iceberg. Every GPU vendor also do
25.
▲
by
flohofwoe
7d ago
That sort of careful work would take more than 7 commits and 1 hour though ;)
26.
▲
by
flohofwoe
7d ago
Tbh, I still wonder why people even bother releasing such tools that were shitted out by an LLM in an hour or two, these are basically the modern equivalent of a hastily cobbled together 10-liner shell script (still useful, but not somethin
27.
▲
by
flohofwoe
8d ago
It has nothing to do with WebGL though, that same problem might happen in native 3D engines too as soon as you need to support multiple 3D APIs from a common shading language. On the contrary, WebGL2 is probably the only 3D API that comes e
28.
▲
by
flohofwoe
8d ago
It turned out to be something different, but another much more common source of shader output differences is when a float value is clamped to integer (with the value being very close to the closest integer), and then use the clamped value a
29.
▲
by
flohofwoe
10d ago
> ...while Russia got kicked out? For starters, neither Israel nor Azerbaijan threaten Europe with nuklear annihilation on a nearly weekly basis.
30.
▲
by
flohofwoe
11d ago
> And while I don't know whether there was blackmail involved I do know that there was terrorism involved (the GermanWings crash on 3/24/15, ridiculously blamed on "pilot suicide"). Lol, ok wacko... whatever you
More ›