Just wanted to take the opportunity to say hello and thank you. I haven't really made anything in juce worth sharing, but for a couple of years I was deep in the vst swamp and tinkered a lot with juce. I learned a lot from it, got a very niche job thanks to it, and as a direct consequence have met some dear friends and made huge progress in my musical "career".
Is it better to learn that it exists through surprise, by way of an engine upgrade suddenly changing the behavior of the software you wrote while in the bliss of your ignorance?
> Is it better to learn that it exists through surprise, by way of an engine upgrade suddenly changing the behavior of the software you wrote while in the bliss of your ignorance?
The premise of your question doesn't work. If one person is going to learn about the option and a second one isn't, the better system for that to occur in is the one in which more people end up with correct behavior.
In this case, that means surprising the guy with existing (buggy) software; he'll have to fix the bugs. It means not bothering the guy who's starting a greenfield project. Neither of them will be subject to this bug.
The alternative, which you seem to be saying you prefer, is that the guy with buggy software should continue to have bugs, and the greenfield guy should also have bugs.
Which is the worse surprise, when you update your dependency during development and get a fault, or when a user somehow ends up with a fault because of the previous default?
... than by surprise, when you find your integer column contains "[object Object]"? Jokes aside, breaking backwards compatibility is obviously a non-starter.
Developing with sqlite isn't quite like developing software that generically works against an ODBC or JDBC interface with minimal tweaking. You probably will want to peruse the documentation.
Well there's always predictive policing, fully automated facial recognition, chat control surveillance systems, nation-scale fingerprinting, and location tracking via inference of arbitrary signals.
We've got army block, FSB block, technocrats, bureaucrats and oligarchs. The usual (more or less) story.
The real problem is - we don't have system that scales horizontally. So when Putin goes people will have to deal with the vertical system he created for himself.
The problem here is this "for himself" part.
For this system to work you will have to be a new Putin (at least for some time) and for this you will have to enforce your decisions and shape your new system. Top to bottom.
Best thing that can happen to Russian (realistically) is that the power will be given to technocrats.
They are not neccesarily more liberal, but they have real education, they do understand a thing or to about economics, open borders, sharing of knowledge etc.
They won't be able to quickly change Russia, but given some time they can reshape it step by step.
Alas - we have FSB and Army blocks, high level of corruption and millions of people who see people like Putin as the best choice. They don't need progress and responsibility. They need their empire back even if they are just peasants with serfdom included.
Kleppman[1] calls it schema-on-read (json, xml) and schema-on-write (typed columns in an RDB). I like it over structured/unstructured, it's a bit more specific.
I have an ipad pro from 2015, an apple pencil 1, and a screen protector that gives it a bit more friction. It's pretty good for the most part, but since it's my only apple product, it doesn't integrate well with anything else I use. OneNote seems to work on multiple platforms but I never got into it. I mostly use goodnotes, and they seem to have released apps for web and non-apple stuff (finally). When I used it the most, the only export I had was as PDFs to Dropbox, which was fine enough but removed any possibility of editing outside of the ipad.
Funny you should say that