02020202

> Or you can use it in whitelist mode, but with all things like Cloudflare and ReCaptcha globally whitelisted.

those two specifically are always the first entries in my blacklist :D

i prefer kvdb-backed grpc for messaging to these pubsub projects because there is always some caveat. either it has at-least-once delivery or at-most-once delivery and other times it will disconnect clients if they are too slow or producers are too fast. there is always something. so tailor-made solution works out the best for me. easy and fast to write. works as one wants it to work. and with go, it's a piece of cake and also part of single binary, no external dependencies.

Depends..without context this question has no meaning...

Anyway, speed-wise, go will get you further faster.

Job-wise, go will get you way mor opportunities.

Performance-wise, rust will be always faster, no way around that.

Future-proof-wise, go, no contest.

Popularity-wise, go, hands down.

tl;dr rust is very niche, low-level, performance-oriented language and should be used in such use-cases. Anything else, Go will do better.

hm, no word on performance comparison with badger, bolt, moss, pogreb, pudge...

"I’ll come work for you because you have the Glenlivet 17 and not the 15" ... obviously not a whisky drinker :D ... nothing against Glenlivet but come on :D

i guess i am still unaware of these issues since i am still using glide.

Rust is the language that everyone loves to talk about but no one really uses.

I use only yaml for humans and json for machines. i see many projects that use toml but i just hate it. maybe toml is not bad itself but i have never seen project that would have toml config really human-friendly. it always loks like a retard-child of some ini monstrosity. yaml all the way, hands down.

there are few alternative OSs already, they could have just promoted one of them, like https://lineageos.org

nevertheless, the more competition to google the better.

i have worked a full-time job one year in my entire life. after that always part-time. part time sounds bad but it's just you leaving the office at 1pm(or however that works out for you). it is the best setup and i have been working like this for over a decade. i prefer to work from office but it is not easy to find local companies for this setup and either way you have to be a self-employed entity. so i rented a desk at my previous job and worked from there for other companies, part-time, for many years. now i work from home since i have not found suitable alternative for my office since the company have moved to new space. but now i work on pre-paid hours, credit-like system, if you will. and have no schedule whatsoever. client pays me for certain amount of hours, upfront, and then as i work i just work up to the amount of hours i got paid. nobody is looking over my shoulder, nobody is giving me deadlines. when it's done, it's done. best setup, bar none. but ymmv. i charge enough so i can work hour or two a day if i want. i could make a bank if i would go do a full-time gig again and i have been thinking about it, for a year, to save money but i have not found interesting jobs so yeah... it is a individualistic lifestyle, not suitable for everyone. but as i have said, you can rent a desk at a company you know people from or something like that, so you are with people and not alone all doy long. i would not recommend corowking spaces at all though. that's the worst setup i can imagine.

no. php is perfect as it is and always was. php got bad name because it was the first language most programmers started with..before javascript became the language of the web browser. so with larger user base you will get more bad programmers, hence the language will get bashed more. since php is not stirngly typed you can end up with really bacode, but it will work so the bad programmer syndrome is constantly fueled by bad code written by bad programmers :D .... to this day it is the most used and most performant interpreted languge and it is still de facto the languge of the web. in other words, php became a victim of its own success. remember before type script how people hated javascript, and still do to this day? well, php is not typed language so amateurs that cannot write a good code if their life would depend on it and the ivory tower armchair java/c#/.. warriors will be always bashing it. but php itself is great. absolutely nothing wrong with it. if you don't like it, don't use it. the language is not the problem, the people are, as usual. there is plenty of alternatives so instead of complaining, people should just stfu and move on.

personally i have moved to GO some years ago after over a decade with php. not because i had enough of it. no, i love php. but there is no money in web development anymore. so i moved to a compiled languge and do purely backend and less web/front oriented stuff, which i always preferred anyway.

though before i left php i remember that i was getting interested in parallel computing and Go had goriutines which served me well. php was getting the reactphp, swoole and other projects at that time but i decided to change the direction so even if it would work for me at that time, now i do more lower level stuff that php would not be suitable for anymore anyway.

Not AHA moments, but some pointers:

- most tech is stupid simple, like retard levels of simple, with incredibly complex description

- SOA is stupid and monlith is always the way to go(maybe with handful simple microservices)

- microservices are not SOA

- event sourcing is almost never a good idea

- raw bytes over the wire or in storage are not as complex and mysterious as you might think

- compiled languages are not "smarter" than interpreted languages, don't feel like you are lesser of a programmer if you do php or javascript

- new cool and shiny tech is cool and shiny for 5 minutes, until you implement it, then you realize it brings a ton of new complexity and a ton of wasted time and you should have stayed with what worked before and you realize the people who promoted it were just trying to make a sale

- mysql/mariadb will handle way more than you think

- if you want to waste resources, use java/jvm

- yagni should be tattooed on every programmer's hand so when he types on the keyboard he is constantly reminded that he is wasting time with stupid crap nobody will use

- don't think in "what if" terms or try to predict the future, just code what is needed right now, avoid being a smartass

- you can charge more for your services the more essential you are for the project and the harder it is to onboard new people, ie. your value increases over time

- if you charge less now, you will get paid less tomorrow

- running your project entirely in cloud will bankrupt you, use it to gather usage data, than move to bare metal. cloud is cool and "in" but it will eat your wallet, for no good reason whatsoever

- single binary is always better than docker

.. i could go on and on...but thesre are more guidelines than aha moments so that is it for me.

they are brok AF. someone needs to pay for the litigations they found themselves in by censoring their own creators before they go under. lol. only dumb mofos pour they money into this black hole.

Google Ads is the biggest financial scam in the human history to this day. Misandry Today made a video on it last year, i think. Worth a watch.

there are 5280 feet in a mile, because there are 8 elbows in a foot and 52 inches in one knee. don't you see? it makes perfect sense.