337
top 50 comments
sorted by: hot top controversial new old
[-] 9thSun@midwest.social 43 points 1 year ago

Listen. I just don't like that they replaced glass with TV screens that show what's behind

[-] DarkenLM@artemis.camp 21 points 1 year ago
[-] DragonTypeWyvern@literature.cafe 25 points 1 year ago

They replaced glass with screens that show what they think the product is.

In stores run by the particularly stupid.

[-] Comment105@lemm.ee 31 points 1 year ago* (last edited 1 year ago)

The screens are there to play ads sometimes, and if you get there while an ad is playing, you either have to know the store and remember which screen the thing you want is behind, or you have to wait until the ad is over. Or you can go open every door until you find what you want. I prefer the latter because it makes the company have to pay more to cool their drinks.

If enough people do it enough, maybe it'll negate the advertising profits.

[-] i_am_hungry@meganice.online 39 points 1 year ago

Svelte my man, I barely have to read the docs, just guess how things should be done because that's how it would work in vanilla JS, and most often it just works.

[-] soeren@iusearchlinux.fyi 15 points 1 year ago

Svelte is very good. If I had to use a frontend framework I would either pick svelte or soldijs both are great.

[-] QuazarOmega@lemy.lol 2 points 1 year ago

svelte or soldijs both are great

What would you say is the most important difference between the two? I feel like I should dip my toes into Svelte, but I haven't had a reason yet

[-] provisional 7 points 1 year ago

Svelte is for if you hate React and like vanilla JavaScript. Solid or Next is if you like React.

[-] space@lemmy.dbzer0.com 4 points 1 year ago
[-] QuazarOmega@lemy.lol 7 points 1 year ago

HTMX I guess, lol

[-] QuazarOmega@lemy.lol 2 points 1 year ago

Never used React, I went straight to Solid, but I quite like vanilla, I mean, you'll always be using "vanilla" in some form or another

[-] Kalothar@lemmy.ca 6 points 1 year ago

Been a react dev for about 4 years now, I’ve heard good things about Svelte. But like from a career perspective would it be worth the switch now?

[-] mesamunefire@lemmy.world 16 points 1 year ago

It's good to play around with different frameworks from time to time, even if it's just to form an initial opinion on. I've been programming for 15+ years and the only constant is learning new things.

[-] Zikeji@programming.dev 4 points 1 year ago

From a career perspective using it enough to know whether you'd like to or be willing to work with it in the future is probably enough. Then when you're looking you know whether you want to apply for jobs focused on it.

On that topic I've been on the market and haven't seen Svelte mentioned a single time when searching, granted I've probably only looked at a couple hundred listings (most being WFH).

load more comments (1 replies)
[-] anti_antidote@lemmy.zip 2 points 1 year ago

Svelte is the way to go

[-] Dirk@lemmy.ml 35 points 1 year ago

I thought HTMX was a joke, but they're serious.

[-] soeren@iusearchlinux.fyi 14 points 1 year ago
[-] ledtasso@lemmy.world 9 points 1 year ago

and don't call me Shirley.

[-] ShortFuse@lemmy.world 5 points 1 year ago* (last edited 1 year ago)

C'mon, what's not to like about bonding every UI action against a remote server? What's a few milliseconds anyway? I'm sure it works fine over cellular networks. I mean, it works great on my dev machine! /s

[-] soeren@iusearchlinux.fyi 3 points 1 year ago

What kind of you UI action are you talking about? Most of the time you need data from the server and if you want have some animations with css it will be client side anyway also it's not like you cannot write JS. I mean downloading thousands of lines of js for some web framework over cellular does not sound better tbh.

[-] ShortFuse@lemmy.world 3 points 1 year ago* (last edited 1 year ago)

That's a strawman. I don't need 1000s of lines of JS to swap a UI. I can do it in 1 line with Web Components: oldElement.replaceWith(newElement). And those modules can be lazy loaded like anything else.

This is just DX in name of UX, which is almost never a good idea.

And maybe you're fine with throwing a server computation for every single UI change, but I'm not made of money and I much rather have stuff on a CDN.

[-] soeren@iusearchlinux.fyi 2 points 1 year ago

I think i missunderstood you I thought you were arguing for modern web frameworks. Nothing wrong with replacing elments with js and not sending it as a request to a server I would do the same for stuff that doesn't need data from the server. If you are really worried about latency you could throw your code in a cloudflare worker but I don't think it matters that much average loading time of websites on desktop is 2.5 seconds . So it doesn't really matter if the server is on the other site of the world latency will not be the biggest factor.

