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

Can't buy one in the EU.

Company samples are tiny.

I own Palm and software is a mess.

Interesting what infrastructure they really share.

Even 30 seems a bit optimistic and 60 is insane.

It is insane that 60 was ever considered a limit :P 20 seems much more than needed

> In traffic, energy used over a specific period of time (power) translates into speed. In this case, the critical quantum will appear as a speed limit. Wherever this limit has been passed, the basic pattern of social degradation by high energy quanta has emerged. Once some public utility went faster than 15 mph, equity declined and the scarcity of both time and space increased. Motorized transportation monopolized traffic and blocked self-powered transit.

>...

> From our limited information it appears that everywhere in the world, after some vehicle broke the speed barrier of 15 mph, time scarcity related to traffic began to grow. After industry had reached this threshold of per capita output, transport made of man a new kind of waif: a being constantly absent from a destination he cannot reach on his own but must attain within the day.

https://www.davidtinapple.com/illich/1973_energy_equity.html


Ultimately the limit is mostly decided by the width of the road. You can set a 10km/h limit but if your road is wide and straight, many will just go at whichever speed they feel comfortable with. The reverse is also true: I can bet it was very rare for anyone to ever reach 60km/h on streets like those shown in the picture.

So to really enforce slower traffic, narrow down your street to the bare minimum required for a car to pass through. Add obstacles as small turns or bumps. You'll also gain space for sidewalks and cycling paths.


gibberish.

M-x ?


For vi-heads: ":" The key combo that puts you into command mode. M is "meta", which is Alt on PC or Cmd on Mac.


That is incorrect. In vi and vim, "ESC" is the key that puts you into command mode (from insert mode). Command mode is the full-screen visual mode where you enter commands by a sequence of keypresses.

":" is the key which issues "ex" commands. vi and ex are two different modes of the same editor. Any command which begins with a colon is an ex command, not a vi command, not done in "Command Mode".


True. ":" is the rough equivalent to M-x, though.

Also worth mentioning is Q , which puts you in ex mode, essentially just ":" prompts one after the other until you exit or issue a "vi" command to go (back) to visual mode.

And then there's open mode, but vim doesn't implement that.


These are all conventions and you can change them, but I'm used to Meta = Opt and Super = Cmd on macOS.


Does that interfere with your being able to use Opt for typing key combos to produce Unicode codepoints that aren't usually found on a "standard" keyboard for your country? E.g., accented characters not found in your country's majority language, Greek letters when you don't have a Greek keyboard, mathematical symbols, and so on? It's been a couple decades since I owned a Mac, and I love Linux's Compose key feature, but I remember that Option+key shortcuts were really good for typing a wide variety of commonly-used Unicode codepoints. How does setting Meta = Opt work with that for you?


It does, yes. It's a reasonable trade-off for me becaues it's rare that I need to do that and if I do, I use [digraph]s in (neo)vim. The alternatives are usually more disruptive for me, (using Cmd as Meta shadows way more commonly used OS-level shortcuts, using Esc as Meta shadows Escape in Vim, and other TUIs).

[digraph]: https://neovim.io/doc/user/digraph/


That is what people use for the Alt key. I mean, I use Emacs daily, and I (mostly) like it. But the terminology *) is really fucked up inside Emacs.

Almost no one realizes that perhaps since 35 years no keyboard in mass-use had an "Meta" key. And if the "e" people now still keep that weird name, then they aren't similarly frozen in the state of time as the Emacs community.

1) There's more. Lisp still let bleed assembler instructions that no CPU used in the last 40 years, like CDR and CAR. That's if like e.g. JavaScript would have a cmpxchg() function.

also 1) Or it uses "window" in a very different sense.

and also 1) and even when the term is what you expect, they -- in best english tradition! -- can't normalize on one writing. You can e.g. find both "assoc" and "assq" in use.

So if you want an extremely powerful editor construction kit with an extremely weird nomenclature of parts of it, then chose Emacs.


...and failed attempts of regulatory capture.


So true..


By destroying them they don't copy only convert them into another format.


It's much harder to make a magic juice that moves though the cables and boxes ;)


Is it really that much harder than making the magic juice that legacy cars run on? By now it is cheaper and less reliant on despots all over the world to get electricity than fuel in most of Europe I assume. Electricity is a great interface as well given the actual source of energy doesn't matter as much and is interchangeable.


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

Search: