It looks very useful with all the software integrations. Now the price tag however... Without financing it would be hard for majority of buyers to justify.
Doesn’t almost everyone finance their phone anyway? You pay a carrier x a month and get a phone and service for a few years. Maybe they’ll push the plan out from 2 years standard to 3 so it’s just as affordable for people?
Yes. In this interview Michael Stonebreaker, one of the original developers of PostgreSQL, discusses (among other topics) replacing the file system with a database :
This is one of those perennial ideas; let's get rid of hierarchical file systems and just keep all the files in a database. Speaking as a user who knows how to keep things organized, I like hierarchical file systems. Store the data in a database if you like, but don't break my metaphor.
I like a hierarchy, too. Presumably the underlying engine could be a database but it would at least appear to the user as a tree. But with the option to find files with SQL or a SQL-like language. I would love to be able to find files based on all kinds of metadata that was available for searching with the OS’s file system, and not using any special tools. I’m thinking things like EXIF data, audio file metadata, text file line count, and so on.
The tree-view is practical for users but seems impractical for relational database performance.
SELECT * FROM files p
LEFT JOIN files c ON p.id = c.parent_id
LEFT JOIN files gc ON c.id = gc.parent_id
LEFT JOIN files ggc ON gc.id = ggc.parent_id
....
where p.id = 123
To achieve maximum career success & maximum effort to be a great dad is not possible.
Time, energy, & your age are finite. That’s all there is to it.
However, if the metric of career/financial success is reduced to just net worth gaining at X% rate consistently, then it is possible to spend as little time as possible on career success and maximum time to be the best dad possible.
As a user I don't really appreciate sites that do this as they tend to have worse latency for UI interactions and less pleasant page transitions. And of course, they are unusable offline
> As for offline, yeah, my Internet web page doesn't work offline.
That's really too bad honestly. What about your users who want to use your site when they're offline? Sympathy with those users is why I made sure that my site works well when offline.
Whether this is actually beneficial (let alone possible) depends heavily on the type of site.
Web apps that are valuable to use offline also tend to be the kind that really do warrant client-side logic and rendering (a spreadsheet web app is a classic example).
If the site's focus is providing information (e.g. Wikipedia), then working offline really just means loading all the backing data into the browser, which quickly becomes impossible.
I'm sure there are cases where offline availability is a huge plus (your site might be a good example), I just don't think it's universally applicable.
The golang implementation of protobuf sucked historically (still does, but is improving) and gogo was an alternative that fixed a lot of problems and was nicer overall. Until its creator burned out and deprecated it. Chasing a constantly moving target that you have no control over is very taxing in the long run.
I think it's less that protobuf is a moving target, and more that gogo tried to add in all the features that google didn't want to maintain, and learned that maintaining a massive feature matrix was impossible.
GoGo was not a completely separate implementation but deeply hooked into the official GoProto implementation. So it wasn't "Protobuf the binary wire format" or "Protobuf the schema language" which changed over time here, changes to the Google's Go library caused it problems. It's like building a library that integrates with Jackson (a JSON library) and Jackson details changed in ways that added toil, versus JSON changing.
The amount things you can map in OSM is impressive. However I ran into two things that have no formal tags: time capsules (historic=time_capsule), and camera obscuras (camera_type=obscura). You can add the values, but they are not official. Time capsule is in the work [0].
reply