Sorry, I'm gonna be that person.
*What. It should say What it feels like.
this post was submitted on 27 Sep 2023
304 points (93.2% liked)
Programmer Humor
31812 readers
450 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
Thanks English is not my native language.
Just for the sake of information, the two common ways to put this in English are "How it feels" and "What it feels like". The former phrase is just descriptive, so it doesn't need the "like" at the end. The latter phrase is comparative to another thing, so it needs the like. Also this is something that native speakers mix up all the time, so don't worry too much; your English is great!
Thanks for the explanation.
Der Name Sören ist definitiv ein Hinweis darauf :D
Eventuell
You can edit titles
Technology we could never dream of on Reddit
Or "How it feels"
I feel like there's been a gradual increase in people saying things like this ("would of" instead of "would've", "apart" instead of "a part", etc)
load more comments
(4 replies)
i found out about htmx just yesterday and I was blown away. i think it’s an amazing idea, really
for small projects that you want to make in less than an eternity it should be very convenient
I don't get it. In my opinion React is like the worst of the bunch...
When it came out in its time it wasn't bad compared to the alternatives. Now there is certainly better, but honestly it will still take a long time before we can choose a standard.
Could you elaborate?
Well, I have worked with two of them React and Angular. Now working with React. And the further the project goes, things just get messy, and I mean really messy. The concept of everything should be a small function is in practice not true. No dependency injection(I know you can bolt another library on top of it, but really?). The testing is a pain, it gets harder and harder to test isolated functions. Custom tags, attributes that look like the standards that are documented at MDN but are not. And most info I can find online feels like elaborate propaganda. I mean there is just nothing against React to be found, really nothing. That's just not possible in IT.
I agree, React sucks. Been using it for years at work.
I'm gonna tell your boss you said that.
Oh he knows 😂
Thank you for the explanation, so do you think angular is better? I want to start doing front-end and I don't know what to pick
Angular is different from React, totally different. For one it's a framework. React is a library. People tend to say Angular is harder to learn then React but I totally disagree with that. I personally found Angular really easy to learn, especially if you look at their documentation at https://angular.io/docs you just need to work through it, step by step. This is not the same with React, again my personal experience. In Angular you have common concepts like observables, subscriptions, dependency injection, separation of concern's, and not to forget functional programming with RxJS. And the documentation that you can find in MDN about html, css, javascript is then also complimentary to it. Overal I found Angular to be a cleaner environment to develop in. And testing is so much more concise.
Anyhow, don't focus on one library/framework. I would even say learn the basics like what you can find on MDN, javascript, html, css, typescript. The rest is always framework/library specific. Let the job decide what you are going to learn first. You know programming, that's great you will learn the stuff they use on the job and in your free hours ;) In my experience you will have to change anyways. For example I have worked at companies, government and private. Where one uses JSP!!!(in 2022, not it was not a government organization) Then Angular, then React.
load more comments
(1 replies)
React is awesome. Sure it has problems but what doesn't? It's easy to learn and JSX is great. I would try Next.js, Remix.js or just use Vite. Personally I'm trying out CT3A but that's a bit on the edge (and uses Next). There are a lot of jobs with react out there and it's a joy to work with imo.
Vue is supposed to be easy but I had a hard time with the initial learning curve. The community seems much smaller too. I have heard good things about Nuxt though.
Angular is robust but the hardest of the bunch to learn based on popular sentiment i've heard.
load more comments
(2 replies)
Look at your local job market, where you want to work, or what you want to build to determine what to learn.
No point learning any tech unless it aligns with the problem(s) you're trying to solve.
Doesn't matter what an internet rando thinks, there are more React jobs at the moment. I've only seen Angular used by large enterprises for internal BI apps, which are harder jobs to get.
Yeah I'm not basing a life choice on a rando, but it can help to hear his motivations. Once I have that I can draw my conclusions.
Thanks for your input too.
load more comments
(1 replies)
load more comments
(1 replies)
load more comments
(1 replies)
I have tried some angular, threw up when I looked at JSX so skipped React and do a lot of Vue, Vue is by far the best of the 3. especially 3 with reusables and better TS support.
That was my experience until I tried Svelte. I loved Vue but didn't like the transition to Vue 3. When I tried Svelte it blew me away and I never looked back.
I... kinda find htmx to be better than all other options.
It is
Depends on the use case tbh, but it's a good choice in a lot of cases.
maybe some want to read this: https://www.thoughtworks.com/content/dam/thoughtworks/documents/radar/2023/09/tr_technology_radar_vol_29_en.pdf
I did not know about this, I'll take a look at it once I'm home. Thanks!
load more comments
(1 replies)
I was genuinely confused why people were talking about xhtml again this year.
PHP sitting in the corner, off screen
PHP is powering a LAMP
I replaced the P in my LAMP with Python
I’m confused as to what PHP has to do with JavaScript front-end frameworks.
Was it just for a quick laugh and a jab at PHP because it’s an easy target or have I misunderstood that these all use JavaScript
I’m confused as to what PHP has to do with JavaScript front-end frameworks.
PHP deserves honorable mention here as the "it's not stupid if it works" of the JavaScript framework world. Everything* JavaScript frameworks can accomplish can also be done (much worse) with static HTML delivered by PHP.
*Please no one give me examples that cannot be done without JavaScript. Trust me, I know. But any business requirement can be met with plain HTML if you really deeply hate your end users enough.
what PHP has to do with JavaScript front-end frameworks.
Everything. Sitting in the corner, munching and handing out cookies to people who don't want any.
load more comments
(1 replies)
load more comments
(3 replies)
Angular can go to hell.
What's wrong little man, can't handle a little boilerplate?
So...dense... Can't... Move...
I'm still on DHTML, ActiveX, and SSIs
Alright, have to ask: what are those icons?
I think I know Vue and Angular.
What is the S? And what is the atom like thing on the left?
react vue angular svelte htmx
My stupid brain thought the s was squarespace.... And now for our sponsor...
I think, Svelte should not salute to React (anymore). Not sure what htmx brings to the table, but Svelte should be doing the same like the Penguin labeled "htmx", because it really frees devs from doing too much stuff to get started and produces fast webpages on top of that.
view more: next ›