[-] shrugal@lemm.ee 25 points 1 year ago

I personally don't like the htmx style of coding. It often feels like having to explain what I want to do to someone else using only a limited set of custom words, instead of just doing it myself.

[-] soeren@iusearchlinux.fyi 17 points 1 year ago

I understand you but for me it's the opposite I am not bound to using js for everything and can just return html from the server like I want. Also everything else still works I can write js if I want to. Htmx gives me more words I can use in html not less. Also I can manage the state via the url and the server. In other frameworks I often had the problem that I was writing the same logic twice in backend and frontend.

[-] provisional 7 points 1 year ago

Exactly. Not everything needs to be a goddamn SPA!

[-] fidodo@lemm.ee 4 points 1 year ago

I just peeked at the docs and right off the bat I don't like how they have conflicting attributes like hx-get and hx-post. What happens if both are set at the same time? Why not just have hx-method?

[-] GissaMittJobb@lemmy.ml 13 points 1 year ago

Reject Web technologies - embrace native mobile app development

Compose feels like React but without the bad JavaScript parts, really pleasant experience!

[-] veganpizza69@lemmy.world 4 points 1 year ago

Ah, yes, let's have thousands of specialized apps, each with uniquely expiring dependencies and vulnerabilities, instead of one browser that can work with apps that are standardized for OSS, UI, accessibility, performance, inspection by humans and machines, and security.

[-] GissaMittJobb@lemmy.ml 6 points 1 year ago

Funnily enough, I've found JavaScript to be by far the worst offender for expiring dependencies and vulnerabilities.

[-] PaperTowel@lemmy.world 1 points 1 year ago

I love Compose, creating UI is actually fun. The whole ViewModel thing though I don't love

[-] GissaMittJobb@lemmy.ml 2 points 1 year ago

I love Compose, creating UI is actually fun.

It's a good time, for sure. That being said, I've stopped working with UI, and I don't really miss it. I still do some side projects in Compose though, and it's always way better than XML.

The whole ViewModel thing though I don't love

When it clicks, it's actually not that bad imo. I think the main problem is that Google aren't really explicit enough about how to leverage them effectively, and as such they can be pretty hard to get right.

load more comments (2 replies)
[-] MrPoopyButthole@lemmy.world 12 points 1 year ago

I'm good with my Vue, thanks. I hate React though. I can see htmx simplifying some things and being adopted by front-end frameworks. The same way improvements in HTML and CSS have been adopted.

[-] karmiclychee@sh.itjust.works 4 points 1 year ago

Fellow Vue enjoyer! I love Vue, it's so friendly. Maintaining a complex React app feels like getting dragged behind a truck down a one way road.

(Did you like my two way data binding joke there?)

[-] MrPoopyButthole@lemmy.world 2 points 1 year ago

Hello sane friend! You used your joke to great effect!

Did you like my useEffect joke haha

[-] orca@orcas.enjoying.yachts 2 points 1 year ago
[-] hackris@lemmy.ml 2 points 1 year ago

When you say "and", do you mean together?

I love Vue, first time I've heard of AlpineJS. From my quick searching, they seem pretty similar. What advantages does one have over the other? Thanks :)

[-] orca@orcas.enjoying.yachts 3 points 1 year ago* (last edited 1 year ago)

Ah, sorry, that was a bit confusing on my part. I use them entirely separate. Here are some real world examples:

Vue: new projects that will require multiple components, state management, etc.

AlpineJS: when I have a tiny project/demo that needs reactivity, or if I have an existing HTML setup that needs state management and reactivity bolted on after the fact (like an old site or something like that).

[-] ______@lemm.ee 10 points 1 year ago
[-] unreachable@lemmy.world 4 points 1 year ago

sveltekit: this is the way

[-] silas@programming.dev 3 points 1 year ago

!sveltejs@programming.dev

There’s quite a few of us :) Looking forward to Svelte 5.

load more comments (1 replies)
[-] marwwin@suppo.fi 5 points 1 year ago

I love HTMX ❤️

[-] dingleberry@discuss.tchncs.de 3 points 1 year ago
[-] Presi300@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

I don't really get what htmx is... does it make things like modals easier? Is it a full framework, or does it just add extra features to html?

load more comments
view more: next ›
this post was submitted on 25 Sep 2023
337 points (94.2% liked)

Programmer Humor

32600 readers
576 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS