I remember arguing to keep the word 'suicide' in due to breaking API changes it would cost to fix it. They made the change and it ended up breaking a bunch of modules and also was way more of a headache to implement. All because a word that is not a great choice.
That's messed up, seems they witnessed the python django community removing the word slave in reference to databases from docs due to it being a word with a weighted impact and said 'hold my beer...'.
Node.js - the JavaScript runtime with a flair for drama.
At some point in the future, maybe someone will come up with vaccines for developers that suppress gender characteristics so we can all go back to shooting down bad ideas without being criticized for being sexist, racist, or biased.
> Node.js - the JavaScript runtime with a flair for drama.
As stupid as I thought it was when everyone started blasting Ruby & Rails performance because of a poorly-reasoned Twitter article that should have been about choosing the wrong data stores, I was so glad to see most of those people leave the Ruby community for their greener pasture because it's so much easier to get work done without their constant, wasteful drama.
I actually love the domain driven work done in this release. I think it was a bold move from the team and breaks them even further away from Rails on EVM that people tend to think.
I have been bit so many times with trying to figure out where to put things like authentication/registration in a traditional MVC rails like app.
This is great for something like a public website. What about a situation where I want some of my users to only be authorized to view some of my data based on a set of rules I set in my backend application. Can Agolia accomplish this?
You could just as easily set up Solr/Elasticsearch locally and index your data for searching. It'll give you the advantage of being able to do more complex queries, faceting, grouping, stemming, synonyms, and things that you expect from a modern search experience.
Ever tried to code a robust Android app in Scala? It's a nightmare. Kotlin you just plugin and you can convert your source files very easily. I would agree syntax is not that much different but the compatibility is.
I learned how to program in the Rom Hacking scene and was involved with a team that released 4 patches for games.
The amount of dedication and hours our team put in was incredible. I think I managed around 30-40 hours with high-school.
Also, a lot of the reasons some games never made it stateside or came way late was often financial or political. The US versions of these companies often ran slightly independent from the Japanese game studios and the RPG adoption was not huge in the early console days here yet.
For number 2, you could expire them by encoding some identifier based off a hash or key tied to the user object. Change that object and have the server reject the token if that meta data no longer validates.
Or have really short lived tokens, requiring regular refresh, and don't worry about expiring them... you can then delete the refresh token so it can't be found requiring full re-auth if necessary.
OAuth2 + JWT is fine... just whitelist the algorithms you allow and use HTTPS for all communications, even internal.
