So true...

FUCK... THIS WAS JUST THE WORST WEEK I'VE EVER HAD IN MY JOB. LITERALLY WANNA JUST THROW MY DESK TO MY BOSS AND THEN CLEAN HIS BLOOD WITH HIS LAPTOP COMPONENTS AND THEN SELL THEIR ORGANS TO THE BLACK MARKET, USE THAT MONEY TO BUY A MACHINE GUN AND USE IT AGAINST THAH GODAMN CLIENT...

Isn't that a great way to comment on visual components?

Made a app in react native when it was on .42 version.
By the time I finished developing it, react native was on .54 version with many components had deprecated.

Ffffffffffuuuuuuuuckkkkkk!!!!!!!!

Facebook why you make changes so fast.

*Crying in corner*

A friend of mine has a PC that was overheating. His solution: Dumping the entire mobo and components in a box with Olive oil.

Pros:
+ Decrease heat by 15℃
+ Low cost solution

Cons:
- Hard to maintain components
- Dust can't be cleaned from the box
- House smells like an Italian kitchen 😂

Radio Shack store closed near my house. Had a huge fire sale. Electric circuit components were 90% off.
My wife thought I'd gone insane when I got home with two huge bags full of LEDs, resistors, switches, IR sensors, photocells, capacitors, bridge rectifiers, a spare breadboard, a pair of helping hands, etc.
My only regret is that I didn't catch the fire sale in time to grab all their Arduinos.

Me, doing ui design: 'hm, i feel like jumping into machine learning right now'

Me, writing a ml chatbot: 'but what if i extend flutter with my old custom android components'

Me, porting java components to dart: 'hold on, p5js has vectors, i could make a physical simulation'

Me to me: 'why are you like this'

Cool. 300$ in Google Cloud credits. Maybe I can get to one of those cool projects I’ve been wanting to get to.
spins up server
installs npm
installs mongo
installs express
installs vue
installs material design components
makes title bar and navigation

*okay, good enough for now, i’ll come back later*

*never gets around to it, and 300$ in free credits get exhausted by server running 24/7*

Me: *spends 4+ hours refactoring existing spaghetti, ensuring components are modular, easier to test and fault tolerant*

Project manager: ...

Also me: *adds pre-loader image to register and login buttons when user submits form*

Project manager: *All excited* Awesome work. 🙌That's some nice improvement..

Like wtf dude 😳..

My takeaway: These noobs only care about what they can directly interact with

My boss now has me writing an angular app but I'm not allowed to reuse components. The retard level is over 9000

Coding destroyed my life. I used to be tripping and seeing flowers，now i feel like media breakpoints，i used to dream about jungle，now i dream about creating components，i used to have a few problems，now i have nothing else but problems，and here i am at 7am ranting for the first time on a nerd application which i didnt get the rants about... But now i laugh...

Where is this going????

Monday : SSD dies
Thursday : HDD dies, so I take one out of the laptop to have a working pc
Today : Said HDD dies

Due to lack of hardware components for my pc to kill off, my current setup consists of 1 usb for live system and two more to act as storage

Next paycheck can't come fast enough

Arduino, all the way...
I have a burn out for 3 years and a few months ago I found arduino.
Burned lots of money in components in the first months because I got so addicted.
No regrets, helped me a lot, been learning a lot and keeps me focused.

"Quality CSS" is much a fucking misnomer. As someone whose been writing this shit at scale for 15+ years I can tell you all CSS code is garbage. The only thing you should do is make sure you don't have name collisions. Classes/components are self contained. And use variables when possible. DRY makes sense usually, but if you're dogmatic about it you shoot yourself in the foot.

This was posted by the largest German railway company "Deutsche Bahn". Rough translation: "Today's quiz photo shows modern fiber optic networks as part of our control center components - who knows what their purpose is?"

That explains a lot. Someone should tell them.

The brief history of Facebook open source:
- FB releases React under an oppressive licence that tells "woopsie, can't sue FB if you use React"
- a lot of money goes into making React popular to gain leverage from mass adoption
- VMware bans React in their company
- FB releases Flux to bring state management. It flops. Replaced by what some Russian student wrote in several evenings (Redux)
- Preact is released. It's faster than React, and it has MIT licence. Vue beats React in GitHub stars.
- Under mass pressure, FB changes React's licence to MIT. Initial plan to gain leverage fails spectacularly.
- FB releases Flow Types. It flops. Replaced by TypeScript.
- FB releases their own app market for React Native. It flops.
- FB releases Relay. It flops. Replaced by Apollo.
- FB tries to push React.Suspense for the whole JS landscape to obey and comply to how it works. Community says "Fuck You".
- FB releases react-native-web. It flops.
- Web Components are out in all browsers, adopted as a standard. React doesn't support them.
- Google releases Lit, a virtual DOM framework on top of Web Components to fuck with React. It's a massive success.
- React 18 is out. Still no Web Components support.
- (you are here)

> An update is available
> Installs update
> Update failed bc of corrupted system components
> Random bluescreens
> Sfc /scannow
> Can't scan because there is one pending repair
> Restart
> Does everything except repairing
> Recovery mode
> System integrity check failed
> Reset Windows
> Reset failed bc of "some" problems
> Media creation tool for bootable USB
> Tool fails to write image
> Media creation tool on another pc
> Successful
> Install Windows
> Missing drivers, cannot install
> Wipes hard drive

Fuck you Microsoft

I hate React.js with a fucking passion. It sounds great on paper, but once your project gets any size. The mental recursive loops of passing data around is insane. Not to mention keeping consistency a cross metric shit ton of components. How do you manage it?

I fucking hate "modern" front end. Just a little "hello world" and you already get a useless bundle of js, which is x times then other assets combined.
Not to mention that no fucking setup I tried works, documentation is as accurate and up-to-date as apple maps and all components are basically part of a civil (cock) war.

So far the most frustration aspect in programming I have to endure

My company is looking for a new React FE.

Just got a response to the add...

"I have 10 years experience with react and styled components."

Vuejs is great. I havent read any of the docs, only the first part of how to make components, and pretty sure i just hackes shit together but i now have a working site. It just speeds everything up, unlike fucking angular lol.

