Learn More
Resend Email
6
dr-ant
5y

A dedicated team has built an "infrastructure" for creating UI for c++ developers in the company. What looks like a poor attempt at recreating what Microsoft did with XAML at first glance, it actually is a horrible exercise in force feeding people the stinking pile of shit that their code is.
The idea is to make it easy to create UI for developers who aren't used to front end development. They should just need to declare the layout. Very noble.
But.
If you want to do anything more than show a checkbox or a radio button, if you dare to define relationships between the UI controls or worse, if you get ambitious with creating a simple UI that uses a lot of similar controls and similar relationships with dynamic content... be prepared to eat your own barf from eating too much of their shit.

Not only do you now need to write front end code (including JS among others), you need to do it with limited or poor support and you have to make sure that it sits well with the house of moist, crumbly cards the team proudly created. Or resort to some very stupid and performance costing "bypasses" that further cripple your application code. Usually you have to do both of these things.
To think that scores of other teams have welcomed this amazing enhancement with full support without any resistance. It's sickening.

I waste too much of energy (and good jokes!) with these people.

rant

poor infra

complicated as fuck

punch holed abstractions

we do what we want

brain farts materialized in code

no brains needed
Favorite
Ranter
Comments
  • 0
    5y
    Poor people, they wanted to make other people's lives easier but made it even more of a shitshow :(
  • 1
    5y
    @alexbrooklyn it is! But they stand by it. It isn't going to change.
  • 2
    5y
    This is the worst sort of anti-pattern. I've dealt with it over and over. It leads to developers having to learn the lame infrastructure/framework thing instead of the underlying technology or a stable framework that everyone else uses.

    So someone says, "Whoohoo! I created this awesome framework, I feel special!" while other people struggle to get it to work, and when they do, they're adding perceived value to the framework.

    At the same time they know that what they're doing is useless because it's proprietary.

    And at the same time because the framework sucks so bad everyone has to go under the hood and deal with what's beneath anyway, defeating the framework's reason for existing in the first place.
  • 0
    5y
    @badwiring it shouldn't even be called a framework!
    Sample this.
    There's a single select list that needs to be shown in the UI. The elements are given by a c++ function based on some inputs.
    Now I have to make an entry in a file that says call this JS function that will call the c++ function. Simple? NO. Because there's no fucking way to pass any arguments to the JS function other than what infra decides. So I have to write a few JS functions with their separate entries in the index that will basically call one common function with some arguments that can be passed to c++. Now all of this becomes hardcoded, difficult to maintain, verbose nonsense. That's just scratching the surface. It gets worse. But I'll shut up for now.
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment