The real question is: why is the default Windows search so terrible? Did Microsoft make it useless on purpose?
`ALTER TABLE books ADD CONSTRAINT fk_books_author FOREIGN KEY (author_id) REFERENCES authors (id)`
Which is not valid in SQLite (https://www.sqlite.org/lang_altertable.html)
Remote: Not needed
Willing to relocate: No
Technologies: C#, F#, dotnet, Aspnet core, CSS, JS, HTML, react, SQL, efcore, nodejs
Résumé/CV: Will be provided upon request
Email: Use the email on my profile, the email I posted here is now getting tons of spam
I have about 8 years of experience in software dev in total, looking for a non-senior position.
Not quite related: I never heard of clawdbot before, so, I guess TIL that's the bot my website keeps getting requests that are obviously malicious from.
That said, I haven't tried getting the same kit working on windows so I can't say if it's any better.
Their moat, for now, makes this possible.
If Microsoft discontinued Windows and switched to just providing web apps, the competition would be a lot stiffer.
ATM windows still has enough of a moat that they can comfortably do the former.
*Yes, they probably make more revenue in Azure or Office365 licenses but at least when I think “Microsoft” I immediately think Windows.
We tried “typed” strings like this on a project once for business identifiers.
Overall it worked in making sure that the wrong type of ID couldn’t accidentally be used in the wrong place, but the general consensus after moving on from the project was that the “juice was not worth the squeeze”.
I don’t know if other languages make it easier, but in c# it felt like the language was mostly working against you. For example data needs to come in and out over an API and is in string form when it does, meaning you have to do manual conversions all the time.
In c# I use named arguments most of the time, making it much harder to accidentally pass the wrong string into a method or constructor’s parameter.
https://fsharpforfunandprofit.com/posts/designing-with-types...