Reactdev, what kind of ui library that usually you guys use and really easy to understand? Something like material ui, react-table or anything like that. I just need a really easy components library that I can use for small projects

This Chinesium power supply looks disgusting 😷 I have no idea what shit this manufacturer put their hands into when they built this piece of garbage (that nonetheless works without blowing up, go figure) but it's all sticky 😐 I want to clean it up before putting it into a new enclosure, but I don't have an ultrasonic cleaner and don't really feel like desoldering all the components and giving it a washing. Are there any other cleaning options that are inexpensive and don't damage the components or the solder joints? Pure alcohol perhaps?

Just got my beta access for Framer X. They describe themselves as "Unity for design" bridging the gap between Sketch and React using code-based components. I think it has a lot of potential. Would love some non-designer perspectives. What do the front-end devs here think of it?

you fucking idiots

why do you always base your library components on some dumbass clown fixed width / height system?

everything should be flex by default, anything else is absolute amateur clown town pile of dumbass horseshit...

...i'll brawl and take down anyone who says otherwise

you waste my time, you waste other's time, when everyone has to go hunting around for your stupid library's unorthodox way of styling

thanks again for wasting and making my evening a living hell

Fucking Visual Studio leaves thousands of components installed even though I asked it to uninstall everything

Match twice, order once, they said. It always works, they said.

Buying PC components is one of the hardest decision I've made in my life

So far one of the biggest challenge for me is if I should spend my money on a girlfriend or computer components.
.
.
.
I am getting a £1400 pc soon

brain storming about system design on miro board

at the beginning, all devs add components they think that might be relevant for the system.

PM heavily moves everything around, deletes or changes meaning of added boxes without asking. after five minutes, he is the only one using the board, rest of the team is just watching.
PM: come on, guys. don't just sit and watch, you can also participate.

besides that, the resulting system in the end was complete garbage.

No prior knowledge on svg. Somehow Built this animated svg using React components 😼

> raw http request injected in the model
> 400 lines long method, followed by three 300 lines long methods
> no autocomplete, no comments
> code called by the whole application, I mess up once there's at least 150 other components that might break
> no documentation, no tests
> pyramid of doom, 13 levels of indentation

Those are the same people getting all puffed up because the cat dared to sit on my shoulder during a call. Management focused on the real fucking problems, no doubt.

Wombat is days away before launching his side project. It is a platform to sell website components for devs and designers.

I am very nervous about it. 😬😬😬

Me and my team has been creating React components for the last two months. Today we realized that not a single component is done the Redux way (as pure functions), which means we have to refactor every component and the tests.

That's what you get for trying out new technology..

Before new years eve I prepared a sheet on google sheets that allowed people to add drink recipes and order drinks (specify how many of each drink they want), calculated part of budget each person had to cover and generated shopping list of drink components with exact amounts needed.
It was more fun to make that thing than to attend the party.

Hertz the car rental company wanted a new website. They hired accenture. Accenture did allegedly a poor job. The site did not come with responsiveness, not with web components and 2 years over deadline. Hertz sues Accenture for $38+ million.

Scope creep deluxe?

The sales team sold a project using our 'innovative framework', which had 'prebuilt components', which we 'only needed to plug n play' with a 10 week deadline. Of course, the framework didn't exist. Guess who was the lucky guy who had to create the framework AND finish the project in 10 weeks? fml...

Yay! I got my head wrapped around Vue3 parent / child components and fed the whole thing JSON data loaded via Axios. A small feat perhaps, but it just feels great to still "get" stuff when learning becomes harder as I get older.

Ok i post it a bit late but what the hell.

This is my monster now! I now shall conquer the world!

MSI GL62 7RD
with that configuration:
CPU: i5 7300HQ
RAM: 8GB DDR4
GPU: gtx1050
HDD: WB blue (small laptop one) 1TB

Ok i already had that configuration for a while... but it was sloooowwwww D:

That is why for my birthday/chrismas i bought myself additional 8GB of ram and a tiny nvme ssd to make everything 1000x faster! 😎

1 ++ for a person who reads how big the ssd is...

*reverts a layout file to the one in git*

*gradle fails, no components found, electricity goes off, office catches fire, the world ends*

A lot of people are very good at making extremely complex and hard-to-read React components.

Very very few are good at making clean and easy-to-understand React components.

Vue components are a gem.

React developers, What do you think about the new hooks api?

Will you refactor your codebases to use functional components or just stick with classes (even though the react community is moving towards removing classes completely)?

I think its awesome as it reduces the bundle sizes if you use function components though. I have been working on an awesome project for a while and I'm being tempted to refactor the whole codebase to use functions instead of classes. What do you think?

I fell in love with Vue and Webpack! 😍😍😍
It is such a breeze to work with components and to be able to just change something and have everything instantly recompile and update on the webpage. I am actually enjoying doing the frontend more than the backend which is strange because I am a backend guy 🤣

How do you deal with someone like this?

I've got this dev at my workplace that is terrible to work with, he's 2 main reasons why I say this:
1. He has no clue about team work, every piece of code he writes is written as if he is the only person that has to ever touch that
2. He's overtly protective and opinionated on things that make no sense, they're non standard "rules" that he sets and enforces by replacing others code with his own (often times you see quite large PRs and after inspection you realize he rewrote parts of code to follow his style). These "rules" also take up a really long time to follow and would make any actually experienced developer question this guy's knowledge, one example of this is where he repeats the same code over multiple components for "encapsulation reasons" and God forbid you create a global helper of some sort, he'll straight up remove it the next chance he gets. Another example is that all his components or utilities live inside 1 base directory, so you have roughly 300+ components in a /components directory, all with non standard names so you can't tell which is related to which.

I hate working with this person, it's annoying and it also sucks because he's sort of a more "senior" Dev so managers take his side most of the time.

Reporter: We are now here reporting live from the native mobile app wilderness. As you can see in our captured footage, a developer is going rampage over some mobile UI components.

Native iOS: grrrr... I hate radio buttons!!!..grrr...dropdown lists, too! keep them away from me! I'm allergic to android and web controls, d*mn it! what kind of designer are you!?!

Reporter: That's it for today's devRant episode. Back to you, Steve.

Any tips on nailing OOP design interview questions? This is a black hole, weak area for me, and I get absolutely no feedback on what I'm doing wrong.

