microblog VS CppCoreGuidelines

In this blog, we're going to address the "on any website" part of a Search Solution. Or at least - propose a starting point for it. There are many great tutorials out there for a deep dive on Flask - one of the best from my colleague Miguel.

- https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial...

If you'd like to deploy a web app, Flask is your best friend. It's very user friendly and there's a lot of great tutorials online. The only thing you'd need other than Python knowledge is some basic understanding of HTML/CSS and Jinja notation for variables, both of which are pretty intuitive to learn. Good luck!

I can't speak highly enough of Miguel Grinberg's work with Python/Flask (https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial...) and the community he's created around it, for both beginners and advanced folks.

Racing through his mega tutorial was a great refresher for me on the fundamentals, and it's easy to plug in computer vision & related libraries/extensions/packages.

Use miguel grinberg’s tutorial https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-i-hello-world

I got a recommendation (from a few places) to use Miguel Grinberg's microblog series to help me get up to speed on some flask things. I'm on ch 15 with blueprints, and am running into pylint cyclic import errors, both on my app and in the actual project (https://github.com/miguelgrinberg/microblog/tree/v0.15?search=1)

In the project root directory create a folder called static with one subfolder called js and another called css. The js folder will contain all of the needed local JavaScript files while the css folder will contain all the CSS stylesheets. In the js folder create a file called index.js and in the css folder one called style.css. Just leave them empty for now. If you want to find out more about web development with Flask I suggest you try out this tutorial. Your current project structure should like this:

https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-i-hello-world is not perfect, but a great start.

If you aren't aware of the c++ core guidelines[1] - it should be on your radar.

Also, it might not be a popular opinion, but I think Bjarne's books are just fine.

A Tour of C++ (3rd edition) [2]

Principles and Practice Using C++ (3rd Edition) was just published in april 2023 [3]

[1] https://github.com/isocpp/CppCoreGuidelines/blob/master/CppC...

You need to talk to Bjarne and Herb...

"C++ Core Guidelines" - https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines

In addition to the other comments -

TypeScript deliberately takes a "good enough" approach to improving JavaScript, instead of designing an ideal but incompatible approach. For example, its handling of [function parameter bivariance](https://www.typescriptlang.org/docs/handbook/type-compatibil...) is unsound but works much better with the existing JavaScript ecosystem. By contrast, a more academic functional programming language would guarantee a sound type system but would be a huge shift from JavaScript.

By analogy, Herb Sutter is arguing that something like the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines), with tooling help in this new Cpp2 syntax, can bring real improvements to safety. Something like Rust's borrow checker would bring much stricter guarantees, backed by academic research and careful design, but would be incompatible and a huge adjustment.

https://www.youtube.com/watch?v=2olsGf6JIkU

Take a look at Effective Modern c++ by Scott Meyers and the ISO c++ core guidelines. These resources are great for learning how to write better, more modern C++. I don't think it would be hard to grasp if you're already familiar with the language, just make sure to actually write some code which makes use of this stuff, otherwise it's easy to forget.

Look to the C++ Core Guidelines. It's not perfect, it has some flaws, including some sabotaging advice apparently adopted for political reasons. But at least it has some C++ authorities (Bjarne and Herb) as authors.