Watch the prisma video by primetime and you'll see the true horrors that lurk beneath the shiny thin layer of improved productivity when getting started with it.

Funnily enough, the reason i got saved from making the mistake of using prisma was at the time it wouldnt compile in my env (not sure anymore why, i think it was alpine on ARM) and i was like THE FUCK U COMPILING FOR?!? Scared the shit out of me as it should :D

Snowflake culture is a really useless pain in the ass. People always feeling descriminated - often even on behalf of others is just stupid. Focus on real problems.

Hating GayPal doesnt mean hating my gay pals.

Yes, PayPal is cancer and should die in a fire. Download Revolut and use single-use debit cards. Can't really get safer than that - and you don't have to support the 4% fee-gouging and account-locking paypal mafia.

@vedmant separation by what you call functionality is something i would consider an antipattern, just like when people thought it's a good idea to keep the css as far from the html it affects as possible.

Stuff that interacts the most should be closest to one another. So a few computed, a ref and a watch that all handle a certain part of the functionality should be together, not separated because they are different types of stuff.

There is also JSON5 which tries to be a bit less verbose without being so lax as to create weird behavior.

YAML really is shit though. I write my CI config in JSON, and have a script to convert to .gitlab-ci.yml (and do a bit of proprietary variable replacement etc.)

And im much happier now😅

@LotsOfCaffeine then don't fucking use it?! And events do invade your privacy. For many concerts for example you agree to be photographed and the image used for promotion. How is that ok and tracking not? Both is invading your privacy for profit.

@Fast-Nop And i post with a nickname because sadly nowadays people get canceled for small things. I know however that i can be doxxed any minute, and it's a risk im willing to take. And if the owners of this site wanted to scrape the everliving shit out of my data, in return for
- free usage of the site
- free stickers
- free stressball
I would support them on that 100%

@LotsOfCaffeine you already get a free site from them, so don't be entitled. You wouldnt go to a free event/attraction (privately financed), and make demands would you?

@Fast-Nop i'm not anti privacy in general, i just think "Hausrecht" for site owners is more important. Also, the privacy that is important for me is one that i will never get because of things like "Vorratsdatenspeicherung" by providers.

I'd rather have my data scraped and analyzed by google or FB instead of the governement, for the simple fact that what they are trying to is make money... And i even get a service in return. And i can choose not to use it if i don't want it.