I feel like most of it is because I *nothing* about what I'm asked to design.

And yes, I ask clarifying questions, list out use cases and constraints, identify nouns/verbs and map them to objects/methods - but these don't help with the overall *design* when you can't even grasp what the components are, nor which parts need extensibility.

Imagine you've *never* been inside a car, let alone even understand there's components to a car (you don't even know that cars have engines, or that they take fuel). Now imagine you're asked to design a car. It's just, silly.

When not logged in, twitter.com opens a welcome message and a login form. twitter.com/login opens a login page with a "remember me" check box so you can stay logged in.

Twitter don't seem to want visitors to their homepage to come back very easily.

Hey React, why won't you die?

Seriously, you are cumbersome to use, heavy as shit, awful syntax and do only the most basic reactive operations possible.

Why do you have to re-render un-changed components?

You were good when you came out, but please, get the fuck out of job requirements everywhere.

now I’m starting to understand why unit testing is helpful as I’m making more and more features to the existing system I’m beginning to realize that the more shit I add the more chances I have of the existing components to fucking break for no reason this is very annoying and time-consuming

I really do like Flutter/Dart but I just cannot be the only who thinks that the way to create several nested components/widgets is even close to somewhat readable, what the fu** Google.

Why do people feel so compelled to create their own custom components when the component library you're already using HAS ONE ALREADY?!

You can change the styling and animations using CSS and props. Stop building buggy shit from scratch.

Not only is the documentation only in Chinese, but also the labels used in the components are. 🤦‍♂️🤦‍♂️🤦‍♂️

Oh well time to get my hands dirty.

I made sure to commit all changes (from my desktop) before leaving my home for the weekend so I can continue my project at the parents house (going for a monthly visit)..

I arrived, synced all my changes to my laptop, all good and well, going perfect. Updated the bower components etc. Time to start some test runs so I started my localhost, opened my browser,..Ended up with a MySQL errors galore.. Unknown table this and that.. I forgot the export my MySQL database :'( #fml

I am just sick of the things that's been going on.

Joined a mid level startup as full Stack developer working on angular and node js . Code base is too shit and application is full of bugs(100+ tickets are being raised for bugs)

Since the product owner(PO) wants to demo the application he is pushing for bug fixes.

UI code:
1. Application is not handled for responsiveness all these years, it is now being trying to address. Code base is very huge to address though .
2. The common reusable components of UI has business logic inside. Any small change in business logic we are forced to handle in common components which might break up on another components.
3. Styling in 40+ components are made global. Small css change in component A is breaking up in component B due to this
4. No time to refactor.
5. Application not at all tested properly all these years. PO wants a stable build.
6. More importantly most of developers have already left the company and we are left with 2 developers including me.

I am not in a position to switch due to other commitments adds up a lot to frustration

Next year I will strive to achieve the best test coverage on all our components and design all our new features using best-practice agile methodology with a realtime user involvement.

Reverend on 7 January: Fuck that, we need to ship this shit to production now.

Why can't managers understand that functionality changes and UX changes should be two separate epics? There's a huge fucking difference between composing an UI from existing components vs. having to figure out new components while at the same time paying attention to 12234234 new scenarios while at the same time duplicating existing components because existing portion of the app has to keep old UX.

And then they say bullshit like "we need solutions, not problems". Fuck you. Solution is to keep existing UX and focus on functionality, and do complex UX changes when functionality is well-defined and STABLE. But no, you fuckers won't listen even when the fucking lead dev tells you to.

Fucken Designers - Have you ever heard of fucken consistency?

Different looks and feels for the same thing in every single page? Wat the fuck man - I am trying to write clean and modular code for components and you guys are making hard -

Bomb Alert:
Fuck Designers *middle finger*

No need to think small when you have eternity to work with. Right now I am building a network operating system, something I've started around 2 years ago. I expect to have an installable and more or less usable system in maybe a few more years.

When I would have an eternity to work with, I'd first look to make our planet redundant. It's insane to imagine that we only have this blue marble to work with, while we have a fireball of hell as a neighbor in our cosmic neighborhood. What even happened there? I'd like to find out. Granted Musk is already figuring out Mars, and he has the money for it while I don't. I don't like the man all that much (too much marketing wank) but hey, at least he's got us covered there.

Maybe one day we could live forever. Maybe we could map and upload our minds. Maybe we could replace our entire body with synthetic components when the frail meat-based components inevitably fail. Perhaps it could even happen in our lifetime, at the pace technology is progressing at. If and when that happens, sign me up!

When your company lays off an architect responsible for building a dozen very important components, and then everyone is left in a panic trying to figure out how to fulfill support requests / bug fixes in a timely manner 😑

I remember the time when netbooks were a thing. An affordable device for easy tasks like web browsing. It’s in the name!
Excuse me, what? The web? It’s heavier than some games now! All thanks to React.js and stupid frontend framework boom of 2016.
Frontend people, wake up. Modern JS has everything you need. It’s time to switch to Web Components.

After replacing all jQuery libraries on a client website with Vue components

I really don’t like when colleagues start refactoring core components in a software application just because they feel like it.

Consult the team first and get everyone’s opinion, cheers.

I can't understand the people who are in love with Qt. Did you ever actually use it?

It has shitty UI components (compare them with Microsoft WPF or even WinForms), and it is fucking full of bugs. Really. I've never seen that many bugs in other frameworks.

I'm a Linux guy, but try .net if you want to see what a great framework is actually like.

Freaking love it when devs from other teams work on you code base and implement components you already have ... Don't talk to each other, just submit your awsome code and leave a mess behind. But OK ... Just a simple click on Pull Request -> Denied!

Some fuckin ppl man wtf, as a said here before I'm not the most skilled or elegant developer at my company but fuck me am not as dumb as some fuckin cunts
We have 2 separate packages dedicated to add reusable components but some asshole with shit for brains just keeps adding these components in one of the main repos and it's like r u retarded or something, like u know that's not what's meant to happen cause you've used the components from those other repos. Sometime I jus wanna die and I've only been working as a dev for about 2 yrs 🤦‍♂️

I can't use Javascript object destrucuring in react components because a colleague doesn't like / understand it for some reason.

So instead of:
({ something }) => {
return (
<div>{something}</div>
)
}

If have to use
(props) => {
return (
<div>{props.something}</div>
)
}

Its no big issue, but I hate it.

Why....?

Why not order the components in a way that makes sense?

*twitch*

My boss started contemplating whether to start using styled-components for react.

I showed him Vue: "oh well, so we're basically recreating Vue within jsx?"

I'm not sure what problem we're solving anymore

Me when I use Laravel components in an old none Laravel project and save myself time.

Lets get some shit crystal clear:

- Angular is amazing.
- If you're complaining about it, then you're not experienced enough with it and you need to learn more
- Im using Angular for years, i built personal, professional and client projects with Angular as frontend and got paid thousands of USD
- I have never had any problems with angular in terms of performance, slow load time or insufficient documentation
- Angular is perfect for large projects. The structure is extremely robust and Easily lets you scale the project no matter how complex the project is
- You can have a trillion components and still be able to easily understand what each component does and add up to it because of how all the components are modularized and decoupled

My boss: Write unit tests for this angular app
Also my boss: what do you mean it will take months to write the necessary mocks for our 177 specs
Also also my boss: why would you need to mock anything for a unit test
Also also also my boss: Just let each component import all the other real components, nevermind that that's an integration test and not a unit test

A 2d simulation of the mars rover curiosity and its commandControl station. Pure java. The two components talk to each other via apache-kafka. Rover has its own operating system (kernel) and resource management. Hooked up some sensors to NASA API.

Me: *holy shit there's a lot of code in this template file, I should probably break it up I to components*

*goes through the effort to break everything up into component parts*

Me: *i should quit being lazy and actually register all my templates the way magento wants me to*

*5 hrs later*

Me: fuck this! *<?php include ...?>*

I had the oppertunity to join a non profit organization to help them automate stuff instead of serving the army. One of their core applications got rewritten like a year ago from a terrible and very old Symfony stack to Laravel / React.

The guys who were in charge for the rewrite didn't really adapt the mindset of either MVC for Laravel nor the component idea behind React. There are a few controllers in the backend, but they sometimes have functions defined which would clearly belong in a model or service class. They rarely defined relationships on models, instead they're joining the tables together for the same effect. The frontend rendering mostly happens in for loops over the returned array from the API instead of breaking things down into little components. This ends in components which have sometimes over 1000 lines with super-nested logic in it.

But I did find my favorite piece of code today in of the controllers. Some many questions ...

"React developers" who write 1-page monolithic pages instead of modular components should be guillotined...

PS: Frustrated AF :(

Swing components

Google keeps reaffirming what I keep telling everyone... it's not 1995 any more. They just ripped Symantic over using 7-year old (un-updated) open-source components in Norton. These are massive zero-day exploits that are wide the hell open. If you're really concerned, use MSE on Windows. If you're on a Mac, grow a brain cell and actually look at what you grant permissions to, and you won't even need AV.

we need you to implement some front end components but design department is not following their own standards, and changing the fucking mockup, so now you have to change your shit again

like fuck, how hard can it fucking be to hand me the locked in design and ill make it, i dont wanna have to muck this shit up and fight css again

5000 scss file with the name global.scss styling.

How fucking dumb can you be to fucking mess up a clean component based architecture like Foundation or Bootstrap and fill it with shit in a single file.

No wonder WP gets shit. The legacy code is usually shit.

And to put the shit cherry on top. This motherfucker had a settings.scss file with all general components and he never used it.

Fucker put different font size in px everywhere! Fucking asshole!!!

working with UX/UI designers who don't understand the concept of style guides or reusable UI components is torturous, why don't they understand things work a bit different in real life than in Photoshop, Illustrator or Sketch

I divide every website I see into components. Dammit React

Client: We want you to copy this iOS app as it is.
Me: But some of the ui components are not android specific. The android user is not accustomed to this.
Client: We don't care, we want the same application.

Converting one of my older projects to use functional components and hooks instead of class components and prop drilling. It's nice.

Though now I have this useState:

const [ disembodiedHead, setDisembodiedHead ] = React.useState("");

Promise it's not as creepy as it sounds.

My boy is alive

For now, until the components start to corrode.

So I came up with an interesting idea for a quick side project. "Should be doable in an afternoon," I thought to myself.

Then I sat myself down and started diagramming all the components and sections I'd need to build. Suddenly, simple project no longer seems so simple.

...dammit, not again.

Checklist of most stupid things I did:

Buy a 500gb SSD and install Windows Server 2008 R2 onto it, then configure it to look like Windows 7 and use it for development/gaming ✅

BTW after installing all features and components, it runs very well.

styled-components is the shit ❤️

Big plays...

function collapseView(element){
/**
*it doesnt work at the first time, the function needs to be called again
*/
element.collapse();
element.collapse();
}

Literally copy and paste this code..

I've decided to change the key components of my Arch Linux system. Of course it's not gonna be quick but here's my plan:

i3 -> bspwm
VSCode -> GNU Emacs

What do you guys think?

How to fuck a web developer:
1- Introduce a shiny new shitty web component that is nearly impossible to figure out how to change it’s fucking background color, yeah.
Welcome everyone to 2019 why even it was so easy to change and customize your own shit, let’s just introduce thaaa faaacking web components and fuck everyone else. Let everyone learn again how to do the simplest shit ever.
Yes fuck everyone that is used to change and customize in an easy way.
“yUo wAnT uS nOt tO UsE SoC anD cLEan koOde?”
No no no. We will fuck you instead.

"We are releasing today" - sentence my project/tech manager keep saying for a week now. Of course, we changed few core components during the week - because, why not - and nothing works now.

When you finished those react components and finally ready to implement them into the app...

Started my first private App project using all the goodies of 2017 android development like TDD, Android architecture components (hence MVVM), kotlin (which I yet have to learn), RxJava2 (if I need it additionally to AAC) and maybe try to set up a CI environment.

Wish me luck guys and girls 😁

The documentation for the matplotlib python library is terrible for newbies.

There is a "Tutorial" section, but the thing doesn't even explain what you can do until you get to the 4th section!
It starts off with some confusing examples, how to change the appearance and only at section 4 do you actually start to get an introduction to the different components you might want to use...

At some point you finally realize, most of the stuff that is shown can be omitted because the .pyplot module is all you need.

wow... the regular react community sucks...

where with react-native 3rd party libraries/components have very clear and detailed docs, the normal react libs out there are like:

20K starred component
"here is a .txt file with some props, TS? yea we use it, but everything is just set to ?: any"

quite the shame :/

My most successful project was in the fisrt year of University in 2016. We had to build a robot from scratch with all the mechanic, electronical and software components, which could solve a given problem, in our case defusing a bomb, in collaboration with an other team. After a lot of frustration, late night debugging and many beers, our team managed to win the competition against 8 other teams.

When you're a total noob and only knew about an html, scss and js file when it comes to websites but then you see an actual website of a company with all separate scss files for components and you feel so overwhelmed... yeah... rip

I coded a simple Java programme when I was a beginner, today I reviewing it. I facepalm myself and thinking "I wish I know about 3 tier Architecture software development earlier" . Now I am looking at a one tier Architecture programme.

Which means UI components, Logic Components and Database components are all in ONE class and one method. Omg. Silly past self...

Angular is not fun to work with. The amount of jumping between files to do a thing is tiring. And its documentation fucking sucks.

I guess I'm just used to single file components and Laravel's amazing docs...

Arduino project going off the budget and teacher asking for more functionality because "it can be made within 30 mins". We are working for 3 days and only things we are getting to know is new components that we need to add. That too in summer holidays... Fml

Meeting about brand new web app system to replace an ancient MFC app.
director: can we just use the old subsystem manager? (horrible mix of management ui and SOAP listeners in the same app...)
developers: No, that's an MFC app... not even just a server.
director: but... can't you just plug it in? you're using web components right?
developers: *weary sigh*

Every time we have finished a project and deployed it the first time at least half of the components are outdated already 😒 Even if we worked only 2 weeks on something.

I hate Murphy's law!

"It doesn't really work like that with React"

Then stop using React for things it wasn't designed for!

It's fantastic as a library for UI components, but sometimes something like Angular is a better fit for when you have complex data flows to manage

Classic example of people picking a single technology and trying to use it to solve every problem

@dfox @trugus It would be great if you talk about the different components of your stack in the podcast. I'm particularly interested in neo4j.

Salesforce lightning web components have such bullshit limitations that they claim is because of security but it's just because it's overengineered garbage.

Want to use web components? Nope.

Want to pass in a value to a function in a click listener expression? Nope.

Want to use scss? Nope, compile it to css yourself.

Want to use the fucking document object? Guess what it's overridden except for very specific third party frameworks.

Who in the fuck thought it was a good idea to override the document object? Your app isn't more secure, literally the entire internet uses the document object and it still becomes available in runtime anyway so what the fuck??

LWC is the biggest garbage I've ever seen, you know a framework's a big red flag when there are developers solely for the framework.

There is a new security release coming out that apparently removes some of these nuances (understatement) so there might be some light at the end of the tunnel.

Good oop is hard to implenent and keep track off in my experience.

I have seen projects so hard which have such large hierarchies and reused components that even the most minimal change breaks an entire change. Dependency injection is a pretty cool tool to use, but I have seen more people fuck it up and make something that supposedly removes tightly coupled components be the extreme opposite.

Remember your basics people. Fuck

Ok everything is good now. Happy thoughts...nuthing but happy thoughts

Anybody used material-ui/react components and wanted to punch whoever wrote this shit in the face? Whats the fucking point of a ux framework where you have to style everything you're fucking self?

To all the front-end engineers here I have a question. Say I am trying to create reusable CSS web components how do you create them? Shadow Dom?.
If not then how do you make sure the custom elements that you create can be resued in other projects?

Got the task of researching the upgrade for an angularjs site with 300 components to newest version.
3 days in still no clue how to take on this Problem.

Frustrated af as I have to come with a proposal till Friday

Sharing a first look at a prototype Web Components library I am working on for "fun"

TL;DR left side is pivot (grouped) table, right side is declarative code for it (Everything except the custom formatting is done declaratively, but has the option to be imperative as well).

====

TL;DR (Too long, did read):

I'm challenging myself to be creative with the cool new things that browsers offer us. Lani so far has a focus on extreme extensibility, abstraction from dependencies, and optional declarative style.

It's also going to be a micro CSS framework, but that's taking the back-seat.

I wanted to highlight my design here with this table, and the code that is written to produce this result.

First, you can see that the <lani-table> element is reading template, data, and layout information from its child elements. Besides the custom highlighting code (Yellow background in the "Tags" column, and green gradient in the "Score" column), everything can be done without opening even a single script tag.

The <lani-data-source> element is rather special. It's an abstraction of any data source, and you, as a developer can add custom data sources and hook up the handlers to your whim (the element itself uses the "type" attribute to choose a handler. In this case, the handler is "download" which simply sends a fetch request to the server once and downloads the result to memory).

Templates are stored in an html file, not string literals (Which I think really fucks the code) and loaded async, then cached into an object (so that the network tab doesn't get crowded, even if we can count on the HTTP cache). This also has the benefit of allowing me to parse the HTML templates once and then caching the parsed result in memory, so templates are never re-parsed from string no matter how many custom elements are created.

Everything is "compiled" into a single, minified .js file that you include on your page.

I know it's nothing extraordinary, but for something that doesn't need to be compiled, transpiled, packaged, shipped, and kissed goodnight, I think it's a really nice design and I hope to continue work on it and improve it over time

The downside to personal projects: it reminds me of how bad I am at designing UIs. I have no idea how to make things look good or where to put components. :/

Hey, would you mind trying this new powerful JS library?

It has really powerful abstraction over powerful features that compose powerful components using powerful patterns based on a powerful new asynchronous paradigm

I have decided to leave my fucking corporate job because of nonsense going on with the management fuckers. a high throughout distributed system with multiple components interacting together was asked to deliver in 2 fucking days starting from scratch.
I am asking for some tips regarding freelancer or remote job work. How do you guys find clients ? From where do I start ? I feel lost

Been trying to make React Native / SDK / Installing React components/ to work properly the whole day. After many hours I got it running on my phone to start working with a camera app idea i have.

Guess what.

When you take a photo with the phone oriented vertically, it takes an horizontal photo.

YES.HELL.

Angular 2+, it's just so elaborate, and over the top complicated. On larger projects it easily becomes a mess. I started a new job where I inherited a angular 2+ project, that is terribly made, it's so frustrating. I now use Vue.js 2, and it's just so beautiful, especially single file components :D

Today I spent hours trying to figure out how the hell to add a Material-UI tooltip onto the ClearIndicator for a react-select multi-select component to warn the user that it would clear _all_ of their selections. Followed the examples in the react-select docs on how to make use of replaceable components, but all of their examples used a different library for the tooltip component, and there was no way I was going to bring in _another_ library that was going to add even more dependencies to the application.

In the end, my problem was that all of the examples were with components that could carry a ref and the component _I_ was targeting was a <path> element, which apparently can’t.

Solution? Add a div between the tooltip and the component I was replacing.

*facepalm*

Tailwind css offers a premium package where you have to pay $300 for access to their tailwind styling components. And even additional $150 and $150 and $150 packages depending if your app is for ecommerce application ui or marketing etc.

WTF????

While in Angular Google has provided 100% FREE MATERIAL DESIGN UI COMPONENTS

WHO THE FUCK PREFERS TO CODE IN REACT/NEXTJS/VUE over ANGULAR???

Just started learning HTML, css and JavaScript. What are the main components to learn thoroughly besides the DOM.

So i'm working with people from another team to bring about a feature. I was wondering, "how come they're churning out so much shit in so little time!?"

Apparently, they make code, merge request to the release branch, and then do unit tests later.

How do people, in good conscience, think that they can skip unit testing for extremely vital components???

Its not a product, but personal opinion working on react for the last 4 years and one thing is for sure Reacts functional components are shit to use compared to the class components. Specifically useEffect. React was never supposed to be written in a functional way when it first launched.

Trying to review the architecture of an internal boilerplate... After having explained Atomic design principles, and the "component approach" to my colleague, he still managed to come back to me with:

- plugin/
- module/
- components/ ....

in his architecture... I don't know what to do. I'm depressed. FML. I'm quitting.

Microsoft stuff.
Everything they are promoting and developing have problems with c++, either messy implementations, non standard extensions, weird behaviours, passive aggressive stance toward official iso standard, broken api, lack of components(libs) or non portable ones, shitloads of errors traced back to undescribed, undocumented anywhere dlls, and shitload of other problems

It is not a rant!!!!!

I want to build my own pc for gaming on budget.
Like Under $1000

Please if anyone can recommend the components, write in the comments.

PS: I want a monitor too, outside the specified budget, shall I go for 144hz or a normal monitor.

For the longest time I've had trouble trying to get my background images full screen viewed and responsive for some components while learning angular 2. Then some one typed this in the CSS
Min-height: 100vh; for height

It felt like I had a heart attack and spontaneous orgasim at the same time.

Am I spoiled when I see how Django makes the separation of components and the database independent way to store migrations easy?

In React, OOP is now the old way of approaching react.js everybody doing functional programming/functional components.. this that the future ???

Ok. The honeymoon with Windows 10 is clearly over and so the gloves are off.

About to lose my mind with both Windows and Visual Studio updates. If A+B, everything goes smoothly but on the other hand if A+B, everything goes to hell.

And when trying to add components to Visual Studio, it fails 9 times out of ten due to some goddamn /NoWeb switch. What/where the hell is this switch and why everything works without issues that one time out of ten!?

About to burn everything with fire!

How do you actually structurize _big_ projects and still use js components?

_big_ = more than 300 pages. Seriously. Not addtodo, listtodos and thats it. A huge fucken amount of pages.

I saw one of my coworkers do a multi step bus ticket purchase in one file (we use angular 4) instead of using components he just hide and show the sections, resulting in a class that have about 2000 lines of code, unused variables, unused functions o just functions that console.log something, and many many lines of declaring variables. I tried to fix that, but this crazy deadlines were fucking with me

Just debugged and patched a broken loveseat. I looked at the components on the working part and compared it to the components on the broken part. Could not figure out what the actual problem was, so I hammered out a makeshift solution that has things temporarily working.

Sounds like my job.

Suggestion please!

I work basically on native android applications. From last week I started exploring cross platform and chose React native. I have zero knowledge on JS. And now it seems very hard to grab. I started a project and learning whatever I'm needing on that purpose. Some props I'm shooting blindly and components I don't even understand clearly how they are working.

Please suggest me a convenient way or guide me with some resources to alleviate my frustration! Pretty please!

Joined a new project. The codebase is… Jesus Christ Vampire Hunter, is there ANY decent project in vue which has an hint of readibility in this damn world?

Every single time anyone talks about vue I roll my eyes “no I swear we managed it well!” 600 lines of code components. Is there even a good way to structure it for big apps?

FUCK NEXTJS

The STUPID STUPID STUPID Server components force me to create 123953298341923 files just to add a FUCKING "use client" and the top that basically turns this fucking mess into basic barebones React

WOW. Let's have 34 million libraries in our project and then let's not use them with one fucking keyword that forces me to write my 10 components project as a 300 million files project

Then, I LOVE that all my FUCKING FILES ARE NAMED PAGE

That makes things easy

NextJS can fuck itself

Since we have premium subscription with gitlab I learned we can now have unlimited repositories. I don't get why all of our source codes(domain components, utils, even 3rd party libs, etc.) are located inside one huge repository.

Whoever came up with the idea of react styled components was obviously not loved as a child.

Just to learn aws building a side project that isnt even in production i have to fucking spend money even in a free tier

Because the components i Really need and cant move forward without them are paid

Class components, although verbose at times, are still far superior than functional components in React. The more I work with React, the more I believe that: Hooks are plain shit.

So. I maintain few open source vuejs components for my company.

We use a lot of open source so when we can and is not conflicting with the work schedule we open source stuff that we do for ourselves, document them and publish them on npm.

All fine, actually all nice!

To be honest the components are not super used but today I got an issue on one of them: "I want this pleaaase implement"

I want? WTF? Am I nervous or this is not the correct approach? What open source santa Claus? I understand that some people may not take the burden of submitting a pr (after i wrote an entire doc section about how to develop the component more) but starting with: I want??

Not okay. NOT OKAY!

Ok, I'm actually raging at vuejs right now, and this is coming from my second year using it.

the fucking shit is weird.
functional components cannot use v-model.
functional components also cannot reference other components via components property, that child component needs either to be global or be injected (an ugly hack).

v-model behaves differently on checkboxes. checkboxes are fucking shit on vue. things update or do not update.

functional components with checkboxes? hahahahahaha.

vue 3 is taking an ungodly shitload of fucking amount of time.

fuck react, but im actually considering giving vue the middle finger as well.

started this product migration 2 months ago and regretting it, looking at svelte with curious eyes.

That moment when you are working on your game. Then you remember all those games you bought cheap on steam but can't enjoy cause you don't have a good enough PC. Then you spend the next hour looking up PC components for a gaming PC that you can't afford and feel sad. And then you realise you haven't coded much anything in your own game. Why procrastination why?

You know something has gone wrong terribly when no MS Office program or Adobe reader starts while the debugger is waiting at a breakpoint.

I'm really curious which part of the kernel or system near userspace-components can cause such behaviour and where MS created pointless tunnels between independet software to let that happen. But I think I will never find out.

Today a member of an other team said that React would be better than Angular 2. Mainly because React allows HTML inside the components declaration and One-Way-Data-Binding.
Me then: Sure, but Angular 2 also has this features 😞

I’m working on a react codebase and company decided to add a new module.
Now im writing markup and css to ensure UX is smooth as designers thought of it.
Imagine my horror when I start to code and find out no matter what HTML tag i use, it’s been FUCKING OVERRIDDEN in the global stylesheet. AND STYLES HAVE BEEN OVERRIDDEN WITH !important

They’re also using Ant design as a component library. Guess what, default ant design classes have been overridden too. So i try to use ant design button or card, and bam, MAGICALLY SOME DESIGN FROM SOME SHITHOLE MODULE DECIDES TO FUCK WITH MY STYLES

On top of that, styles of parts of application has been written in SASS, some part of application uses bootstrap components some use third party components like tables and responsive grids to suit to their preferences. Some parts use handwritten css. Some parts use CSS IN JS and styled components. THE FUCK IS THIS GARBAGE!!!! THE FUCKING CODEBASE HAS A MIND OF ITS OWN!!!!!! YOU NAME A WAY TO ADD STYLES TO A COMPONENT, ITS THERE!!!
And the company’s management thought a “fractal” approach to maintain each individual view is “best” for SCALABILITY!!! HOW THE FUCK DID IT NOT CROSS YOUR DUMB MIND THAT FRACTAL APPROACH ALSO GUIDES TO HAVE ALL COMMON STUFF AT ONE PLACE!!!! THIS CODEBASE HAS DUPLICATE STYLES AND DUPLICATE CODE IN ALMOST EVERY MODULE!!!!

Not to mention every developer choosing to freely decide the way they should write their code without any guidelines.

HOW THE FUCK PEOPLE WRITE THEIR CODE WITHOUT THINKING ABOUT OTHER DEVS!!! SO BASICALLY I AM NOT ONLY CLEANING SOMEONE ELSE’S SHIT BUT ALSO TRY NOT TO SHIT IN THE PROCESS!! FML

Got designs on Wednesday afternoon. Final changes on Thursday and they expected me to work all weekend because they were lats for designs I asked 1 month ago for QA and testing. Not my fucking problem.
And not working on a weekend.

And today got told that components were missing and they needed animations. No fucking duh

So CRA(create-react-app) v2 rolled out.

> started new project with my own boilerplate
> little did I know, I am accidentally doing int CRA2
> gulp-sass fails.
> Internal screaming.
> Bulma React Components fails to compile due to one type, IDK how they missed in previous build.
> fixed by removind browserlist array from package.json
> Guess what, it comes back as you close it.
> So, now I've to keep it open while gulp-sass is running, which is almost always, in order to compile.

Thank you and Fuck you facebook

I hate Vue. There I said it. I hate components. I hate this stupid error that I keep getting. I hate that I just want a simple answer to why I keep getting this error and that seems to be difficult to find. Where is my vanilla JavaScript?

I started learning Unity through their online learning pathways and I can't help it but Unity feelsmkind of gimicky. Like it's a lot of clicking your stuff together and using predefined components (at least at the early learning step I am right now) and very little coding.
I expected more of a Framework.

Wrote an entire complex React component in about an hour. I'm talking it fetches data, manipulates state, renders child components, has some CSS-in-JS, and even uses the React componentWillUnmount method

I'm tired now

You ever look back on a piece of code and think 'damn, did I really write that?'

web components are the best components

Google has announced AMP for emails. Now emails can have dynamic components.

Thoughts?

I never thought I'd have to implement Vue.js but now I have to write components in it all of a sudden. I find myself struggling and I wish I had practiced it sooner. Now I find myself in a sea of debugging npm package errors and other cryptic errors and my pages not showing up.

Ah, Software Development, your requirements always change.

Whoever came up with the idea of styled components and other idiotic css-in-js bullshit because they couldn't be arsed to understand fucking cascade deserved all the bullying they got in the highschool. And all those idiots who adopted it because they couldn't be arsed to understand fucking cascade should get waterboarded.

tl;dr: why is it so hard to build a pc?😒

why is it so damn hard to find the right pc components for developing/image editing/gaming/...?😟
i've been googling around and watched many youtube videos on what components to buy/what to watch out for/tips/problems/etc...
i want to build a decent pc for web, mail, office, developing, running linux as VM (for experiments), edit images, doing most in multitasking (and maybe also play some games) ... basically everything, but i can't wrap my head around what to choose😟
every time when i think (for example) "ok, ryzen 5 2400G, that must be it!' there's always smth negative about it, come on!!🙄😤
i wanted to make an AMD setup for 1000€ max

i feel like as a developer/"kinda it guy" i know what i need, then again i feel dumb as fuck, not knowing what to choose and i'm almost certain i will pick smth wrong😪
do u guys have any suggestions for me/any help?

So started building a game engine in Vala using SDL2, I have never built anything from scratch and decided to do it with no tutorials and just looking at the documentation on valadoc... So of course all of the pages for SDL2 and it's sub components show up fucking blank... Well isn't this dandy .-.

So I've received a link to Figma for the new mobile app from our designer. It looks great and all but...

Each fucking piece of text is styled independently. Half of the cards in the layout are simple rounded rectangles, the other half are some components with a gradient. Icons are a mix of vector graphics and line elements. Even buttons aren't components. Consistence anyone? Please?

And now comes the best part. How am I even supposed to reach half of the screens? There are four variants of a screen with very similar functionality, but only a single button in the main screen which would at least remotely correspond to one of them. The guy who invented the wirescreens just kept adding things which would be nice to have in the final app, without revising it and making clear use case flows out of it?

After a few days of implementing this clusterfuck of a design, I have finally settled on a consistent set of font and element themes. Just please use components in Figma. You are paid to work in this tool which can make it super easy for the developer AND for you as well to make the design come to life, so why don't you learn to use it?

At least the designer is a nice guy, but god, could he learn to use his single tool?

There are tools i use more often, but a place in my heart is reserved for ILSpy.

It shows IL code as c# code and it helped me so much at understanding how components work.

Best moment was when a support guy from a company told me stuff that wasn't correct according to the code...

...no need to tell him. Hope it stays unencrypted :-D

Created redux store, wrote two reducers with multiple actions, thunks, couple of react components to dispatch some actions, bound state to props, bound actions to props, worked 4th time!

Result!

Had a few days off. Talked to my buddy to build an app for practice. I sent him the app design and it's components after doing a ton of research and hr replies saying "that makes it too easy. I'm not gonna do it" Pissed me off like crazy!

Im making my first opensource project, it's a web component library, but I find the naming part so difficult..

How do you Guys find good project names? And anything i should consider regarding copyrights/e.t.c ?

Suggestions/you naming methods are welcome 🤌

Higher order functions and components screw with my brain sometimes.

I've been familiar with C Programming and to sn intermediate level with web design, and currently I'm taking an introductory java Course, And The instructor kinda started with some simple gui apps using swing components on netbeans environment , his claim is that console apps are not that relative in the real word anymore , and gui apps are more interesting for newcomers , and I personally don't think it's a very effective approach , what's your opinion ?

Today I saw how the frontend devs on my team write Vue components + TypeScript. It's bad and it further proves that Vue=bad. Not even TypeScript can save it from being bad. Function defineComponent is ugly

I thought I would be working on a cool web project, learning the best of the current technologies and techniques available. Turns out I'll be working on a JSON that the code will automatically render it on the UI through common components. I haven't touched any line of code so far. But hey, the indentation on my JSON looks nice.

I like react, I really do. But one thing I hate about it, is the number of decisions I need to make, I get so fucking confused whether to use redux thunk or sagaas, inline styles or styles components, redux or flux, even to judicially choose whether to use a state management library or not. It just lack of my own experience or don't know what. But this thing sucks

It is amazes how much brain can be wasted with react.
In those 7hours (impressed myself by my bullshit withstanding), it took me 20min to understand a fucking api and how objects relate altogether, 1h to make the tut
and 5+fucking hours to understand how to plug the components.
I did use vue and backbone before and am 5y nodejs user.
seriously react is a bag of shitty magic.
I don't even want to try to read the code source yet, this could be the fatal move...

Oh. and also. people have to stop with jsx, it is so so so wrong. new syntax with new errors just for a fucking syntaxic sugar for saving a pair of parenthesis!!!!
like it matters after having installed 1e2+ MB of dependancies for a SPA of 10 components...

The only thing we miss is a react IDE to support JSX. #wheregoesthefront
And I am not even to the point of data flow and pubsub hells which i will be sure will be gold as well

What do people think of Vue.js over something like Polymer for making Progressive Web Apps?

I've used Polymer a lot (Angular 1 before that) and I'm not a fan of it's data binding. It is using a web standard though, so should have more components available than any library that makes it's own component system (like Vue.js).

I was building my web-app using Semantic UI, I can make the components work correctly, but can't seem to make the entire layout look good. Are there some good places for Semantic UI template that I can download or buy? Using the components along obviously is not enough.

We're moving our services to a new app interface, and it drives me crazy when a BA tells me to make something look like the old, terrible app because "user's won't like a change." You're making a whole new app! You can fix the terrible appearance and functionality issues! Take advantage of this!

It's starting to feel like I'm putting together an awful Frankenstein's Monster of code and components.

UX/design departments have process, review and do lots of work designing standard look and components for our front end. We use these.

Sometimes when they give us a mockups for new features they break their own rules/components.

Why are you handing me non-standard designs/components, when you made the standard ones and we could just reuse those.

"Front end developers" who don't understand the cascade are my favourite thing. Just use BEM dude, you don't need some fucking scoped components with dynamically evaluated CSS-in-JS.

Been working frontend on a very large ASP.Net Core project with React. The company is a multi national oil company. I asked for some documentation on their React components, like where is the props, why is this component showing this side-effect and is there a component for X and Y so that you won't have to pay me in order to dig around in the codebase? They told me they will document the frontend when the project is finished (whenever that may be?)

So basically, there won't ever be any documentation then.

So Im planning to build a pc, which i will mainly use it for dev and gaming in free time, my main components will be:
CPU: INTEL 8700K
GPU: GTX 1080 msi or gigabyte?
SSD: 860 EVO
RAM: 16GB 3200MHZ
MOTHERBOARD: should i go with msi or gigabyte whixh one is better?
PSU: 650W or 700W deepcooler?

Also for the cpu cooler do i get water colling or a standard cpu fan?

P.S: i plan to overclock the cpu and gpu at some point.
Also whats your opinion on the rgb lightning gpu and motherboard, and is there point in getting a mobo with sli support (is it work buying second gpu at some point or better upgrade the existing)

Started refactoring our app with Android Architecture Components 1 week ago.
Now Android Oreo is released and I don't have to worry about breaking changes anymore.

Yaaasssss!

I'm overhearing two engineers agree that integration tests are enough and unit tests with mock data are unnecessary while the project has problems figuring out what components are critically misbehaving.

Android Architecture components

Spent 30 minutes debugging the new Room database only for I to figure out later was returning an instance of an entity yet was supposed to return a Dao

Is there a sane way to allow external styling of vanilla web components' shadow dom? Right now I do it by using 30 CSS variables, but I feel like there should be a better way.