Live data from Hacker News

Ask HN: What are some unpopular technologies you wish people knew more about?

news.ycombinator.com

91–100 of 417 posts

Re: Ask HN: What are some unpopular technologies you wish people knew more about?

#91

Growing in popularity, but still not as famous as it should be: EdgeDB ( https://EdgeDB.com ) * Graph-relational database * Queries return objects linked to other objects through properties, not rows * ... But it's still Postgres under the hood * Open source

I’ve really enjoyed working with EdgeDB. I totally agree. I’m on a project now that’s using firebase/firestore and edge seems dramatically better suited, but it would be a hard sell.

Re: Ask HN: What are some unpopular technologies you wish people knew more about?

#95

Most people know about MediaWiki even if they don't realize they do, because it powers Wikipedia, but I wish more people used it for documentation. You can create highly specialized templates in Lua, and there's a RDBMS extension called Cargo that gives you some limited SQL ability too. With these tools you can build basically an entirely custom CMS on top of the base MW software, while retaining everything that's gr…

Like any documentation system, its success depends on its audience.

As an administrator, I wish MediaWiki had a built-in updater (bonus points if it could be automated).

Re: Ask HN: What are some unpopular technologies you wish people knew more about?

#96

Earlier quoted context omitted.

The value prop of Sphinx goes down a lot if you're not using reST because you can't use the extensive catalog of directives, such as the ref directive that I mentioned in my first comment. If you must use Markdown then there's not much difference between Sphinx and all the other Markdown-powered SSGs out there. In other words there's not a compelling reason to use Sphinx if you've got to use Markdown. From Sphinx's G…

Myst has parity with most reST features and is equivalent to markdown for users not using those features: https://myst-parser.readthedocs.io/en/v0.13.7/using/syntax.h...

Oh cool I need to revisit MyST then. I thought it didn't support cross-references but it looks like I'm wrong: https://myst-parser.readthedocs.io/en/v0.13.7/using/syntax.h...

I will have to dig into exactly how much parity we're talking here but if it's very strong parity then I redact my previous statement

Thanks for correcting me!

Re: Ask HN: What are some unpopular technologies you wish people knew more about?

#97
post #94

Turn your Postgres database into a REST API: https://postgrest.org Previous discussions on HN: https://hn.algolia.com/?q=postgrest

Wow; this is extremely nice for quick prototyping!

I use it in production. Handling roles and permissions in the DB is a game changer.

Re: Ask HN: What are some unpopular technologies you wish people knew more about?

#98
post #88

Sphinx [1] gets my vote. It's the docs system that powers most sites in the Python ecosystem so it probably looks familiar to you. I call it a docs system rather than static site generator because the web is just one of many output targets it supports. To tap into its full power you need to author in a markup that predates Markdown called reStructuredText (reST). It's very similar to Markdown (MD) so it's never bothe…

I've used Sphinx quite a bit, the syntax is a bit fugly. For markdown's [text](url) one uses `text `_ ...

irobinovitch just corrected me that the library that provides Markdown support for Sphinx supports the features [1] that I care about; have to dig into the details but if the feature parity is very good and you strongly prefer Markdown over reST then I would say... go for the Markdown!

[1] e.g. https://myst-parser.readthedocs.io/en/v0.13.7/using/syntax.h...

Re: Ask HN: What are some unpopular technologies you wish people knew more about?

#100
post #50

Nix package manager's `nix-shell` is something I wish more people knew about. Nix is gaining some popularity, but people often think of using it has to be a really big commitment, like changing your Linux distro to NixOS or replacing your dotfiles with a Nix-based one (using the Nix package manager). What I wish more people knew was that you don't need to do those things to get value from Nix. Create project specific…

It's good for a c or c++ project where libraries are very environment specific. But most modern languages have their own package/environment managers which makes Nix redundant.

Not really. I introduced it to our Python projects at work and it's been great. Partially because of poetry2nix, and partially because it makes it easy to include other stuff like a specific version of Redis for testing purposes. Everybody gets the exact same dev environment, reducing a ton of "works on my machine".
Post reply on HN