@Fast-Nop true, i overread that before (and didn't know it). Then again, why is that so? Exactly, to prevent tracking. So just another thing going to shit in the name of privacy.

@Fast-Nop bye bye caching though... Which does make sense when every second site uses Roboto. Then again, it's true these 100kB probably won't kill anyone, and in turn you save some tls habdshakes

The main problem with GDPR is that it forbids choosing arbitrarily who can use my service and who can't. I think disclosing what I do with the data my users provide me with is good and should be common sense. But if i view data as some form of payment, if my business for whatever reason doesn't work (as good) without it, or if I simply don't want my analytics to not have the full picture, then i should be able to tell said user to fuck right off. My site, my rules.

It's like saying the restaurant has to serve food even to customers that don't pay. It's just not fair. And i know most privacy advocates don't care about that because they think it only affects the big evil G and F. Well, they're gonna see that like with everything (laws, taxes) it sooner or later mostly affects small businesses and consumers.

@LotsOfCaffeine they don't NEED it, they want it. And it should be their fucking right in exchange for a free service. If you don't like that install pihole.

@NotJeckel they claim it also applies if you have EU customers. Ofc enforcement might be complicated (not where i live though, as switzerland couldn't possibly crawl farther up the EU's ass without actually being a member than it already did)

GDPR is one of the most retarded laws anyways, and people still don't understand that all their beloved "free" services are gonna cost more in the future because
1. Ads simply don't work as good if you can't target them with orwellian scripts
2. Trying to achieve GDPR compliance will cost a fortune which in the end the consumer pays
3. GDPR compliance is hard to get right, so companies WILL fail, they WILL get fined and they WILL pass that cost on to their customers.

@spongegeoff if you version control your stuff properly deploying with FTP probably isnt that bad. But what you probably don't have and actually helps is blue/green (or just preview) deployments. And that's worth a lot.

But honestly there is some truth in this, if your projects are small (and few) enough that you don't really need ci/cd, then it's maybe better not having it. Cause it also adds complexity ofc

If PHP stays or not i couldnt care less. But WP has to die

It's funny how so many people rant about disabling text selection with wrong interpretation on why it's done. Like @vintprox said, disabling it for content is mostly stupid.

But the reason it's done is because if you have clickable things on your site sometimes text selection sometimes randomly gets fucked and makes the site look absolutely horrible. Especially if people click and drag or click and scroll for whatever reason.

Same with disabling zoom - sometimes iOS safari zooms in massively when focusing a form field for no reason whatsoever. Things like this are what makes it the "low effort, good enough for 90% of users" to just disable the features.

@stackodev noone will make it. Because it simply cannot and will not ever work. The idea that we can build a website without code that is responsive, has custom features and these features don't fuck eachother up is just unrealistic.

Plugins handling a wide range of different but connected tasks is an idea that just cannot work. And if you don't need/want that THEN there are alternatives. Pure page builders that is. That can work.

"Just" move to hetzner

@sleek what did you use before?

Takes time to get used to it ofc. But vue3 is sooooo much better.

Why even use jira? Gitlab/github issues have most of the useful functionality - and way less stupidity. Jira only supports one assignee for example... Useless piece of crap.

Tax brackets are a fucking scam anyways. They sell it to the people as a way to tax the rich more (which ofc is popular with the 99%), but in reality:

The poor pay little
The middle class pays a lot
The rich circumvent it and pay less than the poor

Also, why should we even want to tax the rich more %? I mean ofc they should pay more, but shouldnt the percentage be the same? Which would basically mean for 20% tax "you work 1 day per week for your country".

Such a system would also be way simpler to calculate: you pay 20% of your income. Farmer? 20%. Selling stocks for Profit? 20%. Hooker? 20%. And imagine the saved time/money in administration in companies, the IRS and people's tax returns.

But that will never happen, because once someone is powerful enough to do sth about it (politician) they more often than not actually profit from the current system with many vulnerabilities to pay close to 0. fuck'em!

My opinion as an employer: continue. The thing is, you won't actually help them much by telling them. They suddebly can't justify paying you a fulltime wage - so they won't, even though they would feel bad about it if they are decent.

At some point your scripts don't work anymore for whatever reason, and they will have to hire a programmer again. So the whole thing repeats.

Just make sure you don't rely on it only being a few hours too much, because requirements can change and you should still be available to help with other problems as they arise...

@Xoka which makes sense, because the whole "return response and error to callback" in JS was a big clusterfuck anyways. Errors are meant to be thrown and not reduced to just another parameter that fucks up everything when nit explicitly handled.
Also:
await Promise.all(foo.map(fnThatReturnsPromise))
Is short, readable and can be used with try catch in a way that mostly makes sense.

Yes a .then makes sense here and there but dismissing await as a whole? It's the first time asynchronous stuff in JS doesn't look like someone shat in my editor.

@IntrusionCM but for what? Scraping as a Service?

Lmao, you know you done fucked up when someone comes along, replaces your Website with WP and it's actually smaller, faster and gets hacked less frequently.

With all my hatred for WP i can only be amazed what kind of pile of shit the other website must have been :D

Let's just stop all this complicated crap with sich days, paid vacation, unpaid vacation, personal leave, 13th salary (dunno if other countries have it) and hire people hourly. Just xx$/h without deductions. No overtime compensation calculations, fuck all this crap.

Just: this week i worked 40h, so i get 40*xx$! DONE.

@JS96 just storing a difference should work, right? You can even use the difference between current and last sync difference to guess the drift and correct timestamps before syncing.

Also, can you not just run your own local ntp server? That would be the most sensible solution.