jrimbault

Why do you wait for these events ? Myself I consider these to be complete non-events.

Personnally, like many things, I've built a custom script atop git to manage my notes. And another to manage a journal. And another, and another. Just building off of git.

Thing heats and deforms (change properties), when it reaches temperature n, thing deforms just a bit too much, cuts electrical contact.

It looks like a paper sheet.

(I have an alias specifically for finding that out)

Personnally, I don't care about any of the crytpo-mining-coining and I think the two are sufficiently distinct.

PHP apps are almost guaranteed to be "stateless", thus scaling up and down is quasi-painless also.

That's just how I phrased it 18 hours ago. The thing I find bad about it is not that exceptions have to be declared in the interface, that's good, it's that every implementations will have to declare them also, even in the case that a particular implementation has no failure mode.

Yes you can do `using Whatever = System.Console;`, fantastic, that's not the common idiom and it is harder to do (longer to write) than the usual idiom.

Forgotten Hope 2 has its own workarounds and launcher. Other mods (and vanilla players) use BF2Hub, which wraps around bf2.exe I think to redirect DNS calls to the defunct EA and gamespy servers.

- declare a namespace for the file (no indentation)

- declare that the file is a class and can only contain one (top level) class (still no indentation)

- `using` statements that don't import every symbol into my namespace :

    using System.Console;
    ...
    Console.WriteLine();

    using Sytem;
    ...
    Console.WriteLine(); // where does "Console" come from ? god/IDE only knows

But alreay with these few changes, I've saved 10% of the 80 columns width. I've made it easy to read a file without an IDE. You can start to write actual code at indentation level 0. I've made it easy to have one class per file and hard to have two class per file, in the spirit of making good pratice easy and bad practice hard.

It's tiny, it's fun, it's enough. Keyword : enough. Yes I could add a preventDefault, but I don't care. Really, I only entered the names of my friends once, it has been in my localStorage since, and it's only really meant to be used by me.

Fixed it.

I made that _tiny_ website for evenings with friends. It works great. You enter a few names, hit the save button, you get a list with scores and a +1 button for each players. When you refresh the page the scores are reset. The most important feature is the _ding_. The ding makes it fun.

It's ridiculously small, but it brings lots of fun.

- an enum (or struct)

- its Display implementation

- its Error implementation, now just one function

And a few `impl From<OtherError> for MyError` to make the try? operator work.

For a library it's really not that much work. And even that can be simplified further to a few derive macros with another library : thiserror.

It's my own preferred definition (Eco's definition), the essay itself is very short, highly recommend it. No mention of state or corporation.

I think the expirement is over and conclusions can be drawn : emacs represent a tiny proportion of text editor's users, not because of a lack of features (is there's one thing missing it won't be for long), but because of what it is and the people and community around it.

Emacs interface and community mannerisms _are_ user-hostile. As demonstrated by history.

Words once written don't need to be abbreviated. Abbrevation is only useful when writting for speed. When writting for being read don't use them.

I'm sorry to react to first quote, but as I kept reading I kept coming back to it. My thoughts on that : how you present yourself is how you want (and are going) to be judged.

In general I think Emacs has been user-hostile, as said here, just by its terminology. Nobody outside a minority of devs (a minority even among programmers) refers to Ctrl+c as C-c.

> Yes, make Emacs appealing and user friendly. But don't forget that a masterful tool in the end requires mastery, which can't come for free.

And the old "I have suffered therefore the others have to suffer".