warmwhisky

joined 1 year ago
[–] warmwhisky@lemmy.world 1 points 9 months ago (1 children)

The second link is not clickable. I see this a lot with different clients. Generally links are confusing and don't always work

[–] warmwhisky@lemmy.world 2 points 10 months ago (3 children)

How do you follow the link without a login for lemmynsfw website?

[–] warmwhisky@lemmy.world 0 points 10 months ago

That is wild! I like the more obscure AI images. So interesting

[–] warmwhisky@lemmy.world 9 points 10 months ago (1 children)

To reach people who missed it like me

[–] warmwhisky@lemmy.world 4 points 10 months ago

So interesting!

[–] warmwhisky@lemmy.world 3 points 1 year ago

Microsoft bought Google in 2028 and integrated Angular into their most popular wysiwyg IDE Frontpage

 

Hey fellow developers,

I just had one of the most mind-bending experiences of my coding life. I recently traveled to the year 2033, and let me tell you, the JavaScript world is a topsy-turvy place. I wanted to share this incredible revelation I had with all of you: React, Vue, and countless other frameworks have faded into obscurity, but guess who's still sitting on the throne? jQuery!

Yes, you read that correctly. jQuery, the tried-and-true JavaScript library from the early days, is not just alive; it's thriving as the number one JavaScript library in 2033. It's like the King of Pop from the '80s, forever reigning supreme.

Now, I know this might sound like a bizarre sci-fi twist, but here's what I saw:

React's Demise: React, the darling of web development for so long, had its moment but eventually fell by the wayside. The relentless pace of change in the tech world left it struggling to keep up. Developers were craving stability, and React's ever-evolving ecosystem couldn't provide it.

Vue's Quiet Exit: Vue, with its simplicity and elegance, had its time in the sun, but it too succumbed to the ebb and flow of trends. In 2033, Vue is remembered fondly but has become a niche choice rather than a mainstream powerhouse.

The Ever-Changing Landscape: Over the years, we've seen a multitude of JavaScript frameworks come and go. Some were brilliant but short-lived, while others left developers scratching their heads. The tech world is a wild ride, my friends.

The Unexpected Survivor: Amid this whirlwind, jQuery not only survived but thrived. It's like the ultimate comeback story. Developers in 2033 appreciate jQuery for its simplicity and reliability. It's like a comforting old friend that's always there when you need it.

So, why is jQuery still reigning supreme in 2033? It turns out that sometimes simplicity and familiarity are what developers truly crave. In a world where new frameworks pop up like mushrooms after rain, jQuery's stability and ease of use make it the go-to choice for a wide range of projects.

I never thought I'd live to see the day when jQuery would make a comeback of epic proportions, but here we are. It's a reminder that in the ever-evolving world of web development, sometimes the old can be gold.

What do you all think about this wild glimpse into the future? Would you ever consider going back to jQuery if it made a resurgence like this? Let's discuss! 🕰️ #jQueryRenaissance2033

[–] warmwhisky@lemmy.world 4 points 1 year ago

Please do post more mature AI gens. The whole topic is fascinating

[–] warmwhisky@lemmy.world 1 points 1 year ago

I find this issue really frustrating as you lose your place. Couple that with the content layout shifts after images load and you're lost

 

When tapping to view an image and then scrolling up to close it, the very next scroll down sometimes scrolls super fast down over maybe 10 posts.

Is there a gesture that makes it scroll super fast that I can turn off?

[–] warmwhisky@lemmy.world 7 points 1 year ago

Yes Trillian. I remember that now

[–] warmwhisky@lemmy.world 4 points 1 year ago* (last edited 1 year ago)

Same here. It happens if I use it for more than 20 minutes or so. Entire system ui crashes and freezes everything... no touch screen response or buttons work. Clearing cache makes no difference. It still crashes after being cleared

 
view more: next ›