atsjie

I don't dislike that they at least want to see you in real life once tbh. I love ease of registration like anyone else, but with tax avoidance and all that, idk. Feels right to me to have at least seen yourself once.

A good way to push foreigners toward competitors and reduce any incentive to base you AI company in the US.

I wouldn't call that "easier" perse.

I'd call that bad pretty bad.

Without internet or AI I wouldn't attempt writing anything like that.

Is this enforcable in the EU? Not allowing a user to delete their data must be in violation of GDPR I imagine (although I'm no expert)?

the Postgres query planner is amazing

Let's agree to disagree.

It's becoming too complex, too unpredictable. Every query and variable becomes a surprise in production. It's too smart for its own good.

Always surprised me in the land of the "Free" they ban a whole lot more than in most other countries. Books, LGBT stuff, no objective media. It feels quite medieval.

These arguments become so vague to me that it just feels like an excuse for governments to do whatever they want.

Calling it "Grey zone conflict" feels like the "Deep state" shenanigans... It's primarily marketing to achieve your goal.

We've seen the invasion of Iraq; that was all based on lies. We got ISIS as a result... "National security circles" look for evidence so it fits their narrative. Like watching FoxNews. It's a very narrowminded funnel of carefully picked pieces of evidence. They are not truth seekers that aim to provide a holistic view of the situation. No, they are scared aged men who love to control the narrative and see danger in everything in the hope to get more funding for their next projects.

Btw; banning TikTok is a good thing, but for other reasons entirely.

From the article;

Today many web developers consider jQuery to be “legacy software.” With all due respect to this perspective, jQuery is currently used on 75% of all public websites, a number that dwarfs all other JavaScript tools.

I feel that is misleading. I worked on a lot of websites and none of them included jQuery willingly or sometimes even knowingly.

Either it's shipped as a peer dependency or we're talking about wordpress and the like which use it (and drives much of the web!).

I've seen it frequently shipped because of scripts embedded into a larger frontend codebase. Stuff they really don't want there to begin with.

I do not for a second believe that 75% of frontend dev work is in jQuery. In fact, I'd be surprised if it's more than 5% of all frontend engineering work is using jQuery.

Obviously some people might still use it for whatever reason; but those are a tiny majority (and probably quite vocal about it / over represented if they still prefer it).

So yes, to all intends and purposes I would claim jQuery is legacy software. Current usage (wherever they got that number from) does not mean it's still the preferred choice for the majority of web developers.

They are switching from sRGB to OKLCH.

First time I heard of OKLCH tbh. Anyone know if that is part of a wider adoption trend or is Tailwind pioneering here?

Looking at the examples it does seem to offer some advantages; but was primarily surprised that they now use it as a default.

Wouldn't that broken behaviour be a potential security issue by itself?

I do remember Go making backwards incompatible changes in some rare scenarios like that.

(and technically the loopvar fix was a big backwards incompatible change; granted that was done with a lot of consideration)

I will personally never use Copilot, or any other AI code generation tool, for the simple reason that I enjoy writing code.

This will sound extremely harsh; but I noticed I strongly favour colleagues who do use AI-assisted tooling over those who do not. The PR, documentation and code just looks cleaner.

So if it comes to who I favour working with; it's usually people who rely on AI-tools. They deliver code I like maintaining more.

No. Two charging points near my home but always occupied. We need more. It's stopping me from buying an EV actually since I can't charge it reliably.

Worked on two GraphQL projects; I was quickly cured from the hype. I recognize a lot of points in this article.

In both these projects the GraphQL had started small. I came in during a more mature phase of these projects (2 and 4 years). That's where the requirements are harder, more specific, and overall complexity has grown. Adoption and demand on the API were growing quickly. Hence you logically spend more time debugging, this is true for any codebase.

But GraphQL has everything in it to make such problems even harder. And both these projects had clear signs of "learning-on-the-go" with loads of bad practices (especially for the N+1 problem). Issue descriptions were much vaguer, harder to find in logs and performance issues popped up in the most random places (code that had been running and untouched for ages).

Fun fact; in both these projects the original devs who set it up were no longer involved. Probably spreading their evangalism further elsewhere.

RPC and REST are just more straightforward to monitor, log, cache, authorize and debug.

It's a bit of stretch to compare a side gig with someone becoming the CEO of a for-profit subsidiary.

My eyes hurt.

JSON RPC:

- Everything is a POST, so normal HTTP caching is out of the question.

- JSON RPC code generators are non-existent or badly maintained depending on the language. Same with doc generators.

- Batching is redundant with HTTP2, just complicates things.

- Because everything is a POST normal logging isn't effective (i.e. see the url in logs, easy to filter etc). You'll have to write something yourself.

- Not binary like Protobufs or similar

But yeah, "the silent pro's choice"... Let's keep it silent.

JSON RPC is pretty much dead at this point and superseded by better alternatives if you're designing an RPC service.

Wait, so unknown hyped tech X didn't work out and you went back to stuff that has been around for 30 years?

I'm shocked.

This makes sense to me. Thank you!

If they are the same, why hasn't Google been banned in Italy all these years?

There must be something fundamentally different between the two, and I'm not sure what it is.

I don't understand this? What is so different from ChatGPT compared to say Google scraping and storing the entire world wide web?

We stopped some devs in our project from adding too may TODOs and FIXMEs.

For good reason; the more TODOs and FIXMEs a codebase contains, the less impactfull they are. We had so many TODOs no-one every batted an eye when seeing them, and they never got fixed. It just made you feel bad.

Also a lot of TODO's expressed opinions about the "ideal" scenario, but in practice most of those TODOs were for code that was "fine" or "good enough". In those scenarios it's better to omit the TODO/FIXME keyword and just describe the design decision that was made.

I want the decisions I make to last decades, not just a few years

New to frontend?

The comments and community feeling in Youtube streaming sucks. Ludwig who made the switch a year ago from Twitch to Youtube said that was his biggest nuisance with Youtube, and I agree. I stopped watching him because of it since there's more fun to be had on Twitch.

Twitch is more like a bunch of monkeys which is fun and builds hype. Youtube is too serious and the chat is too slow for the streamer to properly interact with.

To countercomment:

- Softcore porn (I would not call it porn at all, search online for softcore porn and you get something completely different). You don't have to watch it and I never see it in my feeds, you have to actively search for it to find it. So I'm wondering how you notice it for it to be a problem? Yes; I'm calling you out.

- Ads: youtube has a LOT more ads, and a lot of twitch streamers don't do the ad program. So here too I'm not as convinced it's a problem, I definitely don't see many ads and usually if there are any the streamer is aware and takes a break or something so you don't miss much.

I agree, the days of chaining lodash functions together are pretty much behind us.

But I still like lodash, particularly for functions like these:

- words

- kebabCase / startCase / snakeCase

- partition

- debounce

Basically the more advanced functions for which no readily available alternative exists?

Fully agree. I always downsized my window to read a Wikipedia article (I use fairly large desktop monitors, but not a widescreen). The sentences were comically large making it really hard to see what the next line is.

Even in the new design they're still a bit larger than what I'd like.

I think it's fine, pretty clear what to do.

The user cannot press a wrong button, is not distracted by a whole bunch of fields and there is no ambiguity. Cognitive complexity is low throughout the registration proces.

My only two small points were:

- I miss some some kind of "progress" indication. Normally you see the whole form at a glance, now you don't so you're not sure how far you've progressed.

- The outline of the input field touches the button on the right. There should be a padding between the two.

But these are small points, overall I quite like it tbh. It reminds me of a CLI wizard, which seems fitting for Github.

(tested on desktop only)

It has a 4.6 rating which is good, especially if I can't recall ever being bothered by those automated rating popups.

I use it everyday and works fine, "some" might be a small but vocal group? Might not be representative for a common user.

I disagree with all three of you.

It depends on the use case.