Django, doit, tailwind, vuejs with vite, postgres, redis, poetry, git and ubuntu.
I've tried many alternatives but every time things are just slower to dev.
This stack has a great balance between integration and flexibility. The only things that matches the django ecosystem is the rail/symfony ones, but ruby and php outside the web are limited. Js has diversity but integration is seriously lacking. Anything else is too low level which is not a good cost/benefit ratio for me.
Vite, vue and tailwind makes front dev fun again, postgres and redis can deal with everything without tuning up to millions of users and ubuntu and git are just easier to find tutorials for.
The impact is huge as I can actually focus on my value proposition for my client. They can ask me to add a cms, a weird service auth or some messed up ftp pdf generation workflow and I can leverage existing libs 80% of the way, with just enough custom to charge premium.
I end up twice faster, 3 times cheapers than my competition and yet my hour billing is very good and my stress at sea level.
We are talking about somebody who's company has been guilty of corrupting, lying, insulting, patent trolling, vendor locking, user spying, monopoly abusing, etc.
Yet after years of PR, he is now regarded as a hero.
So it's not unreasonable to think maybe he said it and later decided to rewrite history.
Even still, it's extremely unlikely. Unethical as he was, there's little doubt that Gates has an extremely good understanding of computers. And back then, memory limits were extremely tight and programmers ran into them all the time. Graphics and sound were a serious challenge in the DOS era.
Heck, Gates probably remembered the times where a framebuffer was discussed as a theoretical construct, that would be useful if only one could have enough memory to implement one! And at 320x200, that's 10% of your 640K.
jupyter does allow to produce presentations, and I used it with great success at conferences where a mix of slideshow and interactive programming suits the format perfectly.
But honestly it's only a tiny small part of what it's for.
jupyter is mostly about explorating ideas, code and data. It gives you a comfortable env to quickly try something out. Sharing it with other is just the cherry on the cake, not the main goal. I mostly never share my notebooks, but I will fire one as soon as I want to try a new library, or need to extract data from a file.
Such a wonderful tool, but hardly accessible to beginners.
First, you have to install it, which if you don't use anaconda is going to be full of the usual gotchas.
Then you need to launch it, which because "-m" is broken on jupyter for windows, means people will have an extra hard time.
And then, once everything works, new commers still have to understand they need to create a notebook before entering any python code, find it back in their weird FS browser implementation and get how to execute and create cells.
Not a problems for any dev, but in class, it can quickly become a burden. Thanks to pyiodine, you can now use jupyter directly in the browser with no install at all:
In a teaching environment, maybe it makes sense to use JupyterHub to give every student their own notebook in the browser. You can teach them how to set the thing up later, once they understand what the heck a kernel is and how the system actually works.
Sounds like it's intended for non-git-users to work on an existing git repo - editing docs, graphics, whatever and pretending it's just a bunch of files with no git - rather than particularly for a general purpose filesystem with git as automated backup / version history.
You could do that, but Facata works at a lower level, so for example you can use prepared statements, which SQLAlchemy doesn't support. Also, Facata has better performance and fewer dependencies if you only want to use raw SQL.
I get that Facata is a smaller dependency chain. I'm also curioujs about the performance side, what areas is Facata more performant in, and how was it measure?
That prepared statement caching is a feature of a particular DBAPI driver rather than SQLAlchemy itself. I take your point though, and I'd say that Facata is designed to be an alternative to DBAPI 2 rather than an alternative to SQLAlchemy.
On the performance, I'm basing this on the fact that SQLAlchemy does a lot more than Facata. You're right though, actual measurements would be interesting.
I've tried many alternatives but every time things are just slower to dev.
This stack has a great balance between integration and flexibility. The only things that matches the django ecosystem is the rail/symfony ones, but ruby and php outside the web are limited. Js has diversity but integration is seriously lacking. Anything else is too low level which is not a good cost/benefit ratio for me.
Vite, vue and tailwind makes front dev fun again, postgres and redis can deal with everything without tuning up to millions of users and ubuntu and git are just easier to find tutorials for.
The impact is huge as I can actually focus on my value proposition for my client. They can ask me to add a cms, a weird service auth or some messed up ftp pdf generation workflow and I can leverage existing libs 80% of the way, with just enough custom to charge premium.
I end up twice faster, 3 times cheapers than my competition and yet my hour billing is very good and my stress at sea level.