nicer

Now you've just made it easier to eventually refactor those few remaining classes into something nicer, cleaner, more efficient.

If your domain is 0..99 for example, using unsigned and <100 is nicer than using signed and two conditionals.

It would be a lot nicer to see a Java 8 translation - a lot more comparable.

It's a syntax sugar which is nicer and easier to understand than using functions and prototypes.

The UI got a major overhaul recently (switched to material design) which made some things nicer.

B) arbitrary precision integers: this is nicer, but even today significantly more expensive than ordinary integers.

And the Google+ UI IMO was nicer than Facebook's (and it still is IMO).

Honestly, it's a lot nicer than my University housing and not much more expensive.

I guess lunch hour is much nicer if your home is under 10 minutes from work.

It would have been much nicer if they implemented their algorithm in a framework such as Mitsuba, so that it could be compared with other algorithms.

GraphQL doesn't mean moving to stateful components, it's just a nicer way to have a singleton data store because instead of chunking and passing a map around, components can declare which data they need.

I know a lot of people say it should be plain but you can still make it look nicer while staying simple.

There's probably a good portion of Facebook that just won't bother switching to any similar service no matter how much nicer they make the interface or features because it's just too much "friction" for them.