Hacker Newsnew | past | comments | ask | show | jobs | submit | kazinator's commentslogin

Fellow Vancouverites: what ... fall back ... strategy are you planning on executing, as an alternative? :)

> Residents will have eight months to prepare for Nov. 1, 2026, when the clocks would have been turned back one hour, but will now remain the same.

That's an odd read. Residents have eight months to prepare for an event already known to be nonexistent: a non-happening.


Idiots; of course the language that the 𒀯 compiler should be in had better be 𒀯, or else it is a toy language.

> The literature is clear that repeated, hands-on practice is really the only way to build skills.

The centuries of literature we have on this contrasts hands-on practice with theory: not actually doing the thing, but studying how other people do it, in order to gain knowledge that will be helpful when you get your hands into it.

This is different: this is like having a slave do it for you.

We know from history that the slave owners didn't know how to do the work. E.g. kings and feudal lords didn't know how to herd animals or raise grains, etc.


Where are you measuring the keypress from? The nerve signal to your finger muscles?> Or the time the keycap hits bottom? What if the switch closes before the cap hits bottom: then we are getting a latency figure that looks better than it really is.

I've had a keyboard like that and with it, xterm (and nothing else) felt like it was displaying the characters even slightly before I had pressed them. It was a weird sensation (but good)

Yes, I know this feeling, it's like typing on air. The Windows Terminal has this same feeling. 8 years ago I opened this issue https://github.com/microsoft/terminal/issues/327 and the creators of the tool explained how they do it.

xterm in X11 has this feeling, ghostty does not. It's like being stuck in mud but it's not just ghostty, all GPU accelerated terminals on Linux I tried have this muddy feel. It's interesting because moving windows around feels really smooth (much smoother than X11).

I wish this topic was investigated in more depth because inputting text is an important part of a terminal. If anyone wants to experience this with Wayland, try not booting into your desktop environment straight into a tty and then type. xterm in X11 and the Windows Terminal feel like this.


Nerve signals yes. I just try them side by side, usually running vim on both terminals and measuring how it feels. If you can feel difference, the latency is bad.

Rather, what will win is a terminal that internally builds an efficient, symbolic representation of what is on the display, rather than a pixel representation with all the font glyph, and which efficiently sychronizes that symbolic representation to the graphical canvas, skipping intermediate updates when the abstract display is changing too fast.

That’s already happening I think. Newer terminals redraw at a fixed rate equal to the display refresh rate, usually 60Hz. But if there are more than 60 new characters being printed per second, some of these intermediate states are never rendered on screen.

> It’s one thing for the government to reject Anthropic’s terms—and entirely another to banish them permanently and, absurdly and punitively declare them a supply chain risk. Worse, they did it in favor of someone else who took pretty similar terms and happened to have given more campaign contributions.

It's just a variation on Snowball being chased off Animal Farm.


> When an engineer writes code manually, two parallel processes occur. The first is production: characters appear in files, tests get written, systems change. The second is absorption: mental models form, edge cases become intuitive, architectural relationships solidify into understanding.

That absorption only takes place in the mind of that individual, unfortunately. That doesn't help when they no longer work there or are on vacation.

The ideal situation is the solo open source project. You wrote all 200K lines of code yourself, and will maintain them until death. :)


Someone taking over a project and working directly in it can build up their own deep understanding about it over time even if they didn't write it all. Documentation from the last expert can help, or just reading and changing things as you build up a mental model. But asking an LLM to change it for you will not arrive at the same place.

What'a a "clear room"? A clean room, but with plagiarized code, laundered through an LLM?

A $200 bill from some cloud entity that doesn't have my credit card info would cause nothing but enormous laughter.

What is ugly here is the combination of the free trial (not ugly in an of itself), and they way they are trying to recruit qualified users for it from open source.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: