I use it everyday and works fine, "some" might be a small but vocal group? Might not be representative for a common user.
430 karma · joined December 17, 2016
I use it everyday and works fine, "some" might be a small but vocal group? Might not be representative for a common user.
It depends on the use case.
Basically it's a component-mindset; create some file with everything in it so that in the rest of the app you can just use `<MyButton>...</MyButton>`.
The `<MyButton />` file takes responsibility for everything it does (logic, handlers, markup, style).
However; this does not mean these files should grow large. Instead when things become too big (say over 250 LoC) you split up responsibilities by sub-components.
It's basically dividing problems in ever-smaller problems, but NOT by separating by technology (html/css/js).
Separation of concerns is horizontal slicing of the app architecture, components however slice the architecture vertically.
"Whatever you do, don’t use @apply just to make things look “cleaner”. Yes, HTML templates littered with Tailwind classes are kind of ugly."
That is straight from the Tailwind docs: https://tailwindcss.com/docs/reusing-styles
Using @apply a lot just reinvents CSS; that's not the point of Tailwind.
I can write similar comments about the rest of your statements, but I think you're too narrow minded to accept any input so I won't bother.
`<div css={Css.mx2.black.ifSm.mx1.$}>...</div>;`
That must be one of the most horrid things I've ever seen done to CSS.
So why bother with a DSL like Tailwind over Component CSS/SCSS for example?
Having a neatly encapsulated component that does everything is fine in most setups. Your main challenge will be not growing these components too big.
(( I really dislike Tailwind btw, mostly because I am just translating CSS into something else all the time which feels like a waste of mental effort; and the long lines of cryptic classnames is just bizarre to gain such a big popularity. I loathe it, it's a maintenance hell. I imagine all frontend devs liking this grew up using Bootstrap or something and mostly do small projects ))
In my spare-time I build a small search function with ElasticSearch for a big dataset. The use case was almost identical; and I feel my small setup works better, faster and has more options than where I work.
I don't know, things just grow over time, old developers leave and new ones join who will never be as productive as the original devs were (it's basically rewriting someone else's book without breaking it).
But I'm puzzled about it too sometimes.
That doesn't sound like a bad deal if you have to hire such a big build team; let's say you could fire 10 people, 10 * 150.000 (rough estimate) / 12 = 125k/month. That's a 85k/month saving.
I highly doubt GitLab fits the need of such massive monorepos; my only point is that the financial argument is not very strong IF GitLab were a viable alternative to such a big build team.
Source: https://go.dev/blog/survey2022-q2-results (scroll almost to the bottom)
For the audience of this proposal it's probably fairly evident what the advantages of standardization would be.
Also you argue quite strongly about the poor API design decisions being made; while you similarly admit not having worked with such tools or with web services in Golang general. That's odd.
Just to be clear; I would never use that lib in any circumstance right now, I'd always prefer async/await for idiomatic reasons.
But please have a look at http://caolan.github.io/async/v3/docs.html#controlflow
Forever, queue, series, times, retry, until, waterfall, whilst, etc etc... these are patterns that can all be achieved with promises too but I am sure most devs will do a google search before they do. In fact; some patterns are better served by a library.
Only just yesterday I added https://www.npmjs.com/package/p-limit to get concurrent promise limitation behaviour; one of the many features of that async-lib as well.
Don't misinterpret this as me suggesting these features should be added to the standard; far from it. Community libs do this job quite well.
I moved on from async, I moved on from Promises and embraced async/await.
Do I like it? No, I much rather use Golang's channels. But async/await is idiomatic and plenty of libs out there to handle complex use cases.
Almost everyone has moved on, and anyone writing promises at this moment is just creating legacy for anyone who is going to maintain it. Is that a good reason in itself? No, but it is a very valid one, that is my point.
When Promises came along I didn't feel they added much value; in fact it made things more complicated (new paradigm, harder to compose).
Still, I went with it because everyone else went with it.
Then async/await came along, I had the same issues as described in the article. Most issues in the article I've made manageable (learning patterns over time, using libraries and/or conventions).
To me the article reads as someone who worked with async/await for some time and never wanted to embrace and work with them in the first place.
I'll be honest; if I'm working in a team with a collegue trying to force all code to use promises instead of async/await I'd probably ask him to stop doing that and escalate depending on the response.
Being idiomatic is very important, it makes code recognizable for newer devs. Had I stuck with callbacks until now I'd be writing code few young JS/TS devs would understand or like to work on.
(I'm not from the US, perhaps I'm missing something?)
I beg to differ. The majority of their products are flawed and outdated. I'm not talking Oracle DB or Java but the vast amount of other apps they sell.
They bought lots of stuff, pull funding from development and redirect it to sales. Then they sell it to fit their vision; but nothing integrates cleanly and you'll be spending massive amounts of money on consultants who understand product A & B and how to connect them.
A java-dev can't do that; you need that A and B knowledge + integration skills. Those consultants are very hard to find and good effective ones nearly non-existent. The fees are enormous regardless of whether you use Oracle consultants, Oracle partners or freelancers. If you do manage to find cheaper consultants (offshoring most likely) be prepared for terrible quality as well.
Ow, and once you're finally comfortable with their stuff after spending all that money, be sure to make a reservation for the unexpected additional license fees they'll slap on you because you failed to remember the fine print.
From their job hiring page:
88 open engineering positions, (https://www.hashicorp.com/jobs/engineering)
That's a significant deficit compared to their current org size.
It's only dwarfed by their open sales positions:
102 (https://www.hashicorp.com/jobs/sales, good sales people are hard to come by!)
But yeah, they're swamped, you don't want your few resources to get overwhelmed and burned out before fixing your staffing issues. It's understandable.
Not sure what you mean by that, BBC mentiones a lack of 100.000 drivers just a few days ago: https://www.bbc.com/news/57810729
That's a shortage, no matter how you turn it regardless if people are not available or simply don't want to do it.
Sure, pay can increase but so will the price of goods and components, having a knock-on effect on the rest of the economy and making UK less competitive as a result. Companies want to move stuff and they see no profitable means to do so.
I'm in The Netherlands, there's a driver shortage here too but it's mostly eastern europeans filling the void. With an unemployment rate of 3% why bother with a boring away-from-home job? Unless Trucking is your hobby essentially. I imagine most people in the UK feel the same way; there's better jobs available now with the economy opening up.
My one experience with DDD and microservices was more the reverse; DDD was applied through code patterns but had no organizational/proces adoption. This caused bloated over-engineered microservices where simple things took way too much code and time to figure out.
Anytime you're trying to color outside the tool's predefined lines you'll be hurting and spending ridiculous amounts of time.
But stay within their lines and you'll be fine.
Because of this I don't see any real use-case for it in the B2C market. That in itself makes the 80% mentioned in the article hard to achieve.
In B2B there are more opportunities for low-code tools, but there too I don't see it working everywhere. Simply put; if you build something from scratch it's going to be a lot better than anything built with a low-code tool and you can easily grab market share by providing a better offering than your competitors. Low-code tools are not the means to out-compete the market.
If you do succeed in the B2B market with a low-code tool offering; likely you'll be building some very customized setup that required a huge investment to get to that point. I'd not be surprised it'll be just as unwieldy and difficult to change as most other software is. And for fixing big issues with your app (performance, complex bugs) you'll be requiring devs who worked and understand all those abstraction layers. Those devs will be extremely rare and hard to come by. I was one; but I am not anymore. It's just not fun to develop in them compared to normal coding; you feel constrained and fixing issues all the time that shouldn't exist in the first place.
However if you consider the huge set of internal tools lots of companies develop and use; yes there indeed is a big market for low-code. Basically use cases that were run in excel are generally great candidates for these tools. And that's a lot of use cases. Not the big money-makers though.
There's a reason Frontpage and Dreamweaver never made it; this won't happen to low-code tools. They have their place, but know their limitations.
https://www.bbc.com/news/technology-55281862
It's good to be critical and reflect on the company you're working for. There are bad cultures and attitudes in any big company, not just tech.
But if you're going to sprout your opinions publically about your (ex)-employer like that, sorry, but I wouldn't want her in my team. She sounds like too much of a headache to deal with. Her work must be truly extraordinary to warrent having that headache.
The more options a developer has the less likely he or she chooses the best solution to solve a problem. (Often best is in the eye of the beholder too, complicating things further)
Not sure how food-delivery works in the USA, but I'd think the low density, car-focused infrastructure might make it less competitive compared to cyclist/scooter deliveries elsewhere.
I also told the owners why I left, got a muted response. From their position it's just one guy's opinion. That tech lead left a couple months later I saw on LinkedIn year later, he even moved countries (from Europe to Canada). Couldn't care much tbh. It really was a relief to be away from the guy at that time.
Took a couple of months after leaving, took my time seeking a new opportunity. Moved, refurbished, walked a lot.
Now back at it. I noticed I care much less, I was too attached to the product, too involved. Perhaps if I hadn't I would have dealt with it more constructively rather than avoiding/ignoring/getting frustrated. Now I am perhaps even more productive but I don't care much about the product; not caring saves stress and avoids getting into conflicts.
Perhaps just taking a long time off (couple of months) would have solved the issue, but I don't expect people's character traits to change so in the end I feel I made the right choice.