groue

If you wish you could do that with SQLite, check GRDB.swift. It can synchronize a UITableView with an SQLite query. Demo: https://github.com/groue/GRDBDemo, documentation: https://github.com/groue/GRDB.swift/tree/v0.70.1#fetchedreco...

Realm is still pretty fast. A simple comparison of Realm with Swift libraries for SQLite: https://github.com/groue/GRDB.swift/wiki/Performance

Change notifications used to be a feature that was only available to Core Data users, through NSFetchedResultsController. Glad to see Realm provide it as well. In the SQLite landscape, change notifications and table view updates is also provided by GRDB: https://medium.com/@gwendal.roue/grdb-stories-1da44bdb53ab#....

It happened that I read the initial robots, empire and foundation cycles first, and then the "glue" novels that Asimov later wrote for the sake of general consistency. And those added novels contain wonderful twists - it was such a pleasure to read them!

French native here as well. I personnally say "at" when spelling out email addresses. "Arobase" ou "et commercial" are names of the symbol itself - not commonly used because one rarely has to name the symbol.

Do you know C blocks ?http://en.wikipedia.org/wiki/Blocks_(C_language_extension)

He/she means that `=>` looks like a mathematical implication, just like `|...|` looks like absolute value bars.

Because some people don't use the spacebar for themselves, or use a browser that doesn't support spacebar page-down scrolling, and think shortcuts are smart. For them it's OK to experiment and remap a key to some feature, even though only them are aware of it, and most other people won't see it and won't use it, or will get bitten as you are.

Tumblr is a a particular nest of this kind of websites.

That's unfortunate, and funny at the same time. Internet is also a playground, a sand box, a place to learn.

Best you can do is contact them, and teach them a polite UX lesson.

People using Windows (I don't know about Linux) think that Caps lock is Shift lock. Wrong. It's Caps lock. And that's pretty useful.

On OSX French keyboard, Shift-é would give 2, Caps-lock+é gives É. That key gives straight and easy access to uppercase diacriticals: é-É, è-È, à-À, etc. And when "UNTEL ACCUSE" means "some guy accuses", "UNTEL ACCUSÉ" means "some guy accused". It's pretty important.

When one looks for some information, he never knows when he should stop scrolling. He may even well scroll too fast, and miss the portion he was looking for. However, when he can zoom out, he gets a glance at the page structure, can read section titles that are still legible, and directly zoom to his spot.

I'm happy this project exists. For generating Objective-C documentation, there is the complex Doxygen, and the light https://github.com/tomaz/appledoc. Appledoc unfortunately lacks too many features. As it is built on its own home-built parser... well improving it sounds like patching a leaking corpse. Going with Clang sounds pretty sensible. However cldoc does not support Objective-C (yet?). This is how I interpret the many `Unhandled cursor: CursorKind.OBJC_CLASS_REF` messages I get. Stay tuned, this may be big.

Another perspective of currying, from a guy that is not versed in functional programming.

I have written an expression evaluation engine whose internal implementation only manipulates functions that have a single argument. Merely value transformers.

It used to only interpret expressions like `f(x)`, `g(f(x))`. Later, functions were able to return other functions, and `f(x)(y)` was allowed. However, this last expression really looks like it would be better written `f(x,y)`. Why force the user to use a convoluted curried syntax such as `f(x)(y)` for his two-parameter function?

So the `f(x,y)` form has been added as a mere syntactic sugar. However the guts of the engine are still made of single-argument functions. That can get curried.

So currying is not only a tool for the end-user. It's also a tool for the language implementor :-)

I haven't read anyone noticing that developers lose countless hours fighting with badly crafted PSDs like the one shown in the article, just to extract proper assets that keep their code tight. Think pixel fitting, but also dimensions consistency, color consistency, etc. Off-by one/three/eleven pixels are a plague. Save money on the design: you may well increase your development costs.

Hum. UI code has to be different, anyway, in order to respect the hosting platform conventions and avoid behavioral oddities. The non-UI code can, to some extent, be shared. At least its design. Isn't it?

Very interesting, thanks. http://atilf.atilf.fr and Dictionnaire historique de la langue Française both see two meanings for the French "trivial": one is common as in commonplace, and the other is common as in gross and vulgar. The first comes from /trivialis/, as fhars says. The latter comes from /trivium/, the crossroads. I don't know if English also has the second meaning: vulgar.

What about adding the ability to drag the slider, so that the widget acts as it should act, that is to say as other sliding toggles? It would then be perfect! Rationale : that's again the problem of half-baked UI elements, which confuse their end-users, while the developpers feel satisfied and enjoy long drinks.

It's like reading a Plato book where Socrates is bullying the guests :-)