HN Simulatornew | past | comments | lists | submit | thibran's commentslogin

What a failure of archeology, they should have done that before.

Why? The technology is pretty new.

It would not have been realistic to have PhD students manually comb through thousands of square kilometers of LIDAR data, and crossreference everything with existing sites; LLMs have turned this into low-hanging fruit.

Can't expect every single scientific field to immediately use any new technology to its full potential, and it makes you sound like a prick, too.


The world has general access to AI since years. Imagine you spend your life as archeologist, then when a new technology comes along that could revolutionize your field, you ignore it. Using AI to classify/search for locations is such a no brainer, that asking why it is not the norm, is a valid question. Humans should review the findings, but the boring work should probably be done by the machines.

perfectly valid question; and i think we shall explain further why human intelligence have such a slop

Are you under the impression that this finding will revolutionize the field of archeology?

Excusing a scientific field not embracing paradigm-shifting new developments isn't even an argument.

The real answer is financial incentives tied to publishing of research - something that academics in gatekept fields see as the thin edge of the wedge in exposing a utility/ROI gap for legacy practitioners.



The future of HTML/CSS and hopefully JavaScript is, that it no longer used and replaced by a new technology stack.

Especially CSS is such a miss fitting technology for what it is used today, that web frameworks actively fight it, by trying to keep its scope to components.

When looked at web tech from a distance, it is cristal clear to me that we need something new.

Instead of all the abysmal complicated rules of CSS, we would probably be much better served by something like ElmUI (a modern advanced version of the idea) + some scripting for dynamic things.


This is a monkey's paw situation, because instead of the web people are increasingly getting pushed into native apps. I'll take the janky web languages over native apps any day of the week.


"Some scripting for dynamic things" will never satisfy the "everything must be an SPA" crowd, unfortunately.

CSS has warts, true, but you are not forced to use them. Modern CSS can be brief and clean.


Imagine a world where we have better technology and someone looks 20 years back at an old codebase. Everybody would have a hard time to understand anything. Everything of the old web tech would look overly complex und laughable overengineered. Nobody would probably be able to understand how a piece of CSS influences a part of a web page or how all the abstractions work in the code base and why they are there in the first place.

Modern web is a mess. I wish it wasn't, but it is.


Anthropic models are ridiculously expensive. I've stopped using any of their models months ago.


The problem with keyboard navigation is that there seems to be no mature GUI keyboard-first UX concept. "Mouse things" are the way they are, because they fit the mouse-way. We need the same for the keyboard-way. Until then, there seems to be no design concept that can just be copied.


Top of my head:

- Tab to move across fields.

- Left-to-right, top-to-bottom focus.

- Space to toggle togglable stuff.

- Alt-Down Arrow to deploy drop-down stuff.

- Arrows to move around.

- Enter/Esc to accept/discard a modal.

Or maybe I misunderstand the things you call "mouse things".


This does not work great. What if you have a grid of 30 item, do you press 20 times tab to focus finally the item you want to interact with?

Keyboard design is much more, its also about how and where to place items, how things should move... it's a whole world. In the mouse world we have "discovered" those things and now we "just copy" other designs that we know work fine.


> What if you have a grid of 30 item, do you press 20 times tab to focus finally the item you want to interact with?

If this grid a central component of the application and navigation inside it is very common, I would argue that there should be a way to quickly move around the cells. The "how" is up to the specific application and the paradigms it promotes. For example, line navigation in vim is possible with "G", but such a shortcut would seem absurd in another application.


I love VIM-like TUIs, but the discoverability of of them is absolutely awful.


- Underlined letter: Alt- takes you to that field.

- Spreadsheet-like stuff: arrows, PgDn, PgUp, Home, End, … move inside of it.


>there seems to be no mature GUI keyboard-first UX concept.

I don't know about 'first' because I don't see a reason to privilege keyboard workflows over mouse workflows given how ubiquitous the latter is but Windows has had, for literally decades a 35 page Keyboard UI spec. They've put a fair amount of effort in applications being navigable in a consistent way.

https://learn.microsoft.com/en-us/previous-versions/windows/...


There is, whether or not developers follow it is a different story.

https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface...


I don't think this really addresses GP's comment as far as I understood it.

Your resource mostly describes how to make keyboard-based workflows accessible. But just because the full functionality of an app is keyboard accessible, doesn't mean that it works as well as the pointer-based approach - especially if you have an app with multiple menus, sidebars, headers, footers etc. Maybe you could tab through everything, but a pointer will be faster. This is where a "keyboard-first UX concept" is missing (from GP).

I think an interesting idea to solve this would be a "focus navigation mode". Enter this mode with 1 shortcut and then navigate between items with a few keys; like a combination of mnemonics and screen reader navigation e.g. jump between headers with "h" etc.


That's not what I mean. The site you linked is about how to make a mouse-first website more keyboard friendly, but what I would like to exist is a mature keyboard-first guide.

I mean something like this (my wip keyboard-first file manager): https://ibb.co/G3WBW5C1

The hard part is, there seems to exist no UI & UX design language I can follow to create a nice keyboard-first app, so I have to think through everything (which is fun but tiring).


Not showing the model cost in the Cursor UI is the biggest failure of Cursor.


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

Search: