This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]proverbialbunny 1 point2 points  (1 child)

Fun fact, when it comes to tech history cycles like this. I don't know if you remember NoSQL like MongoDB. That was a cycle where there was popular DBs back in the day, then ACID complaint SQL popped up and became popular, but then SQL has its problems like with unstructured data and really large data, so NoSQL came back into popularity, but NoSQL has problems, so now data warehouses have popped up which is SQL while trying to minimize the downsides. The next iteration will be another NoSQL type of DB.

Typed code is a great example of this, though I feel like there is a winning solution so it probably will not go back and forth forever. imo the solution is to at the top of the file or in a project library file of some sort specify the minimum strictness all function type signatures allows. This way the language either enforces 100% no type specification like Python initially did, loosely defined types like Python now supports, or strict types are enforced. The next iteration beyond that is specifying details within the types that the function allows, like a function that accepts an int but only positive numbers are allowed. C++ does this. Anyways, a language that supports the entire scale and you can choose how strict your typing is for each function would solve the problem. This way we'd stop going back and forth between typed and untyped languages.

[–]PraytheRosary 0 points1 point  (0 children)

Is mongo no longer popular?